Answers: SNMPv2c Secured with ACLs

By Chris July 29, 2016 13:10

This latest lab lets you practice configuring SNMP. At the same time, it lets you configure restrictions so that only some devices are allowed to even use SNMP with the routers in the lab. Check out the lab requirements first, write down your own answer, and then come back here to check your answer.


Figure 1: Two Routers with IP Addresses

Example 3: R1 Config

Example 4: R2 Config



With SNMP version 2c (SNMPv2c), the only security mechanism was to use a simple text password called a community string. Any NMS with knowledge of the read/write community could then change anything accessible to the SNMP agent on the device, which on Cisco routers and switches includes the configuration. Further securing SNMPv2c by restricting the IP addresses allowed to connect to the router makes sense. (Using SNMPv3 makes even more sense.)

In this case, the snmp-server community commands end with a “1”, which refers to access-list 1. ACL 1 permits all traffic from subnet, that is, from the subnet in which the NMS resides. Without the “1” on the end, these first two commands would have enabled SNMP, with no ACL to restrict acces, so that anyone who knew the very poorly chosen community values of “readonly” and “readwrite” would have access to the routers using SNMP.

The two remaining commands on each router simply set the location and contact, which SNMP will use as values for two different SNMP variables.

SNMPv2c Secured with ACLs
Answers: IPv6 Static Routes 3
By Chris July 29, 2016 13:10
Write a comment

No Comments

No Comments Yet!

Let me tell You a sad story ! There are no comments yet, but You can be first one to comment this article.

Write a comment
View comments

Write a comment

Comment; Identify w/ Social Media or Email


Subscribe to our mailing list and get interesting stuff and updates to your email inbox.

Thank you for subscribing.

Something went wrong.