All MIBs › PDN-SECURITY-MIB › newSecurityMgrAccess
newSecurityMgrAccess
Module: PDN-SECURITY-MIB
OID (symbolic): PDN-SECURITY-MIB::newSecurityMgrAccess
OID (numeric): 1.3.6.1.4.1.1795.2.24.2.8.5.1.2
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
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.
What is newSecurityMgrAccess?
This object specifies the combined SNMP and telnet access level for this authorized manager entry, choosing among read(1, SNMP read-only, no telnet), readWrite(2, SNMP read-write, no telnet), noAccess(3, no access at all, which invalidates the row), telnetNoAccess(4, telnet only, no SNMP), telnetRead(5, telnet plus SNMP read-only), or telnetReadWrite(6, telnet plus SNMP read-write); defaults to read(1) when the entry is created or its IP address changes. Admins use this single field to define exactly what combination of management protocol access a given trusted source is granted. Setting this to telnetReadWrite(6) for a manager's IP grants that source both telnet access and full SNMP read-write access to the device.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.2.8.5.1.2 snmpwalk -v2c -c public <target> PDN-SECURITY-MIB::newSecurityMgrAccess
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.2.8.5.1.2.1 snmpget -v2c -c public <target> PDN-SECURITY-MIB::newSecurityMgrAccess.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.1795.2.24.2.8.5.1.2.1 i <value>
Start monitoring Paradyne DSL access multiplexer/network access device (management-plane access control) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PDN-SECURITY-MIB::newSecurityMgrAccess OID value, configure state conditions and alerts, and monitor any Paradyne DSL access multiplexer/network access device (management-plane access control) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.1795.2.24.2.8.5 | newSecurityMgrTable | PDN-SECURITY-MIB |
| 1.3.6.1.4.1.1795.2.24.2.8.5.1 | newSecurityMgrEntry | PDN-SECURITY-MIB |
| 1.3.6.1.4.1.1795.2.24.2.8.5.1.2 | newSecurityMgrAccess | PDN-SECURITY-MIB |