-
Cisco GSS Administration Guide (Software Version 3.1(1))
-
Index
-
Preface
-
Managing GSS Devices from the GUI
-
Managing the GSS from the CLI
-
Creating and Managing User Accounts
-
Managing GSS User Accounts Through a TACACS+ Server
-
Configuring Access Lists and Filtering GSS Traffic
-
Configuring SNMP
-
Backing Up and Restoring the GSSM Database
-
Viewing Log Files
-
Monitoring GSS Operation
-
Configuring the GSS Network with Anycast
-
Installing GSS Licenses
-
Performing GSS Software Upgrades and Downgrades
-
Feedback
Table Of Contents
Supported MIBs and Notifications
Configuring SNMP Server Notifications
Configuring the CPU Performance Threshold Values
Configuring SNMP Server Trap Limits
Specifying Recipients for SNMP Notification Operations
Configuring SNMP
This chapter describes how to configure Simple Network Management Protocol (SNMP) to query GSS devices for standard MIB resources.
It contains the following major sections:
•
Supported MIBs and Notifications
•
•
•
•
Overview
SNMP is a set of network management standards for IP-based internetworks. SNMP includes a protocol, a database-structure specification, and a set of management data objects. SNMP implementations typically consist of a management application running on one or more network management systems (NMSs), and agent applications, usually executing in firmware on various network devices.
SNMP obtains information from the network through a Management Information Base (MIB). The MIB is a database of code blocks called MIB objects. Each MIB object controls one specific function, such as counting how many bytes are transmitted through an agent's port. The MIB object consists of MIB variables, which define the MIB object name, description, and default value.
Each GSS or GSSM contains an SNMP agent, net-snmp version 5.1.2, that network management systems query for MIB resources. SNMP runs on GSS port 161 by default. The SNMP agent receives instructions from the SNMP manager and also sends management information back to the SNMP manager as events occur.
Supported MIBs and Notifications
Table 6-1 identifies the supported MIBs for the GSS.
Table 6-1 SNMP MIB Support
CISCO-GSLB-DNS-MIB
CISCO-GSLB-DNS-CAPABILITY
Description: Defines objects for status and statistics information of DNS-related Global Server Load Balancing (GSLB) operations.
Note the following conditions:
–
–
CISCO-GSLB-HEALTH-MON-MIB
CISCO-GSLB-HEALTH-MON-
CAPABILITYDescription: The GSS does not currently support any OIDs for this MIB, but it does support the related MIB SNMP traps (see Table 6-2).
CISCO-GSLB-SYSTEM-MIB
CISCO-GSLB-SYSTEM-CAPABILITY
Description: Defines the objects for network and system information of the GSLB as a network device. The MIB objects define information about GLSB status, GSLB peers (other GSLB devices on the same network that it interacts with) information and status, GSLB proximity information related statistics, and more. This MIB also defines the related notifications.
CISCO-IMAGE-MIB
CISCO-IMAGE-CAPABILITY
Description: Provides a list of the features supported by the software image running in the GSS.
CISCO-PROCESS-MIB
CISCO-PROCESS-CAPABILITY
Description: Defines the objects for monitoring CPU usage and active system processes. The CPU utilization MIBs provide aggregate CPU utilization for dual-code GSS devices.
Note the following conditions:
–
–
CISCO-SYSTEMS-EXT-MIB
CISCO-SYSTEM-EXT-CAPABILITY
Description: Monitors high availability (HA), SNMP SET errors, and bandwidths. This MIB also provides information about the core files that the GSS generates.
ENTITY-MIB
CISCO-ENTITY-CAPABILITY
Description: Provides comprehensive device information, including hardware and software details.
Note
The following URL provides details about the objects that the GSS supports for each MIB type:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
From this site, choose the GSS from the Cisco Secure and VPN Products drop-down list and then click on the associated Capability MIB. This site provides information about the supported GSS MIBs, Capability MIBs, and notifications. To find the actual MIB OIDs implemented in a MIB, see the corresponding Capability MIB, which describes both the capabilities of an agent with respect to the corresponding MIB module and the variations in the MIB implementations (if any).
In addition to the MIBs listed in Table 6-1, the GSS supports the following generic MIBs:
•
•
•
•
•
•
•
•
Table 6-2 identifies the supported SNMP notifications (traps) for the GSS. The GSS generates the notifications only when you enable them using the GSS CLI (see the "Configuring SNMP Server Notifications" section).
Configuring SNMP on the GSS
Before you use SNMP to monitor the GSS or GSSM, you must enable the SNMP agent on each GSS device. In addition to enabling the SNMP agent on the GSS device, you also specify an SNMP community name, name of the contact person, and the physical location for the GSS device.
Note
Note
You can add the public community string manually in the v2.0 software or higher as explained in the steps that follow. Any community strings that you configured in the pre-v2.0 GSS software will be retained after a v3.0 software upgrade.Use the snmp-server command in global configuration mode to enable and configure SNMP on your GSS device.
To configure SNMP for a GSS device, perform the following steps:
1.
gss1.example.com> enablegss1.example.com#If you are accessing the GSS remotely using Telnet or SSH, the CLI prompts you for the enable password. The default password is default. For more information about the enable password and configuring a new password, see the Cisco Global Site Selector Getting Started Guide.
2.
gss1.example.com# configgss1.example.com(config)#3.
gss1.example.com(config)# snmp-server enable4.
gss1.example.com(config)# snmp-server community-string public5.
gss-pilot1.cisco.com(config)# snmp-server contact JoeSmith-jsmith@cisco.com6.
gss1.example.com(config)# snmp-server location BoxboroughTo disable SNMP or any of the parameters outlined above, use the no form of the snmp command. For example, to disable the SNMP contacts for the GSS, enter:
gss1.example.com(config)# no snmp-server contact JoeSmith-jsmith@cisco.comConfiguring SNMP Server Notifications
You can enable traps on your GSS device by using the snmp-server enable-traps command in global configuration mode. To disable traps, use the no form of this command.
To configure SNMP server notifications for a GSS device, perform the following steps:
1.
gss1.example.com> enablegss1.example.com#If you are accessing the GSS remotely using Telnet or SSH, the CLI prompts you for the enable password. The default password is default. For more information about the enable password and configuring a new password, see the Cisco Global Site Selector Getting Started Guide.
2.
gss1.example.com# configgss1.example.com(config)#3.
gss1.example.com(config)# snmp-server enable4.
•
•
•
•
•
•
•
•
•
•
•
•
gss1.example.com(config)# snmp-server enable-traps kal5.
gss1.example.com(config)# snmp-server trap-source ethernet 0To disable SNMP server notifications, use the no form of the snmp-server enable-traps command. For example, to disable SNMP GSLB keepalive notifications, enter:
gss1.example.com(config)# no snmp-server enable-traps gslb kalConfiguring the CPU Performance Threshold Values
You can configure the GSS to issue SNMP traps that enable you to monitor CPU performance. The GSS can issue CPU performance notification traps when one or both of the following conditions exist:
•
•
The GSS monitors CPU usage every five seconds.
You can configure the CPU usage rising threshold value that determines when the GSS issues a CPU rising threshold crossing notification. Configure the rising threshold value by using the snmp-server cpu-rising-threshold command in global configuration mode.
The syntax of this command is as follows:
snmp-server cpu-rising-threshold rising_threshold
The rising_threshold argument is the threshold value as a percentage of the total CPU utilization. Enter a percentage value from 1 to 100. By default, the threshold value is set to 80 percent of the total CPU utilization. Use the no form of this command to return the threshold to its default value.
You can configure the CPU usage falling threshold value that determines when the GSS issues a CPU falling threshold crossing notification. Configure the falling threshold value using the snmp-server cpu-falling-threshold command in global configuration mode.
The syntax of this command is as follows:
snmp-server cpu-falling-threshold falling_threshold
The falling_threshold argument is the threshold value as a percentage of the total CPU utilization. Enter a percentage value from 1 to 100. By default, the threshold value is set to 80 percent of the total CPU utilization. Use the no form of this command to return the threshold to its default value.
Note
To configure the CPU usage rising and falling threshold values, perform the following steps:
1.
gss1.example.com> enablegss1.example.com#If you are accessing the GSS remotely using Telnet or SSH, the CLI prompts you for the enable password. The default password is default. For more information about the enable password and configuring a new password, see the Cisco Global Site Selector Getting Started Guide.
2.
gss1.example.com# configgss1.example.com(config)#3.
gss1.example.com(config)# snmp-server enable4.
gss1.example.com(config)# snmp-server enable-traps performance5.
gss1.example.com(config)# snmp-server cpu-rising-threshold 756.
gss1.example.com(config)# snmp-server cpu-falling-threshold 75To view the current CPU usage, use the show processes | grep CPU command. The command output displays the CPU usage as a percentage of the total CPU usage over a 5-second interval, 1-minute interval, and 5-minute interval.
Configuring SNMP Server Trap Limits
You can configure the maximum rate at which SNMP traps are set on your GSS device by using the snmp-server trap-limit command in global configuration mode. To set the default trap rate, use the no form of this command. The default is 25 traps per minute.
To configure SNMP server trap limits for a GSS device, perform the following steps:
1.
gss1.example.com> enablegss1.example.com#If you are accessing the GSS remotely using Telnet or SSH, the CLI prompts you for the enable password. The default password is default. For more information about the enable password and configuring a new password, see the Cisco Global Site Selector Getting Started Guide.
2.
gss1.example.com# configgss1.example.com(config)#3.
gss1.example.com(config)# snmp-server enable4.
•
•
•
gss1.example.com(config)# snmp-server trap-limit answer trap 10To set the trap rate back to its default rate, use the no form of the snmp-server trap-limit command as follows:
gss1.example.com(config)# no snmp-server trap-limit answer-trapSpecifying Recipients for SNMP Notification Operations
You can specify the recipient of an SNMP notification operation by using the snmp-server host command in global configuration mode. To remove the specified host, use the no form of this command.
To specify the recipient of an SNMP notification operation, perform the following steps:
1.
gss1.example.com> enablegss1.example.com#If you are accessing the GSS remotely using Telnet or SSH, the CLI prompts you for the enable password. The default password is default. For more information about the enable password and configuring a new password, see the Cisco Global Site Selector Getting Started Guide.
2.
gss1.example.com# configgss1.example.com(config)#3.
gss1.example.com(config)# snmp-server enable4.
gss1.example.com(config)# snmp-server host 10.1.1.1 MyCommunity5.
gss1.example.com(config)# snmp-server host 10.1.1.1 MyCommunity traps
Note
6.
•
•
gss1.example.com(config)# snmp-server host 10.1.1.1 MyCommunity traps version 27.
gss1.example.com(config)# snmp-server host 10.1.1.1 MyCommunity traps version 2 udp-port 500To remove the recipient of an SNMP notification, use the no form of the snmp-server host command. For example, to disable all SNMP notifications for sample IP address 10.1.1.1, UDP port 100, enter:
gss1.example.com(config)# no snmp-server host 10.1.1.1 MyCommunity traps version 2 udp-port 100Viewing the SNMP Status
When SNMP is enabled, you can display the SNMP status on your GSS device by using the show snmp command.
The syntax of this command is as follows:
show snmp
Verify that your SNMP agent, net snmp agent version 5.1.2, is enabled or disabled, as well as the configured names of the community-string, location, and contact.
Note
You can also use the show running-configuration command to display the complete SNMP configuration.For example, enter:
gss1.example.com# show snmpSNMP is enabledsys contact: JSmith jsmith@cisco.comsys location: Boxborough0 SNMP packets input0 Bad SNMP versions0 Unknown community name0 Illegal operation for community name supplied0 Encoding errors0 Number of requested variables0 Number of altered variables0 Get-request PDUs0 Get-next PDUs0 Set-request PDUs0 SNMP packets output0 Too big errors0 No such name errors0 Bad values errors0 General errors0 Trap PDUsCommunity---------publicHost Port Version Type---- ---- ------- ----16.1.1.11 162 v2c trapTrap type Enabled--------- -------GSLB KAL transition YesGSLB DNS clause change YesGSLB answer transition YesGSLB system core file discovery YesGSLB system peer transition YesSNMP authentication YesCold Start YesCpu Rising Threshold YesCpu Falling Threshold YesTrap type Threshold value--------- -------Cpu Rising Threshold 0Cpu Falling Threshold 0Trap type Trap Limit--------- -------GSLB answer transition 0GSLB DNS clause change 0GSLB KAL transition 0gss1.example.com#See the "Configuring SNMP on the GSS" section to change the status of your SNMP agent running on the GSS device.
Viewing MIB Files on the GSS
You can view the generic MIB files contained in the /mibs directory on the GSS by using the dir command. If you want to copy the MIB files from the /mibs directory on the GSS to another location on the GSS or to a remote network location, use the scp command.
For example, enter:
gss1.example.com# dir /mibstotal 1100drwxr-xr-x 2 root root 4096 Jul 18 08:45 .drwxrwxrwx 19 root root 4096 Jul 18 08:46 ..-rw-r--r-- 1 root root 17455 Jul 18 08:45 AGENTX-MIB.txt-rw-r--r-- 1 root root 19850 Jul 18 08:45 DISMAN-SCHEDULE-MIB.txt-rw-r--r-- 1 root root 64311 Jul 18 08:45 DISMAN-SCRIPT-MIB.txt-rw-r--r-- 1 root root 50054 Jul 18 08:45 EtherLike-MIB.txt-rw-r--r-- 1 root root 4660 Jul 18 08:45 HCNUM-TC.txt-rw-r--r-- 1 root root 52544 Jul 18 08:45 HOST-RESOURCES-MIB.txt-rw-r--r-- 1 root root 10583 Jul 18 08:45 HOST-RESOURCES-TYPES.txt-rw-r--r-- 1 root root 4015 Jul 18 08:45 IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt-rw-r--r-- 1 root root 4299 Jul 18 08:45 IANA-LANGUAGE-MIB.txt-rw-r--r-- 1 root root 15661 Jul 18 08:45 IANAifType-MIB.txt-rw-r--r-- 1 root root 5066 Jul 18 08:45 IF-INVERTED-STACK-MIB.txt-rw-r--r-- 1 root root 71691 Jul 18 08:45 IF-MIB.txt-rw-r--r-- 1 root root 6260 Jul 18 08:45 INET-ADDRESS-MIB.txt-rw-r--r-- 1 root root 26781 Jul 18 08:45 IP-FORWARD-MIB.txt-rw-r--r-- 1 root root 23499 Jul 18 08:45 IP-MIB.txt-rw-r--r-- 1 root root 15936 Jul 18 08:45 IPV6-ICMP-MIB.txt-rw-r--r-- 1 root root 48703 Jul 18 08:45 IPV6-MIB.txt-rw-r--r-- 1 root root 2367 Jul 18 08:45 IPV6-TC.txt-rw-r--r-- 1 root root 7257 Jul 18 08:45 IPV6-TCP-MIB.txt-rw-r--r-- 1 root root 4400 Jul 18 08:45 IPV6-UDP-MIB.txt-rw-r--r-- 1 root root 1174 Jul 18 08:45 RFC-1215.txt-rw-r--r-- 1 root root 3067 Jul 18 08:45 RFC1155-SMI.txt-rw-r--r-- 1 root root 79667 Jul 18 08:45 RFC1213-MIB.txt-rw-r--r-- 1 root root 147822 Jul 18 08:45 RMON-MIB.txt-rw-r--r-- 1 root root 4628 Jul 18 08:45 SMUX-MIB.txt-rw-r--r-- 1 root root 15490 Jul 18 08:45 SNMP-COMMUNITY-MIB.txt-rw-r--r-- 1 root root 20750 Jul 18 08:45 SNMP-FRAMEWORK-MIB.txt-rw-r--r-- 1 root root 5261 Jul 18 08:45 SNMP-MPD-MIB.txt-rw-r--r-- 1 root root 19083 Jul 18 08:45 SNMP-NOTIFICATION-MIB.txt-rw-r--r-- 1 root root 8434 Jul 18 08:45 SNMP-PROXY-MIB.txt-rw-r--r-- 1 root root 21495 Jul 18 08:45 SNMP-TARGET-MIB.txt-rw-r--r-- 1 root root 38035 Jul 18 08:45 SNMP-USER-BASED-SM-MIB.txt-rw-r--r-- 1 root root 33430 Jul 18 08:45 SNMP-VIEW-BASED-ACM-MIB.txt-rw-r--r-- 1 root root 8263 Jul 18 08:45 SNMPv2-CONF.txt-rw-r--r-- 1 root root 25052 Jul 18 08:45 SNMPv2-MIB.txt-rw-r--r-- 1 root root 8924 Jul 18 08:45 SNMPv2-SMI.txt-rw-r--r-- 1 root root 38034 Jul 18 08:45 SNMPv2-TC.txt-rw-r--r-- 1 root root 3981 Jul 18 08:45 SNMPv2-TM.txt-rw-r--r-- 1 root root 10765 Jul 18 08:45 TCP-MIB.txt-rw-r--r-- 1 root root 2058 Jul 18 08:45 UCD-DEMO-MIB.txt-rw-r--r-- 1 root root 3131 Jul 18 08:45 UCD-DISKIO-MIB.txt-rw-r--r-- 1 root root 2928 Jul 18 08:45 UCD-DLMOD-MIB.txt-rw-r--r-- 1 root root 8037 Jul 18 08:45 UCD-IPFWACC-MIB.txt-rw-r--r-- 1 root root 30343 Jul 18 08:45 UCD-SNMP-MIB.txt-rw-r--r-- 1 root root 4076 Jul 18 08:45 UDP-MIB.txt
