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.
Parsed from file CISCO-LWAPP-MFP-MIB.mib
Module: CISCO-LWAPP-MFP-MIB
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.
Parsed from file CISCO-LWAPP-MFP-MIB.my.txt
Company: None
Module: CISCO-LWAPP-MFP-MIB
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.
ciscoLwappMfpValidationConfigMismatch NOTIFICATION-TYPE OBJECTS { cLApMacAddress, cLMfpApMfpValidationEnable, cLMfpApMfpValidationActual } STATUS current DESCRIPTION "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." ::= { ciscoLwappMfpMIBNotifs 2 }
Vendor: Cisco
Module: CISCO-LWAPP-MFP-MIB
[Automatically extracted from oidview.com]
ciscoLwappMfpValidationConfigMismatch NOTIFICATION-TYPE OBJECTS { cLApMacAddress, cLMfpApMfpValidationEnable, cLMfpApMfpValidationActual } STATUS current DESCRIPTION "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." ::= { ciscoLwappMfpMIBNotifs 2 }
ciscoLwappMfpValidationConfigMismatch NOTIFICATION-TYPE OBJECTS { cLApMacAddress, cLMfpApMfpValidationEnable, cLMfpApMfpValidationActual } STATUS current DESCRIPTION "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." ::= { ciscoLwappMfpMIBNotifs 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.518.0.1 | ciscoLwappMfpProtectConfigMismatch | 0 | 0 | This notification is sent by the agent when the controller detects that the AP couldn't apply the protection configuration to the… |
| 1.3.6.1.4.1.9.9.518.0.3 | ciscoLwappMfpTimebaseStatus | 0 | 0 | This notification is sent by the agent to indicate the controller's status of synchronization of its timebase with that of a cent… |
| 1.3.6.1.4.1.9.9.518.0.4 | ciscoLwappMfpAnomalyDetected | 0 | 0 | This notification is sent by the agent when the MFP configuration of the WLAN was violated by the radio interface cLApIfSmtDot11B… |
| 1.3.6.1.4.1.9.9.518.0.5 | ciscoLwappMfpAnomalyDetected1 | 0 | 0 | This notification is sent by the agent when the MFP configuration of the WLAN was violated by the radio interface cLApIfSmtDot11B… |