This article provides an example of how to interpret the output of OID 1.3.6.1.4.1.4874.2.2.20.1.8.4.1.10. (juniAaaSubscriberState).
OID outputs do not match what the OID description (BIT map part).
Example:
SNMPWALK of OID 1.3.6.1.4.1.4874.2.2.20.1.8.4.1.10. (juniAaaSubscriberState) returns the following get next outputs:
SNMPv2-SMI::enterprises.4874.2.2.20.1.8.4.1.10.4903589 = Hex-STRING: 40 00
SNMPv2-SMI::enterprises.4874.2.2.20.1.8.4.1.10.6984526 = Hex-STRING: 80 00
OID Description:
"The set of possible AAA subscriber states, expressed as a bit map:
init Initial state (transient)
pending Auth/Acct or Addr Request is pending
established Subscriber is authenticated
deleting Deletion of subscriber is pending
tunneling Subscriber is being tunneled
tunnelAcct Tunnel accounting is enabled
terminated Subscriber has been terminated
counted Subscriber has been counted in statistics
clientHandleSet Client handle is assigned to user profile
sentAcctStart Start accounting record is requested
More than one state bit can be active simultaneously. If no bits are set, the subscriber is in a transient initial state."
SYNTAX BITS {
pending(0),
established(1),
deleting(2),
tunneling(3),
tunnelAcct(4),
terminated(5),
counted(6),
clientHandleSet(7),
sentAcctStart(8) }
The OID BIT maps to the HEX values:
HEX Binary
80 - 0000 0000 1000 0000 – SentAcctStart.
100 - 0000 0001 0000 0000 – ClientHandleSet.
200 - 0000 0010 0000 0000 – Counted.
400 - 0000 0100 0000 0000 – Terminated.
800 - 0000 1000 0000 0000 – TunnelAcct.
1000 - 0001 0000 0000 0000 – Tunneling.
2000 - 0010 0000 0000 0000 – Deleting.
4000 - 0100 0000 0000 0000 – Established.
8000 - 1000 0000 0000 0000 – Pending.
Therefore, in the example above "40 00" maps to "Established" and "80 00" maps to "Pending".