ubpNotifyEAPSignalSequenceNumber
OPSUBP-DEVICE-SIGNALING-MIB ·
.1.3.6.1.4.1.562.42.5.1.3.1.1.7
Object
scalar SNMPv2-SMIUnsigned32
This is a unique sequence identifier for a EAP session start or end event. The EAP user session event signaling is done using SNMPv3 Inform messages. Each time the EAP access point does not get an acknowledgement for the Inform, it may retry sending the Inform message with the same EAP signal sequence number so that the Inform receiver can handle duplicate Informs. This attribute is sent with the notification.
Context
- MIB
- OPSUBP-DEVICE-SIGNALING-MIB
- OID
.1.3.6.1.4.1.562.42.5.1.3.1.1.7- Type
- scalar
- Access
- notifyonly
- Status
- current
- Parent
- ubpNotifyObjects
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'OPSUBP-DEVICE-SIGNALING-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'OPSUBP-DEVICE-SIGNALING-MIB::ubpNotifyEAPSignalSequenceNumber.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'OPSUBP-DEVICE-SIGNALING-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'OPSUBP-DEVICE-SIGNALING-MIB::ubpNotifyEAPSignalSequenceNumber'
Syntax
- Source
- SNMPv2-SMIUnsigned32
- Base type
Unsigned32
Values & Constraints
Type Constraints
range: 0..4294967295
Conformance
Member of