Cisco GSS Administration Guide (Software Version 2.0)
Configuring SNMP
Downloads: This chapterpdf (PDF - 154.0KB) The complete bookPDF (PDF - 5.14MB) | Feedback

Configuring SNMP

Table Of Contents

Configuring SNMP

Overview

Configuring SNMP on the GSS

Configuring SNMP Servers

Configuring SNMP Server Notifications

Configuring SNMP Server Trap Limits

Specifying Recipients for SNMP Notification Operations

Viewing SNMP Status

Viewing MIB Files on the GSS


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:

Overview

Configuring SNMP on the GSS

Configuring SNMP Servers

Configuring SNMP Server Notifications

Configuring SNMP Server Trap Limits

Specifying Recipients for SNMP Notification Operations

Viewing SNMP Status

Viewing MIB Files on the GSS

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, ucd-snmp v4.2.3, to query other GSS devices for standard MIB resources found in MIB-II (RFC-1213) and Host Resources MIB (RFC 2790). 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.

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 Be aware that existing, pre-v2.0, SNMP community, contact, and location configurations are retained after a v2.0 software upgrade. For example, if you have configured a company contact in v1.3 and then upgrade to GSS v2.0, that contact will be retained after the v2.0 upgrade is completed.


Use the snmp command in global configuration mode to enable SNMP on your GSS device. To disable SNMP on the GSS, use the no form of this command.

To configure SNMP for a GSS device, perform the following steps:

1. Log in to the CLI and enable privileged EXEC mode.

gss1.example.com> enable
gss1.example.com# 

2. Access global configuration mode.

gss1.example.com# config
gss1.example.com(config)# 

3. Enable the SNMP agent by using the following command.

gss1.example.com(config)# snmp enable

Note In the pre-v2.0 GSS software, a default community string is set to public after you enable SNMP. After a v2.0 software upgrade, however, no default community string is set when you enable SNMP.

You can add the public community string manually in the v2.0 software 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 v2.0 software upgrade.


4. Specify an SNMP community name for this GSS device by using the snmp community-string command. Each GSS device then becomes part of the named community. To change the SNMP community string, enter an unquoted text string with no space and a maximum length of 32 characters.

When you configure a community-string, location, and SNMP contact, you have two different options available on the GSS. You can configure them by using either the pre-v2.0 software CLI or the new v2.0 software CLI:

a. Using the pre-v2.0 CLI, configure a contact person for this GSS device with the snmp contact command. You can include information on how to contact a person; for example, a phone number or e-mail address. Enter an unquoted text string with a maximum of 255 characters including spaces.

gss-pilot1.cisco.com#
gss-pilot1.cisco.com# conf
gss-pilot1.cisco.com(config)# snmp contact
Enter new Contact Info: Joe Smith jsmith@cisco.com
gss-pilot1.cisco.com(config)#

b. Using the v2.0 CLI, configure a contact for this GSS device with the snmp-server contact command. Enter an unquoted text string with a maximum of 255 characters without any spaces.

gss-pilot1.cisco.com#
gss-pilot1.cisco.com# conf
gss-pilot1.cisco.com(config)# snmp-server contact 
JoeSmith-jsmith@cisco.com
gss-pilot1.cisco.com(config)#

5. Disable SNMP or any of the parameters outlined above by using the no form of the snmp command. For example, to disable the SNMP contacts for the GSS, enter:

gss1.example.com(config)# no snmp contact

Configuring SNMP Servers

You can configure SNMP server information, locations, and names on your GSS device by using the snmp-server command in global configuration mode. To remove the server information, use the no form of this command.

To configure SNMP server information for a GSS device, perform the following steps:

1. Log in to the CLI and enable privileged EXEC mode.

gss1.example.com> enable
gss1.example.com# 

2. Access global configuration mode.

gss1.example.com# config
gss1.example.com(config)# 

3. Enable the SNMP agent by using the following command:

gss1.example.com(config)# snmp enable

4. Configure SNMP server information by using the following command:

gss1.example.com(config)# snmp-server

5. Specify an SNMP community name for this GSS device by using the community command and an unquoted text string with no spaces and a maximum of 32 characters.

gss1.example.com(config)# snmp-server community MyCommunity

6. Specify a location by using the location command and the location itself. The maximum length of the location is 255 characters.

gss1.example.com(config)# snmp-server location Boxborough

7. Disable the SNMP server or any of the parameters outlined here by using the no form of the snmp-server command. For example, to disable the SNMP location for the GSS, enter:

