Troubleshooting Alarms/Alerts to be sent as SNMP Traps

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Troubleshooting Alarms/Alerts to be sent as SNMP Traps)
m (1 revision)

Revision as of 15:21, 9 April 2010

Troubleshooting Alarms/Alerts to be sent as SNMP Traps



Problem Summary The user is not able to send the alarms or alerts generated by the system as SNMP Traps.
Error Message None.
Possible Cause This may be caused either due to the incorrect SNMP configuration or incorrectly set MIB Trap parameters.
Recommended Action For sending the syslog messages as SNMP Traps, follow the below steps:
  • Set the SNMP Trap destination from the Cisco Unified Serviceability interface.
  • Enable trap generation in CISCO-SYSLOG-MIB. Set clogsNotificationEnabled (1.3.6.1.4.1.9.9.41.1.1.2) to true by using the SNMP Set operation
  • Set appropriate SysLog level in CISCO-SYSLOG-MIB. Set clogMaxSeverity (1.3.6.1.4.1.9.9.41.1.1.3) value by using the SNMP Set operation.
  • By default, the Alerts goes to local syslog. So, this will enable Alerts to be sent as SNMP Traps as well.
Release Release 8.0(1)
Associated CDETS # None


Rating: 0.0/5 (0 votes cast)

Personal tools