- Configuring SNMP MIB
Initial Configuration Tasks 
    
    
 
    
 
   
 Configuring SNMP MIB
- About SNMP MIB Support
- Cisco Unified SIP Proxy SNMP MIBs
- Configuring Community String
- Configuring SNMP Traps
About SNMP MIB Support
The Cisco Unified SIP Proxy (Unified SIP Proxy) includes SNMP integration for Release 10.2 with support for Cisco-USP-MIB. It is an enhancement from the SNMP MIB basic support introduced in Unified SIP Proxy Release 8.5. The Cisco Unified SIP Proxy Release 10.2 is SNMP version 2 (SNMPv2c) compliant.
Unified SIP Proxy integrates an SNMP agent and SNMP MIBs to monitor the health and to conduct performance monitoring and data collection for Unified SIP Proxy. Cisco-USP-MIB and Cisco-Process-MIB monitor the following data:
The SNMP integration sends notifications that helps to effectively monitor and manage performance and all the relevant system-specific data. Cisco-Process-MIB is supported in Cisco Unified SIP Proxy Release 10.2 for generating traps on configured CPU thresholds.
You can configure SNMP to send notifications to one or more monitoring systems. The maximum number of SNMP trap hosts that you can configure is limited to five.
Definitions
Table 1 Definition of SNMP MIB Related Terms
Prerequisites
For using Cisco-USP-MIB, you must ensure that the following prerequisites are met:
- Configure Community Strings.
- Administrators of the Unified SIP Proxy must be familiar with the Cisco Command-line Interface (CLI) or the Graphical User Interface (GUI).
- Use a MIB browser or Network Management System (NMS) to interact with the Cisco Unified SIP Proxy Release 10.2.
- Upload the CISCO-USP-MIB to the NMS.
- Ensure that MIB browser or NMS provides SNMP v2c compliance.
Restrictions
SNMP MIB support in Cisco Unity SIP Proxy Release 10.2 is known to have the following limitations or restrictions:
- No Support for SNMP Version 3 (SNMPv3)
- Certain MIB objects in the Cisco Unified SIP Proxy MIB tree are not supported. For a list of MIB objects that are not supported, see MIB Objects.
- If both read-only and read-write community strings are same for SNMP MIBs, then read-only takes preference and SET operations are not allowed.
- If the element table contains nested server group as an element, it does not display the partial state. The element state is shown as either up or down.
Structure
The SNMP MIB structure for Unified SIP Proxy has the following main considerations:
- The Unified SIP Proxy is uniquely identified within the Cisco management (9) group by the number –.1.3.6.1.4.1.9.9.827.
- Use either of the following methods to identify objects in the CISCO-USP-MIB:
 – The object identifier –.1.3.6.1.4.1.9.9.827.<Cisco-USP- MIB-variable>
 The object identifier –.1.3.6.1.4.1.9.9.827.<Cisco-USP- MIB-variable>
 – The object name – iso(1).org(3).dod(6).internet(1).private(4).enterprise(1).cisco(9).ciscoMgmt(9).CISCO-USP-MIB(827).<Cisco- USP-MIB-variable>
 The object name – iso(1).org(3).dod(6).internet(1).private(4).enterprise(1).cisco(9).ciscoMgmt(9).CISCO-USP-MIB(827).<Cisco- USP-MIB-variable>
- Cisco Unified SIP Proxy Release 10.2 supports the following traps in Cisco-Process-MIB for CPU utilization monitoring:
 – cpmCPURisingThreshold (.1.3.6.1.4.1.9.9.109.2.0.1)
 cpmCPURisingThreshold (.1.3.6.1.4.1.9.9.109.2.0.1)
 – cpmCPUFallingThreshold (.1.3.6.1.4.1.9.9.109.2.0.2)
 cpmCPUFallingThreshold (.1.3.6.1.4.1.9.9.109.2.0.2)
