SNMP Issue - server "accepted community name" values

[Wade_13]

When running "configure or repair agents" using the CMS, the target server being repaired accepted community names read-write value is being set to the following number: 9bfdf5fc-674f-408d-a905-fd4993884df1

How can I set the CMS to push the read-write value that's correct for our network? The read-only community name is being set properly and the snmp-trap agent community and desitnation values are being set properly.

The global properties settings have both read and write community strings set correctly in the CMS.

Any ideas why I receive that random number when reparing SNMP community values?

Thanks for your time,

Wade

[Wade_13]

Also, its seems the read-write community name being push out via the CMS is always a different number whether it is being pushed out to the same target or different targets.

Wade

[David Claypool · Accepted solution]

Keep in mind that HP SIM doesn't require an SNMP write string; it only ever does read operations using SNMP. However, the different agent modules use SNMP to flag things among themselves. The write string is internal and never happens on the wire.

With "C or R A" if a write string already exists, it will leave it alone. In the absence of one, one gets set, but in order to avoid introducing a potential security hole, a long, random string is used.

If you have a purpose for using SNMP writes outside the scope of HP SIM usage, once the "C or R A" has run, you have a trust relationship established that allows you to replicate the SNMP strings to all your servers.

So, if you have the correct write string set in your build process and thereafter need to use "C or R A" it will leave it alone. If you don't have a right string set, you end up with a trust relationship that lets you set it from within HP SIM.

[Wade_13]

Thanks David!