Basic SNMP Config 1

Interestingly, Cisco added a couple of smaller management-oriented protocols – including SNMP – to the CCNA R&S exam mix when they changed the exams back in 2013 (exams 100-101, 200-101, 200-120). SNMP which allows management software to send and receive status and configuration data with the various devices in the network. Those devices typically need a small bit of SNMP configuration before they will communicate with the management station; this next lab lets you review some of the common configuration elements for SNMP.

Requirements

For this lab, enable SNMP on the two routers shown in the figure, so that the Network Management Station (NMS) in Raleigh can manage the routers. In particular:

• Use SNMP version 2c
• Configure so that the NMS can change the router’s configuration when using a password-like value of ‘CFG’
• Configure so that the NMS can view the router’s status information using a password-like value of ‘VIEW’
• Set a MIB variable that represents the location of router R1 as ‘Cincinnati’, and R2 as ‘Raleigh’
• Set a MIB variable that represents the contact for the R1 router be ‘Chris’, and R2 be “Sean”
• Assume that all router interfaces work, have IP addresses, and that IP connectivity exists between the NMS and the router interfaces.

Figure 1: Two Routers with IP Addresses

Initial Configuration

Example 1 and 2 show the beginning configuration state of R1 and R2. Note that beyond the interface IP address configuration, both routers use EIGRP to exchange routes.

Example 1: R1 Config

hostname R1
!
interface GigabitEthernet0/1
 ip address 192.168.1.1 255.255.255.252
 no shutdown
!
interface GigabitEthernet0/2
 ip address 192.168.1.65 255.255.255.192
 no shutdown
!
router eigrp 1
 network 192.168.1.0

Example 2: R2 Config

hostname R2
!
interface GigabitEthernet0/0
 ip address 192.168.1.2 255.255.255.252
 no shutdown
!
interface GigabitEthernet0/2
 ip address 192.168.1.129 255.255.255.192
 no shutdown
!
router eigrp 1
 network 192.168.1.0

Answer on Paper, or Maybe Test in Lab

Next, write your answer on paper. Or if you have some real gear, or other tools, configure the lab using them.

If you do try this on real gear, the trick is to test the ability to retrieve SNMP data using the SNMP GET protocol message. To do that, try searching for tools online like snmpget and snmpwalk. These tools let you send SNMP GET messages without a full-fledged NMS installed. In particular, if you text in a lab with a Linux host or VM available, snmpwalk -v 2c -c string ip-address. Begin with a ping of the router IP address, to make sure connectivity exists. If that works, then configure SNMP (that is, do this lab). After that, try one of the command line SNMP tools (e.g., snmpwalk), and your SNMP test will hopefully work.

Do this Lab with Cisco’s VIRL

You can do these labs on paper and still get a lot out of the lab. As an extra help, we have added files for the Virtual Internet Routing Lab (VIRL) software as well. The .VIRL file found here is a file that when used with VIRL will load a lab topology similar to this lab’s topology, with the initial configuration shown in the lab as well. This section lists any differences between the lab exercise and the .VIRL file’s topology and configuration.

Download this lab’s VIRL file!

Network Device Info

All interfaces in topology match the lab figure.

Host Device Info

This table lists host information pre-configured in VIRL, information that might not be required by the lab but may be useful to you.

Handy Host Commands:

To see PC IP address: ifconfig eth1

Ping example: ping -c 4 10.1.1.1

Trace example: traceroute 10.1.1.1

To connect to another node within the topology: telnet 10.1.1.1