CISCO-LWAPP-HA-MIB: View SNMP OID List / Download MIB

VENDOR: CISCO


 Home MIB: CISCO-LWAPP-HA-MIB
Download as:   
SNMPv2-CONF, SNMPv2-MIB, SNMP-FRAMEWORK-MIB, SNMPv2-SMI, INET-ADDRESS-MIB, CISCO-RF-MIB, CISCO-TC, CISCO-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 ciscoLwappHaMIB 1.3.6.1.4.1.9.9.198888
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
               ciscoLwappHaMIBObjects 1.3.6.1.4.1.9.9.198888.0
                   ciscoLwappHaGlobalConfig 1.3.6.1.4.1.9.9.198888.0.1
                       cLHaApSsoConfig 1.3.6.1.4.1.9.9.198888.0.1.1 truthvalue read-write
                       cLHaPeerIpAddressType 1.3.6.1.4.1.9.9.198888.0.1.2 inetaddresstype read-write
                       cLHaPeerIpAddress 1.3.6.1.4.1.9.9.198888.0.1.3 inetaddress read-write
                       cLHaServicePortPeerIpAddressType 1.3.6.1.4.1.9.9.198888.0.1.4 inetaddresstype read-write
                       cLHaServicePortPeerIpAddress 1.3.6.1.4.1.9.9.198888.0.1.5 inetaddress read-write
                       cLHaServicePortPeerIpNetMaskType 1.3.6.1.4.1.9.9.198888.0.1.6 inetaddresstype read-write
                       cLHaServicePortPeerIpNetMask 1.3.6.1.4.1.9.9.198888.0.1.7 inetaddress read-write
                       cLHaRedundancyIpAddressType 1.3.6.1.4.1.9.9.198888.0.1.8 inetaddresstype read-only
                       cLHaRedundancyIpAddress 1.3.6.1.4.1.9.9.198888.0.1.9 inetaddress read-only
                       cLHaPeerMacAddress 1.3.6.1.4.1.9.9.198888.0.1.10 macaddress read-only
                       cLHaVirtualMacAddress 1.3.6.1.4.1.9.9.198888.0.1.11 macaddress read-write
                       cLHaPrimaryUnit 1.3.6.1.4.1.9.9.198888.0.1.12 truthvalue read-write
Indicates 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.
                       cLHaLinkEncryption 1.3.6.1.4.1.9.9.198888.0.1.13 truthvalue read-write
Indicates whether link encryption is enabled or not.
                       cLHaNetworkFailOver 1.3.6.1.4.1.9.9.198888.0.1.14 truthvalue read-write
Indicates whether network failover is enabled or not.
                       cLHaRFStatusUnitIp 1.3.6.1.4.1.9.9.198888.0.1.15 inetaddress read-only
The description of the ip address of unit
                   ciscoLwappHaNetworkConfig 1.3.6.1.4.1.9.9.198888.0.2
                       cLHaNetworkRoutePeerConfigTable 1.3.6.1.4.1.9.9.198888.0.2.1 no-access
A table of the switch's Network Route Peer entries
                           cLHaNetworkRoutePeerConfigEntry 1.3.6.1.4.1.9.9.198888.0.2.1.1 no-access
Switch's Network Route Peer entry
                               cLHaNetworkRoutePeerIPAddressType 1.3.6.1.4.1.9.9.198888.0.2.1.1.1 inetaddresstype no-access
Network Route IP Address type of the standby.
                               cLHaNetworkRoutePeerIPAddress 1.3.6.1.4.1.9.9.198888.0.2.1.1.2 inetaddress no-access
Network Route IP Address of the standby.
                               cLHaNetworkRoutePeerIPNetmaskType 1.3.6.1.4.1.9.9.198888.0.2.1.1.3 inetaddresstype read-only
Network Route IP Netmask type of the standby.
                               cLHaNetworkRoutePeerIPNetmask 1.3.6.1.4.1.9.9.198888.0.2.1.1.4 inetaddress read-only
Network Route IP Netmask of the standby.
                               cLHaNetworkRoutePeerGatewayType 1.3.6.1.4.1.9.9.198888.0.2.1.1.5 inetaddresstype read-only
Network Route IP Gateway type of the standby.
                               cLHaNetworkRoutePeerGateway 1.3.6.1.4.1.9.9.198888.0.2.1.1.6 inetaddress read-only
Network Route IP Gateway of the standby.
                               cLHaNetworkRoutePeerTransferStatus 1.3.6.1.4.1.9.9.198888.0.2.1.1.7 integer read-write
Network Route transfer status from standby. Enumeration: 'initiate': 1, 'inProgress': 2, 'timeout': 5, 'success': 3, 'failure': 4.
                               cLHaNetworkRoutePeerRowStatus 1.3.6.1.4.1.9.9.198888.0.2.1.1.8 rowstatus read-only
Network Route Peer Row Status.
                   ciscoLwappHaMIBNotifs 1.3.6.1.4.1.9.9.198888.0.3
                       cLHaSecondaryControllerUsageTrap 1.3.6.1.4.1.9.9.198888.0.3.1
This notification is sent on the event of a generic failure between the active and standby unit
                       cLHaRFSwapInfoTrap 1.3.6.1.4.1.9.9.198888.0.3.2
The 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
                   ciscoLwappHaNotificationVariable 1.3.6.1.4.1.9.9.198888.0.4
                       cLHaSecondaryControllerUsageTrapType 1.3.6.1.4.1.9.9.198888.0.4.1 integer read-only
This 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. Enumeration: 'usageComplete': 2, 'usageStart': 1, 'overUsage': 3.
                       cLHaSecondaryControllerUsageDayCounter 1.3.6.1.4.1.9.9.198888.0.4.2 counter32 read-only
This object represents the number of days the secondary controller is used.