This field is used to specify the access allowed for an authorized
NMS when Manager Validation is performed.
If the IP address for the NMS sending an SNMP message is on the list
of allowed managers, this option along with the Community Name access
determine the type of access allowed for the that manager.
When ever a new Security Manager is added or an existing
Security Manager's IP Address is modified, the newSecurityMgrAccess
object is set to the default value of read (1).
If the index for this object is not in the existing table and if there
is room in the table then the index will be used to create a new
Security Manager and will be given the requested access level.
In addition changing an existing access permission to noAccess
invalidates the corresponding row of this table. It is upto
the implementation to decide whether to actually remove this
entry from the table or not.
read (1) ==> no telnet access and snmp read only access
readWrite (2) ==> no telnet access and snmp read-write access
noAccess (3) ==> no telnet access and no snmp read-write access
telnetNoAccess (4) ==> telnet access and no snmp access
telnetRead (5) ==> telnet access and snmp read only access
telnetReadWrite (6) ==> telnet access and snmp read-write access.
Parsed from file pdndce.mib.txt
Company: None
Module: PDNDCE-MIB
This field is used to specify the access allowed for an authorized
NMS when Manager Validation is performed.
If the IP address for the NMS sending an SNMP message is on the list
of allowed managers, this option along with the Community Name access
determine the type of access allowed for the that manager.
When ever a new Security Manager is added or an existing
Security Manager's IP Address is modified, the newSecurityMgrAccess
object is set to the default value of read (1).
If the index for this object is not in the existing table and if there
is room in the table then the index will be used to create a new
Security Manager and will be given the requested access level.
In addition changing an existing access permission to noAccess
invalidates the corresponding row of this table. It is upto
the implementation to decide whether to actually remove this
entry from the table or not.
read (1) ==> no telnet access and snmp read only access
readWrite (2) ==> no telnet access and snmp read-write access
noAccess (3) ==> no telnet access and no snmp read-write access
telnetNoAccess (4) ==> telnet access and no snmp access
telnetRead (5) ==> telnet access and snmp read only access
telnetReadWrite (6) ==> telnet access and snmp read-write access.
Parsed from file PDN-SECURITY-MIB.mib
Module: PDN-SECURITY-MIB
Vendor: Paradyne
Module: PDN-SECURITY-MIB
[Automatically extracted from oidview.com]
newSecurityMgrAccess OBJECT-TYPE SYNTAX INTEGER { read (1), readWrite (2), noAccess (3), telnetNoAccess (4), telnetRead (5), telnetReadWrite (6) } ACCESS read-write STATUS mandatory DESCRIPTION "This field is used to specify the access allowed for an authorized NMS when Manager Validation is performed. If the IP address for the NMS sending an SNMP message is on the list of allowed managers, this option along with the Community Name access determine the type of access allowed for the that manager. When ever a new Security Manager is added or an existing Security Manager's IP Address is modified, the newSecurityMgrAccess object is set to the default value of read (1). If the index for this object is not in the existing table and if there is room in the table then the index will be used to create a new Security Manager and will be given the requested access level. In addition changing an existing access permission to noAccess invalidates the corresponding row of this table. It is upto the implementation to decide whether to actually remove this entry from the table or not. read (1) ==> no telnet access and snmp read only access readWrite (2) ==> no telnet access and snmp read-write access noAccess (3) ==> no telnet access and no snmp read-write access telnetNoAccess (4) ==> telnet access and no snmp access telnetRead (5) ==> telnet access and snmp read only access telnetReadWrite (6) ==> telnet access and snmp read-write access." ::= { newSecurityMgrEntry 2 }
newSecurityMgrAccess OBJECT-TYPE SYNTAX INTEGER { read (1), readWrite (2), noAccess (3), telnetNoAccess (4), telnetRead (5), telnetReadWrite (6) } ACCESS read-write STATUS mandatory DESCRIPTION "This field is used to specify the access allowed for an authorized NMS when Manager Validation is performed. If the IP address for the NMS sending an SNMP message is on the list of allowed managers, this option along with the Community Name access determine the type of access allowed for the that manager. When ever a new Security Manager is added or an existing Security Manager's IP Address is modified, the newSecurityMgrAccess object is set to the default value of read (1). If the index for this object is not in the existing table and if there is room in the table then the index will be used to create a new Security Manager and will be given the requested access level. In addition changing an existing access permission to noAccess invalidates the corresponding row of this table. It is upto the implementation to decide whether to actually remove this entry from the table or not. read (1) ==> no telnet access and snmp read only access readWrite (2) ==> no telnet access and snmp read-write access noAccess (3) ==> no telnet access and no snmp read-write access telnetNoAccess (4) ==> telnet access and no snmp access telnetRead (5) ==> telnet access and snmp read only access telnetReadWrite (6) ==> telnet access and snmp read-write access." ::= { newSecurityMgrEntry 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1795.2.24.2.8.5.1.1 | newSecurityMgrIpAddress | 0 | 0 | This is used to specify the IP address that identifies the SNMP manager(s) that are authorized to send SNMP messages. This object… |
| 1.3.6.1.4.1.1795.2.24.2.8.5.1.3 | newSecurityMgrSubnetMask | 0 | 0 | This object is used to specify the subnet mask |