MGC won't register with primary security server

[steve64]

we have one SMG running rel 7.5 that was working properly and then decided the MGC wouldn't register with the primary security domain system session manager. When I run the reg u device (IP) I get the following response. Does anyone know what the "reason 6" means? I have other SMGs on this primary system and they have no problem.

This is in LD 117 on the SMGs call server

=> register u device 192.168.202.216
IP address of the Primary Security Server [192.168.201.45]:
SEC037 Security domain membership has been granted. (Centralized authentication is now
enabled.)

User Name (UCM): admin
Password (admin):
Sending messages to 192.168.202.216 to authorizing it to request security domain membership.
Waiting for status updates from the element...

=>
Communication about security domain membership with the element 192.168.202.216 failed. (Reason: 6)

 

[scotthdiv]

If it's an SMG, shouldn't you be registering the MGC from the main system?

Is UCM on System Manager?

 

[janaya]

STAT UCM SYS, from the main system to see if it is already registered. Scott is right, you shouldn't need to register via the SMG Call server.

John Anaya
Signet6 Network Sciences
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile

http://www.linkedin.com/pub/john-anaya/25/1b9/a9b/Edit

 

[steve64]

Ok here is the deal. I am aware that you do the reg U S in the main site. Here is the situation. Reg U s in the main system only finds the main site MGCs and the other SMG and they show "registered". If I do a stat IPMG it shows all 4 MGCs registered, but if you do a stat IPMG in the SMG pbx it also shows the local MGC registered and the other 3 MGCs unregistered. They should all show unregistered. Also if I do a stat u s on the SMG it says no MGCs to register. The other SMG that is registered to the main and in the stat IPMG shows all MGCs as unregistered. So bottom line is that the bad SMG thinks the MGC is registered locally and the main site thinks it is registered there also. Although the security domin say I don't know anything about you even though it has acknowledged the MGC in the security domain. It's messed up. I'm begining to think that maybe the MGC is bad. All programing has been checked and is proper. Avaya support as also looked at it confirmed all programing was correct but don't really have any ideas so far. They pulled a bunch of logs and I did a wireshark capture of the MGC doing a cold boot up for them. I'll see where it goes on Monday.

 

[M1spezi]

First, I would enter on the MGC leaveSecDomain. Maybe some old /or wrong information are stored in the card. Then I would enter on the MGC joinSecDomain.
On the Main system all MGC have show as registered. On the SMG in normal mode all MGC have show as unregistered


Meridian, Callpilot, CCM (Symposium) from Germany

 

[KCFLHRC]

Do a stat ucm sys refresh and see if it updates