06-27-2017 08:12 AM - edited 03-17-2019 10:39 AM
When you look at Device / Phone the Status / IP or Real-Time Device Status is unknown. But Publisher and Subscriber 2 show proper status.
Solved! Go to Solution.
06-27-2017 08:42 PM
That is good to hear
Regards
Abhay
06-27-2017 08:16 AM
Restart the Cisco ris data collector service on the affected node and that should resolve it.
Regards
Abhay
Kindly rate all helpful posts !!!
06-27-2017 08:30 AM
Hi,
Abhey is right, “The Real-time Information Server (RIS) maintains real-time information such as device registration status, performance counter statistics, critical alarms generated, and so on. The Cisco RIS Data Collector service provides an interface for applications, such as the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT), SOAP applications, and so on, to retrieve the information that is stored in all RIS nodes in the cluster.”
In short, RisDC is a service running on CUCM that collects information (counters, status of devices, performance data) from CCM service and presents them to different “Clients”. By “Clients” we mean RTMT, CUCM User Web Page, SOAP Requests; the mentioned clients usually presents those data to our end customers in readable and user friendly form.
So if the device is working fine and just showing unregistered try restarting RIS DC service it is not production impacting.
(Rate if it helps)
JB
06-27-2017 08:48 AM
It has been 20 minutes. Status not updating. I also took a stab and reset RTMT Reporter Servlet. Most services on this server have up time of 370 days. I have been told a server should be reset periodically. Maybe rebooting the server would be a better solution?
06-27-2017 08:57 AM
Hi
did you restart service on all server, i would start from PUB and then move to SUB for restart order
also what is the CUCm version?
JB
06-27-2017 09:11 AM
Ok, Restarted on all 3 servers. No Status. This is ver 10.5.2.12901-1
06-27-2017 09:21 AM
Sounds like below BUG
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCus29507/?reffering_site=dumpcr
Can you confirm the condition in workaround is true for you?
06-27-2017 09:25 AM
This is not the case. Phone Configuration / Real-time Device Status is not shown here. I'm inclined to think server reboot may be easiest solution. :)
06-27-2017 09:28 AM
If cluster reboot is not an issue you can always try that, start with PUB first and then move to SUB.
Let us know if that works :-)
JB
06-27-2017 05:06 PM
So later today, my Pub was not showing status. I reset RIS service. Pub was ok now. Then I checked Sub1. It had started working also. So now all is ok.
06-27-2017 08:42 PM
That is good to hear
Regards
Abhay
02-25-2021 05:00 AM
Thank you so much Abhay,
After many years still your shared information are very useful.
06-27-2017 11:37 AM
What are the chances that the subscriber is on another LAN and there's a FW between the publisher and the subscriber?
If so, please check that those TCP ports are open: TCP/2555-2556.
06-27-2017 11:49 AM
Well, The servers are within the same facility. But, Pub and Sub2 are on the same Virtual host which moved to a new data building on site. The Sub1 is schedule to move next week. I guess they could be isolated enough on the network that it's creating this issue. Although it shouldn't. I'm interested to see if a reboot fixes it, in the current location or if the move fixes it, when it will be next to the Pub again.
06-27-2017 12:00 PM
So, like I thought. That's the problem :)
I bet that there's a Firewall between the old building and the new one that is blocking all the relevant ports, and I guess it also blocks the replication traffic between the nodes.
Try to do the following command:
utils dbreplication runtimestate
I think you'll see that the replication is OK between the Publisher and Subscriber 2, but not to Subscriber 1. Try it just out of curiosity ;)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide