Tripp Lite PDU3VSR6L2130 Owner's Manual for SNMPWEBCARD 9332CE - Page 61

would be Realm 5 for Customer One, Realm 7 for Customer Two and Realm

Page 61 highlights

4. Telnet/SSH Console continued 4.2 System Configuration continued 4.2.3.2 Local Users continued Logging This facility allows access to logs and log rotation actions. Log rotation actions will only be available if the user has at least Read Only access to the Contacts facility. Device Status The facility provides access to all device variable information. These would include device status variables, personalization variables and threshold variables. By default, the localadmin and localmanager have Read/Write access and localguest has only Read Only access. Device Controls This facility configures whether a user has access to device controls. Since this is a subset of devices, it is required that the user has Read Only access to device status to either view or control loads. Configuring this to No Access will restrict a user from seeing the controls area of the program. Device Events This facility configures whether a user has access to device events. Since this is a subset of devices it is required that the user has Read Only access to the device status and contacts facility to properly view or modify events. Configuring this to No Access will restrict a user from seeing events program area. Device Loads This facility configures whether a user has access to device loads. Since this is a subset of devices it is required that the user has Read Only access to device status to either view or control loads. Configuring this to No Access will restrict a user from seeing loads. Actions This facility is the program area that defines what will happen when an event/alarm is detected. For a user to be able to setup any action requires that the user have Read/Write access to the facilities, device loads, device controls and at least Read Only access to the contacts facility. Schedules To allow a user to add scheduled tasks requires that the user have Read/Write access to the device controls facilities. Discovery This facility is the program area that allows execution of a device discovery. This program area is most commonly used for detecting an ENVIROSENSE temp/humidity probe that has been connected to the SNMPWEBCARD after initial startup. Access Levels • Read Only The user may read the data but make no changes. • Read Write The user may not only read the data but make changes as well. • None The user has no access to the data in the facility Facility Rules and Dependencies Outlet Realms Outlet realms are an integer between 1 and 32 used to identify a logical grouping of outlets to be used to limit a user's access to a subset of outlets. In the user definition, it is a comma separated list of realms or range of realms that the user may access. Each load may be assigned a single realm and multiple outlets may use the same realm. For example, a PDU may be powering devices at a co-hosting facility where Customer One has all of his equipment connected to Circuit 1 of a 3-phase PDU, Customer Two is on Circuit 2, and Customer Three is on Circuit 3. This PDU may have outlets 1, 4, 7, 10, 13, 16, 19 and 22 on Circuit 1, outlets 2, 5, 8, 11, 14, 17, 20 and 24 on Circuit 2 and outlets 3, 6, 9, 12, 15, 18, 21, and 23 on Circuit 3. The outlets on Circuit 1 could be assigned to Realm 5. The outlets on Circuit 2 could be assigned to Realm 7 and the outlets on Circuit 3 could be assigned to Realm 9. The user realm mapping would be Realm 5 for Customer One, Realm 7 for Customer Two and Realm 9 for Customer Three. Assigning the realm to the user gives Read/Write access only for the outlets assigned to the users' realms, meaning they will be able to turn On or Off outlets only in the same realm. Although the concept of realms may seem similar to outlet groups, it provides no other grouping functionality other than permissions. The access level to the realms indicated is Read/Write. Each load may optionally be assigned to a realm. Whatever loads belong to the realms indicated here, the user may access. In order to correctly access the data, a user should have at least Read Only permission for Device Status and Device Loads to be able to user the realms. 192.168.1.1 (single) 192.168.1.0 (range) 192.168.0.0 192.0.0.0 0.0.0.0 (everyone) 255.255.255.255 255.255.255.0 255.255.0.0 255.0.0.0 0.0.0.0 ACL IP Address (Users with SNMP Access Only) This defines what IP Address (or Addresses when used with the ACL IP Mask) from which this user may access the data via SNMP. ACL IP Mask (Users with SNMP Access Only) This defines the Subnet Mask to user with the ACL IP Address to determine if an address is one from which the user is allowed to access the data via SNMP. Password (N/A for SNMPv1 or SNMPv2c) This is the user password for logging in. For SNMP V3 users, this is the Priv Password. Auth Password (N/A for SNMPv1 or SNMPv2c) For SNMP v3 Users only, this is the Auth Password. Idle Timeout in Minutes (N/A for SNMPv1 or SNMPv2c) This applies to data access other than SNMP which does not use the concept of a logged in session. This is the amount of time that the session can be idle before it will time out and no longer have access to the data. When the value is 0, that means that idle sessions will not time out. Session Expiration Minutes (N/A for SNMPv1 or SNMPv2c) This applies to data access other than SNMP which does not use the concept of a logged in session. This is the amount of total time that a session may last whether or not the session is idle or active. When the value is 0, the session will not expire. 61

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100

