The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
SNMP, an application layer protocol, facilitates the exchange of management information among network devices, such as nodes and routers. As part of the TCP/IP suite, SNMP enables administrators to remotely manage network performance, find and solve network problems, and plan for network growth.
Note |
Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information about which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to the following URL: 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:
For issues with third-party products that have not been certified through the CTDP process, contact the third-party vendor for support. |
You use the serviceability GUI to configure SNMP-associated settings, such as community strings, users, and notification destinations for V1, V2c, and V3. The SNMP settings that you configure apply to the local node; however, if your system 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.
An SNMP-managed network comprises three key components: managed devices, agents, and network management systems.
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).
The SNMP interface provides these Cisco Standard MIBs:
Observe the following limitations:
The SNM) 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:
Use the CDP subagent to read the Cisco Discovery Protocol MIB, CISCO-CDP-MIB. This MIB enables the SNMP managed device to advertise themself to other Cisco devices on the network.
The CDP subagent implements the CDP-MIB. The CDP-MIB contains the following objects:
Note |
The CISCO-CDP-MIB is dependent on the presence of the following MIBs: CISCO-SMI, CISCO-TC, CISCO-VTP-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:
Command |
Description |
||
Device-Related Queries | |||
sysApplInstallPkgVersion | Provides the version number that the software manufacturer assigned to the application package. | ||
sysApplElmPastRunUser | Provides the process owner's login name (for example, root). | ||
Memory, Storage, and CPU-Related Queries | |||
sysApplElmPastRunMemory | Provides the last-known total amount of real system memory measured in kilobytes that was allocated to this process before it terminated. | ||
sysApplElmtPastRunCPU | Provides the last known number of centi-seconds of the total system CPU resources consumed by this process.
|
||
sysApplInstallElmtCurSizeLow | Provides the current file size modulo 2^32 bytes. For example, for a file with a total size of 4,294,967,296 bytes this variable would have a value of 0; for a file with a total size of 4,294,967,295 bytes this variable would be 4,294,967,295. | ||
sysApplInstallElmtSizeLow | Provides the installed file size modulo 2^32 bytes. This is the size of the file on disk immediately after installation. For example, for a file with a total size of 4,294,967,296 bytes this variable would have a value of 0; for a file with a total size of 4,294,967,295 bytes this variable would be 4,294,967,295. | ||
sysApplElmRunMemory | Provides the total amount of real system memory, measured in kilobytes, that is currently allocated to this process. | ||
sysApplElmRunCPU | Provides the number of centi-seconds of the total system CPU resources consumed by this process.
|
||
Process-Related Queries | |||
sysApplElmtRunState | Provides the current state of the running process. The possible values are running(1), runnable(2) but waiting for a resource such as CPU, waiting(3) for an event, exiting(4), or other(5). | ||
sysApplElmtRunNumFiles | Provides the number of regular files currently opened by the process. Transport connections (sockets) should not be included in the calculation of this value, nor should operating-system-specific special file types. | ||
sysApplElmtRunTimeStarted | Provides the time the process was started. | ||
sysApplElmtRunMemory | Provides the total amount of real system memory, measured in kilobytes, that is currently allocated to this process. | ||
sysApplElmtPastRunInstallID | Provides the index into the installed element table. The value of this object is the same value as the sysApplInstallElmtIndex for the application element of which this entry represents a previously executed process. | ||
sysApplElmtPastRunUser | Provides the process owner's login name (for example, root). | ||
sysApplElmtPastRunTimeEnded | Provides the time the process ended. | ||
sysApplElmtRunUser | Provides the process owner's login name (for example, root). | ||
sysApplRunStarted | Provides the date and time that the application was started. | ||
sysApplElmtRunCPU | Provides the number of centi-seconds of the total system CPU resources consumed by this process.
|
||
Software Component-Related Queries | |||
sysApplInstallPkgProductName | Provides the name that the manufacturer assigned to the software application package. | ||
sysApplElmtRunParameters | Provides the starting parameters for the process. | ||
sysApplElmtRunName | Provides the full path and filename of the process. For example, '/opt/MYYpkg/bin/myyproc' would be returned for process 'myyproc' whose execution path is 'opt/MYYpkg/bin/myyproc'. | ||
sysApplInstallElmtName | Provides the name of this element, which is contained in the application. | ||
sysApplElmtRunUser | Provides the process owner's login name (for example, root). | ||
sysApplInstallElmtPath | Provides the full path to the directory where this element is installed. For example, the value would be '/opt/EMPuma/bin' for an element installed in the directory '/opt/EMPuma/bin'. Most application packages include information about the elements that are contained in the package. In addition, elements are typically installed in subdirectories under the package installation directory. In cases where the element path names are not included in the package information itself, the path can usually be determined by a simple search of the subdirectories. If the element is not installed in that location and no other information is available to the agent implementation, then the path is unknown and null is returned. | ||
sysApplMapInstallPkgIndex | Provides the value of this object and identifies the installed software package for the application of which this process is a part. Provided that the parent application of the process can be determined, the value of this object is the same value as the sysApplInstallPkgIndex for the entry in the sysApplInstallPkgTable that corresponds to the installed application of which this process is a part. If, however, the parent application cannot be determined (for example, the process is not part of a particular installed application), the value for this object is then '0', signifying that this process cannot be related back to an application, and in turn, an installed software package. | ||
sysApplElmtRunInstallID | Provides the index into the sysApplInstallElmtTable. The value of this object is the same value as the sysApplInstallElmtIndex for the application element of which this entry represents a running instance. If this process cannot be associated with an installed executable, the value should be '0'. | ||
sysApplRunCurrentState | Provides the current state of the running application instance. The possible values are running(1), runnable(2) but waiting for a resource such as CPU, waiting(3) for an event, exiting(4), or other(5). This value is based on an evaluation of the running elements of this application instance (see sysApplElmRunState) and their Roles as defined by sysApplInstallElmtRole. An agent implementation may detect that an application instance is in the process of exiting if one or more of its REQUIRED elements are no longer running. Most agent implementations will wait until a second internal poll is completed to give the system time to start REQUIRED elements before marking the application instance as exiting. | ||
sysApplInstallPkgDate | Provides the date and time this software application was installed on the host. | ||
sysApplInstallPkgVersion | Provides the version number that the software manufacturer assigned to the application package. | ||
sysApplInstallElmtType | Provides the type of element that is part of the installed application. | ||
Date/Time-Related Queries | |||
sysApplElmtRunCPU | The number of centi-seconds of the total system CPU resources consumed by this process
|
||
sysApplInstallPkgDate | Provides the date and time this software application is installed on the host. | ||
sysApplElmtPastRunTimeEnded | Provides the time the process ended. | ||
sysApplRunStarted | Provides the date and time that the application was started. |
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:
Command |
Description |
||
Device-Related Queries | |||
sysName | Provides an administratively assigned name for this managed node. By convention, this name is the fully qualified domain name of the node. If the name is unknown, the value is the zero-length string. | ||
sysDescr | Provides a textual description of the entity. This value should include the full name and version identification of the system hardware type, software operating-system, and networking software. | ||
SNMP Diagnostic Queries | |||
sysName | Provides an administratively assigned name for this managed node. By convention, this name is the fully-qualified domain name of the node. If the name is unknown, the value is the zero-length string. | ||
sysUpTime | Provides the time (in hundredths of a second) since the network management portion of the system was last reinitialized. | ||
snmpInTotalReqVars | Provides the total number of MIB objects that were retrieved successfully by the SNMP protocol entity as the result of receiving valid SNMP Get-Request and Get-Next PDUs. | ||
snmpOutPkts | Provides the total number of SNMP Messages that were passed from the SNMP entity to the transport service. | ||
sysServices | Provides a value that indicates the set of services that this entity potentially offers. The value is a sum. This sum initially takes the value zero, then, for each layer, L, in the range 1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which is a host offering application services would have a value of 4 (2^(3-1)). In contrast, a node which is a host offering application services would have a value of 72 (2^(4-1) + 2^(7-1)).
|
||
snmpEnableAuthenTraps | Indicates whether the SNMP entity is permitted to generate authenticationFailure traps. The value of this object overrides any configuration information; as such, it provides a means whereby all authenticationFailure traps may be disabled.
|
||
Syslog-Related Queries | |||
snmpEnabledAuthenTraps | Indicates whether the SNMP entity is permitted to generate authenticationFailure traps. The value of this object overrides any configuration information; as such, it provides a means whereby all authenticationFailure traps may be disabled.
|
||
Date/Time-Related Queries | |||
sysUpTime | Provides the time (in hundredths of a second) since the network management portion of the system was last reinitialized. |
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:
Command |
Description |
Device-Related Queries | |
hrFSMountPoint | Provides the path name of the root of this file system. |
hrDeviceDescr | Provides a textual description of this device, including the device manufacturer and revision, and optionally, the serial number. |
hrStorageDescr | Provides a description of the type and instance of the storage. |
Memory, Storage, and CPU Related Queries | |
hrMemorySize | Provides the amount of physical read-write main memory, typically RAM, that the host contains. |
hrStorageSize | Provides the size of the storage, in units of hrStorageAllocationUnits.This object is writable to allow remote configuration of the size of the storage area in those cases where such an operation makes sense and is possible on the underlying system. For example, you can modify the amount of main memory allocated to a buffer pool or the amount of disk space allocated to virtual memory. |
Process-Related Queries | |
hrSWRunName | Provides a textual description of this running piece of software, including the manufacturer, revision, and the name by which it is commonly known. If this software is installed locally, it must be the same string as used in the corresponding hrSWInstalledName. |
hrSystemProcesses | Provides the number of process contexts that are currently loaded or running on this system. |
hrSWRunIndex | Provides a unique value for each piece of software that is running on the host. Wherever possible, use the native, unique identification number of the system. |
Software Component-Related Queries | |
hrSWInstalledName | Provides a textual description of this installed piece of software, including the manufacturer, revision, the name by which it is commonly known, and optionally, the serial number. |
hrSWRunPath | Provides a description of the location of long-term storage (for example, a disk drive) from which this software was loaded. |
Date/Time-Related Queries | |
hrSystemDate | Provides the host local date and time of day. |
hrFSLastPartialBackupDate | Provides the last date at which a portion of this file system was copied to another storage device for backup. This information is useful for ensuring that backups are being performed regularly. If this information is not known, then this variable will have the value corresponding to January 1, year 0000, 00:00:00.0, which is encoded as (hex)'00 00 01 01 00 00 00 00'. |
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:
Note |
The CISCO-SYSLOG-MIB is dependent on the presence of the CISCO-SMI MIB. |
Command |
Description |
||
Syslog-Related Queries | |||
clogNotificationEnabled | Indicates whether clogMessageGenerated notifications will be sent when the device generates a syslog message. Disabling notifications does not prevent syslog messages from being added to the clogHistoryTable. | ||
clogMaxSeverity | Indicates which syslog severity levels will be processed. The agent will ignore any syslog message with a severity value greater than this value.
|
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 systems. IM and Presence Service and Cisco Unity Connection do 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.
Note |
‘The "ccmAlarmConfigInfo" and "ccmQualityReportAlarmConfigInfo" groups in the CISCO-CCM-MIB define the configuration parameters that relate to the notifications that are described. |
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 and IM and Presence Service do not support this MIB. |
The Connection SNMP Agent supports the following objects.
The following procedures provides an overview of the steps for configuring SNMP.
Review this section for troubleshooting tips. Make sure that all of the feature and network services are running.
Problem
You cannot poll any MIBs from the system.
This condition means that the community string or the snmp user is not configured on the system or they do not match with what is configured on the system. By default, no community string or user is configured on the system.
Solution
Check whether the community string or snmp user is properly configured on the system by using the SNMP configuration windows.
Problem
You cannot receive any notifications from the system.
This condition means that the notification destination is not configured correctly on the system.
Solution
Verify that you configured the notification destination properly in the Notification Destination (V1/V2c or V3) Configuration window.
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 following table provides the required SNMP configuration settings.
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 the serviceability GUI, you configure SNMPv1 support in the V1/V2c Configuration window.
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 the serviceability GUI, you configure SNMPv2c support in the V1/V2c Configuration window.
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 requested objects). To prevent SNMP packets from being exposed on the network, you can configure encryption with SNMPv3.
Instead of using community strings like SNMPv1 and v2, SNMPv3 uses SNMP users.
In the serviceability GUI, you configure SNMPv3 support in the V3 Configuration window.
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. |
Although SNMP community strings provide no security, they authenticate access to MIB objects and function as embedded passwords. You configure SNMP community strings for SNMPv1 and v2c only.
SNMPv3 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 the serviceability GUI, no default community string or user exists.
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 the serviceability GUI.
Note |
Cisco Unified Communications Manager supports SNMP traps in Cisco Unified Communications Manager and IM and Presence Service systems. |
For SNMP notifications, the system sends traps immediately if the corresponding trap flags are enabled. In the case of the syslog agent, 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:
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 the serviceability GUI. |
The following table provides information about 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. |
For IM and Presence Service, you configure only clogNotificationsEnabled and clogMaxSeverity trap/inform parameters on the NMS.
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. |
|||
Set the ccmPhoneFailedAlarmInterval to a value between 30 and 3600. |
|||
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. |
|||
When you set clogMaxSeverity to warning, a SNMP trap generates when applications generate a syslog message with at least a warning severity level. |
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 Cisco Unity Connection SNMP agent in the Trace Configuration window in Cisco Unity Connection Serviceability by choosing the Connection SNMP Agent component.
This section describes how to configure the SNMP managed device for SNMP V1/V2c.
To find a community string, perform the following procedure.
Review the tasks in the overview procedure to set up SNMP.
Step 1 | Select . | ||
Step 2 | Select the specific search criteria that you want to use for the community string from the Find Community Strings where Name list box. | ||
Step 3 | Enter the community string for which you want to search. | ||
Step 4 | Select the hostname or IP address of the server where the community string exists in the Server list box. | ||
Step 5 | Select Find. | ||
Step 6 |
(Optional)To apply the configuration from one of the options in the search results to all nodes in a cluster, check the check box next to the name of the option and check the Apply to All Nodes check box. This step applies to Unified Communications Manager and IM and Presence Service clusters only. |
||
Step 7 |
Select the community string that you want to view from the list of results.
|
||
Step 8 | From the list of results, click the community string that you want to view. |
Because the SNMP agent provides security by using community strings, you must configure the community string to access any management information base (MIB) in the SNMP managed device's system. Change the community string to limit access to the SNMP managed device's system. To add, modify, and delete community strings, access the SNMP Community String configuration window.
Step 1 | Select . | ||
Step 2 | Select the required server from the Server list box, and then select Find. | ||
Step 3 |
Perform one of the following tasks:
|
||
Step 4 |
Enter the community string configuration settings.
|
||
Step 5 |
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. A message indicates that changes will not take effect until you restart the SNMP master agent. |
||
Step 6 |
Perform one of the following actions:
|
Field | 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 find a community string. To change the server for the community string, perform the find a community string procedure. |
|||
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 (_).
When you edit a community string, you cannot change the name of the community string. |
|||
To accept SNMP only from specified hosts, click this button.
|
|||
|
|||
To apply the community string to all nodes in the cluster, check this check box. This field applies to Cisco Unified Communications Manager and IM and Presence Service clusters only. |
To delete a community string, perform the following procedure:
Step 1 | Locate the community string. |
Step 2 | Check the community string that you want to delete from the list of matching records. |
Step 3 | Select Delete Selected. A message indicates that the system will delete notification entries that relate to this community string. |
Step 4 | Select OK to continue the deletion. A message indicates that changes will not take effect until you restart the SNMP master agent. |
Step 5 | Perform one of the following actions: |
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 |
Enter the hostname or IP address of the server that supports the notification destination in the Server list box, and then click Find. After you click Find, the Add New button displays. After the search results display, the Apply to All Nodes check box displays. |
||
Step 5 |
(Optional)Perform one or more of the following actions:
|
To configure the notification destination (trap/inform receiver) for V1/V2c, perform the following procedure.
Step 1 | Select . | ||
Step 2 | Select the required server from the Server list box, and then click Find. | ||
Step 3 |
Perform one of the following tasks:
|
||
Step 4 |
Enter the notification destination configuration settings.
|
||
Step 5 | Perform one of the following actions: | ||
Step 6 |
Select OK to restart the SNMP master agent or select Cancel to continue the configuration without restarting the SNMP master agent.
|
Field | Description |
---|---|
This setting displays as read only because you specified the server when you performed the procedure to find a notification destination. To change the server for the notification destination, perform the procedure to find a community string. |
|
From the drop-down list box, select the Host IP address of the trap destination or click Add New. If you click 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 Create New uiCommunity String to create a community string. IM and Presence only: Only community strings with minimum notify privileges (ReadWriteNotify, ReadNotifyOnly, 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 Create New Community String to create a 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. This applies to Cisco Unified Communications Manager and IM and Presence Service clusters only. |
To delete an SNMP V1/V2c notification destination, perform the following procedure:
Step 1 | Find the notification destination that you want to delete. | ||
Step 2 | Check the check box next to the notification destination that you want to delete in the list of matching records in the Find/List window. | ||
Step 3 | Click Delete Selected. A message asks whether you want to delete the notification entries. | ||
Step 4 | Click OK to continue the deletion. A message indicates that changes will not take effect until you restart the SNMP master agent. | ||
Step 5 |
Perform one of the following:
After the window refreshes, the notification destination that you deleted no longer displays in the results. |
This section describes how to configure the SNMP managed device for SNMP V3.
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 | Select . |
Step 2 | Select the specific search criteria that you want to use to find the user; for example, begins with. |
Step 3 | Enter the username for which you want to search. |
Step 4 | Select the hostname or IP address of the server where you access the user from the Server list box, and then click Find. |
Step 5 |
(Optional)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. This applies to Cisco Unified Communications Manager and IM and Presence Service clusters only. |
Step 6 | Select the user that you want to view from the list of results. |
To setup users for SNMP V3, perform the following procedure.
Step 1 |
Select and locate the SNMP V3 user to set up. See the procedure to find the SNMP V3 user for details. |
||||
Step 2 |
Perform one of the following tasks:
|
||||
Step 3 |
Enter the SNMP V3 user configuration settings.
|
||||
Step 4 |
To add a new user, click Insert, or click Save to save changes to an existing user. A message indicates that changes will not take effect until you restart the SNMP master agent. |
||||
Step 5 |
Perform one of the following:
|
Field | Description | ||
---|---|---|---|
This setting displays as read only because you specified the server when you performed the find notification destination procedure. To change the server where you want to provide access, perform the procedure to find an 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 (_).
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.
|
|||
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. |
|||
|
|||
To apply the user configuration to all nodes in the cluster, check this check box. This applies to Cisco Unified Communications Manager and IM and Presence Service clusters only. |
Step 1 |
Select and locate the SNMP V3 user to delete. See the procedure to find the SNMP V3 user for details. |
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. A message indicates that the system will delete notification entries that relate to this user. |
Step 4 |
To continue the deletion, click OK. A message indicates that changes will not take effect until you restart the SNMP master agent. |
Step 5 |
Perform one of the following actions:
Cisco recommends that you wait until you finish all the SNMP configuration before you restart the SNMP master agent service. After the window refreshes, the user that you deleted no longer displays in the results. |
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, and then click Find. After you click Find, the Add New button displays. After the search results display, the Apply to All Nodes check box displays. |
Step 5 |
(Optional)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 then check the Apply to All Nodes check box. This applies to Cisco Unified Communications Manager and IM and Presence Service clusters only. |
Step 6 | Select the notification destination that you want to view from the list of results. |
To configure the trap/Inform receiver, perform the following procedure.
Step 1 |
Select and locate the notification destination for SNMP V3 to set up. See the procedure to find the notification destination for SNMP V3 for details. |
||
Step 2 | Perform one of the following tasks: | ||
Step 3 |
Configure the SNMP V3 notification destination configuration settings.
|
||
Step 4 |
Perform one of the following actions to save a notification destination:
A message indicates that changes will not take effect until you restart the SNMP master agent. |
||
Step 5 |
Perform one of the following actions:
|
Field | Description | ||
---|---|---|---|
This setting displays as read only because you specified the server when you performed the procedure to find an SNMP V3 notification destination. To change the server for the notification destination, perform the procedure to find an SNMP V3 notification destination and select a different server. |
|||
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.
|
|||
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.
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. This applies to Cisco Unified Communications Manager and IM and Presence Service clusters only. |
To delete an SNMP V3 notification destination, perform the following procedure.
Step 1 |
Select and locate the notification destination to delete. See the procedure to find the notification destination for SNMP V3 for details. |
||
Step 2 | From the list of matching records, check the check box next to the notification destination that you want to delete. | ||
Step 3 | Select Delete Selected. A message asks you if you want to delete the notification destination. | ||
Step 4 | Select OK to continue the deletion. A message indicates that changes will not take effect until you restart the SNMP master agent. | ||
Step 5 |
Perform one of the following actions:
|
Use the serviceability GUI to configure the system contact and system location objects for the SNMP 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.
Perform 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 SNMP MIB2 system group configuration settings. |
Step 3 | Click Save. A message indicates that changes will not take effect until you restart the SNMP master agent. |
Step 4 | Select OK to restart the SNMP master agent service or select Cancel to continue the configuration without restarting the SNMP master agent. |
Step 5 | Perform one of the following actions: |
From the drop-down list box, choose the server for which you want to configure contacts, and then click Go. |
|
Enter the location of the person that is identified as the system contact. |
|
Check to apply the system configuration to all of the nodes in the cluster. This applies to Cisco Unified Communications Manager and IM and Presence Service clusters only. |
Use CLI commands to set the configurable SNMP trap settings. SNMP trap configuration parameters and recommended configuration tips are provided for CISCO-SYSLOG-MIB, CISCO-CCM-MIB, and CISCO-UNITY-MIB.
To set up SNMP traps, perform the following steps.
Step 1 | Login to Cisco Unified Serviceability and confirm that Cisco CallManager SNMP Services and SNMP Master Agent are activated and running by performing the following steps: |
Step 2 | If you want to run SNMP V1 or V2, confirm that the community string and notification destination is set up by performing the following steps: |
Step 3 | If you want to run SNMP V3, confirm that the user and notification destination is set up by performing the following steps: |
Step 4 | Login to CLI and run the utils snmp test CLI command to verify that SNMP is running. |
Step 5 | Follow Generate SNMP traps to generate specific SNMP traps (for example, the ccmPhoneFailed or MediaResourceListExhausted traps). |
Step 6 | If the traps do not generate, perform the following steps: |
Step 7 | Reproduce the traps and check if the corresponding alarm is logged in CiscoSyslog file. |
This section describes the process for generating specific types of SNMP traps. SNMP must be set up and running on the server in order for the individual traps to generate. Follow Set up SNMP traps for instructions on how to set up your system to generate SNMP traps.
Note |
The processing time for individual SNMP traps varies depending on which trap you are attempting to generate. Some SNMP traps may take up to a few minutes to generate. |
SNMP Traps |
Process |
||
---|---|---|---|
ccmPhoneStatusUpdate |
To trigger the ccmPhoneStatusUpdate trap:
|
||
ccmPhoneFailed |
To trigger the ccmPhoneFailed trap:
|
||
ccmGatewayFailed |
To trigger the ccmGatewayFailed SNMP trap: |
||
ccmGatewayLayer2Change |
To trigger the ccmGatewayLayer2Change trap on a working gateway where layer 2 is monitored (for example, the MGCP backhaul load): |
||
MediaResourceListExhausted |
To trigger a MediaResourceListExhausted trap:
|
||
RouteListExhausted |
To trigger a RouteListExhausted trap: |
||
MaliciousCallFailed |
To trigger a MaliciousCallFailed trap: |
||
ccmCallManagerFailed |
To trigger the ccmCallManagerFailed trap:
The CallManager Failed Alarm is generated when internal errors are generated. These internal errors may include an internal thread quitting due to the lack of CPU, pausing the CallManager server for more than 16 seconds, and timer issues.
|
||
syslog messages as traps |
To receive syslog messages above a particular severity as traps, set the following two mib objects in the clogBasic table:
|
Use these guidelines to configure CISCO-SYSLOG-MIB trap settings on your system:
snmpset -c <community string> -v2c <transmitter ipaddress> 1.3.6.1.4.1.9.9.41.1.1.2.0 i 1
snmpset -c public -v2c 1<transmitter ipaddress> 1.3.6.1.4.1.9.9.41.1.1.3.0 i <value>
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. |
snmpset -c <community string> -v2c <transmitter ipaddress> 1.3.6.1.4.1.9.9.156.1.9.2 .0 i <value>
snmpset -c <community string> -v2c <transmitter ipaddress> 1.3.6.1.4.1.9.9.156.1.9.4.0 i <value>
Cisco Unity Connection only: The Cisco Unity 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.