The Unified SIP Proxy MIB structure has the following groups and subgroups:
Cisco Unified SIP Proxy SNMP MIBs
The Cisco Unified SIP Proxy captures the following in a management information base.
MIB Objects
The supported Cisco Unified SIP Proxy MIB Objects are:
Cisco Unified SIP Proxy Release 10.2 does not support the following MIB objects:
- cuspMemoryThresholdAlert
- cuspDiskSpaceThresholdAlert
- cuspBackupProcessFailAlert
- cuspConnectionExceptionAlert
- cuspThresholdValues
- cuspDiskSpaceThresholdValue
- cuspMemoryThresholdValue
- cuspMessageStats
- cuspStrayMessageCount
- cuspNoOfMessagesRecieved
- cuspMemoryThresholdAlertEnable
- cuspExtensiveLoggingAlertEnable
- cuspDiskSpaceThresholdAlertEnable
- cuspBackupProcessFailAlertEnable
- cuspConnectionExceptionAlertEnable
- cuspDiskSpaceUsed
cuspScalar
This table contains a list of Unified SIP Proxy scalars. An entry in this table represents Unified SIP Proxy information relevant to licenses, system state, and memory.
Table 2 MIB Description for cuspScalar
cuspCallStats
This Unified SIP Proxy MIB defines data related to calls.
Table 3 MIB Description for cuspCallStats
 
 
   Note There is no CLI and GUI equivalent for the data retrieved through MIB objects related to Calls Per Second (CPS) such as cuspCPS, cuspAvgCPSOneMin, cuspMaxCPSOneMin, cuspDroppedCallsOneSec, cuspAvgDroppedCPSOneMin, cuspMaxDroppedCPSOneMin, cuspCallsRoutedOneSec, cuspAvgCallsRoutedOneMin, and cuspMaxCallsRoutedOneMin. For example, GUI provides data for a five-minute average CPS while the MIB object cuspCPS retrieves CPS data only for the last second.
 There is no CLI and GUI equivalent for the data retrieved through MIB objects related to Calls Per Second (CPS) such as cuspCPS, cuspAvgCPSOneMin, cuspMaxCPSOneMin, cuspDroppedCallsOneSec, cuspAvgDroppedCPSOneMin, cuspMaxDroppedCPSOneMin, cuspCallsRoutedOneSec, cuspAvgCallsRoutedOneMin, and cuspMaxCallsRoutedOneMin. For example, GUI provides data for a five-minute average CPS while the MIB object cuspCPS retrieves CPS data only for the last second.
 
 
   Note CUSP dropped call MIB objects are not updated if the license is in unidentified state.
 CUSP dropped call MIB objects are not updated if the license is in unidentified state.
 
 
   Note If call rate limit is set to a value lesser than license limit, cuspCallsDroppedExceedingLicense MIB counts calls that are dropped due to call rate limit.
 If call rate limit is set to a value lesser than license limit, cuspCallsDroppedExceedingLicense MIB counts calls that are dropped due to call rate limit. 
cuspThresholdValues
The Unified SIP proxy MIB object cuspThresholdValues (.1.3.6.1.4.1.9.9.827.1.1.12) provides threshold value information (as configured by user) on disk space and memory utilization.
Table 4 MIB Description for cuspThresholdValues
cuspTable
The Unified SIP proxy MIB object cuspTable (.1.3.6.1.4.1.9.9.827.1.2) consists of two main subgroups of objects:
- cuspServerGroupTable (OID:.1.3.6.1.4.1.9.9.827.1.2.1)
- cuspElementTable (OID:.1.3.6.1.4.1.9.9.827.1.2.2)
 
 
   Note If data is retrieved from multiple network elements using cuspTable MIBs, the CPU utilization can spike beyond the optimum levels.
 If data is retrieved from multiple network elements using cuspTable MIBs, the CPU utilization can spike beyond the optimum levels.
cuspServerGroupTable
The MIB cuspServerGroupTable represents a list of server groups that are part of active configuration. Server groups define the elements with which the Cisco Unified SIP Proxy system interacts for each network.
Table 5 MIB Description for cuspServerGroupTable
|  |  |  | 
|---|---|---|
| The Server group status is given as up, partial down, and down. | ||
 
 
   Note CuspservergroupPingStatus MIB object retrieves the information of a group, irrespective of the global ping status.
 CuspservergroupPingStatus MIB object retrieves the information of a group, irrespective of the global ping status.
cuspElementTable
The MIB cuspElementTable provides a list of elements in a server group table. Also, the table contains information on status (up or down) of the element, its Q-value, weight, and transport type.
Table 6 MIB Description for cuspElementTable
cuspNotifControlInfo
The MIB cuspNotifControlInfo (OID is.1.3.6.1.4.1.9.9.827.1.3) contains object that manages (enabling and disabling) the traps defined in CiscoUspMIBNotifs.
Table 7 MIB Description for cuspNotifControlInfo
MIB Notifications (Traps)
Unified SIP Proxy generates trap notifications when the Network Management Station (NMS) or the administrator has to be informed about an event. The notification describes the operation state information of a service when a condition occurs. Traps provide information on issues that occur in the network element without polling for SNMP objects.
The administrator can control traps using the Command-line Interface (CLI), the Graphical User Interface (GUI), or through SNMP. By default, the traps are set to disabled state.
Unified SIP Proxy Release 10.2 supports a generic trap and raises SNMP traps on the following events:
- License Limit is exceeded
- System Failure
- Change in Server element state
- Change in Server group element state
Unified SIP Proxy Release 10.2 does not support SNMP traps on the following events:
- Backup Process Failure
- Memory threshold is exceeded
- Disk space threshold is exceeded
- Extensive Debug level logging
- Connection Exception
Table 8 MIB Description for MIB Traps
 
 
   Note cuspLicenseExceededAlert is not generated if the license is in unidentified state.
 cuspLicenseExceededAlert is not generated if the license is in unidentified state.
