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 Cisco Light-weight LWAPP Access Points.
Information provided by this MIB is used to manage
AAA information on the controller.
The relationship between CC and the LWAPP APs
can be depicted as follows:
+......+ +......+ +......+
+ + + + + +
+ CC + + CC + + CC +
+ + + + + +
+......+ +......+ +......+
.. . .
.. . .
. . . .
. . . .
. . . .
. . . .
+......+ +......+ +......+ +......+
+ + + + + + + +
+ AP + + AP + + AP + + AP +
+ + + + + + + +
+......+ +......+ +......+ +......+
. . .
. . . .
. . . .
. . . .
. . . .
+......+ +......+ +......+ +......+
+ + + + + + + +
+ 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.
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
and client are used interchangeably.
Terminal Access Controller Access-Control System
( TACACS )
A remote authentication protocol that is used to
communicate with an authentication server.
TACACS allows a remote access server to communicate
with an authentication server in order to determine
if the user has access to the network.
Remote Authentication Dial In User Service (RADIUS)
It is an AAA (authentication, authorization and accounting)
protocol for applications such as network access or
IP mobility. It is intended to work in both local and
roaming situations.
Wireless LAN ( WLAN )
It is a wireless local area network, which is the
linking of two or more computers without using wires.
It uses radio communication to accomplish the same
functionality of a wired LAN.
PAP - Password Authentication Protocol
CHAP - Challenge Handshake Authentication Protocol
MD5-CHAP - Message Digest 5 Challenge Handshake Authentication
Protocol
LSC - Local Significant Certificate
LSC can be used if we want our own public key
infrastructure (PKI) to provide better security,
to have control of our certificate authority (CA),
and to define policies, restrictions, and usages
on the generated certificates.
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
ication is sent by the agent when the
controller detects that the RADIUS server is
activated in the global list. The RADIUS server
is identified by the address (claRadiusAddress)
and port number (claRadiusPortNum).
ciscoLwappAAARadiusServerGlobalDeactivated
.1.3.6.1.4.1.9.9.598.0.2
ication is sent by the agent when the
controller detects that the RADIUS server is
deactivated in the global list. The RADIUS server
is identified by the address (claRadiusAddress)
and port number (claRadiusPortNum).
ciscoLwappAAARadiusServerWlanActivated
.1.3.6.1.4.1.9.9.598.0.3
ication is sent by the agent when the
controller detects that the RADIUS server is
activated on the WLAN. The RADIUS server
is identified by the address (claRadiusAddress)
and port number (claRadiusPortNum).
ciscoLwappAAARadiusServerWlanDeactivated
.1.3.6.1.4.1.9.9.598.0.4
ication is sent by the agent when the
controller detects that the RADIUS server is
deactivated on the WLAN. The RADIUS server
is identified by the address (claRadiusAddress)
and port number (claRadiusPortNum).
ciscoLwappAAARadiusReqTimedOut
.1.3.6.1.4.1.9.9.598.0.5
ication is sent by the agent when the
controller detects that the RADIUS server failed
to respond to request from a client/user. The RADIUS
server is identified by the address (claRadiusAddress)
and port number (claRadiusPortNum).
ciscoLwappAAARadiusAuthServerAvailable
.1.3.6.1.4.1.9.9.598.0.6
ication is sent by the agent when the
controller detects that the RADIUS authenticating
server is available/responsive when it was
previously unavailable/unresponsive. The state
change triggers this notification. The RADIUS
server is identified by the address
(claRadiusAddress) and port number
(claRadiusPortNum).
ciscoLwappAAARadiusAuthServerUnavailable
.1.3.6.1.4.1.9.9.598.0.7
ication is sent by the agent when the
controller detects that the RADIUS authenticating
server is unavailable/unresponsive when it was
previously available/responsive. The state change
triggers this notification. The RADIUS server
is identified by the address (claRadiusAddress)
and port number (claRadiusPortNum).
ciscoLwappAAARadiusAcctServerAvailable
.1.3.6.1.4.1.9.9.598.0.8
ication is sent by the agent when the
controller detects that the RADIUS accounting server
is available/responsive when it was previously
unavailable/unresponsive. The state change
triggers this notification. The RADIUS server
is identified by the address (claRadiusAddress)
and port number (claRadiusPortNum).
ciscoLwappAAARadiusAcctServerUnavailable
.1.3.6.1.4.1.9.9.598.0.9
ication is sent by the agent when the
controller detects that the RADIUS accounting server
is unavailable/unresponsive when it was previously
available/responsive. The state change triggers
this notification. The RADIUS server is identified
by the address (claRadiusAddress) and port number
(claRadiusPortNum).