CISCO-LWAPP-HA-MIB
AI MIB Summary
The CISCO-LWAPP-HA-MIB provides monitoring and configuration capabilities for High Availability (HA) statistics on Cisco Central Controllers terminating LWAPP tunnels from Lightweight Access Points. It enables the tracking of controller redundancy states, failover events, and synchronization metrics within the LWAPP architecture to ensure continuous wireless service availability.
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points.
This MIB is used to show and configure High availability (HA) related statistics.
The relationship between CC and the LWAPP APs can be depicted as follows:
+......+ +......+ +......+ +......+
+ + + + + + + +
+ CC + + CC + + CC + + CC +
+ + + + + + + +
+......+ +......+ +......+ +......+
.. . . . .. . . . . . . . . . . . . . . . . . . . . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ AP + + AP + + AP + + AP + + AP +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
. . . . . . . . . . . . . . . . . . . . . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ MN + + MN + + MN + + MN + + MN +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
The LWAPP tunnel exists between the controller and the APs. The MNs communicate with the APs through the protocol defined by the 802.11 standard.
LWAPP APs, upon bootup, discover and join one of the controllers and the controller pushes the configuration, that includes the WLAN parameters, to the LWAPP APs. The APs then encapsulate all the 802.11 frames from wireless clients inside LWAPP frames and forward the LWAPP frames to the controller.
GLOSSARY
Access Point ( AP )
An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides access to the distribution services via the wireless medium for associated clients.
LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends them to the controller to which it is logically connected.
Central Controller ( CC )
The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'.
Light Weight Access Point Protocol ( LWAPP )
This is a generic protocol that defines the communication between the Access Points and the Central Controller.
Mobile Node ( MN )
A roaming 802.11 wireless device in a wireless network associated with an access point. Mobile Node, Mobile Station(Ms) and client are used interchangeably.
REFERENCE
[1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications.
[2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol
Main OID:
ciscoLwappHaMIB.1.3.6.1.4.1.9.9.198888
35
Objects
Active
Status
9
Dependencies
Imported Objects
Objects
35 total| Object Name |
|---|
ciscoLwappHaMIBThis MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Access Point Protocol
tunnel from Cisco Light-weight LWAPP Access Points.
This MIB is used to show and configure High availability
(HA) related statistics.
The relationship between CC and the LWAPP APs
can be depicted as follows:
+......+ +......+ +......+ +......+
+ + + + + + + +
+ CC + + CC + + CC + + CC +
+ + + + + + + +
+......+ +......+ +......+ +......+
.. . . .
.. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ AP + + AP + + AP + + AP + + AP +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ MN + + MN + + MN + + MN + + MN +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
The LWAPP tunnel exists between the controller and
the APs. The MNs communicate with the APs through
the protocol defined by the 802.11 standard.
LWAPP APs, upon bootup, discover and join one of the
controllers and the controller pushes the configuration,
that includes the WLAN parameters, to the LWAPP APs.
The APs then encapsulate all the 802.11 frames from
wireless clients inside LWAPP frames and forward
the LWAPP frames to the controller.
GLOSSARY
Access Point ( AP )
An entity that contains an 802.11 medium access
control ( MAC ) and physical layer ( PHY ) interface
and provides access to the distribution services via
the wireless medium for associated clients.
LWAPP APs encapsulate all the 802.11 frames in
LWAPP frames and sends them to the controller to which
it is logically connected.
Central Controller ( CC )
The central entity that terminates the LWAPP protocol
tunnel from the LWAPP APs. Throughout this MIB,
this entity also referred to as 'controller'.
Light Weight Access Point Protocol ( LWAPP )
This is a generic protocol that defines the
communication between the Access Points and the
Central Controller.
Mobile Node ( MN )
A roaming 802.11 wireless device in a wireless
network associated with an access point. Mobile Node,
Mobile Station(Ms) and client are used interchangeably.
REFERENCE
[1] Wireless LAN Medium Access Control ( MAC ) and
Physical Layer ( PHY ) Specifications.
[2] Draft-obara-capwap-lwapp-00.txt, IETF Light
Weight Access Point Protocol MODULE-IDENTITY .1.3.6.1.4.1.9.9.198888 |
ciscoLwappHaMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.198888.0 |
ciscoLwappHaGlobalConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.198888.0.1 |
cLHaApSsoConfigrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.198888.0.1.1 |
cLHaPeerIpAddressTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.1.2 |
cLHaPeerIpAddressrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.1.3 |
cLHaServicePortPeerIpAddressTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.1.4 |
cLHaServicePortPeerIpAddressrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.1.5 |
cLHaServicePortPeerIpNetMaskTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.1.6 |
cLHaServicePortPeerIpNetMaskrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.1.7 |
cLHaRedundancyIpAddressTypero InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.1.8 |
cLHaRedundancyIpAddressro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.1.9 |
cLHaPeerMacAddressro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.198888.0.1.10 |
cLHaVirtualMacAddressrw MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.198888.0.1.11 |
cLHaPrimaryUnitIndicates whether this is the primary redundant unit or
not. If this unit is the primary unit, this object is true. If
this unit is the secondary unit, this object is false.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.198888.0.1.12 |
cLHaLinkEncryptionIndicates whether link encryption is enabled or not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.198888.0.1.13 |
cLHaNetworkFailOverIndicates whether network failover is enabled or not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.198888.0.1.14 |
cLHaRFStatusUnitIpThe description of the ip address of unitro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.1.15 |
ciscoLwappHaNetworkConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.198888.0.2 |
cLHaNetworkRoutePeerConfigTableA table of the switch's Network Route Peer entries SEQUENCE OF CLHaNetworkRoutePeerConfigEntry .1.3.6.1.4.1.9.9.198888.0.2.1 |
cLHaNetworkRoutePeerConfigEntrySwitch's Network Route Peer entry CLHaNetworkRoutePeerConfigEntry .1.3.6.1.4.1.9.9.198888.0.2.1.1 |
cLHaNetworkRoutePeerIPAddressTypeNetwork Route IP Address type of the standby. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.2.1.1.1 |
cLHaNetworkRoutePeerIPAddressNetwork Route IP Address of the standby. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.2.1.1.2 |
cLHaNetworkRoutePeerIPNetmaskTypeNetwork Route IP Netmask type of the standby.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.2.1.1.3 |
cLHaNetworkRoutePeerIPNetmaskNetwork Route IP Netmask of the standby.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.2.1.1.4 |
cLHaNetworkRoutePeerGatewayTypeNetwork Route IP Gateway type of the standby.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.2.1.1.5 |
cLHaNetworkRoutePeerGatewayNetwork Route IP Gateway of the standby.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.198888.0.2.1.1.6 |
cLHaNetworkRoutePeerTransferStatusNetwork Route transfer status from standby.rw Enumeration .1.3.6.1.4.1.9.9.198888.0.2.1.1.7 |
cLHaNetworkRoutePeerRowStatusNetwork Route Peer Row Status.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.198888.0.2.1.1.8 |
ciscoLwappHaMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.198888.0.3 |
cLHaSecondaryControllerUsageTrapThis notification is sent on the event of a generic failure
between the active and standby unit NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.198888.0.3.1 |
cLHaRFSwapInfoTrapThe notification is sent by the active redundant
unit whenever its RF state changes or the RF state of the peer
unit changes.
To avoid a flurry of notifications for all state transitions,
notifications will only be sent for transitions to the
following RF states:
disabled (for the peer state)
standbyCold
standbyHot
active
activeExtraload NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.198888.0.3.2 |
ciscoLwappHaNotificationVariable OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.198888.0.4 |
cLHaSecondaryControllerUsageTrapTypeThis object represents the usage of secondary controller. After the usuage of 90 days, one trap is generated per day for over usage.
usageStart - start of secondary controller usage.
usageComplete - completion of secondary controller usage period of 90 days.
overUsage - Secondary controller overusage.ro Enumeration .1.3.6.1.4.1.9.9.198888.0.4.1 |
cLHaSecondaryControllerUsageDayCounterThis object represents the number of days the secondary controller is used.ro Counter32 .1.3.6.1.4.1.9.9.198888.0.4.2 |