Table Of Contents

Configuring SNMP Trap/Inform Parameters

Configuring CISCO-SYSLOG-MIB Trap Parameters

Configuring CISCO-CCM-MIB Trap Parameters

Configuring CISCO-UNITY-MIB Trap Parameters

Where to Find More Information

Configuring SNMP Trap/Inform Parameters

---

This section describes how to use CLI commands to set configurable trap settings. Table 15-3 provides the SNMP trap configuration parameters and recommended configuration for CISCO-SYSLOG-MIB, CISCO-CCM-MIB, and CISCO-UNITY-MIB.

This chapter provides information on the following topics:

•Configuring CISCO-SYSLOG-MIB Trap Parameters

•Configuring CISCO-CCM-MIB Trap Parameters

•Configuring CISCO-UNITY-MIB Trap Parameters

Configuring CISCO-SYSLOG-MIB Trap Parameters

Use these guidelines to configure CISCO-SYSLOG-MIB trap settings on your system:

•Set clogsNotificationEnabled (1.3.6.1.4.1.9.9.41.1.1.2) to true by using the SNMP Set operation; for example, use the net-snmp set utility to set this OID to true from the linux command line using: snmpset -c <community string> -v2c <transmitter ipaddress> 1.3.6.1.4.1.9.9.41.1.1.2.0 i 1

You can also use any other SNMP management application for the SNMP Set operation.

•Set clogMaxSeverity (1.3.6.1.4.1.9.9.41.1.1.3) value by using the SNMP Set operation; for example, use the net-snmp set utility to set this OID value from the linux command line using: snmpset -c public -v2c 1<transmitter ipaddress> 1.3.6.1.4.1.9.9.41.1.1.3.0 i <value>

Enter a severity number for the <value> setting. Severity values increase as severity decreases. A value of 1 (Emergency) indicates highest severity, and a value of 8 (Debug) indicates lowest severity. Syslog agent ignores any messages greater than the value that you specify; for example, to trap all syslog messages, use a value of 8.

You can also use any other SNMP management application for the SNMP Set operation.

---

Note Before logging, Syslog truncates any trap message data that is larger than the specified Syslog buffer size. The Syslog trap message length limitation equals 255 bytes.

---

Configuring CISCO-CCM-MIB Trap Parameters

Unified CM and Unified CM BE 5000 only: Use these guidelines to configure CISCO-CCM-MIB trap settings on your system:

•Set ccmPhoneFailedAlarmInterval (1.3.6.1.4.1.9.9.156.1.9.2) to a value in the range 30-3600 by using the SNMP Set operation; for example, use the net-snmp set utility to set this OID value from the linux command line using: snmpset -c <community string> -v2c <transmitter ipaddress> 1.3.6.1.4.1.9.9.156.1.9.2 .0 i <value>

You can also use any other SNMP management application for the SNMP Set operation.

•Set ccmPhoneStatusUpdateAlarmInterval (1.3.6.1.4.1.9.9.156.1.9.4) to a value in the range 30-3600 by using the SNMP Set operation; for example, use the net-snmp set utility to set this OID value from the linux command line using: snmpset -c <community string> -v2c <transmitter ipaddress> 1.3.6.1.4.1.9.9.156.1.9.4.0 i <value>

You can also use any other SNMP management application for the SNMP Set operation.

Configuring CISCO-UNITY-MIB Trap Parameters

Connection only: The Connection SNMP Agent does not enable trap notifications, though traps can be triggered by Cisco Unity Connection alarms. You can view Cisco Unity Connection alarm definitions in Cisco Unity Connection Serviceability, on the Alarm > Definitions screen.

You can configure trap parameters by using the CISCO-SYSLOG-MIB. See the "Configuring CISCO-SYSLOG-MIB Trap Parameters" section.

Where to Find More Information

Related Topics

•Understanding Services, page 9-1

•Configuring Services, page 11-1

•Configuring SNMP Trap/Inform Parameters

•Configuring SNMP V1/V2c, page 16-1

•Configuring SNMP V3, page 17-1

•Configuring SNMP System Group, page 18-1

Related Documentation

Command Line Interface Reference Guide for Cisco Unified Solutions