MC-32 CLI Configuration Question ? 1

[golfdoctor]

Hi guys, I am at wits end. I posted previously with my intent to try and network an OPT 11c and an OPT 81C together using VRTKS between the 2 nodes. The main site (81C) contains a Signalling Server, and the NRS. I was told that I would only need the MC Card at the second site as it would do the trick. There is no IP phones at the Opt 11C site; simply using the MC Card for the DSP resource and H323 trunking. My problem is that because I have separated the ELAN and TLAN I cannot seem to get the necessary IP info into the MC Card from the main sites Signalling server across our LAN (TLAN)using element manager. Even before I tried the change I did not see how it could work from Element Manager however the NTP says configuring different nodes is the way to go?

Node 100
TLAN NODE 192.168.5.100
TLAN IP 192.168.5.xxx
ELAN IP 137.135.128.xxx

Node 101
TLAN NODE 192.168.3.100
TLAN IP 192.168.3.xxx
ELAN IP 137.135.128.xxx

I have read and tried entering the IP info via the CLI into the MC Card however when using the NVRIPSet command and others it seems to be more geared towards the ELAN ixpMac1 vs the TLAN ixpMac0. Could someone stear me in the right direction as how to get node and TLAN IP info into the MC Card via CLI or am I just missing something obvious besides my brains!

Any thoughts would be appreciated.

Thanks again,

TGD

 

[westcoaster]

For ip trunk 3.01 to work you will need your system to be at succession 3.0 (minimum) and to use OTM 2.1 to configure the card.

I have no information on how to configure earlier versions....

 

[westcoaster]

IP Trunk requires a minimum of release 25.15 software. To interwork with the CS 1000s/CS 1000M Gatekeeper, CS 1000 release 3.0 software (or later) is required.

page 39 of 644 ntp 553-3001-363 ip trunk

None of the course material I have/had go through how to configure ip trunk via CLI. The ntp's state otm 2.1 is a requirement (page 47 of the same book)

 

[golfdoctor]

Thanks WestCoaster ,

I thought I should be able configure through the CLI, however am probably wrong. I did not provide very much info on previous post. Running out of steam. When I installed the software on the Opt11(C) I selected "No Signalling Server" because their is not one attached to that node. Not sure if that prevents any configuration issues. I do not have OTM however I am running Element Manager from the Signalling Server attached to the Opt 81C. When I use Element Manager and try to update the new node the transfer fails to the new node because I suspect it is trying to send the update via the ELAN. Was hoping the update transfer would take place across the TLAN as the ELAN is physically separated and not routed.
All the NTP documentation seems to suggest I require a signalling server at the Opt 11 end? If I cannot configure the MC Card via CLI or through my existing Element Manager I may have no choice.

Node 100 (Opt 81C) Succession 4.00T
TLAN NODE 192.168.5.100
SS/NRS TLAN IP 192.168.5.xxx
MC TLAN IP 192.168.5.xxx (IP Line 4.0)
MC TLAN IP 192.168.5.xxx (IP Line 4.0)
ELAN IP 137.135.128.xxx

Trying to configure the Opt11(C)with the folowing ....

Node 101 (Opt 11C) Succession 4.5
TLAN NODE 192.168.3.100
MC TLAN IP 192.168.3.xxx (IP Line 4.0)
MC ELAN IP 137.135.128.xxx

 

[dlesap]

You can connect an ITG trunk card configured with OTM, with a node configured with SigServ.
You just have to register the ITG card in the NRS as a static IP@ in Gateway endpoint tab and route calls to the site.

However, when you have a SigServ, Nortel recommend to change ITG trunk remote site to Voice Gateway elements. You need to upgrade these board going in site. Need a PCMCIA with software to proceed. FTP is also possible, but if any problems, you will have to go on site...

When upgrade will be done, all SigServ and MC will be managed from element manager at once.

 

[golfdoctor]

Hi dlesap, I was hoping you might respond

I think I am on board with you as the NRS has been configured wrt the gateway endpoints. You assisted me previously when I registered the main site. Where I seem to be out to lunch is with the Opt 11(C) or the remote node. I have it installed in my shop and am in the process of configuring for deployment. It is connected via IP to our TLAN only.(simulated deployment) The ELAN connections on the Opt11 are connected to a separate hub. (SSC/SMC)Also the ELAN connections at the main site are physically separated/isolated for the TLAN and our LAN.

Maybe I am using the wrong terms but the card I have in the Opt11 is a 32 port media card. I have installed it into slot 9 and have configured the TN's as VGW. The virtual trunks have been configured also and have been setup on V99-0 to V99-31.

My problem seems to be that I cannot get the new Node info to be passed to the SMC card from the Signalling Server when I select transfer. The error says it cannot find the element 137.135.128.110. The network address for the ELAN is 137.135.128.xxx . I have basically used the same IP and SubMask address for the 2 different call server nodes 137.135.128.253. I used 2 different TLAN Node IP's for the 2 different nodes. 192.168.5.100, 192.168.3.100. The Opt 11 C and the SMC card are both brand new. The SMC front LEDs is stuck on T20.

Does the SS send the new node information over the TLAN to configure a new nodes element (MC card) or the TLAN ?

dlesap, I think my SMC board is the latest and greatest vintage so I hope it is ok. When I tried to configure the SMC (setLeader)via CLI maybe I should have used the TLAN IP info instead of the ELAN IP info because I am thinking if the ELAN is the communication path utilized between 2 different sites I am hooped as the nodes ELANS are not physically connected?

Any thoughts ?

Thanks again,
TGD

 

[dlesap]

I can see different problems:

1- You don't have SigServ on Remote site. It's not in the same Node as your opt81. So, your MC on opt11 must be configured with OTM as a ITG trunk using an external gatekeeper(SS on Opt81C)

2- T20 display on MC, means the board is not ready.
Is the compact flash installed?
When you connect on the Serial port of the MC, on the boot you may see which software rls is loaded on the compact flash.

3- There is no problems that your TLAN Subnet are differents. You just have to check that you are able to ping it from both side, by installing your PC on the same LAN, and ping SS and MC. You don't have to configure the remote MC in SS IP configuration page, but only to register it in the NRS with a static IP@. So ELAN of Opt81 and ELAN of Opt11 don't have to be reachable each other.

Am i clear enough?

 

[golfdoctor]

Hi dlesap, thank you for your response !

The compact flash is in the MC Card. If I remember right I believe it is at version 8.2. I will verify though.

Glad to hear about para 3.

In response to para 1, since I do not have OTM, do you think it is fair to say I am hooped unless I put a SS at the remote site or get OTM. Sounds like I did the node and IP stuff ok, and I think I have a grip on the NRS. I have configured the IP/H323 RAS etc for the Opt 11C endpoint. NRS testing seems ok for now at least.

As always your assistance is greatly appreciated



TGD

 

[dlesap]

Hello

For compact flash, 8.2 is firmware version not Software version. Soft rls might be 4.x.x or 3.x.x. It's displayed later on board starting, after Nortel logo.

Then you have 2 solutions: Get OTM without dongle cause not necessary for configuring IP Trunk, or install a sigserv at remote site (about 2000$)
With OTM, you will not be able to give a RAS name to ITG. So, you will have to register it in NRS with static IP (not a problem)
With a SS at remote site, define another node number, configure SS and MC. In the NRS at main site, register that node as RAS endpoint.

Your actual Node definition seems to be correct, but ITG registration must be done a different way. Good luck