Toshiba RemotEye III, Руководство пользователя

Страница: 102 / 167

RemotEye III User Manual – 62330-005 101
Analysis: Any NMS get request will be honoured when using ronly or rwrite community string. Any NMS set
requests will be honoured 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 172.18.63.1 will be honoured 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.
Case #3: NMS is listed in the SNMP Communities using one of the global community strings.
SNMP Communities settings:
[1] 172.18.63.1 ronly Read/Write
Analysis: Both get and set requests from this NMS will be honoured when using the ronly community string. Any
requests from NMS using rwrite, however, will be denied.
Case #4: NMS is listed in the SNMP Communities multiple times using the same community string.
SNMP Communities settings:
[1] 172.18.63.1 foobar Read
[2] 172.18.63.1 foobar Read/Write
Analysis: The NMS will only be allowed to use SNMP gets when using the community string foobar. This NMS can
still use global community strings ronly for gets or rwrite for gets and sets as well.
Case #5: NMS is listed in the SNMP Communities under No Access.
SNMP Communities settings:
[1] 10.0.7.31 foobar Read
[2] 10.0.7.31 public No Access
Analysis: The NMS can perform only gets using the community string foobar. No other set or get requests will be
honoured.
Case #6: NMS’s first listing is in the SNMP Communities under NoAccess
Community Read-Only: ronly
Community Read/Write: rwrite
[1] 10.0.7.31 foobar No Access
[2] 10.0.7.31 public Read/Write
Analysis: All NMS get or set requests are refused.
Toshiba MIB
The MIB is a set of objects that are processed via a network protocol. These objects determine what UPS parameters
may be monitored and controlled using SNMP requests.
The RemotEye III communication implements standard MIB III and the following MIBs for TOSHIBA UPS:
1) Toshiba Enterprise RMTI-3 1600XP MIB File
2) Toshiba Enterprise RMTI-3 4200FA/4300 MIB File
3) Toshiba Japanese JEMA-Compliant MIB File