Feedback
Contents
- Cisco Unified CM SNMP
- Simple Network Management Protocol
- Simple Network Management Protocol support
- SNMP basics
- SNMP configuration requirements
- SNMP version 1 support
- SNMP version 2c support
- SNMP version 3 support
- SNMP services
- SNMP community strings and users
- SNMP traps and informs
- SNMP Management Information Base (MIB)
- SNMP trace configuration
- Set up SNMP
- SNMP V1 and V2c
- Find community string
- Set up community string
- Community string configuration settings
- Delete community string
- SNMP notification destination
- Find notification destination
- Set up notification destination
- Notification destination configuration settings
- Delete notification destination
- SNMP V3
- Find SNMP user
- Set up SNMP user
- SNMP user configuration settings
- Delete SNMP user
- SNMP notification destination
- Find notification destination
- Set up notification destination
- Notification destination configuration settings
- Delete notification destination
- SNMP system group
- Set up MIB2 system group
- MIB2 system group configuration settings
- SNMP trap settings
- CISCO-SYSLOG-MIB trap parameters
- CISCO-CCM-MIB trap parameters
- CISCO-UNITY-MIB trap parameters
Cisco Unified CM SNMP
Simple Network Management Protocol
Simple Network Management Protocol support
SNMP, an application layer protocol, facilitates the exchange of management information among network devices, such as nodes, routers, and so on. As part of the TCP/IP protocol suite, SNMP enables administrators to remotely manage network performance, find and solve network problems, and plan for network growth.
http://www.cisco.com/pcgi-bin/ctdp/Search.pl
For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to the following URL:
http://www.globalscape.com/gsftps/cisco.aspx
Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:
- Open SSH (refer to http://sshwindows.sourceforge.net/)
- Cygwin (refer to http://www.cygwin.com/)
Titan (refer to http://www.titanftp.com/)
For issues with third-party products that have not been certified through the CTDP process, contact the third-party vendor for support.
You use Cisco Unified Serviceability to configure SNMP-associated settings, such as community strings, users, and notification destinations for V1, V2c, and V3. The settings that you configure in Cisco Unified Serviceability apply to the local node; however, if your Cisco Unified Communications Manager or Cisco Unity Connection configuration supports clusters, you can apply settings to all servers in the cluster with the "Apply to All Nodes" option in the SNMP configuration windows.
SNMP supports IPv4, although the CISCO-CCM-MIB includes columns and storage for IPv6 addresses, preferences, and so on.
- SNMP basics
- SNMP configuration requirements
- SNMP version 1 support
- SNMP version 2c support
- SNMP version 3 support
- SNMP services
- SNMP community strings and users
- SNMP traps and informs
- SNMP Management Information Base (MIB)
SNMP basics
An SNMP-managed network comprises three key components: managed devices, agents, and network management systems.
- Managed device - A network node that contains an SNMP agent and resides on a managed network. Managed devices collect and store management information and make it available by using SNMP. Unified CM BE only: The server where Cisco Unified Communications Manager is installed acts as the managed device. Unified CM only: In a configuration that supports clusters, the first node in the cluster acts as the managed device.
- Agent - 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. Cisco Unified Communications Manager and Cisco Unity Connection use 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. Likewise, the master agent contains a few MIB variables that relate to MIB-II. 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 Cisco Unified Communications Manager subagent interacts with the local Cisco Unified Communications Manager only. The Cisco Unified Communications Manager subagents send trap and information messages to the SNMP Master Agent, and the SNMP Master Agent communicates with the SNMP trap receiver (notification destination).
- 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. An NMS executes applications that monitor and control managed devices. Cisco Unified Communications Manager works with the following NMS:
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. Table 1 provides the required SNMP configuration settings.
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.
Instead of using community strings like SNMP v1 and v2, SNMP v3 uses SNMP users, as described in the SNMP community strings and users.
In Cisco Unified Serviceability, you configure SNMP v3 support in the V3 Configuration window.
SNMP services
For a description of each service, see the Services.
Caution
Stopping any SNMP service may result in loss of data because the network management system no longer monitors the Cisco Unified Communications Manager or Cisco Unity Connection network. 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.
Note
Cisco Unified Communications Manager supports SNMP traps in Cisco Unified Communications Manager and Cisco Unified Communications Manager Business Edition 5000 systems.
For all notifications, the system sends traps immediately if the corresponding trap flags are enabled. In the case of the syslog agent, the CallManager alarms and system level log messages get sent to syslog daemon for logging. Also, some standard third-party applications send the log messages to syslog daemon for logging. These log messages get logged locally in the syslog files and also get converted into SNMP traps/notifications.
The following list contains Cisco Unified Communications Manager SNMP trap/inform messages that are sent to a configured trap destination:
- Cisco Unified Communications Manager failed
- Phone failed
- Phones status update
- Gateway failed
- Media resource list exhausted
- Route list exhausted
- Gateway layer 2 change
- Quality report
- Malicious call
- Syslog message generated
Tip
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 or in Cisco Unified Serviceability.
The following table comprises information about Cisco Unified Communications Manager trap/inform parameters that you configure on the Network Management System (NMS). You can configure the values in the table by issuing the appropriate commands on the NMS, as described in the SNMP product documentation that supports the NMS.
Note
All the parameters that are listed in the table are part of CISCO-CCM-MIB except for the last two parameters. The last two, clogNotificationsEnabled and clogMaxSeverity, comprise part of CISCO-SYSLOG-MIB.
Table 3 Cisco Unified Communications Manager Trap/Inform Configuration Parameters
Note Although you can configure a Cisco ATA 186 device as a phone in Cisco Unified Communications Manager Administration, when Cisco Unified Communications Manager sends SNMP traps for the Cisco ATA device, it sends a gateway type trap; for example, ccmGatewayFailed.
Set the ccmPhoneStatusUpdateAlarmInterval to a value between 30 and 3600. See CISCO-CCM-MIB trap parameters.
Set the ccmPhoneFailedAlarmInterval to a value between 30 and 3600. See CISCO-CCM-MIB trap parameters.
Note This trap gets generated only if the Cisco Extended Functions service is activated and running on the server; or, in the case of a cluster configuration (Cisco Unified Communications Manager only), on the local Cisco Unified Communications Manager server.
To enable trap generation, set clogNotificationsEnable to True. See CISCO-SYSLOG-MIB trap parameters.
When you set clogMaxSeverity to warning, a SNMP trap generates when Cisco Unified Communications Manager applications generate a syslog message with at least a warning severity level.CISCO-SYSLOG-MIB trap parameters.
SNMP Management Information Base (MIB)
SNMP allows access to Management Information Base (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 (variables).
Note
Cisco Unified Communications Manager supports the following MIBs except for CISCO-UNITY-MIB. Cisco Unified Communications Manager Business Edition 5000 supports all the following MIBs. Cisco Unity Connection supports the following MIBs except for CISCO-CCM-MIB.
The SNMP interface provides these Cisco Standard MIBs:
The Simple Network Management Protocol (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).
The SNMP interface also provides these Industry Standard MIBs:
For vendor-specific supported hardware MIBS, refer to the Vendor-Specific MIBs section.
Cisco Unified Communications Manager SNMP Interface supports the following MIBs.
CISCO-CDP-MIB
Use the Cisco Unified Communications Manager CDP subagent 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 network.
The CDP subagent implements the CDP-MIB. The CDP-MIB contains the following objects:
SYSAPPL-MIB
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.
System Application Agent supports the following object groups of SYSAPPL-MIB:
MIB-II
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:
HOST-RESOURCES MIB
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:
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:
The Cisco Syslog Agent supports trap functionality with the following MIB objects:
CISCO-CCM-MIB/CISCO-CCM-CAPABILITY MIB
The CISCO-CCM-MIB contains both dynamic (real-time) and configured (static) information about the Cisco Unified Communications Manager and its associated devices, such as phones, gateways, and so on, that are visible on this Cisco Unified Communications Manager node. Simple Network Management Protocol (SNMP) tables contain information such as IP address, registration status, and model type.
SNMP supports IPv4, although the CISCO-CCM-MIB includes columns and storage for IPv6 addresses, preferences, and so on.
Note
Cisco Unified Communications Manager supports this MIB in Cisco Unified Communications Manager and Cisco Unified Communications Manager Business Edition 5000 systems. Cisco Unity Connection does not support this MIB.
To view the support lists for the CISCO-CCM-MIB and MIB definitions, go to the following link:
ftp://ftp.cisco.com/pub/mibs/supportlists/callmanager/callmanager-supportlist.html
To view MIB dependencies and MIB contents, including obsolete objects, across Cisco Unified Communications Manager releases, go to the following link: http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=CISCO-CCM-CAPABILITY
Dynamic tables get populated only if the Cisco CallManager service is up and running (or the local Cisco CallManager service in the case of a Cisco Unified Communications Manager cluster configuration); static tables get populated when the Cisco CallManager SNMP Service is running.
Table 4 Cisco-CCM-MIB Dynamic Tables This table stores the version and installation ID for the local Cisco Unified Communications Manager. The table also stores information about all the Cisco Unified Communications Manager in a cluster that the local Cisco Unified Communications Manager knows about but shows "unknown" for the version detail. If the local Cisco Unified Communications Manager is down, the table remains empty, except for the version and installation ID values.
ccmPhoneFailed, ccmPhoneStatusUpdate, ccmPhoneExtn, ccmPhone, ccmPhoneExtension
For the Cisco Unified IP Phone, the number of registered phones in ccmPhoneTable should match Cisco Unified Communications Manager/RegisteredHardware Phones perfmon counter. The ccmPhoneTable includes one entry for each registered, unregistered, or rejected Cisco Unified IP Phone. The ccmPhoneExtnTable uses a combined index, ccmPhoneIndex and ccmPhoneExtnIndex, for relating the entries in the ccmPhoneTable and ccmPhoneExtnTable.
The ccmCTIDeviceTable stores each CTI device as one device. Based on the registration status of the CTI Route Point or CTI Port, the ccmRegisteredCTIDevices, ccmUnregisteredCTIDevices, and ccmRejectedCTIDevices counters in the Cisco Unified Communications Manager MIB get updated.
The ccmH323DeviceTable contains the list of H323 devices for which Cisco Unified Communications Manager contains information (or the local Cisco Unified Communications Manager in the case of a cluster configuration). For H.323 phones or H.323 gateways, the ccmH.323DeviceTable contains one entry for each H.323 device. (The H.323 phone and gateway do not register with Cisco Unified Communications Manager. Cisco Unified Communications Manager generates the H.323Started alarm when it is ready to handle calls for the indicated H.323 phone and gateway.) The system provides the gatekeeper information as part of the H323 trunk information.
For Cisco uOne, ActiveVoice, the ccmVoiceMailDeviceTable includes one entry for each voice-messaging device. Based on the registration status, the ccmRegisteredVoiceMailDevices, ccmUnregisteredVoiceMailDevices, and ccmRejectedVoiceMailDevices counters in the Cisco Unified Communications Manager MIB get updated.
The ccmRegisteredGateways, ccmUnregistered gateways, and ccmRejectedGateways keep track of the number of registered gateway devices or ports, number of unregistered gateway devices or ports, and number of rejected gateway devices or ports, respectively.
Cisco Unified Communications Manager generates alarms at the device or port level. The ccmGatewayTable, based on CallManager alarms, contains device- or port-level information. Each registered, unregistered, or rejected device or port has one entry in ccmGatewayTable. The VG200 with two FXS ports and one T1 port has three entries in ccmGatewayTable. The ccmActiveGateway and ccmInActiveGateway counters track number of active (registered) and lost contact with (unregistered or rejected) gateway devices or ports.
Based on the registration status, ccmRegisteredGateways, ccmUnregisteredGateways, and ccmRejectedGateways counters get updated.
The table contains a list of all media devices which have tried to register with the local CallManager at least once.
This tables contains the Cisco Unified CM groups in a Cisco Unified Communications Manager cluster.
This table maps all Cisco Unified CMs in a cluster to a Cisco Unified CM group. The table remains empty when the local Cisco Unified CM node is down
Table 5 CISCO-CCM-MIB Static Tables The table contains the list of product types that are supported with Cisco Unified Communications Manager (or cluster, in the case of a Cisco Unified Communications Manager cluster configuration), including phone types, gateway types, media device types, H323 device types, CTI device types, voice-messaging device types, and SIP device types.
ccmRegionTable contains the list of all geographically separated regions in a Cisco Communications Network (CCN) system. The ccmRegionPairTable contains the list of geographical region pairs for a Cisco Unified Communications Manager cluster. Geographical region pairs are defined by Source region and Destination region.
The table contains the list of all time zone groups in a Cisco Unified Communications Manager cluster.
The tables contains the list of all device pools in a Cisco Unified Communications Manager cluster. Device pools are defined by Region, Date/Time Group, and Cisco Unified CM Group.
Note
‘The "ccmAlarmConfigInfo" and "ccmQualityReportAlarmConfigInfo" groups in the CISCO-CCM-MIB define the configuration parameters that relate to the notifications that are described.
CISCO-UNITY-MIB
The CISCO-UNITY-MIB uses the Connection SNMP Agent to get information about Cisco Unity Connection.
To view the CISCO-UNITY-MIB definitions, go to the following link and click SNMP V2 MIBs:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Note
Cisco Unity Connection supports this MIB. Cisco Unified Communications Manager does not support this MIB.
The Connection SNMP Agent supports the following objects.
Table 6 CISCO-UNITY-MIB Objects This table contains general information about the Cisco Unity Connection servers such as host name and version number.
This table contains general information about the Cisco Unity Connection voice messaging ports.
This group contains information about capacity and utilization of the Cisco Unity Connection voice messaging ports.
Vendor-Specific MIBs
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 tables:
SNMP trace configuration
For Cisco Unified Communications Manager, you can configure trace for the Cisco CallManager SNMP agent in the Trace Configuration window in Cisco Unified Serviceability by choosing the Cisco CallManager SNMP Service in the Performance and Monitoring Services service group. 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.
For Cisco Unity Connection, you can configure trace for the Connection SNMP agent in the Trace Configuration window in Cisco Unity Connection Serviceability by choosing the Connection SNMP Agent component.
Set up SNMP
Procedure
Step 1 Install and configure the SNMP NMS. Step 2 In the Control Center - Network Services window, verify that the system started the SNMP services. Step 3 Unified CM and Unified CM BE only: In the Service Activation window, activate the Cisco CallManager SNMP service. Connection only: The Connection SNMP Agent service automatically activates. Step 4 If you are using SNMP V1/V2c, configure the community string. Step 5 If you are using SNMP V3, configure the SNMP user. Step 6 Configure the notification destination for traps or informs. Step 7 Configure the system contact and location for the MIB2 system group. Step 8 Configure trap settings for CISCO-SYSLOG-MIB. Step 9 Unified CM and Unified BE only: Configure trap settings for CISCO-CCM-MIB. Step 10 Restart the Master Agent service. Step 11 On the NMS, configure the Cisco Unified Communications Manager trap parameters.
Related Tasks
SNMP V1 and V2c
This section describes how to configure SNMP versions 1 and 2c, so the network management system can monitor Cisco Unified Communications Manager.
Tip
If you use SNMP version 3, see the SNMP V3.
- Find community string
- Set up community string
- Community string configuration settings
- Delete community string
- SNMP notification destination
- Find notification destination
- Set up notification destination
- Notification destination configuration settings
- Delete notification destination
Find community string
Procedure
Tip
The Add New button does not display in the SNMP Community String Configuration window until you click the Find button. If no community strings exist and you want to add a community string, click the Find button and wait for the window to refresh. The Add New button displays.
To find a community string, perform the following procedure:
Step 1 Choose . The Find/List window displays.
Step 2 From the Find Community Strings where Name drop-down list box, choose the specific search criteria that you want to use for the community string. Step 3 Enter the community string for which you want to search. Step 4 In the Server field, enter the hostname or IP address of the server where the community string exists. Step 5 Click Find. After you click the Find button, the Add New button displays. After the search results display, the Apply to All Nodes check box displays.
Step 6 Unified CM clusters only: If you want to apply the configuration from one of the options in the search results to all nodes in the cluster, check the check box next to the name of the option and check the Apply to All Nodes check box. Step 7 From the list of results, click the community string that you want to view. Step 8 To add or update a community string, see the Set up community string.
Set up community string
ProcedureBecause the SNMP agent provides security by using community strings, you must configure the community string to access any management information base (MIB) in a Cisco Unified Communications Manager system. Change the community string to limit access to the Cisco Unified Communications Manager system. To add, modify, and delete community strings, access the SNMP Community String configuration window.
Step 1 Perform the procedure in the Find community string. Step 2 Perform one of the following tasks:
Step 3 Enter the configuration settings, as described in Community string configuration settings.
Tip Before you save the configuration, you can click the Clear All button at any time to delete all information that you entered for all settings in the window.
Step 4 After you complete the configuration, click Add New to save a new community string or click Save to save changes to an existing community string. Step 5 A message indicates that changes will not take effect until you restart the SNMP master agent. To continue the configuration without restarting the SNMP master agent, click Cancel. To restart the SNMP master agent service, click OK.
Note Cisco recommends that you wait until you finish all the SNMP configuration before you restart the SNMP master agent service. For information on how to restart the service, see the Configuring services.
The system refreshes and displays the SNMP Community String Configuration window. The community string that you created displays in the window.
Community string configuration settings
The following table describes the community string configuration settings.
Table 8 Community String Configuration SettingsField Description This setting in the Community String configuration window displays as read only because you specified the server choice when you performed the procedure in the Find community string.
To change the server for the community string, perform the procedure in the Find community string.
Enter a name for the community string. The name can contain up to 32 characters and can contain any combination of alphanumeric characters, hyphens (-), and underscore characters (_).
Tip Choose community string names that will be hard for outsiders to figure out.
When you edit a community string, you cannot change the name of the community string.
To accept SNMP packets from any host, click this radio button.
To accept SNMP only from specified hosts, click this radio button.
Tip In the Host IP Address field, enter a host from which you want to accept packets and click Insert. Repeat this process for each host from which you want to accept packets. To delete a host, choose that host from the Host IP Addresses list box and click Remove.
- ReadOnly
The community string can only read the values of MIB objects.
- ReadWrite
The community string can read and write the values of MIB objects.
- ReadWriteNotify
The community string can read and write the values of MIB objects and send MIB object values for a trap and inform messages.
- NotifyOnly
The community string can only send MIB object values for a trap and inform messages.
- ReadNotifyOnly
The community string can read values of MIB objects and also send the values for trap and inform messages.
- None
The community string cannot read, write, or send trap information.
Tip To change the trap configuration parameters, you need to configure a community string with NotifyOnly, ReadNotifyOnly, or ReadWriteNotify privileges.
To apply the community string to all nodes in the cluster, check this check box.
Delete community string
Procedure
Step 1 Locate the community string, as described in the Find community string. Step 2 From the list of matching records, check the check box next to the community string that you want to delete. Step 3 Click Delete Selected. Step 4 A message indicates that the system will delete notification entries that relate to this community string. To continue the deletion, click OK. Step 5 A message indicates that changes will not take effect until you restart the SNMP master agent. To continue the configuration without restarting the SNMP master agent, click Cancel. To restart the SNMP master agent service, click OK.
Tip Cisco recommends that you wait until you finish all the SNMP configuration before you restart the SNMP master agent service. For information on how to restart the service, see the Set up status of services.
After the window refreshes, the string that you deleted no longer displays in the results.
SNMP notification destination
Find notification destination
Procedure
Tip
The Add New button does not display in the SNMP Notification Destination Configuration window until you click the Find button. If no notification destinations exist and you want to add a notification destination, click the Find button and wait for the window to refresh. The Add New button displays.
To find a notification destination for V1/V2c, perform the following procedure:
Step 1 Choose . The Find/List window displays.
Step 2 From the Find Notification where Destination IP drop-down list box, choose the specific search criteria that you want to use to find the notification destination. Step 3 Enter the notification destination for which you want to search. Step 4 In the Server field, enter the hostname or IP address of the server that supports the notification destination. Step 5 Click Find. After you click the Find button, the Add New button displays. After the search results display, the Apply to All Nodes check box displays.
Step 6 Unified CM clusters only: If you want to apply the configuration from one of the options in the search results to all nodes in the cluster, check the check box next to the name of the option and check the Apply to All Nodes check box. Step 7 To view the configuration for one of the items in the search results, click the item. Step 8 To add or update a notification string, see the Set up notification destination.
Set up notification destination
ProcedureTo configure the notification destination (trap/inform receiver) for V1/V2c, perform the following procedure.
Step 1 Perform the procedure in the Find notification destination. Step 2 Perform one of the following tasks:
Step 3 Enter the configuration settings, as described in Notification destination configuration settings.
Tip Before you save the configuration, you can click the Clear button at any time to delete all information that you entered for all settings in the window.
Step 4 To save a notification destination, click Insert, or click Save to save changes to an existing notification destination. Step 5 A message indicates that changes will not take effect until you restart the SNMP master agent. To continue the configuration without restarting the SNMP master agent, click Cancel. To restart the SNMP master agent, click OK. For information on how to restart the service, see the Configuring services.
Note Cisco recommends that you wait until you finish the SNMP configuration before you restart the SNMP master agent service.
Notification destination configuration settings
The following table describes the notification destination configuration settings for V1/V2c.
Table 9 Notification Destination Configuration Settings for V1/V2Field Description This setting displays as read only because you specified the server when you performed the procedure in the Find notification destination.
To change the server for the notification destination, perform the procedure in the Find community string.
From the drop-down list box, choose the Host IP address of the trap destination or choose Add New. If you choose Add New, enter the IP address of the trap destination.
For existing notification destinations, you cannot modify the host IP address configuration.
In the field, enter the notification-receiving port number on the destination server that receives SNMP packets.
From the SNMP Version Information pane, click the appropriate SNMP version radio button, either V1 or V2c, which depends on the version of SNMP that you are using.
From the drop-down list box, choose the community string name to be used in the notification messages that this host generates.
Only community strings with minimum notify privileges (ReadWriteNotify or Notify Only) display. If you have not configured a community string with these privileges, no options appear in the drop-down list box. If necessary, click the Create New uiCommunity String button to create a community string, as described in the Set up community string.
From the drop-down list box, choose the appropriate notification type.
To apply the notification destination configuration to all nodes in the cluster, check this check box.
Delete notification destination
Procedure
Step 1 Locate the notification destination, as described in the Find notification destination. Step 2 From the list of matching records, check the check box next to the notification destination that you want to delete. Step 3 Click Delete Selected. Step 4 A message asks whether you want to delete the notification entries. To continue the deletion, click OK. Step 5 A message indicates that changes will not take effect until you restart the SNMP master agent. To continue the configuration without restarting the SNMP master agent, click Cancel. To restart the SNMP master agent service, click OK.
Tip Cisco recommends that you wait until you finish all the SNMP configuration before you restart the SNMP master agent service.
For information on how to restart the service, see the Configuring services.
After the window refreshes, the notification destination that you deleted no longer displays in the results.
SNMP V3
This section describes how to configure SNMP v3, so the network management system can monitor Cisco Unified Communications Manager or Cisco Unity Connection.
Tip
If you use SNMP v1 or v2c, see the SNMP V1 and V2c.
- Find SNMP user
- Set up SNMP user
- SNMP user configuration settings
- Delete SNMP user
- SNMP notification destination
- Find notification destination
- Set up notification destination
- Notification destination configuration settings
- Delete notification destination
Find SNMP user
Procedure
Tip
The Add New button does not display in the SNMP User Configuration window until you click the Find button. If no users exist and you want to add a user, click the Find button and wait for the window to refresh. The Add New button displays.
Step 1 Choose . The SNMP User Configuration window displays.
Step 2 From the Find User where Name list box, choose the specific search criteria that you want to use to find the user; for example, begins with. Step 3 Enter the user name for which you want to search. Step 4 From the Server drop-down list box, choose the hostname or IP address of the server where you access the user. Step 5 Click Find. After you click the Find button, the Add New button displays. After the search results display, the Apply to All Nodes check box displays.
Step 6 Unified CM clusters only: If you want to apply the configuration from one of the options in the search results to all nodes in the cluster, check the check box next to the name of the option and check the Apply to All Nodes check box. Step 7 From the list of results, click the user that you want to view. Step 8 To add or update a user, see the Set up SNMP user.
Set up SNMP user
Procedure
Step 1 Find the notification destination. Step 2 Perform one of the following tasks:
Step 3 Enter the configuration settings, as described in SNMP user configuration settings.
Tip Before you save the configuration, you can click the Clear All button at any time to delete all information that you entered for all settings in the window.
Step 4 To add a new user, click Insert, or click Save to save changes to an existing user. Step 5 A message indicates that changes will not take effect until you restart the SNMP master agent. To continue the configuration without restarting the SNMP master agent, click Cancel. To restart the SNMP master agent service, click OK.
Tip Cisco recommends that you wait until you finish the SNMP configuration before you restart the SNMP master agent service.
Note To access this server that has the user that you configure, make sure that you configure this user on the NMS with the appropriate authentication and privacy settings.
SNMP user configuration settings
The following table describes the SNMP user configuration settings for V3.
Table 10 SNMP User Configuration Settings for V3Field Description This setting displays as read only because you specified the server when you performed the procedure in the Find notification destination.
To change the server where you want to provide access, perform the procedure in the Find SNMP user.
In the field, enter the name of the user for which you want to provide access. The name can contain up to 32 characters and can contain any combination of alphanumeric characters, hyphens (-), and underscore characters (_).
Tip Enter users that you have already configured for the network management system (NMS).
For existing SNMP users, this setting displays as read only.
To require authentication, check the check box, enter the password in the Password and Reenter Password fields, and choose the appropriate protocol. The password must contain at least 8 characters.
If you checked the Authentication Required check box, you can specify privacy information. To require privacy, check the check box, enter the password in the Password and Reenter Password fields, and check the protocol check box. The password must contain at least 8 characters.
Tip After you check the Privacy Required check box, the DES (Data Encryption Standard) check box automatically appears checked. The DES protocol prevents packets from being disclosed.
To accept SNMP packets from any host, click the radio button.
To accept SNMP packets from specific hosts, click the radio button. In the Host IP Address field, enter a host from which you want to accept SNMP packets and click Insert. Repeat this process for each host from which you want to accept SNMP packets. To delete a host, choose that host from the Host IP Addresses pane and click Remove.
- ReadOnly
The user can only read the values of MIB objects.
- ReadWrite
The user can read and write the values of MIB objects.
- ReadWriteNotify
The user can read and write the values of MIB objects and send MIB object values for a trap and inform messages.
- NotifyOnly
The user can only send MIB object values for trap and inform messages.
- ReadNotifyOnly
The user can read values of MIB objects and also send the values for trap and inform messages.
- None
The user cannot read, write, or send trap information.
Tip To change the trap configuration parameters, you need to configure a user with NotifyOnly, ReadNotifyOnly, or ReadWriteNotify privileges.
To apply the user configuration to all nodes in the cluster, check this check box.
Delete SNMP user
Procedure
Step 1 Locate the SNMP user, as described in the Find SNMP user. Step 2 From the list of matching records, check the check box next to the user that you want to delete. Step 3 Click Delete Selected. Step 4 A message indicates that the system will delete notification entries that relate to this user. To continue the deletion, click OK. Step 5 A message indicates that changes will not take effect until you restart the SNMP master agent. To continue the configuration without restarting the SNMP master agent, click Cancel. To restart the SNMP master agent service, click OK.
Tip Cisco recommends that you wait until you finish all the SNMP configuration before you restart the SNMP master agent service.
For information on how to restart the service, see the Configuring services.
After the window refreshes, the user that you deleted no longer displays in the results.
SNMP notification destination
Find notification destination
Procedure
Tip
The Add New button does not display in the SNMP Notification Destination Configuration window until you click the Find button. If no users exist and you want to add want a user, click the Find button and wait for the window to refresh. The Add New button displays.
To find a notification destination for V3, perform the following procedure:
Step 1 Choose . Step 2 From the Find Notification where Destination IP drop-down list box, choose the specific search criteria that you want to use to find the notification destination; for example, begins with. Step 3 Enter the IP address/hostname of notification destination for which you want to search. Step 4 In the Server field, choose the hostname or IP address of the server that supports the notification destination. Step 5 Click Find. After you click the Find button, the Add New button displays. After the search results display, the Apply to All Nodes check box displays.
Step 6 Unified CM clusters only: If you want to apply the configuration from one of the options in the search results to all nodes in the cluster, check the check box next to the name of the option and check the Apply to All Nodes check box. Step 7 From the list of results, click the notification destination that you want to view. Step 8 To add or update a notification destination, see the Set up notification destination.
Set up notification destination
Procedure
Step 1 Perform the procedure in the Find notification destination. Step 2 Perform one of the following tasks:
- To add a new SNMP notification destination, click the Add New button in the search results window and go to step 3.
- To modify an existing SNMP notification destination, locate the notification destination in the search results window; click the name of the SNMP notification destination that you want to edit and go to step 3.
- To delete an SNMP notification destination, see the Delete notification destination.
Step 3 Configure the settings, as described in Notification destination configuration settings.
Tip Before you save the configuration, you can click the Clear button at any time to delete all information that you entered for all settings in the window.
Step 4 To save a notification destination, click Insert, or click Save to save changes to an existing notification destination. Step 5 A message indicates that changes will not take effect until you restart the SNMP master agent. To continue the configuration without restarting the SNMP master agent, click Cancel. To restart the SNMP master agent service, click OK.
Tip Cisco recommends that you wait until you finish the SNMP configuration before you restart the SNMP master agent service.
For information on how to restart the service, see the Configuring services.
Notification destination configuration settings
The following table describes the notification destination configuration settings for V3.
Table 11 Notification Destination Configuration Settings for V3Field Description This setting displays as read only because you specified the server when you performed the procedure in the Find notification destination.
To change the server for the notification destination, perform the procedure in the Find notification destination.
From the drop-down list box, choose the Host IP address or choose Add New. If you chose Add New, enter the IP address for the host.
In the field, enter the notification-receiving port number on the destination server.
From the drop-down list box, choose Inform or Trap.
Tip Cisco recommends that you choose the Inform option. The Inform function retransmits the message until it is acknowledged, thus, making it more reliable than traps. This setting displays if you chose Inform from the Notification Type drop-down list box.
From the drop-down list box, choose the engine ID or choose Add New. If you chose Add New, enter the ID in the Remote SNMP Engine Id field, which requires a hexidecimal value.
From the pane, perform one of the following tasks to associate or disassociate the notification destination with the user.
- To create a new user, click the Create New User button and see the Set up SNMP user.
- To modify an existing user, click the radio button for the user and click Update Select ed User; then, see the Set up SNMP user.
- To delete a user, click the radio button for the user and click Delete Selected User.
The users that display vary depending on the security level that you configured for the notification destination.
To apply the notification destination configuration to all nodes in the cluster, check this check box.
Delete notification destination
Procedure
Step 1 Locate the SNMP notification destination, as described in the Find notification destination. Step 2 From the list of matching records, check the check box next to the notification destination that you want to delete. Step 3 Click Delete Selected. Step 4 A message asks you if you want to delete the notification destination. To continue the deletion, click OK. Step 5 A message indicates that changes will not take effect until you restart the SNMP master agent. To continue the configuration without restarting the SNMP master agent, click Cancel. To restart the SNMP master agent service, click OK.
Tip Cisco recommends that you wait until you finish all the SNMP configuration before you restart the SNMP master agent service.
For information on how to restart the service, see the Configuring services.
After the window refreshes, the notification destination that you deleted no longer displays in the search results window.
SNMP system group
Cisco Unified Serviceability provides the MIB2 System Group Configuration window where you can configure the system contact and system location objects for the MIB-II system group. For example, you could enter Administrator, 555-121-6633, for the system contact and San Jose, Bldg 23, 2nd floor, for the system location.
Set up MIB2 system group
ProcedurePerform the following procedure to configure a system contact and system location for the MIB-II system group.
Tip
This procedure supports SNMP v1, v2c, and v3 configuration.
Step 1 Choose . Step 2 Configure the settings, as described in MIB2 system group configuration settings. Step 3 Click Save. Step 4 A message indicates that changes will not take effect until you restart the SNMP master agent. To continue the configuration without restarting the SNMP master agent service, click Cancel. To restart the SNMP master agent service, click OK.
Note To clear the System Contact and System Location fields, click the Clear All button. To delete the system configuration, click the Clear All button and the Save button.
MIB2 system group configuration settings
The following table describes the MIB2 System Group configuration settings.
Table 12 MIB2 System Group Configuration SettingsFrom the drop-down list box, choose the server for which you want to configure contacts; then, click Go.
In the field, enter the location of the person that is identified as the system contact.
To apply the system configuration to all of the nodes in the cluster, check the check box.
SNMP trap settings
This section describes how to use CLI commands to set configurable trap settings. SNMP traps and informs provides the SNMP trap configuration parameters and recommended configuration for CISCO-SYSLOG-MIB, CISCO-CCM-MIB, and CISCO-UNITY-MIB.
CISCO-SYSLOG-MIB trap parameters
Use these guidelines to configure CISCO-SYSLOG-MIB trap settings on your system:
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.
CISCO-CCM-MIB trap parameters
Unified CM and Unified CM BE only: Use these guidelines to configure CISCO-CCM-MIB trap settings on your system:
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 screen.
You can configure trap parameters by using the CISCO-SYSLOG-MIB. See the CISCO-SYSLOG-MIB trap parameters.
