MGC Registration issue

[srcvh1]

Has anyone ever seen this before? I started looking into a GR backup issue when I ran into this issue:

=> stat ucm sys
MGC 192.168.5.26 UNKNOWN
MGC 192.168.167.21 UNKNOWN
MGC 10.255.253.34 UNKNOWN
MGC 192.168.5.23 UNKNOWN
MGC 192.168.47.21 UNKNOWN
MGC 192.168.5.27 UNKNOWN
MGC 192.168.5.24 UNKNOWN
MGC 192.168.5.28 UNKNOWN
MGC 192.168.157.21 UNKNOWN
MGC 192.168.5.25 UNKNOWN
MGC 192.168.107.21 UNKNOWN
MGC 10.255.253.21 UNKNOWN
MGC 192.168.5.22 UNKNOWN
MGC 192.168.107.22 UNKNOWN
MGC 10.255.253.35 UNKNOWN
MGC 192.168.5.21 UNKNOWN

=> reg ucm sys
IP address of the Primary Security Server [192.168.5.29].
User Name (UCM): XXXXXX
Password (XXXXXX):

These elements are registered with the Call Server
MGC 192.168.5.26
MGC 192.168.167.21
MGC 10.255.253.34
MGC 192.168.5.23
MGC 192.168.47.21
MGC 192.168.5.27
MGC 192.168.5.24
MGC 192.168.5.28
MGC 192.168.157.21
MGC 192.168.5.25
MGC 192.168.107.21
MGC 10.255.253.21
MGC 192.168.5.22
MGC 192.168.107.22
MGC 10.255.253.35
MGC 192.168.5.21
MGC 10.252.8.5
Register these 17 elements to the security domain using your credentials if not
already registered? (Y/N)y
Sending messages to 17 elements authorizing them request security domain members
hip.
Waiting for status updates from each of the elements...
..............
SRPT316 Internal communications message transmission failed.
(Transport: AFS; Subject: SDM; Action: PUBLISH; IP: 192.168.5.26; Reason: 3; De

tails: )
................................................................................
.......
SRPT316 Internal communications message transmission failed.
(Transport: AFS; Subject: SDM; Action: PUBLISH; IP: 192.168.5.23; Reason: 3; De

tails: )
................................................................
SRPT316 Internal communications message transmission failed.
(Transport: AFS; Subject: SDM; Action: PUBLISH; IP: 192.168.5.27; Reason: 3; De

tails: )
...............................
SRPT316 Internal communications message transmission failed.
(Transport: AFS; Subject: SDM; Action: PUBLISH; IP: 192.168.5.24; Reason: 3; De

tails: )
.........................
SRPT316 Internal communications message transmission failed.
(Transport: AFS; Subject: SDM; Action: PUBLISH; IP: 192.168.5.28; Reason: 3; De

tails: )
.......................................................
SRPT316 Internal communications message transmission failed.
(Transport: AFS; Subject: SDM; Action: PUBLISH; IP: 192.168.5.25; Reason: 3; De

tails: )
..................................................16/06/2014 09:39:27 LOG0006 VG
W: vgwQoSAlarmGenerate: QoS Alarm is suppressed because alarm notification is tu
rned off
.........................................
SRPT316 Internal communications message transmission failed.
(Transport: AFS; Subject: SDM; Action: PUBLISH; IP: 192.168.5.22; Reason: 3; De

tails: )
................................................................................
..............
SRPT316 Internal communications message transmission failed.
(Transport: AFS; Subject: SDM; Action: PUBLISH; IP: 192.168.5.21; Reason: 3; De

tails: )
................................................................................
................................................................................
................................................................................
...........................
TIM000 09:46 16/6/2014 CPU 0

PRI009 DCH: 130 DATA: 00000004
................................................................................
...................................................................No new elemen
ts were registered to the security domain.
17 element(s) failed to request security domain registration.

It says that SMGs are registered yet they all have UNKNOWN next to their status. I tried to re register them and had the results documented. I'm sure whatever this is is causing my GR backup issue. Obviously this is a much bigger issue. Has anyone ever run into this and found the cause?

Thank you,

Scott C

 

[Tacosoup]

For the replication backup......Try disabling secure transfers in LD117. Then perform backup

** Proofread carefully to see if you any words out.

 

[srcvh1]

Just an update on this issue. It looks like there is a patch that addresses this issue. This switch has not been patched in over a year so that is my next step. Fingers crossed!

 

[KCFLHRC]

A patch for replication or the MGC issue?

 

[srcvh1]

I believe it was for the Replication issue. I was pulled from this job for another emergency. The remote engineers made the patch find. I'll update when I go out to update the deplist