Simple Network Management Protocol (SNMP) is an industry-standard interface for exchanging management information between network devices. SNMP and its components provide you with information about your Cisco Unified CCX system. You can refer to this information to monitor and manage the status of the Cisco Unified CCX system, its subsystems, and its related installed components. You can also use this information to troubleshoot problems, if they arise.
You can set up SNMP traps to automatically notify you of high-severity messages and errors that are generated by the Cisco Unified CCX system.
A network management system (NMS) uses SNMP to exchange management information between devices on a network. An SNMP-managed network is made up of the following main components:
Managed devices—Network nodes, each containing an SNMP agent. Managed devices collect and store information and make this information available using SNMP.
Agents—A network-managed software module that resides on a managed device. An agent contains local knowledge of management information and translates it into a form that is compatible with SNMP.
Network Management System (NMS)—A SNMP management application (together with the PC on which it runs) that provides the bulk of the processing and memory resources that are required for network management.
Cisco Unified CCX uses a master agent and subagent components to support SNMP. The master agent acts as the agent protocol engine and performs the authentication, authorization, access control, and privacy functions that relate to SNMP requests. The master agent also connects and disconnects subagents after the subagent completes necessary tasks. The SNMP master agent listens on port 161 and forwards SNMP packets for Vendor MIBs.
The subagents send trap and the requested information messages to the SNMP Master Agent, and the SNMP Master Agent communicates with the Network Management Stations.
SNMP configuration requirements
The system provides no default SNMP configuration. You must configure SNMP settings after installation to access MIB information. Cisco supports SNMP V1, V2c, and V3 versions.
SNMP agent provides security with community names and authentication traps. You must configure a community name to access MIB information.
The table below provides the required SNMP configuration settings.
Table 1 SNMP configuration requirements
Cisco Unified Serviceability Page
V1/V2c Community String
SNMP > V1/V2c > Community String
V3 Community String
SNMP > V3 > User
System Contact and Location for MIB2
SNMP > SystemGroup > MIB2 System Group
Trap Destinations (V1/V2c)
SNMP > V1/V2c > Notification Destination
Trap Destinations (V3)
SNMP > V3 > Notification Destination
SNMP version 1 support
SNMP version 1 (SNMPv1), the initial implementation of SNMP that functions within the specifications of the Structure of Management Information (SMI), operates over protocols, such as User Datagram Protocol (UDP) and Internet Protocol (IP).
The SNMPv1 SMI defines highly structured tables (MIBs) that are used to group the instances of a tabular object (that is, an object that contains multiple variables). Tables contain zero or more rows, which are indexed, so SNMP can retrieve or alter an entire row with a supported command.
With SNMPv1, the NMS issues a request, and managed devices return responses. Agents use the Trap operation to asynchronously inform the NMS of a significant event.
In Cisco Unified Serviceability, you configure SNMP v1 support in the V1/V2c Configuration window.
SNMP version 2c support
As with SNMPv1, SNMPv2c functions within the specifications of the Structure of Management Information (SMI). MIB modules contain definitions of interrelated managed objects. The operations that are used in SNMPv1 are similar to those that are used in SNMPv2. The SNMPv2 Trap operation, for example, serves the same function as that used in SNMPv1, but it uses a different message format and replaces the SNMPv1 Trap.
The Inform operation in SNMPv2c allows one NMS to send trap information to another NMS and to then receive a response from the NMS.
In Cisco Unified Serviceability, you configure SNMP v2c support in the V1/V2c Configuration window.
SNMP version 3 support
SNMP version 3 provides security features such as authentication (verifying that the request comes from a genuine source), privacy (encryption of data), authorization (verifying that the user allows the requested operation), and access control (verifying that the user has access to the objects requested.) To prevent SNMP packets from being exposed on the network, you can configure encryption with SNMPv3.
In Cisco Unified Serviceability, you configure SNMP v3 support in the V3 Configuration window.
The services in the table below support SNMP operations. For a description of each service, see the Understanding Services.
SNMP Master Agent serves as the primary service for the MIB interface. All the SNMP services should be up and running after installation.
Table 2 SNMP Services
Cisco Unified CCX Voice Subagent
Cisco Unified CCX Serviceability > Tools > Control Center - Network Services. Choose a server; then, choose System Services category.
SNMP Master Agent
Cisco Unified Serviceability > Tools > Control Center - Network Services. Choose a server; then, choose Platform Services category.
Cisco CDP Agent
System Application Agent
Host Resources Agent
Cisco Syslog Agent
Native Agent Adaptor
Stopping any SNMP service may result in loss of data because the network management system no longer monitors the Cisco Unified CCX. Do not stop the services unless your technical support team tells you to do so.
SNMP community strings and users
Although SNMP community strings provide no security, they authenticate access to MIB objects and function as embedded passwords. You configure SNMP community strings for SNMP V1 and V2c only.
SNMP V3 does not use community strings. Instead, version 3 uses SNMP users. These users serve the same purpose as community strings, but users provide security because you can configure encryption or authentication for them.
In Cisco Unified Serviceability, no default community string or user exists.
SNMP traps and informs
An SNMP agent sends notifications to NMS in the form of traps or informs to identify important system events. Traps do not receive acknowledgments from the destination whereas informs do receive acknowledgments. You configure the notification destinations by using the SNMP Notification Destination Configuration windows in Cisco Unified Serviceability.
The Unified CCX Voice MIB (CISCO-VOICE-APPS-MIB) does not support INFORM notifications.
For all notifications, the system sends traps immediately if the corresponding trap flags are enabled. Before you configure notification destination, verify that the required SNMP services are activated and running. Also, make sure that you configured the privileges for the community string/user correctly.
You configure the SNMP trap destination by choosing SNMP > V1/V2 > Notification Destination or SNMP > V3 > Notification Destination in Cisco Unified Serviceability.
The table below comprises information about Cisco Unified CCX trap/inform parameters that you configure on the Network Management System (NMS). You can configure the values in the table below by issuing the appropriate commands on the NMS, as described in the SNMP product documentation that supports the NMS. The two parameters listed in the following table are part of CISCO-SYSLOG-MIB.
To enable trap generation, set clogNotificationsEnable to True.
When you set clogMaxSeverity to warning, a SNMP trap generates when Cisco Unified CCX applications generate a syslog message with at least a warning severity level.
SNMP Management Information Base (MIB)
A Management Information Base (MIB) designates a collection of information that is organized hierarchically. You access MIBs with SNMP. MIBs are made up of managed objects, which are identified by object identifiers. Managed objects are made up of one or more object instances, which are essentially variables. MIBs provide status monitoring, provisioning and notification.
The SNMP interface provides these Cisco Standard MIBs:
The SNMP interface also provides these Industry Standard MIBs:
Cisco Unified CCX SNMP Interface supports the following MIBs.
The CISCO-VOICE-APPS-MIB provides information associated with the installed workflow applications provisioned on the Unified CCX Server. It also provides information on the supported SNMP Traps on Unified CCX.
In Unified CCX 9.0(1), while exposing the Unified CCX workflow information through CISCO-VOICE-APPS-MIB, only one trigger per application row will be returned when doing a walk on the workflow table (cvaWorkflowInstallTable object). If there are multiple triggers associated with a Workflow application, these will be shown as separate entries (rows).
Unified CCX Voice Subagent
Cisco Unified CCX Voice Subagent service implements the CISCO-VOICE-APPS-MIB.
Cisco Unified CCX Voice Subagent Service communicates with the SNMP Master Agent through Cisco Unified CCX SNMP Java Adaptor. The Cisco Unified CCX SNMP Java Adaptor service should be up and running for the Unified CCX Voice Subagent to work properly.
You can manage Cisco Unified CCX SNMP Java Adaptor service from Cisco Unified CCX Serviceability web interface.
Unified CCX SNMP Traps
Subsystems which are the functional blocks for of Unified CCX send out alarms which are routed to the Syslog or as SNMP Traps. SNMP Traps are generated when any Unified CCX Subsystem/module or processes starts or stops, a runtime failure occurs for a module. These can be tracked for each major component to track the health of the Unified CCX system.
Syslog messages can also be sent as SNMP traps using the CISCO-SYSLOG-MIB. Refer to the section on CISCO-SYSLOG-MIB for details. They can be correlated to the failure of important features of Unified CCX.
The following Traps are supported as part of the CISCO-VOICE-APPS-MIB:
A cvaModuleStart notification signifies that an application module or subsystem has successfully started and transitioned into in-service state.
A cvaModuleStop notification signifies that an application module or subsystem has stopped. If failure cause is known then it will be specified as part of the Trap message.
cvaModuleRunTimeFailure notification signifies that a run time failure has occurred. If failure cause is known then it will be specified as part of the Trap message.
A cvaProcessStart notification signifies that a process has just started.
A cvaProcessStop notification signifies that a process has just stopped.
The ModuleStart and ModuleStop traps are generated when the key Unified CCX services including Cisco Unified CCX Engine, Cisco Unified CCX Cluster View Daemon and Cisco Unified CCX Administration and their modules/subsystems are started and stopped respectively.
The ProcessStart and ProcessStop traps are generated when the key Unified CCX services including Cisco Unified CCX Engine, Cisco Unified CCX Cluster View Daemon and Cisco Unified CCX Administration are started and stopped.
SNMP Traps are not generated for events when the Unified CCX services and/or their subsystems goes Out of Service or comes In Service. Rather these events are sent as Remote Syslog messages and can be viewed through any third-party Syslog Viewers. You can refer to the list of CCX services and their subsystems/modules from the Cisco Unified CCX Serviceability under Tools - Control Center Network Services.
The CISCO-CDP-MIB provides information about device identifications, CDP running status, CDP transmitting frequency, and the time for the receiving device to hold CDP messages (time to live). This MIB stores information in a table called cdpGlobalInfo.
Use the System Application Agent to get information from the SYSAPPL-MIB, such as installed applications, application components, and processes that are running on the system.
Some of the important tables exposing these information are explained below:
SysAppl MIB Table
The table listing the software application packages installed on a host computer.
Provides the list of some of the important Unified CCX components listed in the table.
The table details the individual application package elements (files & executables) which comprise the applications defined in the sysApplInstallPkg table.
The table describes the applications which are executing on the host. Each time an application is invoked, an entry is created in this table. When an application ends the entry is removed from this table and a corresponding entry is created in the SysApplPastRunTable.
The SNMP managers can monitor the current state of the running application instance by querying the field sysApplRunCurrentState (OID: 126.96.36.199.188.8.131.52.184.108.40.206)
The table describes the processes which are currently executing on the host system. Each entry represents a running process and is associated with the invoked application of which that process is a part, if possible.
Unlike previous releases of Unified CCX, the SysAppl MIB implementation in Unified CCX 9.0(1) does not distinguish between Unified CCX activated services and deactivated services. It shows all the installed services in Unified CCX.
In Unified CCX 9.0(1), the SysAppl MIB will not provide the Unified CCX subsystem information and their status information. You can view the subsystem and their status information through Cisco Unified CCX Serviceability web interface.
The SYSAPPL-MIB allows you to use CiscoWorks or a third-party NMS browser to remotely access information about the Cisco Unified CCX components including:
Cisco Unified CCX Notification Service
Cisco Unified Intelligence Center Serviceability Service
Cisco Unified Intelligence Center Reporting Service
Cisco Unified CCX Engine
Cisco Desktop License and Resource Manager Service
Cisco Desktop Call/Chat Service
Cisco Desktop Enterprise Service
Cisco Desktop Sync Service
Cisco Desktop Browser and IP Phone Agent Service
Cisco Desktop Recording and Statistics Service
Cisco Desktop VoIP Monitor Service
Cisco Desktop Recording and Playback Service
Cisco Desktop LDAP Monitor Service
Cisco Desktop Agent E-Mail Service
Cisco Unified CCX Cluster View Daemon
Cisco Unified CCX Database
Cisco Unified CCX Voice Subagent
Cisco Unified CCX SNMP Java Adapter
Cisco Unified CCX DB Perfmon Counter Service
Cisco Unified CCX Perfmon Counter Service
Use MIB2 agent to get information from MIB-II. The MIB2 agent provides access to variables that are defined in RFC 1213, such as interfaces, IP, and so on, and supports the following groups of objects:
Use Host Resources Agent to get values from HOST-RESOURCES-MIB. The Host Resources Agent provides SNMP access to host information, such as storage resources, process tables, device information, and installed software base. The Host Resources Agent supports the following groups of objects:
Syslog tracks and logs all system messages, from informational through critical. With this MIB, network management applications can receive syslog messages as SNMP traps:
The Cisco Syslog Agent supports trap functionality with the following MIB objects:
The following MIBs exist on various Cisco MCS, depending on vendor and model number. To query these MIBS, you can use the standard MIB browsers that the hardware vendors develop; for example, HP Systems Insight Manager (SIM) and IBM Director Server+Console. For information on using the MIB browsers, refer to the documentation that the hardware vendor provides.
To review the vendor-specific MIB information, see the following table:
Table 4 IBM MIBs
Supported for browsing only
Provides temperature, voltage, and fan status
Provides hardware component asset data
Provides temperature, voltage, and fan details
Provides Network Interface Card (NIC) status
Provides physical memory details
Provides power supply details
Provides CPU asset/status data
Supported for system traps
Provides temperature, voltage, fan, disk, NIC, memory, power supply, and CPU details
A default setting exists for all the agents. For Cisco CDP Agent and Cisco Syslog Agent, you use the CLI to change trace settings, as described in the Command Line Interface Reference Guide for Cisco Unified Solutions.
SNMP configuration checklist
Install and configure the SNMP NMS.
In the Control Center—Network Services window, verify that the system started the SNMP services.
The Cisco Unified CCX Voice Subagent automatically activates.
Perform any one of the tasks:
If you are using SNMP V1/V2c, configure the community string.
If you are using SNMP V3, configure the SNMP user.
Configure the notification destination for traps or informs.
Configure the system contact and location for the MIB2 system group.
Configure trap settings for CISCO-SYSLOG-MIB.
Restart the Master Agent service.
On the NMS, configure the Cisco Unified CCX trap parameters.