VOIP Monitor Subsystem is in partial service or OOS

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(New page: == VOIP Monitor Subsystem is in partial service or OOS == {| border="1" |- ! '''Problem Summary''' | VOIP Monitor Subsystem is in partial service or OOS |- ! '''Error Message''' | VOIP Mo...)
(VOIP Monitor Subsystem is in partial service or OOS)
 
Line 20: Line 20:
   Check both LDAP for the "''ipHostName'':" entry, under key  " ''dn: svrType=LRM Server,ou=Servers,lcc=Call Center 1,ou=Company,o=Spanlink Communications''".  
   Check both LDAP for the "''ipHostName'':" entry, under key  " ''dn: svrType=LRM Server,ou=Servers,lcc=Call Center 1,ou=Company,o=Spanlink Communications''".  
   The value should be the same in both LDAP.
   The value should be the same in both LDAP.
 +
5. Node2's VoipMon SS failed to connect to node2's LDAP with ConnectionException.
 +
 +
e.g.
 +
%MIVR-LIB_LDAP-3-LDAP_CON_ERROR:Error accessing LDAP: ldap url=ldap://10.208.16.64:3016,Exception=javax.naming.CommunicationException: 10.208.16.64:3016 [Root exception is java.net.ConnectException: Connection refused]
 +
|-
|-
Line 28: Line 33:
For possible causes 4, restart the LDAP Monitor Service followed by the VoIp Monitor Service on the current master server. Check the LDAP again, if still out of synch then restart both Engine
For possible causes 4, restart the LDAP Monitor Service followed by the VoIp Monitor Service on the current master server. Check the LDAP again, if still out of synch then restart both Engine
-
If after all the above the issue remains, then reboot both uccx servers.  
+
For possible cause 5, reboot both uccx servers.  
 +
 
|-
|-
! '''Release'''
! '''Release'''

Latest revision as of 18:43, 19 September 2011

VOIP Monitor Subsystem is in partial service or OOS

Problem Summary VOIP Monitor Subsystem is in partial service or OOS
Error Message VOIP Monitor Subsystem shows as in partial service or OOS on "Control Center - Network Services" page in Cisco Unified CCX Serviceability.
Possible Cause

1. One or both (in case of HA) of the Cisco Desktop VoIP Monitor Service in the cluster are OOS.

2. One or both (in case of HA) of the Cisco Desktop Call/Chat Service in the cluster are OOS.

3. Cisco Desktop LDAP Monitor Service is OOS.

4. None of the above, but the LDAP between the nodes (HA) are out of synch in terms of which is the active LRM server. Below is how to determine:

  Check both LDAP for the "ipHostName:" entry, under key  " dn: svrType=LRM Server,ou=Servers,lcc=Call Center 1,ou=Company,o=Spanlink Communications". 
  The value should be the same in both LDAP.

5. Node2's VoipMon SS failed to connect to node2's LDAP with ConnectionException.

e.g. %MIVR-LIB_LDAP-3-LDAP_CON_ERROR:Error accessing LDAP: ldap url=ldap://10.208.16.64:3016,Exception=javax.naming.CommunicationException: 10.208.16.64:3016 [Root exception is java.net.ConnectException: Connection refused]


Recommended Action

For possible causes 1 to 3, restart the problematic services followed by VoIp Monitor Service. Make sure all services are up.

For possible causes 4, restart the LDAP Monitor Service followed by the VoIp Monitor Service on the current master server. Check the LDAP again, if still out of synch then restart both Engine

For possible cause 5, reboot both uccx servers.

Release Unified CCX Release 8.0 & Unified CCX Release 8.5
Associated CDETS # CSCtk34897,CSCtn16852

Rating: 5.0/5 (3 votes cast)

Personal tools