Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

SNMP setting for discover metrics in CM ??? need help


I am facing a problem.

I install cisco works2000 . when I configure snmp setting option for discover metrics, i am face a problem.

In SNMP setting has option read and write community. all are know their setting by default public.

for security purpose i use in my device

snmp setting only read only like read community "cisco123"

when I setting only "cisco123" and write

community keep blank and save .

but after save i found in write community shows public. and for this reason i can not discover any device.

so my question is without write community , can i discover metrics ?? if possible how i can ?..

I expect experts are help me to provide the information.



Cisco Employee

Re: SNMP setting for discover metrics in CM ??? need help

Campus Manager only requires a valid read-only community string to perform discovery. If you have configured this correctly, and discovery is not finding your devices, then there is some other problem. What version of CiscoWorks are you using?

New Member

Re: SNMP setting for discover metrics in CM ??? need help


I uses CM 3.3

IN SNMP setting when i put readonly cisco123 and write community blank then after save it shows their "public"

but in my device I configure only

snmp-server community "cisco123" ro

NB: beside my switch have another string "noc123" ro so i should check multiple sting box check mark ?

I think you understand my problem.



Cisco Employee

Re: SNMP setting for discover metrics in CM ??? need help

The value of the read-write community string in Campus is not important if you are not using a read-write community string on the device. It will not hinder discovery.

You only need to enable multiple community strings if you have different community strings for the same range. For example, if you have two *.*.*.* entries, then you need to enable multiple community strings. If you are just using different community strings for different sections of your network, and you specify those sections with discrete ranges, then you do not need to enable multiple community strings. So:

*.*.*.* cisco123

*.*.*.* noc123

Requires multiple community strings. But:

10.*.*.* cisco123

11.*.*.* noc123

Does not.