Hi,
We have an issue in Cisco ASR 1006, randomly the adjacenys down. These adjacencys are configured towards CUCM trunk sip.
In CUCM the trunks sip are OK, there are not any logs about drops of the trunk sips.
Cisco ASR 1006 >> ASR1000 Software (X86_64_LINUX_IOSD-ADVENTERPRISEK9-M), Version 15.3(3)S4
CUCM >> System version: 10.5.2.11005-1
Below you can find the logs in Cisco Cube:
Oct 29 02:44:40 195.59.212.117 4405665: An adjacency's peer has been detected as unreachable.
Oct 29 02:44:40 195.59.212.117 4405666: Current signaling destination address: 172.31.16.3
Oct 29 02:44:40 195.59.212.117 4405667: Oct 29 02:44:40.789: %SBC-1-MSG-0415-0001-62B005-0604:
Oct 29 02:44:40 195.59.212.117 4405668: An alarm has been raised.
Oct 29 02:44:40 195.59.212.117 4405669: Severity: 80
Oct 29 02:44:40 195.59.212.117 4405670: OID: 4355434D2D637573743136312D33
Oct 29 02:44:40 195.59.212.117 4405671: ID: 0X50000000
Oct 29 02:44:40 195.59.212.117 4405672: Info: 172.31.16.3
Oct 29 02:44:41 195.59.212.117 4405673: Oct 29 02:44:40.790: %SBC-3-MSG-1501-0158-1FD3C4-0763:
Oct 29 02:44:41 195.59.212.117 4405674: This Routing Action is unusable. Reason: A signaling channel is offline.
Oct 29 02:44:41 195.59.212.117 4405675: This may be due to order of activation at start of day or after failover.
Oct 29 02:44:41 195.59.212.117 4405676: In this case expect a second log, to signal the routing action is usable.
Oct 29 02:44:41 195.59.212.117 4405677: Config set index = 1161
Oct 29 02:44:41 195.59.212.117 4405678: Routing table index = LCR-CUCM-C161
Oct 29 02:44:41 195.59.212.117 4405679: Routing action index = 2
Oct 29 02:44:41 195.59.212.117 4405680: Oct 29 02:44:41.797: %SBC-1-MSG-0415-0000-62B005-0581:
Oct 29 02:44:41 195.59.212.117 4405681: An alarm has been cleared.
Oct 29 02:44:41 195.59.212.117 4405682: OID: 4355434D2D637573743136312D33
Oct 29 02:44:41 195.59.212.117 4405683: ID: 0X50000000
Oct 29 02:44:41 195.59.212.117 4405684: Oct 29 02:44:41.797: %SBC-2-MSG-5001-0378-A3C708-0447:
Oct 29 02:44:41 195.59.212.117 4405685: An adjacency's peer has been detected as reachable after a previous
Oct 29 02:44:41 195.59.212.117 4405686: failure.
Oct 29 02:44:41 195.59.212.117 4405687: Current signaling destination address: 172.31.16.3
Oct 29 02:44:42 195.59.212.117 4405688: Oct 29 02:44:41.797: %SBC-3-MSG-1501-0251-1FD3C4-0940:
Oct 29 02:44:42 195.59.212.117 4405689: The following Routing Action is now usable.
Oct 29 02:44:42 195.59.212.117 4405690: Config set index = 1161
Oct 29 02:44:42 195.59.212.117 4405691: Routing table index = LCR-CUCM-C161
Oct 29 02:44:42 195.59.212.117 4405692: Routing action index = 2
Could you please help with this issue?
Thanks for your help,
Regards,
David Lozano
