ciscoLwappMeshSecBackhaulChange
CISCO-LWAPP-MESH-STATS-MIB ·
.1.3.6.1.4.1.9.9.617.0.3
Object
notification
This notification is generated by the agent when the MAP identified by clApName intiates the backhaul change from primary to secondary. cLApName identifies the AP that receives the change. The MAC address of the initiating AP is sent as a part of the index of clMeshNodeBackhaul. clMeshNodeBackhaul identifies the secondary backhaul channel used. The MAC address of the receiving AP is sent as a part of the index of cLApName.
Context
- MIB
- CISCO-LWAPP-MESH-STATS-MIB
- OID
.1.3.6.1.4.1.9.9.617.0.3- Type
- notification
- Status
- current
- Parent
- ciscoLwappMeshStatsMIBNotifs
- Groups
- 2
Net-SNMP examples
How SNMP and these commands workNotifications are emitted by an agent; they cannot be read with snmpget or walked.
Inspect the notification definition
/usr/bin/snmptranslate -Pud -Ir -Td -m 'CISCO-LWAPP-MESH-STATS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-MESH-STATS-MIB::ciscoLwappMeshSecBackhaulChange'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-LWAPP-MESH-STATS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-MESH-STATS-MIB::ciscoLwappMeshSecBackhaulChange'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.