Configuring Community String
Summary Steps
Detailed Steps
|  |  | |
|---|---|---|
|  | ||
| snmp-server community community string {RO| RW} | Configures the community string. The access could be read-only or read-write based on the selected configuration. | |
|  | ||
|  | 
Example
The following example configures Community Strings on the Cisco Unified SIP Proxy:
Configuring SNMP Traps
Summary Steps
  2. snmp-server host   IP Address community string
  snmp-server host   IP Address community string 
  3. snmp-server enable traps [All | System-State | Server-Group | SG-Element | CPU-Rising | CPU-Falling |License-Exceeded | Extensive-Logging | SIP-Message-Queue-Overflow]
 snmp-server enable traps [All | System-State | Server-Group | SG-Element | CPU-Rising | CPU-Falling |License-Exceeded | Extensive-Logging | SIP-Message-Queue-Overflow]
Detailed Steps
Example
The following example configures SNMP Traps on the Cisco Unified SIP Proxy:
se-10-1-0-0(config)# snmp-server host 10.104.54.108 public
se-10-1-0-0(config)# snmp-server enable traps SG-Element
se-10-1-0-0(config)# snmp-server enable traps
 
 
   Note The trap body information can only be seen on the trap listener host. However, a generic trap notification will be logged in the vCUSP atrace.log logs.
Configuring CPU Threshold Values for Traps
To define rising and falling CPU threshold values for traps, perform these steps:
Summary Steps
  2. process cpu threshold type total rising   percentage  interval   seconds  falling percentage interval   seconds
  process cpu threshold type total rising   percentage  interval   seconds  falling percentage interval   seconds   
Detailed Steps
Example
The following example configures CPU thresholding values for SNMP traps on the Cisco Unified SIP Proxy:
se-10-1-0-0(config)# process cpu threshold type {total} rising 80 interval 300 falling 5 interval 300
Configuring Smart Licensing
About Smart Licensing
Cisco Smart Software Licensing is a standardized licensing platform that facilitates you to deploy and manage Cisco software licenses easily and quickly. Cisco Smart Software Licensing establishes a pool of software licenses that can be used across your network in a flexible and automated manner. It also provides visibility to your purchased and deployed licenses in your network. Cisco Smart Software Licensing removes the need for Product Activation Keys (PAKs) and reduces your license activation and registration time.
 
 
   Note For more information on Smart Licensing, see http://www.cisco.com/go/smartlicensing.
 For more information on Smart Licensing, see http://www.cisco.com/go/smartlicensing.
Summary Steps
  2. license smart destinationAddr   url
  license smart destinationAddr   url 
  3. license smart   httpProxyAddr   url
  license smart   httpProxyAddr   url 
Detailed Steps
Example
The following example configures Smart License on the Cisco Unified SIP Proxy:
se-10-1-0-0# license smart destinationAddr https://tools.cisco.com/its/service/oddce/services/DDCEService
se-10-1-0-0# license smart httpProxyAddr 10.1.1.1
se-10-1-0-0# license smart activate cusp 100
se-10-1-0-0# license smart register token_id MjgxZjdkY2RtMWY5Ny00YTk4LOI2N2MtNjcxNmYaMTkzZGFhLHE0MjA3MjY0%0AMjI5NDZ8OVAOdmNzSjdIeG4MMHIzTmZubNFzMHhKOTYyeHl67ZWQzQzVIM3Jk%0AHVk3MD0A3D%0N
Setting Backup Parameters
About Backup Parameters
Cisco Unified SIP Proxy backup and restore functions use an SFTP server to store and retrieve data. The backup function copies the files from Cisco Unified SIP Proxy to the SFTP server and the restore function copies the files from the SFTP server to Cisco Unified SIP Proxy. The SFTP server can reside anywhere in the network as long as the backup and restore functions can access it with an IP address or hostname.
All Cisco Unified SIP Proxy backup files are stored on the specified server. You can copy the backup files to other locations or servers, if necessary.
The backup parameters specify the SFTP server to use for storing Cisco Unified SIP Proxy backup files and the number of backups that are stored before the system overwrites the oldest one.
Prerequisites
- Verify that an SFTP administrator or other user who can log in to the SFTP server has full permission on the SFTP server, such as read, write, overwrite, create, and delete permissions for files and directories.
- Gather the SFTP server URL and the username and password of the SFTP server login.
Make sure that the SFTP server URL is pointing to the absolute path of the backup directory. For example, sftp://<hostname>/full/path/from/root/to/backup_directory.
Summary Steps
  2. backup server    url   backup-sftp-url   username  backup-sftp-usrname   password  backup-sftp-password
  backup server    url   backup-sftp-url   username  backup-sftp-usrname   password  backup-sftp-password 
