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

Zero Monitored Phones on 1040 after upgrade to CUSM 2.2

The two 1040 sensors were running and I could see MOS reports on CUSM 2.1.

After the upgrade to CUOM 2.2/CUSM 2.2 I can see the CUCM based CVTQ reports but not the sensor based reports. The two sensors show zero Monitored Phones. From the sensors web page I can see on the Diagnostics link that the sensors are indeed analysing streams and sending data. The sensor image file was changed to the SvcMonAB2_102.img as required by the install procedures. Both sensors are registered with the CUSM 2.2.

Any help is appreciated

2 REPLIES
Community Member

Re: Zero Monitored Phones on 1040 after upgrade to CUSM 2.2

The syslog.log only shows data after setting Logging debug level an shows sensor data:

19-Aug-2009|17:09:12.181|INFO |syslog|Thread-311|<14>Aug 19 17:07:00 PJCCRPB-P01 SvcMonA_200908191707[001120FFFF72]: %%%%

19-Aug-2009|17:09:12.197|INFO |syslog|Thread-311|<14>Aug 19 17:07:00 PJCCRPB-P02 SvcMonA_200908191707[001120FFE596]: %%%%

So the sensor are sending the data.

I have found errors on the monitor.log:

14-Aug-2009|12:25:05.447|ERROR|Monitor|main|QOVRDbMonitor loaded from : C:/Program Files/CSCOpx/SimpleLog/sl_monitor.conf

14-Aug-2009|16:43:41.873|ERROR|Monitor|main|QOVRDbMonitor loaded from : C:/Program Files/CSCOpx/SimpleLog/sl_monitor.conf

19-Aug-2009|02:11:41.381|ERROR|Monitor|Thread-1|Occurred during maintenance: java.io.IOException: Cannot run program "cmd": CreateProcess error=1450, Insufficient system resources exist to complete the requested service

19-Aug-2009|02:16:41.392|ERROR|Monitor|Thread-1|Occurred during maintenance: java.io.IOException: Cannot run program "cmd": CreateProcess error=1450, Insufficient system resources exist to complete the requested service

19-Aug-2009|16:27:50.961|ERROR|Monitor|main|QOVRDbMonitor loaded from : C:/Program Files/CSCOpx/SimpleLog/sl_monitor.conf

Any help is appreciated

Community Member

Re: Zero Monitored Phones on 1040 after upgrade to CUSM 2.2

After opening a Case in Cisco TAC the problem was solved. The sensors were not defined on the DNS, but they learned their names from the IOS DHCP server whose configuration has the client-name command. As the data from the sensor to the CUSM server contains the name instead of the IP, the CUSM server could not match the data among the sensors registered by their IP address. So the data was discarded. The simple solution was to add the sensor names to the ...\etc\hosts file and the reports started showing. This behavior is new with the CUSM 2.2, because before under CUSM 2.1 it worked with the same configuration.

237
Views
0
Helpful
2
Replies
CreatePlease to create content