Hello all, I have been reading 1

[rheine]

Hello all,

I have been reading the MGC trends and have not seen anything specific to my issue. I have a release 5.0 site and for whatever reason the ELAN and TLAN network cables were removed from this MGC. The shelf is powered up because we are using the AUX connection on the back to power up some power fail units but the MGC card was unseated.

I asked the tech who worked on this last if he recalls there being an issue with this MGC card and he said no. I am not sure why the network cables were removed from this card?

I plugged the MGC card back in plus the ELAN and TLAN connections to the appropriate connections on the baystack and the MGC card did not register with the call-server.

The display was as follows: passed, unregistered and then an E002.

Now what happened in the PBX is very odd. Some of the cards had gotten disabled and so the PBX acted like it had initialized. But when I looked at the logs I did not see an INI. The logs are below:

BUG8021 Connection close (Maint Task), bug marker = 0.

SRPT016 OMM: IP link is DOWN between Call Server and IPMG[4 1]

SRPT257 shutDownServerSession: shutting down ssd server session [3] for IPMG [4 1]

ELAN009 ELAN 0 host IP=10.12.90.23 disabled, write to socket
fail due to far end disconnect or Ethernet problems

ELAN009 ELAN 0 host IP=10.12.90.23 disabled, write to socket
fail due to far end disconnect or Ethernet problems


SRPT017 OMM: IP link is UP between Call Server and IPMG[4 1]

SRPT219 Reg DENIED for IP[10.12.90.23] IPMG[4 1] Reason[8] OldStatus[1] MainReset[0] Exp
RegRegStatus[2] TS[967476718]

SRPT016 OMM: IP link is DOWN between Call Server and IPMG[4 1]

SRPT077 IPMG[4 1]: Loadware version mismatch detected. Adding to sequential upgrade queu
e.

SRPT210 Reg GRANTED for IP[10.12.90.23] IPMG[4 1] TS[967545996]

ELAN009 ELAN 0 host IP=10.12.90.23 disabled, write to socket
fail due to far end disconnect or Ethernet problems


initiateGwUpg: RPC: Program not registered

BUG2006 RPC: Server terminated. Cabinet type [Call Server] Reason [initiateGwUpg: could
not create RPC client.
]
initiateGwUpg: RPC: Program not registered

BUG2006 RPC: Server terminated. Cabinet type [Call Server] Reason [initiateGwUpg: could
not create RPC client.
]
initiateGwUpg: RPC: Program not registered

BUG2006 RPC: Server terminated. Cabinet type [Call Server] Reason [initiateGwUpg: could
not create RPC client.
]

SRPT063 IPMG[4 1]: Unable to initiate Centralized Software Upgrade.


XMI002 4 1 10 XMLC

XMI002 4 1 1 XDLC

XMI002 4 1 2 XDLC

XMI002 4 1 3 XMLC

XMI002 4 1 4 XMLC

XMI002 4 1 7 XMLC

XMI002 4 1 8 XMLC

XMI002 4 1 9 XMLC


SRPT017 OMM: IP link is UP between Call Server and IPMG[4 1]

ELAN014 ELAN 0 host IP=10.12.90.23 is enabled

I have since removed that MGC and brought it to another site. I obviously can't have a PBX have issues during the day. I would like to verify the IP information in this card so I removed my SSC card from a spare 1000E cabinet plus the network connections to that cabinet. I plugged in my octopus cable to the com connection on the back of the cabinet and of course the MGC card is plugged into slot 0 where my SSC card was. I powered up the cabinet and I can see allot of information on my computer but I am not able to talk to this MGC. I had believed during the bootup process there should be an option to press control I to enter the setup but control I never shows up.

Someone told me to serial to this MGC but isn't that what I am doing plugging in an octopus cable to the com port on the back of the cabinet doing?

Could it be my MGC is bad and needs to be replaced and then I can start from scratch? Maybe there is an IP conflict?


I do see when I boot-up this card that it is attemtping to connect to the call-server IP address. There is just the one CPPM card and this is supposed to be the last loop 12-1..

The below per the superloop information on this MGC location is shown below:

012 IPMG ---- -- - - -- - - 0 004 10.12.90.26
1 004 10.12.90.27

Does anyone have any ideas or should I just order a replacement?

Thank you

 

[KCFLHRC]

Not sure why you are not seeing the prompt to do a CTRL I. You definitely should. You can try logging into the card by holding down ctrl and then typing OAM. This should get you to a login prompt. Then you can login with your admin1 or admin2 credentials. Once you get logged into the card type the command mgcsetup and that will walk you through configuring the IP info.

 

[rheine]

I will try that and let you know. In case that does not work is there a way to connect a network cable to the faceplace of the MGC and talk to it that way? I would need to set my computer up on the same subnet as that card. I know that it is on 10.12.90.xx...

Would I plug into the 1E on the faceplate?

 

[KCFLHRC]

You could plug into the card with a crossover cable and telnet to it.

 

[rheine]

Ok, I was able to log into that card by holding the control button down and typing OAM.

