Connecting To The Remoteye Ii Via Snmp - Toshiba RemotEye II User Manual

Connecting to the RemotEye II via SNMP

Executing SNMP Gets and Sets
Besides receiving traps, an NMS can perform the valuable functions of SNMP gets and sets through
RemotEye II.
An SNMP get entails retrieving information. This is a request from a Manager to an Agent for information
the Agent has collected.
An SNMP set entails configuring a device parameter. This is a command from a Manager to an Agent
instructing the Agent to change some setup parameter. The setup parameter may apply to the agent or
the agent's network device for which it is responsible.
SNMP Get/Set Criteria
Successful SNMP gets and sets from an NMS depend upon RemotEye II settings. The RemotEye II acts
as a shield, refusing access to machines that do not meet its setup criteria. If the RemotEye II provides
an NMS with Read access, SNMP gets are allowed, if RemotEye II provides NMS with Write access, both
SNMP gets and SNMP sets are allowed.
The RemotEye II uses the community values listed in the RemotEye II Control Group and the entries
listed in the SNMP Communities to render get/set requests from network machines. The evaluation
techniques are described in the following sections.
NMS Unlisted in SNMP Communities
If an NMS is not listed in the SNMP Communities, the global RemotEye II communities are used for
evaluation. The global communities are set within the Control Group table of the RemotEye II. If a get
request matches either the Community Read-Only or the Community Read/Write values, the request is
honored. A set, however, is only allowed if the request includes the Community Read/Write value.
NMS Listed in SNMP Communities
If the NMS appears in the SNMP Communities with Read or Read/Write Access rights, the corresponding
community name and privileges listed within this table, in conjunction with the global community values,
are used to evaluate the request.
If the NMS community listing matches any of the global communities, the SNMP Communities table listing
will override the permissions established by the global listings. First, the SNMP Communities entry
negates both global values, and second, the permissions for this entry will apply to requests from the
NMS.
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
82 RemotEye II User Manual – 50024-014