SNMP Version 3 Tools Implementation Guide
SNMP Version 3 Tools Implementation Guide
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
© 2022 Cisco Systems, Inc. All rights reserved.
Preface
This preface includes the following sections:
• Obtaining Documentation and Submitting a Service Request, on page iii
• Obtaining Additional Tools Application Documentation, on page iii
Cisco has tested these tools for interoperability between the NMS and the ASA.
Network Topology
The following figure shows the network topology for implementing SNMP Version 3.
ASA Setup
The ASA requires that you configure the SNMP server group, the SNMP server user associated with the
group, and the SNMP server host, which specifies the user for receiving SNMP traps.
To configure SNMP Version 3 operations, the required sequence of commands is as follows:
• snmp-server group
• snmp-server user
• snmp-server host
ciscoasa# snmp-server user md5des authPriv v3 auth md5 mysecretpass priv des passphrase
ciscoasa# snmp-server user md5user authNoPriv v3 auth md5 mysecretpass
ciscoasa# snmp-server user noauthuser noAuthNoPriv v3
Net-SNMP
Net-SNMP Version 5.1.2 provides the following tools and libraries:
• An extensible agent
• An SNMP library
• Tools to request or set information from SNMP agents
• Tools to generate and handle SNMP traps
You can download the Net-SNMP network management tool from the following URL: http://sourceforge.net/
projects/net-snmp/
This section includes the following topics:
• Polling a MIB
• Sending a Trap
Polling a MIB
To poll a MIB, after you have finished configuring the ASA, run the snmpwalk command from the NMS to the ASA:
Note No specific configuration is required for Net-SNMP on Linux when you run the snmpwalk command.
Sending a Trap
When the ASA sends a trap, it is authoritative, which means that the user created within the snmptrapd
command must be associated with the EngineID sending the trap.
To establish this association, perform the following steps:
For this statement, define the listed parameters, which include the following:
• ENGINEID—The EngineID of the application that is going to be sending the trap
• myuser—The USM username that is going to be sending the trap
• authentication protocol—The authentication type (SHA or MD5, with SHA the preferred setting.)
• “my authentication pass”—The authentication pass-phrase to use to generate the secret authentication key. Enclose
the pass-phrase in quotation marks if it includes spaces.
• privacy protocol—The encryption type to use (AES or DES, with AES the preferred setting)
• “my privacy pass”—The encryption pass-phrase to use to generate the secret encryption key. Enclose the pass-phrase
in quotation marks if it includes spaces. If you do not enclose the encryption pass-phrase in quotation marks, it is
set to the same value as the authentication pass-phrase.
Step 4 Run the snmptrap command from the ASA to send a linkdown or linkup trap by entering the following commands:
Running SilverCreek
To run the SilverCreek software, choose Start > All Programs > SilverCreekMx Evaluation > Run Test
Suite and Tools (Start Here).
When the application starts, along with the SilverCreek main window, a console window appears that shows
the following information:
• Logging messages
• Debugging messages
• Other message exchanges that occur between the NMS and the SNMP Version 3 agent
• MIBs that are loaded
Step 2 Enter the hostname or the IP address, port number, and SNMP Version 3 parameters.
After the agent is connected, as shown in the following figure, you can run SNMP test suites from the Test Suites tab in
the left pane.
Step 1 To manually load and delete MIBs, choose MIB > Load | Delete MIBs.
Step 2 To view the loaded MIBs, click View Loaded Modules.
You can maintain all the MIB files in the default mibs directory, which is defined by the environment variable, MIB_PATH.
Step 1 In the main window, select a test category (for example, MIB-II tests) in the left pane (see figure below).
The list of available tests for the selected test category appears in the right pane, and test details appear in the bottom
pane.
Step 2 Select a single test or multiple tests, and click Run All or Selected Tests.
The test status appears in the Status column. The total number of tests run, passed, failed, and so on appears at the bottom
of the window.
Enabling Debugging
The following figure shows the warning message that appears to indicate that the test runs more slowly with debugging
turned on.
The following figure shows the console dialog box that lists the debugging messages, which appear when you run a test.
Testing MIBs
To test MIBs, perform the following steps:
Step 1 In the left pane of the main window, click the MIB Testing tab.
All the MIB modules that are loaded and available for testing appear.
Step 2 Click the radio buttons for the MIBs that need to be tested.
Step 3 In the right pane, select the tests that need to be run.
The purpose and details of the tests appear in the bottom pane.
Figure 12: MIB Browser: Local MIB Tree Mode Dialog Box
Step 2 Scroll down to the OID, .iso.org.dod.internet.mgmt.mib-2.system and right-click system; then choose the option to walk
this tree.
The MIB browsing results appear in the right pane, as shown in the following figure.
Figure 13: MIB Browser: Local MIB Tree Mode Dialog Box Showing MIB Results
Note See the Release Notes for the Cisco ASA 5500 Series for a list of the open caveats that apply to SNMP MIBs.
Testing Performance
To test performance, perform the following steps:
Step 1 Choose Tools > Performance Monitoring Tool, select an operation that you want to perform (for example, Walk
(get-bulks), and provide an Object name. You can run various commands multiple times.
Step 2 Click Send Synchronously.
The selected SNMP operations start. Results appear in a separate window.
The following example uses ifType, asks how many times you want to repeat the operation, and uses the value, 10.
Step 1 Click the Credentials link, and enter the SNMP device object ID information.
Step 2 Click the button next to the SNMP v1/v2/v3 credentials drop-down list and enter the username, authentication and
encryption algorithms, and corresponding passwords, then click OK.
Figure 20: Edit SNMP v3 Credential Type Dialog Box
The following figure shows the added SNMP Version 3 node on the network.
Figure 22: Network Explorer Window with Added SNMP Version 3 Node
Step 1 Choose Start > Programs > IpSwitch WhatsUp Gold v12.3 > WhatsUp Web Interface. You can perform SNMP
Version 3 walks and polls from this location.
Step 2 The following figure shows the initial login window. Enter the default username and password, which is “admin.”
Figure 23: WhatsUp Gold Login Window for Web Interface
The following figure shows the Home Workspace pane that appears after the user logs in.
Step 2 In the Network Tool: SNMP MIB Walker dialog box, enter the following information:
• The agent IP address or hostname
• The OID or MIB that needs to be walked
• The SNMP Version 3 credentials
Figure 27: Network Tool: SNMP MIB Walker Results - Tree View
Step 1 Choose Program Options > Passive Monitor Listeners > SNMP Trap > Configure.
The SNMP Listener Configuration dialog box appears. From here you can configure the listener port and forward traps
to a host.
Figure 30: SNMP Listener Configuration Dialog Box
Step 2 Click the Reports tab and select SNMP Trap Log.
Note See the Release Notes for the Cisco ASA 5500 Series for a list of the open caveats that apply to NNM 8.x.
Installing NNM
NNM 7.53 was tested on the Windows 2003 Server platform. A trial version with the required installation
instructions is available at the following URL:
https://h10078.www1.hp.com/cda/hpms/display/main/hpms_content.jsp?zn=bto&cp=1-11-15-119%5E1155_
4000_100__
Step 1 From the command prompt of the NNM server, choose one of the following:
• Start > Programs > HP OpenView > Network Node Manager Admin > Network Node Manager.
• Double-click the ovw.exe file, located in C:\Program Files\HP OpenView\bin.
The Root window appears, with the Internet map icon displayed.
Figure 33: NNM Console Root Window
Loading MIBs
To load MIBs, perform the following steps:
Step 1 In the NNM main window, choose Options > Load/Unload MIBs:SNMP.
A list of currently loaded MIBs appears.
Step 2 Click Load to select additional MIBs from the server file system.
Step 1 Find the IP address and hostname of at least one high-traffic device within the network that you want to add
Step 2 In the Internet-level submap, choose Edit > Add Objects.
The Add Object Palette dialog box appears.
Step 3 Click the Connector Symbol Class icon, and drag the Gateway Symbol Subclass icon onto the Internet-level submap.
Choose this gateway connector, regardless of the type of device you are using to start the discovery.
The Add Object dialog box appears.
Step 5 Type the IP address and hostname of an SNMP-enabled device within the network that you want to add to your management
domain, and click Verify.
Step 6 After NNM checks the configuration, NNM corrects the symbol choice and (if necessary) its placement for you. The
device is now configured to be managed by NNM and should be visible on the Internet map.
Note When you set SNMP Version 3 credentials, you must use the overloaded SNMP string. For more information,
see Step 2 in the Configuring the NNM MIB Browser.
Step 1 From the Internet map, drill down to a specific node for a view of all available interfaces.
Step 2 To view additional interface information, right-click an interface, then choose Interface Properties or Interface Status.
The Network Interface Properties dialog box appears.
Step 1 From the NNM server command prompt, start the MIB Browser, located in C:\Program Files\HP
OpenView\bin\xnmbrowser.exe.
Step 2 Enter the IP address of the SNMP host and the community string. For SNMP Version 3 connections, the community
string uses the syntax for the overloaded community string.
The following is an example of the syntax used for the overloaded community string:
SNMPv3 noAuthNoPriv
3N[/KEEP]/[ [contextEngineID] [-contextName]/ ]username
SNMPv3 authNoPriv
3A[;[MD5ˆ|SHAˆ]authKey[/KEEP]]/[ [contextEngineID] [-contextName]/
]username
SNMPv3 authPriv
3P[;[MD5ˆ|SHAˆ]authKey[;[DESˆ|AESˆ|3DESˆ]privKey][/KEEP]]/[
[contextEngineID] [-contextName]/ ]username
Note The default authentication is MD5, and the default encryption is DES.
Step 1 To configure the UUT group, enter the snmp-server group asanoauth v3 noauth command.
Step 2 To configure the UUT user, enter the snmp-server user titannoauth asanoauth v3 command.
Step 3 For the community name, enter 3N/titannoauth.
Step 1 To configure the UUT group, enter the snmp-server group asaauth v3 auth command.
Step 2 To configure the UUT user, enter the snmp-server user titanauth asaauth v3 auth md5 authpass command.
Step 3 For the community name, enter 3A:authpass/titanauth.
Step 1 To configure the UUT group, enter the snmp-server group asaauth v3 auth command.
Step 2 To configure the UUT user, enter the snmp-server user titanshaauth asaauth v3 auth sha authpass command..
Step 3 For the community name, enter 3A:SHA^authpass/titanshaauth.
Step 1 To configure the UUT group, enter the snmp-server group asapriv v3 priv command.
Step 2 To configure the UUT user, enter the snmp-server user titandes asapriv v3 auth md5 authpass privdes privpass
command.
Step 3 For the community name, enter one of the following:
• 3P:authpass:privpass/titandes
• 3P:MD5^authpass:DES^privpass/titandes
Step 1 To configure the UUT group, enter the snmp-server group asapriv v3 priv command.
Step 2 To configure the UUT user, enter the snmp-server user titanshades asapriv v3 auth sha authpass privdes privpass
command.
Step 3 For the community name, enter 3P:SHA^authpass:DES^privpass/titanshades.
Browsing a MIB
To browse a MIB, perform the following steps:
Step 1 Drill down to the OID, .iso.org.dod.internet.mgmt.mib-2.system, and select the system object.
Step 2 Click Start Query to fill in the MIB Values field with the DUT description.
Step 1 Make sure that the SNMP Version 3 credentials of a user on the SNMP agent are cached in the NNM.
Step 2 When using the MIB Browser to query an SNMP agent, enter the following community string:
3P:authpass:privpass/KEEP/titandes
Note By using the KEEP parameter in the overloaded community string, you save the user credentials in the NNM
configuration file, which is required because secure SNMP Version 3 traps and inform requests are sent from
the SNMP agent to the NNM, and authentication must occur. The user information is included in the configuration
file, located in C:\etc\srconf\mgr\mgr.cnf. You can modify this file directly. For instructions, see the NNM SPI
SNMP Version 7.53 documentation.
Alternatively, you can use the snmpget command, as shown in the following example:
C:\Program Files\HP OpenView\bin>snmpget-c “3P;MD5^authpass;DES^privpass/KEEP/titandes”
10.0.0.33 sysDescr.0
Step 3 To configure the SNMP agent to send traps, enter the following command on the ASA:
cicoasa (config)# snmp-server host inside 10.0.0.10 traps version 3 titandes
Note The command syntax may differ slightly between ASA platforms. The user configured in this example is the
same as the user defined in the community string in the Configuring the NNM MIB Browser.
The NNM traprcv utility is a command-line tool that receives SNMP trap messages and responds to SNMP inform requests
from remote SNMP entities. It binds to the SNMP trap port (udp/162) to listen for notifications, and as a result, must be
run as root. It prints standard output messages about the notifications that it has received. The traprcv utility can receive
SNMP Version 1 traps, SNMP Version 2c traps, SNMP Version 2c inform requests, SNMP Version 3 traps, and SNMP
Version 3 inform requests. For more information, see the NNM SPI SNMP Version 7.53 documentation.
Step 4 Run the traprcv utility and wait for traps on the SNMP agent. The utility is available at the following location: C:\Program
Files\HP OpenView\snmpv3\utils\traprcv.exe.
Figure 44: SNMP Trap Receiver
Step 3 To view node properties, double-click the selected node to open a new browser window with the node information.
CiscoWorks
CiscoWorks LAN Management Solution (LMS) is a suite of powerful management tools that simplify the
configuration, administration, monitoring, and troubleshooting of Cisco networks. For more information, see
the following URL: http://www.cisco.com/en/US/products/sw/cscowork/ps2425/index.html
This section includes the following topics:
Starting CiscoWorks
To start CiscoWorks on a Windows 2003 server, perform the following steps:
Choose Start > All Programs > CiscoWorks. The following figure shows the login page.
Step 2 Enter the IP address or device name or choose a device from the list in the Device Selector pane, and click Go.
Step 1 In the Functions Available pane, click the SNMP Walk link.
The SNMP Walk dialog box appears.
Step 2 Choose the SNMP version to use from the following options:
• For SNMP Version 3 (NoAuthNoPriv and AuthNoPriv Security Levels)
a. Enter the SNMPv3 Username.
b. Enter the SNMPv3 Auth Password.
c. Choose the SNMP v3 Auth Protocol from the drop-down list (either MD5 or SHA).
d. Enter the SNMP Context Name.
Note Because the ASA does not support contexts, you must leave the SNMP Context Name blank.
Note Because the ASA does not support contexts, you must leave the SNMP Context Name blank.
g. (Optional) Enter the starting OID. If you leave this field blank, the tool starts from 1.
h. Enter the SNMP Timeout. The default value is 10 seconds.
i. (Optional) Check the Output OIDs Numerically check box to print the output OIDs numerically.
j. By default, the corresponding OID name is printed in the output window.
k. (Optional) Check the Output Indexes Numerically check box to show the output index numerically.
l. (Optional) Check the Debug check box to enable the debugging option. All the fields are case-sensitive.
m. Click OK to obtain the results, which are based on the parameters that you entered.
n. When the walk is complete, save it as a text file.
Note A full walk may take a long time to finish.
The read-write username and password for SNMP Version 3 and the read-write community string for SNMP Versions
1 and 2c are case sensitive. The SNMP Walk dialog box displays the credentials (SNMP Versions 1, 2c, and 3) for the
device from the Device and Credential Repository (DCR), if they are available. Otherwise, the default values for the
respective SNMP versions appear.
If you use the SNMP Walk feature with Network Operator/Help Desk access privileges, device credential fetching fails
and the fields of the read/write community strings for SNMP Versions 1, 2c, and 3 credentials are set to default values.
The following figure shows the list of privacy protocols supported. You must manually enter SNMP Versions 1, 2c, and
3 credentials.
Figure 52: SNMP Walk Dialog Box
The following figure shows the SNMP walk results for the MD5 authentication and AES256 encryption algorithm settings.
Figure 54: SNMP Walk Results Dialog Box
The management station to device check occurs only for protocol connectivity. Credentials for the corresponding
protocols are not tested or verified. If you enter a hostname instead of an IP address, the tool performs a name
lookup to discover the address. This task fails if the tool cannot find an address.
You can use this tool to send an SNMP GET request to the destination device for an SNMP read test (SNMPR).
The tool also sends an SNMP SET request to the device for an SNMP write test (SNMPW). This protocol is
supported for SNMP Versions 1, 2c, and 3.
If you start the Management Station to Device tool with Network Operator/Help Desk access privileges, device
credential fetching fails and the fields of the read-write community strings for SNMP Versions 1, 2c, and 3
credentials are set to default values. You must manually enter SNMP Versions 1, 2c, and 3 credentials.
To start the Management Station to Device tool, perform the following steps:
Step 4 Choose the connectivity applications that you want to include from the following options. All fields are case sensitive.
• If you choose SNMP v3 (NoAuthNoPriv Security Level), enter the following information:
• Read Username.
• Write Username.
• Timeout (in seconds). The default value is two seconds.
• If you choose SNMP v3 (AuthNoPriv Security Level), enter the following information:
• Read Username.
• Read Auth Password.
• Read Auth Protocol. Choose either MD5 or SHA from the drop-down list.
• Write Username.
• Write Auth Password.
• Write Auth Protocol. Choose MD5 or SHA from the drop-down list.
• Timeout (in seconds). The default value is two seconds.
• If you choose SNMP v3 (AuthPriv Security Level), enter the following information:
• Read Username.
The Interface Test Results dialog box displays the results (see Figure 2-55). The Interface Details Results dialog box
shows the interfaces tested and the test results for each option.
Note The read-write username and password for SNMP Version 3 and the read-write community string for SNMP
Versions 1 and 2c are case sensitive.