| I'm a little confused by your note. Your title asks, "How to change
Read Only community" yet the content of your note says your customer
wants to "change the Read/Write Community but leave the Read Only as
"public'". I'm just going to spew out some facts and hope I hit on
answering your question.
To change the read-only community you must set the
"pcomSnmpAuthReadOnlyCommunity" object. This object is in a MIB called,
"dec-hub900-hubmgr-mib-v1-1.txt". The MIB is available via anonymous
ftp to gatekeeper.dec.com. You can't use the console to change the
read-only community. It was not deemed important or common enough to
warrant a menu item on the console.
To change the read-write community and leave the read-only community
unchanged use the console to change the read-write community. The read-only
community will remain unchanged. Objects may still be read using
the read-only community ("public"). Sets may only be done using the
read-write community (whatever the customer selects).
Changing the read-only community without changing the read-write community
has no affect. In other words, when the read-only community is "secret"
and the read-write community is "public" users will still be able to
(as the name implies) read and write using the community "public".
(Okay it has a subtle affect. Users who use community "secret" will only
be able to read.)
There is currently a bug in the Management Agent Module (MAM) which causes
us to recommend that users reset the MAM after changing its read-write
community. (Note: you don't have to reset a line-card after changing
its read-write community - only the MAM.) See note 1517.6 for more detail.
-Shawn
|
| Shawn,
Thanks for spewing out the facts. You hit it right on the money. My
customer was concerned about intruders if he left the community name
Read/Write as "public". So all we do is change the community name via
console port, and Read only stays public. Exactly what the doctor
ordered. Thanks again.
Ed
|