This document describes how to configure Management Information Base
(MIB) Trap Parameters for Cisco Unity Connection for Simple Network Management
Protocol (SNMP) monitoring.
There are no specific requirements for this document.
The information in this document is based on Cisco Unity Connection 7.x
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
Refer to the
Technical Tips Conventions for more information on document
SNMP allows access to a MIB, which is a collection of information that
is organized hierarchically. MIBs comprise managed objects, which are
identified by object identifiers. A MIB object, which contains specific
characteristics of a managed device, comprises one or more object instances
The SNMP interface provides these Cisco Standard MIBs:
CISCO-CDP-MIB - Use the Cisco Unified Communications Manager CDP
subagent in order to read the Cisco Discovery Protocol MIB (CISCO-CDP-MIB).
This MIB enables Cisco Unified Communications Manager and Cisco Unity
Connection to advertise themselves to other Cisco devices on the
CISCO-SYSLOG-MIB - Syslog tracks and logs all system messages, from
informational through critical. With this MIB, network management applications
can receive syslog messages as SNMP traps.
CISCO-UNITY-MIB - The CISCO-UNITY-MIB uses the Connection SNMP Agent
in order to get information about Cisco Unity Connection.
CISCO-CCM-MIB - The SNMP extension agent resides in the server and
exposes the CISCO-CCM-MIB, which provides detailed information about devices
that are known to the server. In the case of a cluster configuration, the SNMP
extension agent resides in each server in the cluster. The CISCO-CCM-MIB
provides device information such as device registration status, IP address,
description, and model type for the server (not the cluster, in a configuration
that supports clusters).
Note: Cisco Unity Connection supports all of these MIBs except for
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 Message Definitions
Use these guidelines in order to configure CISCO-SYSLOG-MIB trap
settings on your system:
Use the SNMP Set operation in order to set clogsNotificationEnabled
(184.108.40.206.220.127.116.11.18.104.22.168) to true. For example, use the
net-snmp set utility in order to set this OID to true from the Linux command
snmpset -c <community
string> -v2c <transmitter
ipaddress> 22.214.171.124.126.96.36.199.188.8.131.52.0 i 1
Note: You can also use any other SNMP management application for the SNMP
Use the SNMP Set operation in order to set clogMaxSeverity
(184.108.40.206.220.127.116.11.18.104.22.168) value. For example, use the net-snmp set utility in
order to set this OID value from the Linux command line:
snmpset -c public -v2c 1<transmitter
ipaddress> 22.214.171.124.126.96.36.199.188.8.131.52.0 i
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. The syslog agent ignores any
messages greater than the value that you specify. For example, in order to trap
all syslog messages, use a value of
This is an overview of the steps needed in order to configure
Install and configure the SNMP NMS.
In the Control Center - Network Services window, verify that the
system started the SNMP services.
The Unity Connection SNMP Agent service automatically
If you are using SNMP V1/V2c, configure the community
If you are using SNMP V3, configure the SNMP user.
Configure the notification destination for traps or
Configure the system contact and location for the MIB2 system
Configure trap settings for CISCO-SYSLOG-MIB.
Restart the Master Agent service.