show ccm "backup ready continues to go down"

Unanswered Question
Feb 4th, 2008

Issue here is that when I issue the command show ccm, my backup which is the publisher, goes back and forth between backup ready and down. I have multiple gateways that are running the same IOS and the issues doe not seem to be occurring there.

I looked at traces on the publisher and this is what I see.

02/04/2008 06:48:08.455 CCM|MGCPBhHandler 192.168.3.1 - internal ERROR wait_SdlConnectionInd - mMGCPBhGWInfo not clean on last TCP close!!!|<CLID::StandAloneCluster><NID::192.168.2.20><CT::0,0,0,0.0><IP::><DEV::>

I do not know exactly what this trace is telling me. The ip that the trace is referencing is the gateway in question.

The below is the output from the debug ccm-manager events. It looks as if the connection is opening and closing again

*Feb 4 15:01:34.643: cmapp_host_fsm: Processing event CONN_OPEN for host 1 (192.168.

2.20) in state STANDBY_OPENING

*Feb 4 15:01:34.643: cmapp_stop_host_tmr: for host 1 (192.168.2.20)

*Feb 4 15:01:34.643: cmapp_host_fsm: New state STANDBY_READY for host 1 (192.168.2.2

0)

*Feb 4 15:01:34.643: cmapp_mgr_process_event: Host 1 (192.168.2.20) is standby ready

*Feb 4 15:01:34.643: cmapp_mgr_check_hostlist: Active host is 0 (192.168.2.21)

*Feb 4 15:01:34.651: cmapp_host_fsm: Processing event CONN_CLOSED for host 1 (192.16

8.2.20) in state STANDBY_READY

*Feb 4 15:01:34.651: cmapp_start_host_tmr: Host 1 (192.168.2.20), tmr 0

*Feb 4 15:01:34.651: cmapp_open_new_link: Open link for [1]:192.168.2.20

*Feb 4 15:01:34.651: cmbh_open_tcp_link: Using MGCP bound IP addr 192.168.3.1

*Feb 4 15:01:34.651: cmbh_open_tcp_link: Opening TCP link with Rem IP 192.168.2.20,

Local IP 192.168.3.1, port 2428

*Feb 4 15:01:34.651: cmapp_open_new_link: Open initiated OK: Host 1 (192.168.2.20),

session_id=461CC274

*Feb 4 15:01:34.651: cmapp_host_fsm: New state STANDBY_OPENING for host 1 (192.168.2.20

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
mattcalderon Mon, 02/04/2008 - 07:19

Well it seems to have been resolved. I just restarted the ccm service on the publisher from the control center. Service seems to be steady now and not bouncing back and forth between down/backup ready. Not sure why that happened though.

Actions

This Discussion