I am having an issue with a Cisco 2821 router that seems to loose it's connection to CCM. The backhauling for layer 3 of the PRIs stops and the gateway seems to un-register. In the Real Time Monitoring Tool I see "NumberOfRegisteredGatewaysDecreased" and then "NumberOfRegisteredGatewaysIncreased" a few seconds later.
To eliminate this as a carrier issue there are currently two PRIs on the router. They both drop and go out of service simultaneously. The issue occurs with just one PRI configured as well.
The IOS version on the router is (C2800NM-ADVIPSERVICESK9-M), Version 12.4(9)T7 The CCM version is 22.214.171.12403-1
The debug output is as follows and I am attaching a file with extended output
Jun 10 14:28:25.114: cmbh_tcp_rdhdr: TCP link to x.x.x.x closing... Jun 10 14:28:25.114: cmbh_tcp_fini: TCP link to x.x.x.x closed -- calling callback Jun 10 14:28:25.114: cmbh_remove_link: Freeing link record with address 49DFDBF0 for x.x.x.x. Jun 10 14:28:26.846: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/1:23, TEI 0 changed to down Jun 10 14:28:26.854: cmbrl_send_pak: No active CCM -- ignore packet Jun 10 14:28:26.854: ISDN Se0/0/1:23 Q931: L3_ShutDown: Shutting down ISDN Layer 3 Jun 10 14:28:26.854: cmbrl_send_pak: No active CCM -- ignore packet Jun 10 14:28:26.858: cmbrl_send_pak: No active CCM -- ignore packet Jun 10 14:28:27.546: cmbrl_config_changed: idb=Serial0/0/1:23,set_or_cleared=0 Jun 10 14:28:27.546: cmbrl_clear: cmbrl_ptr=49DC3100 Jun 10 14:28:27.546: cmbh_notify_func: event = 0 Jun 10 14:28:27.546: cmbh_notify_func: Se0/0/1:23: Removing CCM Backhaul binding Jun 10 14:28:28.766: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:23, TEI 0 changed to down Jun 10 14:28:28.774: cmbrl_send_pak: No active CCM -- ignore packet Jun 10 14:28:28.774: ISDN Se0/0/0:23 Q931: L3_ShutDown: Shutting down ISDN Layer 3 Jun 10 14:28:28.774: cmbrl_send_pak: No active CCM -- ignore packet Jun 10 14:28:28.774: cmbrl_send_pak: No active CCM -- ignore packet Jun 10 14:28:28.830: %LINK-5-CHANGED: Interface Serial0/0/1:23, changed state to administratively down
Here are the pertinent parts of the configuration:
Well, you don't have to run to H.323 just yet. At least not until you have better reason than a one liner on the netpro forum...
Anyway, the gateway is losing connectiong to the CUCM for some reason. Whether it is a software bug or not is TBD at this time. I have not checked that myself due to time constraints. Some things to consider:
1. When did this start or has it been happening since you implemented? If it is a recent thing, what changed?
2. Have you reveiwed the CUCM application logs and traces for the time period in questions. You will need these to get a better picture of what is going on. In particular, are any other devices exhibiting issues? When the device unregisters in the application log, you will find reason codes. Sometimes they are helpful. Usually they can help narrow the fault domain.
3. Check the network interface from the gateway to the attached switch or WAN. Look for interface up/down hits, CRCs, errors, etc. Check on both sides of the link if possible. If this router connects to a LAN environment, check uplink interfaces for hits, errors, etc.
4. Does this happen when no calls are occurring?
5. Does this happen only on ingress or egress calling?
A word on bugs and protocols and IOS. There are plenty of bugs to spread around. There almost like opinions in that way.
I would not eliminate the carrier yet just cause there are two circuits. They more than likely both ride into the building under the same cable sheath, if there is a problem with the cable (or other shared facilities along the way) you could get this problem. Also, the PRI's share a 2MFT card. Maybe it can be changed. I agree with the other post to look at errors on the interfaces but focus on the controllers that terminate the PRI's.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.