CISCO-LWAPP-MFP-MIB
This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight Access Point Protocol
tunnel from Light-weight LWAPP Access Points.
This MIB instrumentation provides the parameters used
by the controller to control and monitor the behavior
of the associated Access Points when following the
newly defined Management Frame Protocol. The
controller would pass the MFP settings configured by
the user through this MIB to the APs through LWAPP
messages. The APs then begin to validate and verify
the integrity of 802.11 Management frames and report
the anomalies found, if any, to the controller.
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,
which 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. Reference [2]
explains in detail about the communication between
the controller and APs, while Reference [1] explains
the AP-MN communication.
To secure the 802.11 management traffic, the controller
and the APs perform specific roles. The controller
acts as the central entity to generate and distribute
signature keys using which the APs generate integrity
check values, also known as signatures, for individual
management frames. The APs append this signature in
the form of an Information Element to the respective
management frame to be transmitted. This is needed to
isolate those potential rogue APs whose frames may not
carry the frame signature.
The APs use the signature keys, generated and pushed
to them by the controller for each BSSID reported
as heard by the APs, to validate the integrity of the
the management traffic originating from various
802.11 sources. Any anomalies observed by the APs
are reported to the controller. The controller
makes the information about such events available
for a network management Station in the form of
notifications.
GLOSSARY
Access Point ( AP )
An entity that contains an 802.11 media 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.
AP-Authentication
With this feature enabled, the Access Points sending
radio resource management neighbor packets with
different RF network names will be reported as rogues.
Basic Service Set Identifier ( BSSID )
The identifier of the Basic Service Set controlled by
a single coordination function. The identifier is
usually the MAC address of the radio interface that
hosts the BSS.
Central Controller ( CC )
The central entity that terminates the LWAPP protocol
tunnel from the LWAPP APs. Throughout this MIB,
this entity is 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.
Management Frame Protection ( MFP )
A proprietary mechanism devised to integrity protect
the otherwise unprotected management frames of the
802.11 protocol specification.
Message Integrity Check ( MIC )
A checksum computed on a sequence of bytes and made
known to the receiving party in a data communication,
to let the receiving party make sure the bytes
received were not compromised enroute.
Mobile Node ( MN )
A roaming 802.11 wireless device in a wireless
network associated with an access point.
Network Management Station ( NMS )
The system through which the network administrator
manages the controller and the APs associated to
it.
REFERENCE
[1] Wireless LAN Medium Access Control ( MAC ) and
Physical Layer ( PHY ) Specifications, ANSI/IEEE
Std 802.11, 1999 Edition.
[2] Draft-obara-Capwap-lwapp-00.txt, IETF Light
Weight Access Point Protocol
- Source file
CISCO-LWAPP-MFP-MIB- Last revised
- Identity
ciscoLwappMfpMIB- Base OID
1.3.6.1.4.1.9.9.518
Imported Objects
| CISCO-LWAPP-AP-MIB | cLApDot11IfSlotId cLApIfSmtDot11Bssid cLApName cLApSysMacAddress |
| CISCO-LWAPP-DOT11-CLIENT-MIB | cldcClientMacAddress |
| CISCO-LWAPP-TC-MIB | CLEventFrames CLMfpEventType CLMfpVersion CLTimeBaseStatus |
| CISCO-LWAPP-WLAN-MIB | cLWlanIndex (no object page) |
| CISCO-SMI | ciscoMgmt |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Gauge32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | MacAddress TimeInterval TruthValue |
Net-SNMP examples using the cisco MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-LWAPP-MFP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-MFP-MIB::ciscoLwappMfpMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-MFP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-MFP-MIB::ciscoLwappMfpMIB'
Objects (40)
Showing 40 of 40 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.9.518 |
||
.1.3.6.1.4.1.9.9.518.0 |
||
.1.3.6.1.4.1.9.9.518.1 |
||
.1.3.6.1.4.1.9.9.518.1.1 |
||
.1.3.6.1.4.1.9.9.518.1.10 |
||
|
Unsigned32
|
.1.3.6.1.4.1.9.9.518.1.2 |
|
.1.3.6.1.4.1.9.9.518.1.3 |
||
.1.3.6.1.4.1.9.9.518.1.4 |
||
.1.3.6.1.4.1.9.9.518.1.5 |
||
.1.3.6.1.4.1.9.9.518.1.6 |
||
.1.3.6.1.4.1.9.9.518.1.7 |
||
.1.3.6.1.4.1.9.9.518.1.8 |
||
.1.3.6.1.4.1.9.9.518.2 |
||
.1.3.6.1.4.1.9.9.518.2.1 |
||
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.518.2.1.1 |
.1.3.6.1.4.1.9.9.518.2.1.2 |
||
|
CISCO-LWAPP-WLAN-MIBcLWlanIndex
|
.1.3.6.1.4.1.9.9.518.2.1.2.1 |
|
.1.3.6.1.4.1.9.9.518.2.1.2.1.2 |
||
|
|
.1.3.6.1.4.1.9.9.518.2.1.2.1.3 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.518.2.1.2.1.4 |
|
.1.3.6.1.4.1.9.9.518.2.1.3 |
||
.1.3.6.1.4.1.9.9.518.2.1.4 |
||
.1.3.6.1.4.1.9.9.518.2.2 |
||
.1.3.6.1.4.1.9.9.518.2.2.1 |
||
.1.3.6.1.4.1.9.9.518.2.2.2 |
||
.1.3.6.1.4.1.9.9.518.2.2.2.1 |
||
.1.3.6.1.4.1.9.9.518.2.2.2.1.1 |
||
.1.3.6.1.4.1.9.9.518.2.2.2.1.2 |
||
|
|
.1.3.6.1.4.1.9.9.518.2.2.3 |
|
|
|
.1.3.6.1.4.1.9.9.518.2.2.3.1 |
|
|
|
.1.3.6.1.4.1.9.9.518.2.2.3.1.1 |
|
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.518.2.2.3.1.2 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.518.2.2.3.1.3 |
.1.3.6.1.4.1.9.9.518.2.2.4 |
||
.1.3.6.1.4.1.9.9.518.2.2.5 |
||
.1.3.6.1.4.1.9.9.518.2.2.5.1 |
||
.1.3.6.1.4.1.9.9.518.2.2.5.1.1 |
||
.1.3.6.1.4.1.9.9.518.3 |
||
.1.3.6.1.4.1.9.9.518.3.1 |
||
.1.3.6.1.4.1.9.9.518.3.2 |
Dependencies (32) 8 direct · 24 transitive 1 circular Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Circular imports detected
CISCO-LWAPP-AP-MIB → CISCO-LWAPP-DOT11-MIB → CISCO-LWAPP-AP-MIBDependency tree
Suggested compile order
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- CISCO-LWAPP-TC-MIBcisco
- SNMPv2-CONFrfc
- SNMP-FRAMEWORK-MIBrfc
- CISCO-LWAPP-DOT11-MIBcisco
- CISCO-TCcisco
- INET-ADDRESS-MIBrfc
- CISCO-LWAPP-WLAN-MIBcisco
- CISCO-LWAPP-RF-MIBcisco
- IANA-ENTITY-MIBrfc
- UUID-TC-MIBrfc
- ENTITY-MIBrfc
- IANAifType-MIBrfc
- CISCO-LWAPP-AP-MIBcisco
- CISCO-LWAPP-WLAN-POLICY-MIBcisco
- CISCO-QOS-PIB-MIBcisco
- SNMPv2-MIBrfc
- IF-MIBrfc
- BRIDGE-MIBrfc
- P-BRIDGE-MIBrfc
- RMON-MIBrfc
- RFC-1212rfc
- RFC1155-SMIrfc
- RFC1213-MIBrfc
- RFC1271-MIBrfc
- TOKEN-RING-RMON-MIBrfc
- RMON2-MIBrfc
- Q-BRIDGE-MIBrfc
- CISCO-LWAPP-MOBILITY-EXT-MIBcisco
- CISCO-LWAPP-DOT11-CLIENT-MIBcisco
- CISCO-LWAPP-MFP-MIBciscoselected
Conformance Groups (9)
|
ciscoLwappMfpConfigGroup
deprecated
|
This collection of objects represent the
global and WLAN-specific protection capabilities on the controller. |
.1.3.6.1.4.1.9.9.518.3.2.1
|
|
cLMfpCtrlTimeBaseStatus cLMfpCtrlNotifEnable cLMfpApIfMfpVersionSupported cLMfpApIfMfpProtectionCapability cLMfpApIfMfpValidationCapability cLMfpApMfpValidationEnable
This collection of objects provides the information
about the MFP signature protection capabilities as observed on the dot11 interfaces of the LWAPP APs. |
.1.3.6.1.4.1.9.9.518.3.2.2
|
|
|
cLApMacAddress cLApDot11IfSlotIdx cLWlanIdx cLMfpApIfMfpProtectionActual cLMfpApMfpValidationActual cLMfpEventType cLMfpEventTotal cLMfpEventPeriod cLMfpEventFrames
This collection of objects represent the information
carried by the MFP related notifications sent by the agent to a network management station. |
.1.3.6.1.4.1.9.9.518.3.2.3
|
|
|
ciscoLwappMfpNotifsGroup
deprecated
|
ciscoLwappMfpProtectConfigMismatch ciscoLwappMfpValidationConfigMismatch ciscoLwappMfpTimebaseStatus ciscoLwappMfpAnomalyDetected
This collection of objects represent the MFP related
notifications sent by the agent to a network management station. |
.1.3.6.1.4.1.9.9.518.3.2.4
|
|
This collection of objects represent the configuration
for client protection on the controller. |
.1.3.6.1.4.1.9.9.518.3.2.5
|
|
|
This collection of objects represent the status
of client protection on the controller. |
.1.3.6.1.4.1.9.9.518.3.2.6
|
|
|
This collection of objects represent the client
related information in the MFP notifications generated by the controller. |
.1.3.6.1.4.1.9.9.518.3.2.7
|
|
|
ciscoLwappMfpProtectConfigMismatch ciscoLwappMfpValidationConfigMismatch ciscoLwappMfpTimebaseStatus ciscoLwappMfpAnomalyDetected1
This collection of objects represent the MFP related
notifications sent by the agent to a network management station. |
.1.3.6.1.4.1.9.9.518.3.2.8
|
|
|
cLMfpProtectType cLMfpApImpersonation cLMfpKeyRefreshInterval cLMfpVersionRequired cLMfpProtectionEnable
This collection of objects represent the
global and WLAN-specific protection capabilities on the controller. |
.1.3.6.1.4.1.9.9.518.3.2.9
|
Compliance Statements (3)
OID
.1.3.6.1.4.1.9.9.518.3.1.1The compliance statement for the SNMP entities that
implement the ciscoLwappMfpMIB module.
implement the ciscoLwappMfpMIB module.
Required groups
| mandatory | ciscoLwappMfpConfigGroup | |
| mandatory | ciscoLwappMfpStatusGroup | |
| mandatory | ciscoLwappMfpNotifObjsGroup | |
| mandatory | ciscoLwappMfpNotifsGroup |
OID
.1.3.6.1.4.1.9.9.518.3.1.2The compliance statement for the SNMP entities that
implement the ciscoLwappMfpMIB module.
implement the ciscoLwappMfpMIB module.
Required groups
| mandatory | ciscoLwappMfpConfigGroup | |
| mandatory | ciscoLwappMfpStatusGroup | |
| mandatory | ciscoLwappMfpNotifObjsGroup | |
| mandatory | ciscoLwappMfpNotifsNewGroup | |
| mandatory | ciscoLwappMfpConfigSup1Group | |
| mandatory | ciscoLwappMfpStatusSup1Group | |
| mandatory | ciscoLwappMfpNotifObjsSup1Group |
OID
.1.3.6.1.4.1.9.9.518.3.1.3The compliance statement for the SNMP entities that
implement the ciscoLwappMfpMIB module.
implement the ciscoLwappMfpMIB module.
Required groups
| mandatory | ciscoLwappMfpConfigGroupVer1 | |
| mandatory | ciscoLwappMfpStatusGroup | |
| mandatory | ciscoLwappMfpNotifObjsGroup | |
| mandatory | ciscoLwappMfpNotifsNewGroup | |
| mandatory | ciscoLwappMfpConfigSup1Group | |
| mandatory | ciscoLwappMfpStatusSup1Group | |
| mandatory | ciscoLwappMfpNotifObjsSup1Group |
Notifications / Traps (5)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.9.9.518.0.1 |
This notification is sent by the agent when the
controller detects that the AP couldn't apply the protection configuration to the specific radio interface for the specified WLAN. The controller detects the mismatch by matching the MFP configuration requested to be applied with the configuration returned in the acknowledgement as having been applied to the radio interface. The controller also generates this notification to indicate that configuration mismatch is cleared when the values of cLMfpProtectionEnable and cLMfpApIfMfpProtectionActual are found to be the same. This notification is generated by the controller only if MFP has been configured as the protection mechanism through cLMfpProtectType. |
|
.1.3.6.1.4.1.9.9.518.0.2 |
This notification is sent by the agent when the
controller detects that the AP couldn't configure itself with the MFP signature validation configuration. The controller detects the mismatch by matching the MFP configuration requested to be applied with the configuration returned in the acknowledgement as having been configured by the AP. The controller also generates this notification to indicate that configuration mismatch is cleared when the values of cLMfpApMfpValidationEnable and cLMfpApMfpValidationActual are found to be the same. This notification is generated by the controller only if MFP has been configured as the protection mechanism through cLMfpProtectType. |
|
.1.3.6.1.4.1.9.9.518.0.3 |
This notification is sent by the agent to indicate
the controller's status of synchronization of its timebase with that of a central timebase. The notification is sent once after the controller comes up and thereafter, it is sent everytime the status changes. |
|
|
ciscoLwappMfpAnomalyDetected
deprecated
|
.1.3.6.1.4.1.9.9.518.0.4 |
This notification is sent by the agent when the
MFP configuration of the WLAN was violated by the radio interface cLApIfSmtDot11Bssid and detected by the radio interface cLApDot11IfSlotId of the AP cLApMacAddress. The violation is indicated by cLMfpEventType. Through this notification, the controller reports the NMS the occurrence of a total of cLMfpEventTotal volation events, of type cLMfpEventType, upon observing the management frame(s) indicated by cLMfpEventFrames for the last cLMfpEventPeriod time units. When cLMfpEventTotal is 0, it indicates that no further anomalies have recently been detected and that the NMS should clear any alarm raised about the MFP errors. This notification is generated by the controller only if MFP has been configured as the protection mechanism through cLMfpProtectType. |
.1.3.6.1.4.1.9.9.518.0.5 |
This notification is sent by the agent when the
MFP configuration of the WLAN was violated by the radio interface cLApIfSmtDot11Bssid and detected by the radio interface cLApDot11IfSlotId of the AP cLApMacAddress. The violation is indicated by cLMfpEventType. Through this notification, the controller reports the NMS the occurrence of a total of cLMfpEventTotal volation events, of type cLMfpEventType, upon observing the management frame(s) indicated by cLMfpEventFrames for the last cLMfpEventPeriod time units. When cLMfpEventTotal is 0, it indicates that no further anomalies have recently been detected and that the NMS should clear any alarm raised about the MFP errors. cLClientLastSourceMacAddress is used only when the controller generates notifications about client-related attacks. The controller will populate zeros as the value for cLClientLastSourceMacAddress when reporting anomalies sourced by infrastructure devices. This notification is generated by the controller only if MFP has been configured as the protection mechanism through cLMfpProtectType. |