SNMP Issues on Call Manager 5.X server

Unanswered Question
Feb 28th, 2009

I'm having issues where the Call Manager server is not responding to SNMP requests even though the server claims to be up and running SNMP correctly, when I do a "utils snmp test" I get the following output. Any ideas what is happening? Any input that anyone can offer would be greatly appreciated.

Thanks,

Steve

admin:utils snmp test

Service Manager is running

Test SNMP Trap starts

Alarm Configuration page enable 'Sys Log' alarms to 'Debug' level for Cisco CallManager

The catalog name is TestAlarmCatalogfacility name is Cisco CallManager

Thread[main,5,main]:Alarms:Alarm Initalization returned:0

TestAlarmInformational sent [Returncode=0]

TestAlarmEmergency sent [Returncode=0]

TestAlarmAlert sent [returncode=0]

TestAlarmCritical sent [Returncode=0]

TestAlarmDebug sent [Returncode=0]

TestAlarmNotice sent [Returncode=0]

TestAlarmWarning sent [Returncode=0]

Message from [email protected] at Sat Feb 28 13:06:55 2009 ...

CMGR2 local7 0 : 1: Feb 28 18:06:55.548 UTC : %CCM_CALLMANAGER-UNKNOWN-0-TestAlarmEmergency: Testing EMERGENCY_ALARM App ID:Cisco CallManager Cluster ID: Node ID:CMGR2

Message from [email protected] at Sat Feb 28 13:06:55 2009 ...

127.0.0.1 local7 0 1: Feb 28 18:06:55.549 UTC : %CCM_CALLMANAGER-UNKNOWN-0-TestAlarmEmergency: Testing EMERGENCY_ALARM App ID:Cisco CallManager Cluster ID: Node ID:CMGR2

Catalog Name is TestAlarmCatalog and facility name is Cisco CallManagerGenericAlarmJNI_init SetMonitorInformation 0

GenericAlarmJNI_addMonitors MonitorName Sys Log,Server Name 127.0.0.1,AppName Cisco CallManager,Facility Name Cisco CallManager

GenericAlarmJNI_addMonitors SetMonitorInformation 0

GenericAlarmJNI_addMonitors MonitorName SNMP Traps,Server Name 127.0.0.1,AppName Cisco CallManager,Facility Name Cisco CallManager

GenericAlarmJNI_addMonitors SetMonitorInformation 0

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion