The question about the snmp configure

Published on by dellpe

Question:

Since using version 5 I have one recurring issue with a couple of Cisco WS-C3750X-48T-L Stacks. When it runs the scan it returns the model and IOS version but no interfaces.

After the scan snmp no longer works on the stack reporting 'queue length full' errors until I either restart snmp on the stack or reload the stack (which I don't want to do)

The strange thing is that polling the same devices with Solarwinds NPM causes no problems and also gathering the information into racktables (which definately uses the same OID 1.3.6.1.4.1.9.1.516) cause no issues of this type

Answer:

Simple Network Management Protocol (SNMP) uses the default UDP port 161 for general SNMP messages and UDP port 162 for SNMP trap messages.

I would say you don't need to create groups/users. This is only if you want to work with different SNMP Agents or if you want to use an access policy for more than one user. SNMPv3 provides secure access to devices by authenticating and encrypting packets.

You can create snmp groups just for management like I see, to create different SNMP views/access to your device. I never used it before...

If you see the command "snmp-server engineID", I'm sorry I don't understand that too...

To create groups and users pls use:

snmp-server group groupname {v1 | v2c | v3 {auth | noauth | priv}} [read readview] [writewriteview] [notify notifyview] [access access-list]

snmp-server user username groupname {remote host [udp-port port]} {v1 [access access-list] | v2c [access access-list] | v3 [encrypted] [access access-list] [auth {md5 | sha} auth-password]}

Example(No authentication no access-list...):

snmp-server group test v1 read test

snmp-server user test test v1

For example:

Router(config)#snmp-server community public RO

Router(config)#snmp-server community Q@W123EAS RW

Router(config)#snmp-server host 172.18.42.10 public

Router(config)#snmp-server enable traps

Published on Cisco 3750

To be informed of the latest articles, subscribe:
Comment on this post