securityUserTableEntry OBJECT-TYPE
SYNTAX SecurityUserTableEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"1. Creating a new user is done by using the username as
a qualifier and SETting any of the items in the row -
defaults will be used for the remaining values.
2. Deleting a user is by writing invalid to the status
column.
3. There must always be users called monitor, manager
and security - these cannot be deleted."
INDEX { securityUserName }
View at oid-info.com
1. Creating a new user is done by using the username as
a qualifier and SETting any of the items in the row -
defaults will be used for the remaining values.
2. Deleting a user is by writing 'invalid' to the status
column.
3. There must always be users called 'monitor', 'manager'
and 'security' - these cannot be deleted.
Parsed from file msh100.mib.txt
Company: None
Module: LBMSH-MIB
1. Creating a new user is done by using the username as
a qualifier and SETting any of the items in the row -
defaults will be used for the remaining values.
2. Deleting a user is by writing 'invalid' to the status
column.
3. There must always be users called 'monitor', 'manager'
and 'security' - these cannot be deleted.
Parsed from file LBHUB-MSH-MIB.mib
Module: LBHUB-MSH-MIB
Automatically extracted from a file named S3M_AGENT
securityUserTableEntry OBJECT-TYPE SYNTAX SecurityUserTableEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "1. Creating a new user is done by using the username as a qualifier and SETting any of the items in the row - defaults will be used for the remaining values. 2. Deleting a user is by writing 'invalid' to the status column. 3. There must always be users called 'monitor', 'manager' and 'security' - these cannot be deleted." INDEX { securityUserName } ::= { securityUserTable 1 }
securityUserTableEntry OBJECT-TYPE SYNTAX SecurityUserTableEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "1. Creating a new user is done by using the username as a qualifier and SETting any of the items in the row - defaults will be used for the remaining values. 2. Deleting a user is by writing 'invalid' to the status column. 3. There must always be users called 'monitor', 'manager' and 'security' - these cannot be deleted." INDEX { securityUserName } ::= { securityUserTable 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.43.10.4.2.1.1 | securityUserStatus | 0 | 0 | User Status. `invalid' is used to indicate this user is no longer allowed to access this device, and the table entry may subsequ… |
| 1.3.6.1.4.1.43.10.4.2.1.2 | securityUserName | 0 | 0 | An ASCII string for the User Name. Empty strings are not allowed. The index column for the User Table. |
| 1.3.6.1.4.1.43.10.4.2.1.3 | securityUserLevel | 0 | 0 | User Access Level defining the scope of management allowed for this user. Note that the access level of default Users cannot be … |
| 1.3.6.1.4.1.43.10.4.2.1.4 | securityUserPassword | 0 | 0 | The password required for user confirmation, when access is made via the local serial port, the front panel, or via Telnet. |
| 1.3.6.1.4.1.43.10.4.2.1.5 | securityUserCommunity | 0 | 0 | The community string identifying this user, when access is made via the original community-based SNMP (RFC1157). |
| 1.3.6.1.4.1.43.10.4.2.1.6 | securityUserLocParty | 0 | 0 | The local party identity of this user, when access is made via secure SNMP. |
| 1.3.6.1.4.1.43.10.4.2.1.7 | securityUserMgrParty | 0 | 0 | The manager party identity for this user, when access is made via secure SNMP. |