96
If the NMS appears in the SNMP Communities multiple times, using the same
community, the entry with the highest priority (lowest line number) is used to evaluate
the request though this community name.
If a NoAccess listing for the NMS appears anywhere in the table, the permissions
assigned by the global community names are negated. Any request from the NMS
using the global community names will be refused. In addition, only SNMP
Communities entries with higher priority are applicable. To complete SNMP get or
sets from this NMS, an entry above the NoAccess line must assign the NMS Read or
Read/Write permissions.
If the highest priority listing for an NMS in the SNMP Communities labels the
machine with access rights as NoAccess, no get/set requests from this machine,
regardless of its community string, are permitted.
SNMP Get/Set Examples
The following scenarios can be used to provide guidelines when configuring
RemotEye II. In all the examples, assume the Control Group settings are:
Community Read-Only: ronly
Community Read/Write: rwrite
Also, assume the NMS has the IP Address 172.18.63.1.
Case #1: NMS is not listed in the SNMP Communities
Assume the SNMP Communities Table is empty.
Analysis: Any NMS get request will be honored when using ronly or rwrite
community string. Any NMS set requests will be honored only when using rwrite
community string.
Case #2: NMS is listed in SNMP Communities with additional community
strings
SNMP Communities settings:
[1] 172.18.63.1 foobar Read/Write
[2] 172.18.63.1 reading Read
Analysis: Get requests from the NMS with IP 10 will be honored when using the
reading, foobar, rwrite or the ronly community strings. The NMS will have set ability
when using either the foobar or the rwrite community strings.