61
4. Telnet/SSH Console
continued
192.168.1.1 (single)
255.255.255.255
192.168.1.0 (range)
255.255.255.0
192.168.0.0
255.255.0.0
192.0.0.0
255.0.0.0
0.0.0.0 (everyone)
0.0.0.0
Logging
This facility allows access to logs and log rotation actions. Log rotation
actions will only be available if the user has at least Read Only access
to the Contacts facility.
Device Status
The facility provides access to all device variable information. These
would include device status variables, personalization variables and
threshold variables. By default, the localadmin and localmanager have
Read/Write access and localguest has only Read Only access.
Device Controls
This facility configures whether a user has access to device controls.
Since this is a subset of devices, it is required that the user has Read Only
access to device status to either view or control loads. Configuring this to
No Access will restrict a user from seeing the controls area of the program.
Device Events
This facility configures whether a user has access to device events.
Since this is a subset of devices it is required that the user has Read
Only access to the device status and contacts facility to properly view
or modify events. Configuring this to No Access will restrict a user from
seeing events program area.
Device Loads
This facility configures whether a user has access to device loads. Since
this is a subset of devices it is required that the user has Read Only
access to device status to either view or control loads. Configuring this
to No Access will restrict a user from seeing loads.
Actions
This facility is the program area that defines what will happen when an
event/alarm is detected. For a user to be able to setup any action requires
that the user have Read/Write access to the facilities, device loads, device
controls and at least Read Only access to the contacts facility.
Schedules
To allow a user to add scheduled tasks requires that the user have
Read/Write access to the device controls facilities.
Discovery
This facility is the program area that allows execution of a device
discovery.
This program area is most commonly used for detecting an
ENVIROSENSE temp/humidity probe that has been connected to the
SNMPWEBCARD after initial startup.
Access Levels
• Read Only
The user may read the data but make no changes.
• Read Write
The user may not only read the data but make changes as well.
• None
The user has no access to the data in the facility
Facility Rules and Dependencies
Outlet Realms
Outlet realms are an integer between 1 and 32 used to identify a logical
grouping of outlets to be used to limit a user's access to a subset of
outlets. In the user definition, it is a comma separated list of realms or
range of realms that the user may access.
Each load may be assigned
a single realm and multiple outlets may use the same realm.
For example, a PDU may be powering devices at a co-hosting facility where
Customer One has all of his equipment connected to Circuit 1 of a 3-phase
PDU, Customer Two is on Circuit 2, and Customer Three is on Circuit 3.
This PDU may have outlets 1, 4, 7, 10, 13, 16, 19 and 22 on Circuit 1,
outlets 2, 5, 8, 11, 14, 17, 20 and 24 on Circuit 2 and outlets 3, 6, 9, 12,
15, 18, 21, and 23 on Circuit 3.
The outlets on Circuit 1 could be assigned
to Realm 5.
The outlets on Circuit 2 could be assigned to Realm 7 and the
outlets on Circuit 3 could be assigned to Realm 9.
The user realm mapping
would be Realm 5 for Customer One, Realm 7 for Customer Two and Realm
9 for Customer Three.
Assigning the realm to the user gives Read/Write
access only for the outlets assigned to the users’ realms, meaning they will
be able to turn On or Off outlets only in the same realm.
Although the concept of realms may seem similar to outlet groups, it
provides no other grouping functionality other than permissions.
The access level to the realms indicated is Read/Write.
Each load may
optionally be assigned to a realm.
Whatever loads belong to the realms
indicated here, the user may access.
In order to correctly access the
data, a user should have at least Read Only permission for Device
Status and Device Loads to be able to user the realms.
ACL IP Address
(Users
with SNMP Access Only)
This defines what IP
Address (or Addresses
when used with the ACL
IP Mask) from which
this user may access
the data via SNMP.
ACL IP Mask
(Users with SNMP Access Only)
This defines the Subnet Mask to user with the ACL IP Address to
determine if an address is one from which the user is allowed to access
the data via SNMP.
Password
(N/A for SNMPv1 or SNMPv2c)
This is the user password for logging in. For SNMP V3 users, this is the
Priv Password.
Auth Password
(N/A for SNMPv1 or SNMPv2c)
For SNMP v3 Users only, this is the Auth Password.
Idle Timeout in Minutes
(N/A for SNMPv1 or SNMPv2c)
This applies to data access other than SNMP which does not use the
concept of a logged in session. This is the amount of time that the session
can be idle before it will time out and no longer have access to the data.
When the value is 0, that means that idle sessions will not time out.
Session Expiration Minutes
(N/A for SNMPv1 or SNMPv2c)
This applies to data access other than SNMP which does not use the
concept of a logged in session. This is the amount of total time that a
session may last whether or not the session is idle or active. When the
value is 0, the session will not expire.
4.2 System Configuration
continued
4.2.3.2 Local Users
continued