Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help!! PP8k - How do you config SNMP Communities w/3.7 code?

Status
Not open for further replies.

dane775

Technical User
Oct 28, 2004
151
CA
This is getting confusing, the PDFs for this stuff seem to bounce back and forth with the commands you use between 3.3, 3.5, 3.7, and 4.0.

If I want to run SNMP version 1 & 2 (no version 3) and I'm running 3.7 code, what commands would I use to config the following: Read/Write Access/all (rwa) community string = "hilevel"

With the older code the command would've been:

config sys set snmp community rwa hilevel

The PDFs bounce back and forth when indicating whether or not those commands exist.

It looks like for 3.7 code you start with:

config snmp-v3 community create ???

That's as far as I get.

By the time you get back to 4.0 code...config sys snmp commands are back.

Am I going crazy or what? Any help would be greatly appreciated. I'm sure if I search hard enough I'll find the right doc, but I'm not having much luck so far.
 

Figured it out...

The indexes that point to public and private are called "first" and "second" respectively. You can't see the public and private community strings but you can change the name associated with the indexes "first" and "second" with the community new-name command.

If you want to disable some of the other access levels (l1, l2, etc.) you need to delete the indexes: Index1, Index2, and Index6.

Later All...
 
The schizophrenic code changes are because the
4.0 code branch is based on the 3.5 code branch,
which is also why there are a lot of features
in 3.7.x that are not in 4.0.x
The 4.1 code branch will merge 3.7 and 4.0
features, plus other cool stuff like flow-based
monitoring.

I'm glad to hear that we can delete those unused
access levels, its something I've been complaining
about since 3.1
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top