Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

RTMT 8.5 / Can not observe CCM when subscriber reboot

Hello,

I've a cluster of 2 CCMs in version 8.0.3.

I launch RTMT.

I see both CCMs.

When I reboot the subscriber, I don't see the subscriber (normal) but I don't see too the Publisher (anormal).

I've got an error on RTMT : "replies contain error,, [ErrorMsg] : AMC is not running on Ip@Subscriber."

"Error polling alert status - AMC service is down."

What is the solution to see the publisher when subscriber reboot ?

Best regards.

./dwam

Everyone's tags (3)
3 REPLIES
Silver

Re: RTMT 8.5 / Can not observe CCM when subscriber reboot

Hi Dwam,

How many times have you experienced this issue?

Did you try to restart the AMC service on the pub, when you face this, i believe restarting the AMC service should help.

Also i see a related bug: RTMT on secondary node does not work if primary node is down, but its an internally found bug.

Also can you provide a screen shot of the error, if restarting the service does not help, we might need to look at sniffers(packet captures from the client and the call manager server.

HTH

Kunal

New Member

Re: RTMT 8.5 / Can not observe CCM when subscriber reboot

Hello Kunal,

Thank you for your answer.

I 'm facing this behaviour all the time I reboot the subscriber (5 times).

I have rebooted the cluster but the problem occurs.

I insert 2 screenshots of RTMT with error message.

1 when the server subscriber is stop.

1 after the server subscriber is up.

We can see that during 14 minutes, we can not see statistics about publisher.

I will try to restart the AMC Service.

If the problem stay, I will snif.

Best regards.

./DWAM

New Member

Re: RTMT 8.5 / Can not observe CCM when subscriber reboot

Thank You Kunal.

I have checked on CCM Service AMC and seen that there is a misconfiguration about Primary Collector : it was the subscriber.

I have changed to publisher and reboot subscriber.

Now it 's good.

Best regards.

./DWAM

1292
Views
4
Helpful
3
Replies
CreatePlease login to create content