Detailed Steps
Example
The following example configures a backup server and displays the show backup output:
se-10-1-0-0# configure terminal
se-10-1-0-0(config)> backup revisions 5
se-10-1-0-0(config)> backup server url sftp://10.12.0.1/sftp username “admin” password “wxyz”
Server URL: sftp://10.12.0.1/sftp
Number of Backups to Retain: 5
- For information about the CLI commands, see the CLI Command Reference for Cisco Unified SIP Proxy Release 10.2.
- For information about backing up and restoring your configuration, see Backing Up and Restoring Data .
Configuring NTP Servers
When you install the Cisco Unified SIP Proxy software, the system gives you the option of adding up to two Network Time Protocol (NTP) servers. You can add additional NTP servers (the system supports up to three NTP servers), remove one or more NTP servers, or display NTP server information using the CLI.
Adding NTP Servers
About Adding NTP Servers
You can specify an NTP server using its IP address or its hostname.
Cisco Unified SIP Proxy uses the DNS server to resolve the hostname to an IP address and stores the IP address as an NTP server. If DNS resolves the hostname to more than one IP address, Cisco Unified SIP Proxy randomly chooses one of the IP addresses that is not already designated as an NTP server. If you do not want to go with the random choice, set the prefer attribute for one server.
To configure an NTP server with multiple IP addresses for a hostname, repeat the configuration steps using the same hostname. Each iteration assigns the NTP server to its remaining IP addresses.
Summary Steps
Detailed Steps
Examples of Adding NTP Servers
The following commands configure the NTP server:
The output from the show ntp status command looks similar to the following:
Removing an NTP Server
You can remove an NTP server using its IP address or hostname.
Summary Steps
Detailed Steps
Displaying NTP Server Information
Commands to Display NTP Server Information
The following commands are available to display NTP server configuration information and status:
Examples of Showing NTP Server Information
The following is sample output for the show ntp associations command:
The following is sample output for the show ntp servers command:
The following is sample output for the show ntp source command:
The following is sample output for the show ntp status command:
- For information about the CLI commands, see the CLI Command Reference for Cisco Unified SIP Proxy Release 10.2.
- For information about the initial installation of the Cisco Unified SIP Proxy system and the post installation configuration tool, see the Installation Guide for Cisco Unified SIP Proxy Release 10.2. For information about copying the configuration, see Copying Configurations.
Setting the Time Zone
When you install the Cisco Unified SIP Proxy software, the system prompts you to set the time zone. If you need to change it, use the clock timezone command in Cisco Unified SIP Proxy configuration mode.
To display the time zone, use the show clock detail command in module EXEC mode.
Example of Setting the Time Zone
Configuring Sub-interfaces
You can define multiple sub-interfaces on Virtual Cisco Unified SIP Proxy (vCUSP) and there is no specific restriction on the number of sub-interfaces from vCUSP.
 
 
  Note Ensure that all the sub-interfaces are configured with IP addresses from the same subnet, as the trunk port config with sub-interfaces are not supported on vCUSP 10.x and later.
 Ensure that all the sub-interfaces are configured with IP addresses from the same subnet, as the trunk port config with sub-interfaces are not supported on vCUSP 10.x and later.
Summary Steps
Detailed Steps
|  |  | |
|---|---|---|
|  | ||
|  | ||
| se-10-64-86-166(config-subif)# ip address 10.64.86.159 255.255.255.0 | ||
|  | 
Example
The following example configures subinterface for Fastethernet:
se-10-64-86-166(config-subif)# interface FastEthernet 0.11
 Feedback
Feedback