cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
436
Views
0
Helpful
3
Replies

SNMP Community Strings

ksiow
Level 1
Level 1

Hi all,

How many community strings can be specified under CW2K -> Server Configuration -> Setup -> ANI Server Admin -> SNMP settings?

I've tried to specify 4 different lines but it doesn't work on all the devices; there's no discovery on all the devices on Campus Manager even the SNMP community strings are correct. The ANI Server cannot discover all the devices in the network (mostly are missing from the map) or marked the devices unreachable (a box with Question mark). FYI, it's only takes the first line, "public0" and all devices under this community strings are able to be discovered.

*.*.*.*:public0::::::private0

*.*.*.*:public1::::::private1

*.*.*.*:public2::::::private2

*.*.*.*:public3::::::private3

How should I put all these 4 different community strings in SNMP settings for ANI?

Appreciates and Regards,

Kevin

3 Replies 3

rmushtaq
Level 8
Level 8

Campus Manager only uses the RO string for doing the discovery. Also have you checked to see that the devices which are showing up in the topolgy map as '?' are listed in the supported device list of Campus Manager?. You can have multiple strings defined under the ANI SNMP settings for discovery. You can add a combination of general and specific entries, but the ANI Server reads the community strings from most specific to least specific. Also make sure that you enter the correct number of colons between entries. If you incorrectly add or delete colons, the ANI Server cannot correctly read the community strings. If you enter duplicate community strings for the same device, the most specific community string is used.

Some additional useful related information including troubleshooting:

http://www.cisco.com/warp/public/cc/pd/wr2k/cpmn/prodlit/wk2ke_wp.htm

http://www.cisco.com/warp/public/477/Campus/ani.shtml

Let me restate what was said above. Since you have *.*.*.*, this will match every IP address, so the discovery process will not look any further. If you have different community strings, you must be more specific on IP addresses, and you cannot use a global wildcard.

Hope this helps.

You actually can use the global wildcard, you just can't use more than one global wildcard. What the ANI Server will do is look for the most specific entry so with the lines

10.1.2.3:public2::::::public2

*.*.*.*:public1::::::public1

10.1.2.3 will use public2 while all others will use public1. When you have two lines that are global wildcards, ANI will only use the first one and ignore the second. Either you have to specify each device seperately or somehow differentiate which devices should be tried with which strings, i.e.

10.1.2.3:public0::::::private0

10.1.2.*:public1::::::private1

10.1.3.*:public2::::::private2

10.2.*.*:public3::::::private3

*.*.*.*:public4::::::private4

The RME sychronization will put an entry for each device in RME. This may help if you have already specified the community strings in RME.

-Dave