Simple Network Management Protocol Support
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.
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.
Tip |
Unified Communications Manager only: SNMP configuration parameters that you specified in Cisco Unified CallManager or Unified Communications Manager 4.X do not migrate during a Unified Communications Manager 6.0 and later upgrade. You must perform the SNMP configuration procedures again in Cisco Unified Serviceability. |
SNMP supports IPv4 and IPv6, the CISCO-CCM-MIB includes columns and storage for both IPv4 and IPv6 addresses, preferences, and so on.
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 Communications Manager and IM and Presence Service 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.
The master agent and subagent components are used 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 Management Information Base (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 Unified Communications Manager subagent interacts with the local Unified Communications Manager only. The 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).
The IM and Presence Service subagent interacts with the local IM and Presence Service only. The IM and Presence Service 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) - An 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. The following NMSs are supported:
-
CiscoWorks LAN Management Solution
-
HP OpenView
-
Third-party applications that support SNMP and Unified Communications Manager SNMP interfaces
-
SNMP Management Information Base
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:
-
CISCO-CDP-MIB
-
CISCO-CCM-MIB
-
CISCO-SYSLOG-MIB
-
CISCO-UNITY-MIB
Observe the following limitations:
-
Unified Communications Manager does not support CISCO-UNITY-MIB.
-
Cisco Unity Connection does not support CISCO-CCM-MIB.
-
IM and Presence Service does not support CISCO-CCM-MIB and CISCO-UNITY-MIB.
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:
-
SYSAPPL-MIB
-
MIB-II (RFC 1213)
-
HOST-RESOURCES-MIB
CISCO-CDP-MIB
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:
-
cdpInterfaceIfIndex
-
cdpInterfaceMessageInterval
-
cdpInterfaceEnable
-
cdpInterfaceGroup
-
cdpInterfacePort
-
cdpGlobalRun
-
cdpGlobalMessageInterval
-
cdpGlobalHoldTime
-
cdpGlobalLastChange
-
cdpGobalDeviceId
-
cdpGlobalDeviceIdFormat
-
cdpGlobalDeviceIdFormatCpd
Note |
The CISCO-CDP-MIB is dependent on the presence of the following MIBs: CISCO-SMI, CISCO-TC, CISCO-VTP-MIB. |
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:
-
sysApplInstallPkg
-
sysApplRun
-
sysApplMap
-
sysApplInstallElmt
-
sysApplElmtRun
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. |
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:
-
system
-
interfaces
-
at
-
ip
-
icmp
-
tcp
-
udp
-
snmp
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. |
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:
-
hrSystem
-
hrStorage
-
hrDevice
-
hrSWRun
-
hrSWRunPerf
-
hrSWInstalled
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'. |
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:
-
clogNotificationsSent
-
clogNotificationsEnabled
-
clogMaxSeverity
-
clogMsgIgnores
-
clogMsgDrops
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.
|
CISCO-CCM-MIB/CISCO-CCM-CAPABILITY MIB
The CISCO-CCM-MIB contains both dynamic (real-time) and configured (static) information about the Unified Communications Manager and its associated devices, such as phones, gateways, and so on, that are visible on this Unified Communications Manager node. Simple Network Management Protocol (SNMP) tables contain information such as IP address, registration status, and model type.
SNMP supports IPv4 and IPv6, the CISCO-CCM-MIB includes columns and storage for both IPv4 and IPv6 addresses, preferences, and so on.
Note |
Unified Communications Manager supports this MIB in 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 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 Unified Communications Manager cluster configuration); static tables get populated when the Cisco CallManager SNMP Service is running.
Table(s) |
Contents |
---|---|
ccmTable |
This table stores the version and installation ID for the local Unified Communications Manager. The table also stores information about all the Unified Communications Manager in a cluster that the local Unified Communications Manager knows about but shows "unknown" for the version detail. If the local 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 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. |
ccmCTIDevice, ccmCTIDeviceDirNum |
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 Unified Communications Manager MIB get updated. |
ccmSIPDevice |
The CCMSIPDeviceTable stores each SIP trunk as one device. |
ccmH323Device |
The ccmH323DeviceTable contains the list of H.323 devices for which Unified Communications Manager contains information (or the local 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 Unified Communications Manager. 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 H.323 trunk information. |
ccmVoiceMailDevice, ccmVoiceMailDirNum |
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 Cisc MIB get updated. |
ccmGateway |
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. 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. |
ccmMediaDeviceInfo |
The table contains a list of all media devices which have tried to register with the local Unified Communications Manager at least once. |
ccmGroup |
This tables contains the Unified Communications Manager groups in a Unified Communications Manager cluster. |
ccmGroupMapping |
This table maps all Unified Communications Manager's in a cluster to a Unified Communications Manager group. The table remains empty when the local Unified Communications Manager node is down. |
Table(s) |
Content |
---|---|
ccmProductType |
The table contains the list of product types that are supported with Unified Communications Manager (or cluster, in the case of a Unified Communications Manager cluster configuration), including phone types, gateway types, media device types, H.323 device types, CTI device types, voice-messaging device types, and SIP device types. |
ccmRegion, ccmRegionPair |
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 Unified Communications Manager cluster. Geographical region pairs are defined by Source region and Destination region. |
ccmTimeZone |
The table contains the list of all time zone groups in a Unified Communications Manager cluster. |
ccmDevicePool |
The tables contains the list of all device pools in a Unified Communications Manager cluster. Device pools are defined by Region, Date/Time Group, and Unified Communications Manager 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. Unified Communications Manager and IM and Presence Service do not support this MIB. |
The Connection SNMP Agent supports the following objects.
Object |
Description |
---|---|
ciscoUnityTable |
This table contains general information about the Cisco Unity Connection servers such as hostname and version number. |
ciscoUnityPortTable |
This table contains general information about the Cisco Unity Connection voice messaging ports. |
General Unity Usage Info objects |
This group contains information about capacity and utilization of the Cisco Unity Connection voice messaging ports. |
SNMP Configuration Requirements
The system provides no default SNMP configuration. You must configure SNMP settings after installation to access MIB information. Cisco supports SNMP V1, V2c, and V3 versions.
SNMP agent provides security with community names and authentication traps. You must configure a community name to access MIB information. The following table provides the required SNMP configuration settings.
Configuration |
Cisco Unified Serviceability Page |
---|---|
V1/V2c Community String |
|
V3 Community String |
|
System Contact and Location for MIB2 |
|
Trap Destinations (V1/V2c) |
|
Trap Destinations (V3) |
|
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 the serviceability GUI, you configure SNMPv1 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 the serviceability GUI, you configure SNMPv2c 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 requested objects). To prevent SNMP packets from being exposed on the network, you can configure encryption with SNMPv3.
Note |
From Release 12.5(1)SU1 onwards, the MD5 or DES encryption methods are not supported in Unified Communications Manager. You can choose either SHA or AES as the authentication protocols while adding an SNMPv3 user. |
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.
SNMP Services
The services in the following table support SNMP operations.
Note |
SNMP Master Agent serves as the primary service for the MIB interface. You must manually activate Cisco CallManager SNMP service; all other SNMP services should be running after installation. |
MIB | Service | Window |
---|---|---|
CISCO-CCM-MIB |
Cisco CallManager SNMP service |
. Choose a server; then, choose Performance and Monitoring category. |
SNMP Agent |
SNMP Master Agent |
Choose a server; then, choose Platform Services category. Choose a server; then, choose Platform Services category. |
CISCO-CDP-MIB |
Cisco CDP Agent |
|
SYSAPPL-MIB |
System Application Agent |
|
MIB-II |
MIB2 Agent |
|
HOST-RESOURCES-MIB |
Host Resources Agent |
|
CISCO-SYSLOG-MIB |
Cisco Syslog Agent |
|
Hardware MIBs |
Native Agent Adaptor |
|
CISCO-UNITY-MIB |
Connection SNMP Agent |
Choose a server; then, choose Base Services category. |
Caution |
Stopping any SNMP service may result in loss of data because the network management system no longer monitors the 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 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.
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 the serviceability GUI.
Note |
Unified Communications Manager supports SNMP traps in 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 Unified Communications Manager SNMP trap/inform messages that are sent to a configured trap destination:
-
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 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.
Parameter Name |
Default Value |
Generated Traps |
Configuration Recommendations |
---|---|---|---|
ccmCallManagerAlarmEnable |
True |
ccmCallManagerFailed ccmMediaResourceListExhausted ccmRouteListExhausted ccmTLSConnectionFailure |
Keep the default specification. |
ccmGatewayAlarmEnable |
True |
ccmGatewayFailed ccmGatewayLayer2Change Although you can configure a Cisco ATA 186 device as a phone in Cisco Unified Communications Manager Administration, when Unified Communications Manager sends SNMP traps for the Cisco ATA device, it sends a gateway type trap; for example, ccmGatewayFailed. |
None. The default specifies this trap as enabled. |
ccmPhoneStatusUpdateStorePeriod ccmPhoneStatusUpdateAlarmInterval |
1800 0 |
ccmPhoneStatusUpdate |
Set the ccmPhoneStatusUpdateAlarmInterval to a value between 30 and 3600. |
ccmPhoneFailedStorePeriod ccmPhoneFailedAlarmInterval |
1800 0 |
ccmPhoneFailed |
Set the ccmPhoneFailedAlarmInterval to a value between 30 and 3600. |
ccmMaliciousCallAlarmEnable |
True |
ccmMaliciousCall |
None. The default specifies this trap as enabled. |
ccmQualityReportAlarmEnable |
True |
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 (Unified Communications Manager only), on the local Unified Communications Manager server. ccmQualityReport |
None. The default specifies this trap as enabled. |
clogNotificationsEnabled |
False |
clogMessageGenerated |
To enable trap generation, set clogNotificationsEnable to True. |
clogMaxSeverity |
Warning |
clogMessageGenerated |
When you set clogMaxSeverity to warning, a SNMP trap generates when applications generate a syslog message with at least a warning severity level. |
SFTP Server Support
For internal testing, we use the SFTP Server on Cisco Prime Collaboration Deployment (PCD) which is provided by Cisco, and which is supported by Cisco TAC. Refer to the following table for a summary of the SFTP server options:
SFTP Server |
Support Description |
||
---|---|---|---|
Cisco Prime Collaboration Deployment |
This server is the only SFTP server that is provided and tested by Cisco, and which is fully supported by Cisco TAC. Version compatibility depends on your version of Unified Communications Manager and Cisco Prime Collaboration Deployment. See the Cisco Prime Collaboration Deployment Administration Guide before you upgrade its version (SFTP) or Unified Communications Manager to ensure that the versions are compatible. |
||
SFTP Server from a Technology Partner |
These servers are third party provided and third party tested. Version compatibility depends on the third party test. See the Technology Partner page if you upgrade their SFTP product and/or upgrade Unified Communications Manager for which versions are compatible: |
||
SFTP Server from another Third Party |
These servers are third party provided, have limited Cisco testing, and are not officially supported by Cisco TAC. Version compatibility is on a best effort basis to establish compatible SFTP versions and Unified Communications Manager versions.
|