Unable to sync node in UCM.

[1norteltech]

We "upgraded" our wireless network and now the 6140 wireless phones are having roaming issues. In UCM I checked the box for low latency mode to see if it would help, but after saving and saving the node, when I tried to sync the node all failed with error failed to connect to server. How do I get the node syncronized again? CS1000M R6.

 

[janaya]

go into your Call Server.

LD 117

=>reg ucm cs

Re-register your call server to the domain. It can lose this and the call server will still work.

I just ran into changing my node and trying to sync and got the same thing. Once I re-registered it worked fine. Give it a try and let us know.

John Anaya
Amdocs Inc.
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/

 

[1norteltech]

=> reg ucm cs
SCH0099 CS?

 

[mikepbx1]

try:
=> reg u s

http://pbxbook.com

 

[1norteltech]

reg u s
IP address of the Primary Security Server [10.239.0.201]:

User Name (UCM): shawn
Password (shawn):


10.239.0.201 (RSA) permanently added to the Authorized key file

SEC037 Security domain membership has been granted. (Centralized authentication is now
enabled.)

SEC097 This element has successfully requested membership in the security domain

These elements are registered with the Call Server
MC32S 10.247.3.210
MC32S 10.247.3.220
MC32S 10.247.3.216
MC32S 10.247.3.218
MC32S 10.247.3.212
MC32S 10.247.3.214
Do you want to allow these 6 elements to request security domain membership using your credentials? (Y/N) [N] y
Sending messages to 6 elements authorizing them to request security domain membership.
Waiting for status updates from each of the elements...
..............
SEC102 Element 10.247.3.210 failed to request membership in the security domain, Reason
FAILED.
......
SRPT259 AFS: AFS failed to synchronize [SDM] application with target [10.247.3.210].

Communication about security domain membership with the element 10.247.3.210 failed. (Reason: 6)
...........
SEC102 Element 10.247.3.220 failed to request membership in the security domain, Reason
FAILED.
......
SRPT259 AFS: AFS failed to synchronize [SDM] application with target [10.247.3.220].
.
Communication about security domain membership with the element 10.247.3.220 failed. (Reason: 6)
.............
SEC102 Element 10.247.3.216 failed to request membership in the security domain, Reason
FAILED.
......
SRPT259 AFS: AFS failed to synchronize [SDM] application with target [10.247.3.216].
.
Communication about security domain membership with the element 10.247.3.216 failed. (Reason: 6)
....
SEC102 Element 10.247.3.218 failed to request membership in the security domain, Reason
FAILED.
......
SRPT259 AFS: AFS failed to synchronize [SDM] application with target [10.247.3.218].
.
Communication about security domain membership with the element 10.247.3.218 failed. (Reason: 6)
..............
SEC102 Element 10.247.3.212 failed to request membership in the security domain, Reason
FAILED.
......
SRPT259 AFS: AFS failed to synchronize [SDM] application with target [10.247.3.212].
.
Communication about security domain membership with the element 10.247.3.212 failed. (Reason: 6)
........
SEC102 Element 10.247.3.214 failed to request membership in the security domain, Reason
FAILED.
.The Call Server and 0 attached elements successfully requested security domain membership, but 6 elements failed.

=>
SRPT259 AFS: AFS failed to synchronize [SDM] application with target [10.247.3.214].

DTC001

Sorry, this is all new to me. A couple years ago we went from R25.40 to R6 and got no training.

 

[janaya]

did you try to sync after you did this?

John Anaya
Amdocs Inc.
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/

 

[1norteltech]

Yes and it failed. Also appears the mc32s cards are unregistered. I rebooted oneand was able to reg u s and it registered, the others still failed. Going to reboot the rest to see if I can get them registered and try sync again.

 

[1norteltech]

mc32s' registered sync still failed.