zxAnPortIdAccessNodeSlaveId

ZTE-AN-PORT-LOCATING-MIB · .1.3.6.1.4.1.3902.1015.32.7
Commands MIB view Table view

Object

scalar r/w OctetString 
This field is designed for Deutsche Telekom. 
By using the DHCP relay agent function the device 
must be able to create the CID and the RID as described 
in BBF TR-101 and TR-156.The CID contains Access-Node-Identifier.
Access-Node-Identifier which is required by Deutsche Telekom
consists of two IDs:Access-Node-ID1 and Access-Node-ID2.
This field indicates Access-Node-ID2.

Context

MIB
ZTE-AN-PORT-LOCATING-MIB
OID
.1.3.6.1.4.1.3902.1015.32.7
Type
scalar
Access
readwrite
Status
current
Parent
zxAnPortLocatingMib

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'ZTE-AN-PORT-LOCATING-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZTE-AN-PORT-LOCATING-MIB::zxAnPortIdAccessNodeSlaveId.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'ZTE-AN-PORT-LOCATING-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ZTE-AN-PORT-LOCATING-MIB::zxAnPortIdAccessNodeSlaveId'

Syntax

OctetString

Values & Constraints

Object Constraints
range: 1-50