gss1.example.com(config)# no snmp-server community MyCommunity

Configuring 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. Log in to the CLI and enable privileged EXEC mode.

gss1.example.com> enable
gss1.example.com# 

2. Access global configuration mode.

gss1.example.com# config
gss1.example.com(config)# 

3. Enable the SNMP agent by using the following command:

gss1.example.com(config)# snmp enable

4. Enable SNMP server notifications by entering the snmp-server enable-traps command and following it with one of the available options:

gslb—Enables all SNMP GSLB notifications.

gslb dns—Enables SNMP DNS server notification.

gslb kal—Enables SNMP GSLB keepalive notification.

gslb peer-status—Enables SNMP GSLB peer-status change notification.

core—Enables SNMP core-file discovery notification.

snmp—Enables all SNMP agent notifications.

snmp authentication—Enables only SNMP agent authentication notification.

gss1.example.com(config)# snmp-server enable-traps kal

5. Disable SNMP server notifications by using the no form of the snmp-server enable-traps command. For example, to disable SNMP GSLB keepalive notification, enter:

gss1.example.com(config)# no snmp-server enable-traps gslb kal

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. Log in to the CLI and enable privileged EXEC mode.

gss1.example.com> enable
gss1.example.com# 

2. Access global configuration mode.

gss1.example.com# config
gss1.example.com(config)# 

3. Enable the SNMP agent by using the following command:

gss1.example.com(config)# snmp enable

4. Enable SNMP server trap limits by entering the snmp-server trap-limit command and following it with one of the available options and a specified value:

answer-trap value—Configures a rate-limit for the answer trap.

dns-clause-trap value—Configures the rate-limit for DNS clause traps.

keepalive-trap value—Configures the rate-limit for the keepalive trap.

gss1.example.com(config)# snmp-server trap-limit answer trap 10

5. Set the default trap rate by using the no form of the snmp-server trap-limit command as follows:

gss1.example.com(config)# no snmp-server trap-limit answer-trap

Specifying 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. Log in to the CLI and enable privileged EXEC mode.

gss1.example.com> enable
gss1.example.com# 

2. Access global configuration mode.

gss1.example.com# config
gss1.example.com(config)# 

3. Enable the SNMP agent by entering the following command:

gss1.example.com(config)# snmp enable

4. Specify the recipients of SNMP notification operations by using the snmp-server host command and a host-address and a community-string.

gss1.example.com(config)# snmp-server host 10.1.1.1 MyCommunity

5. Send SNMP traps to the specified host by entering the following command:

gss1.example.com(config)#snmp-server host 10.1.1.1 MyCommunity 
traps

Note You can configure a maximum of 10 hosts for traps notification.


6. Specify the version of the SNMP protocol used to send the traps by entering the version command and one of the available keywords:

1—Specifies SNMPv1 (the default).

2—Specifies SNMPv2c.

gss1.example.com(config)# snmp-server host 10.1.1.1 MyCommunity 
traps version 2

7. Specify the host UDP port to use by entering the udp-port command and the port number.

gss1.example.com(config)# snmp-server host 10.1.1.1 MyCommunity 
traps version 2 udp-port 500

8. Remove the recipient of an SNMP notification by using 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 100

Viewing SNMP Status

Once SNMP is enabled, you can display the SNMP status on your GSS device by using the show snmp command. Verify that your SNMP agent, ucd-snmp v4.2.3, is enabled or disabled, as well as the configured names of the community-string, location, and contact.


Note You can also use the show services command to verify if SNMP is enabled or disabled.


For example, enter:

gss1.example.com# show snmp 
SNMP is enabled
sys contact: JSmith jsmith@cisco.com
sys location: Boxborough

0 SNMP packets input
        0 Bad SNMP versions
        0 Unknown community name
        0 Illegal operation for community name supplied
        0 Encoding errors
        0 Number of requested variables
        0 Number of altered variables
        0 Get-request PDUs
        0 Get-next PDUs
        0 Set-request PDUs
0 SNMP packets output
        0 Too big errors
        0 No such name errors

        0 Bad values errors
        0 General errors


Community
---------
public

Host                            Port Version  Type
----                            ---- -------  ----
16.1.1.11                       162  v2c      trap

Trap type				Enabled
---------				-------
GSLB KAL transition	Yes
GSLB system core file discovery	Yes
GSLB system peer transition	Yes
SNMP authentication	Yes
gss1.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 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 /mibs
total 1100
drwxr-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