• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Cisco Extended ACLs with SNMP

phatrabt

Senior member
Just ran across this today when working on a 7609. It seems that when inputting a snmp-server community string I can only use a standard ACL and not extended. Is this a bug? Is there a workaround? Thanks all!
 
An extended ACL isn't needed. So no reason to have one. You're just telling the device what hosts can send SNMP commands to it.
 
Originally posted by: spidey07
An extended ACL isn't needed. So no reason to have one. You're just telling the device what hosts can send SNMP commands to it.

Correct, but you can use name-based ACLs above a certain minor IOS revision -- 12.3(16) rings a bell but... don't quote me on that. :S

You can also define views based on ACLs if you need to secure certain parts of the tree.
 
Originally posted by: phatrabt
Just ran across this today when working on a 7609. It seems that when inputting a snmp-server community string I can only use a standard ACL and not extended. Is this a bug? Is there a workaround? Thanks all!

Why do you need extended-ACL on a community string?
 
Back
Top