M000 display on MC32 card

[voip64]

When I install an MC32 card and push the config to it Via Element Manager, the display shows F000 for about 2 minutes and then reverts to M000. E-Lan or T-Lan problems?????

 

[atascoman]

It sounds like a ELAN problem. This message means that the card is going into a master state because it can't see the leader signaling server. This is the backup TPS feature which allows IP phones to register to the MC32 in the event the signaling server is out of service.

Is this the only MC32 card in the system? If you hard boot the card after the push does it still do this?

 

[voip64]

I have three MC32 cards and two are doing the same thing. Both on one customer provided ethernet layer 2 switch. The other that works is on a seperate ethernet switch. I'm trying to prove this to be a network issue. If I hard boot the card and push the config it does the same thing. Lasts for about two minutes and then becomes the master, both of them. I was confused as to whether it was an E-lan error or t-lan.

 

[Tman45]

POSSIBLE SOLUTION:

We are a Foundry shop and our network core was 1 1/2 years behind in IOS 4.0 or so. The network guys recently upgraded the OS and rebooted our Core with IOS 5.0 or so. THIS event caused our 4.5 Nortel MG1000 system with MC 32 cards to display M000 as you state above!!! So, our vendor came in and plugged in a simple switch and the cards immediately showed F000 and stayed that way! SO, I somehow convinced our network engineers to downgrade the Core OS back to 4.0 to see if it cleared the M000 on the MC 32 cards AND IT DID!!!! We are going to test this next month by reloading with 5.0 version IOS to see if the cards show M000 again, but it would appear that they will. So the next step for us is to go to Foundry and figure out what changed in code that messed with the Nortel TLAN. This appears to be an issue with Layer 2 TLAN. ELAN did not appear impacted. I will post once we have time to perform the confirmation test above.

 

[voip64]

Thank you very much.

 

[AnthonyHardy]

FYI, I have this same issue and spent a LOT of time working on this. I am contacting my foundry people to find out why the UDP broadcasts weren't going out properly and will post the info in this thread:

http://www.tek-tips.com/viewthread.cfm?qid=1556433&page=1

 

[Tman45]

VERY NICE POST AnthonyHardy!! Sorry that you had an 'exasperated' night when you learned that the M000 will still display!!! We had a vendor come in and plug in a simple switch and BOOM the MC32 went to F000 as they are supposed to. So, this is definitely something to do with Foundry routing and it must occur with an IOS upgrade along the way. You say 4.3v does the same thing, right? I can try to find out what version of IOS we were on when it was working properly and let you know!!!

 

[Tman45]

I did verify with my NetEng team that our Foundry was running version 4.0 IOS when the communication was working properly ... so it has to be 4.1 or higher that caused this TPS issue between the SigServers and MC32 cards trying to be Master.