This is what I am seeing: ( I did need to login with the PDT2 username and the weird password 2tdp22ler


Welcome to the Media Gateway Controller command line.
Firmware Version: MGCCAD45
Management IP: 10.12.90.23
IPMG:
Primary CS IP Address: 10.12.90.10
Installed Daughterboards: 1
OS Created on: Date [Feb 12 2008] Time [10:50:15]

ldb> 03/01/2000 05:23:10 LOG0004 tMgcVgwAppStartRetry: DSP DBs are present, waiting for mgcdb.xml from Primary Call Server
mgcsetup


ELAN IP : 10.12.90.23 03/01/2000 05:23:25 LOG0004 tMgcVgwAppStartRetry: DSP DBs are present, waiting for mgcdb.xml from
Primary Call Server

ELAN subnet mask : 255.255.255.0
ELAN gateway IP : 10.12.90.49

Primary CS IP : 10.12.90.10


Could you tell me what is wrong with my IP information? It is loop 12 and the IP should be 10.12.90.27. So the ELAN IP should be changed to 10.12.90.27 and not 10.12.90.23? The below are the superloops:


>ld 97
SCSYS000
MEM AVAIL: (U/P): 98901144 USED U P: 5194773 173904 TOT: 104269821
DISK SPACE NEEDED: 309 KBYTES
REQ prt
TYPE supl
SUPL

SUPL SUPT SLOT XPEC0 XPEC1 SHLF ZONE0/1 IPR0/1

000 IPMG ---- -- - - -- - - 0 001 10.12.90.20
1 001 10.12.90.21
004 IPMG ---- -- - - -- - - 0 002 10.12.90.22
1 002 10.12.90.23
008 IPMG ---- -- - - -- - - 0 003 10.12.90.24
1 003 10.12.90.25
012 IPMG ---- -- - - -- - - 0 004 10.12.90.26
1 004 10.12.90.27
100 ---- ---- PHANTOM -- - - --- --- - --- ---------------

REQ

It looks like there was an IP conflict with loop 4 and that is why that MGC card went down, correct?

 

[rheine]

Ok, that worked. I needed to use the PDT2 password and the 2tdp22ler password to login OAM.

Here is the existing information out of the PBX:


>ld 97
SCSYS000
MEM AVAIL: (U/P): 98901144 USED U P: 5194773 173904 TOT: 104269821
DISK SPACE NEEDED: 309 KBYTES
REQ prt
TYPE supl
SUPL

SUPL SUPT SLOT XPEC0 XPEC1 SHLF ZONE0/1 IPR0/1

000 IPMG ---- -- - - -- - - 0 001 10.12.90.20
1 001 10.12.90.21
004 IPMG ---- -- - - -- - - 0 002 10.12.90.22
1 002 10.12.90.23
008 IPMG ---- -- - - -- - - 0 003 10.12.90.24
1 003 10.12.90.25
012 IPMG ---- -- - - -- - - 0 004 10.12.90.26
1 004 10.12.90.27
100 ---- ---- PHANTOM -- - - --- --- - --- ---------------

REQ


This is what I had seen on this MGC card.

03/01/2000 05:35:49 LOG0004 tMgcVgwAppStartRetry: DSP DBs are present, waiting for mgcdb.xml from Primary Call Server
mgcsetup


ELAN IP : 10.12.90.23 03/01/2000 05:36:04 LOG0004 tMgcVgwAppStartRetry: DSP DBs are present, waiting for mgcdb.xml from
Primary Call Server

ELAN subnet mask : 255.255.255.0
ELAN gateway IP : 10.12.90.49

Primary CS IP : 10.12.90.10


It looks like it conflicts with loop 4 and that would explain why the MGC on loop 4 lost it's connection. Do I just need to change the ELAN IP to 10.12.90.27 for loop 12-1?

 

[KCFLHRC]

If your superloop programming is correct then just go into the MGC card and do the mgcsetup command and put in the correct IP info

 

[KCFLHRC]

If your mgc card programming is correct then just change the superloop programming in ld 97.

 

[rheine]

I did make that change below:


ELAN IP : 10.12.90.27
ELAN subnet mask : 255.255.255.0
ELAN gateway IP : 10.12.90.49
Primary CS IP : 10.12.90.10
TLAN set to auto negotiate.
ELAN set to auto negotiate.
ELAN security Disabled
Is this correct? (y/n/[a]bort) : regWithMainCabinet: RPC: Port mapper failure - RPC: Unable to send
03/01/2000 05:38:49 LOG0003 regRetry: Failed to Register with Primary Call Server[10.12.90.10]
03/01/2000 05:38:49 SRPT1018 STARTUP: unable to send registration request to Primary Call Server.
03/01/2000 05:38:49 LOG0004 tMgcVgwAppStartRetry: DSP DBs are present, waiting for mgcdb.xml from Primary Call Server
y
The above changes require reboot to take effect.

Do you want to reboot now? (y/n/[a]bort) : y


I should be able to plug my card back in now. Thank you for all of your help. I will add to my post if there are still issues.

 

[KCFLHRC]

Good deal, let us know if you need any more help.