AnsweredAssumed Answered

cisco_unity - SNMP & WMI test OK, but status = fail

Question asked by topside844 on Nov 16, 2010
Latest reply on Nov 19, 2010 by topside844

I'm having issues adding a couple Unity servers to the cisco_unity probe.

 

I'm getting good responses when testing WMI authentication and the Unity SNMP extensions are loaded on the servers.

Test SNMP queries work great.

 

However, this is what I get in the cisco_unity logs..

I see the "TaskExec: ping 'server.domain' failed....but if I try to ping from the server directly, all is well. I do not think this is a ping issue as pings, snmp, and WMI all work just fine from this robot.

 

Has anyone seen this before where WMI & SNMP & ICMP respond just fine, but the logs indicate otherwise? Thanks. I'm open to any suggestions :smileywink:

 

 

Nov 15 15:06:33:155 [2988] cisco_unity: TaskExec: completed 'lhc-unity.lhcgroup' status is 0x0000 [OK], next run in 60s 
Nov 15 15:06:41:624 [2540] cisco_unity: TaskExec: ping 'sela-Unity.redcross' failed... 
Nov 15 15:06:41:624 [3340] cisco_unity: TaskExec: ping 'causewayum02.causeway' failed... 
Nov 15 15:06:41:624 [0620] cisco_unity: TaskExec: ping 'causewayum01.causeway' failed... 
Nov 15 15:06:41:624 [2540] cisco_unity: ALARM: AgentState 'sela-Unity.redcross' [sela-Unity.redcross] - CRITICAL  
Nov 15 15:06:41:624 [3340] cisco_unity: ALARM: AgentState 'CausewayUM02.Causeway' [causewayum02.causeway] - CRITICAL  
Nov 15 15:06:41:624 [0620] cisco_unity: ALARM: AgentState 'CausewayUM01.Causeway' [causewayum01.causeway] - CRITICAL  
Nov 15 15:06:41:624 [0620] cisco_unity: TaskExec: completed 'CausewayUM01.Causeway' status is 0x0001 [FAIL], next run in 300s 
Nov 15 15:06:41:624 [3340] cisco_unity: TaskExec: completed 'CausewayUM02.Causeway' status is 0x0001 [FAIL], next run in 300s 
Nov 15 15:06:41:624 [2540] cisco_unity: TaskExec: completed 'sela-Unity.redcross' status is 0x0001 [FAIL], next run in 300s 

 

Nov 15 15:06:33:155 [2988] cisco_unity: TaskExec: completed 'lhc-unity.lhcgroup' status is 0x0000 [OK], next run in 60s 

Nov 15 15:06:41:624 [2540] cisco_unity: TaskExec: ping 'sela-Unity.redcross' failed... 

Nov 15 15:06:41:624 [3340] cisco_unity: TaskExec: ping 'causewayum02.causeway' failed... 

Nov 15 15:06:41:624 [0620] cisco_unity: TaskExec: ping 'causewayum01.causeway' failed... 

Nov 15 15:06:41:624 [2540] cisco_unity: ALARM: AgentState 'sela-Unity.redcross' [sela-Unity.redcross] - CRITICAL  

Nov 15 15:06:41:624 [3340] cisco_unity: ALARM: AgentState 'CausewayUM02.Causeway' [causewayum02.causeway] - CRITICAL  

Nov 15 15:06:41:624 [0620] cisco_unity: ALARM: AgentState 'CausewayUM01.Causeway' [causewayum01.causeway] - CRITICAL  

Nov 15 15:06:41:624 [0620] cisco_unity: TaskExec: completed 'CausewayUM01.Causeway' status is 0x0001 [FAIL], next run in 300s 

Nov 15 15:06:41:624 [3340] cisco_unity: TaskExec: completed 'CausewayUM02.Causeway' status is 0x0001 [FAIL], next run in 300s 

Nov 15 15:06:41:624 [2540] cisco_unity: CheckMonitor: sela-Unity.redcross/AvCsGateway next in 300s 

Nov 15 15:06:41:624 [2540] cisco_unity: CheckMonitor: sela-Unity.redcross/AvCsMgr next in 300s 

Nov 15 15:06:41:624 [2540] cisco_unity: CheckMonitor: sela-Unity.redcross/SNMP Service next in 300s 

Nov 15 15:06:41:624 [2540] cisco_unity: CheckMonitor: sela-Unity.redcross/SQL Server next in 300s 

Nov 15 15:06:41:624 [2540] cisco_unity: TaskExec: completed 'sela-Unity.redcross' status is 0x0001 [FAIL], next run in 300s 

Outcomes