CISCO-LWAPP-CLIENT-ROAMING-MIB
AI MIB Summary
The CISCO-LWAPP-CLIENT-ROAMING-MIB enables monitoring of Cisco Compatible Extensions (CCX) roaming RF parameters and client association states on Lightweight Access Point Protocol (LWAPP) Central Controllers. It provides visibility into the roaming behavior of Mobile Nodes (clients) as they transition between Access Points within a centralized wireless architecture.
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.
Information provided by this MIB is for CCX related features as specified in the CCX specifications. This MIB covers roaming RF parameters for CCX clients.
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.
Basic Service Set ( BSS )
The IEEE 802.11 BSS of an AP comprises of the stations directly associating with the AP.
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'.
Cisco Compatible eXtensions (CCX)
Wireless LAN Access Points (APs) manufactured by Cisco Systems have features and capabilities beyond those in related standards (e.g., IEEE 802.11 suite of standards ,Wi-Fi recommendations by WECA, 802.1X security suite,etc). A number of features provide higher performance.For example, Cisco AP transmits a specific Information Element, which the clients adapt to for enhanced performance. Similarly, a number of features are implemented by means of proprietary Information Elements, which Cisco clients use in specific ways to carry out tasks above and beyond the standard. Other examples of feature categories are roaming and power saving.
Client Roaming
A client may decide to reassociate with another AP for reasons of its own choosing. The decision of whether or not to use the information contained in the AP list is up to the discretion of the implementor, as long as the roam time requirement is met.
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.
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:
ciscoLwappClRoamMIB.1.3.6.1.4.1.9.9.523
44
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
44 total| Object Name |
|---|
ciscoLwappClRoamMIBThis 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.
Information provided by this MIB is for CCX related
features as specified in the CCX specifications.
This MIB covers roaming RF parameters for CCX
clients.
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.
Basic Service Set ( BSS )
The IEEE 802.11 BSS of an AP comprises of the
stations directly associating with the AP.
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'.
Cisco Compatible eXtensions (CCX)
Wireless LAN Access Points (APs) manufactured by Cisco
Systems have features and capabilities beyond those in
related standards (e.g., IEEE 802.11 suite of
standards ,Wi-Fi recommendations by WECA, 802.1X
security suite,etc). A number of features provide
higher performance.For example, Cisco AP transmits a
specific Information Element, which the clients adapt
to for enhanced performance. Similarly, a number of
features are implemented by means of proprietary
Information Elements, which Cisco clients use in
specific ways to carry out tasks above and beyond the
standard. Other examples of feature categories are
roaming and power saving.
Client Roaming
A client may decide to reassociate with another AP for
reasons of its own choosing. The decision of whether
or not to use the information contained in the AP list
is up to the discretion of the implementor, as long as
the roam time requirement is met.
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.
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.523 |
ciscoLwappClRoamMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.523.0 |
ciscoLwappClRoamMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.523.1 |
clcrRoamDot11aRfParamConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.523.1.1 |
clcrDot11aModeThis object represents how the controller chooses
the values of the RF parameters needed to manage
roaming in 802.11a networks.rw CLDot11RfParamMode (CISCO-LWAPP-TC-MIB) .1.3.6.1.4.1.9.9.523.1.1.1 |
clcrDot11aMinRssiThis object indicates the Minimum Received Signal
Strength Indication (RSSI) in dBm required to
associate with the AP. It also defines the edge of
coverage for the BSS. If the client's average
received signal power dips below this threshold,
clients must have roamed to another AP with a
stronger signal.
This object is superceded by clcrDot11aMinRssiV2rwdeprecated Integer32 (-90..-80) UNITS "dBm" .1.3.6.1.4.1.9.9.523.1.1.2 |
clcrDot11aHysteresisThis object indicates how much stronger the signal
strength (dB) of a neighbor AP must be, in order
for the client to roam to it. The use of roaming
hysteresis is intended to reduce the amount of
clients roaming back and forth between BSSs if the
client is physically located on or near the border
between two BSSs.
This object is superceded by clcrDot11aHysteresisV2rwdeprecated Integer32 .1.3.6.1.4.1.9.9.523.1.1.3 |
clcrDot11aAdaptiveScanThresholdThis object configures the threshold for the
strength of the signals received(RSSI) from an AP,
as seen by an associated client, below which the
client must be able to roam to a neighbor AP within
the specified Transition Time configured through
clcrDot11aTransitionTime.
This object is superceded by clcrDot11aAdaptiveScanThresholdV2rwdeprecated Integer32 (-77..-70) UNITS "dBm" .1.3.6.1.4.1.9.9.523.1.1.4 |
clcrDot11aTransitionTimeThis object configures the maximum time duration
permitted for the client to detect a suitable
neighbor AP to roam to and to complete the roam,
whenever the RSSI from the client?s associated AP
is below the adaptive scan threshold configured
through clcrDot11aAdaptiveScanThreshold. The time
is expressed in 100th of a second.
This object is superceded by clcrDot11aTransitionTimeV2rwdeprecated TimeInterval .1.3.6.1.4.1.9.9.523.1.1.5 |
clcrDot11aMinRssiV2This object indicates the Minimum Received Signal
Strength Indication (RSSI) in dBm required to
associate with the AP. It also defines the edge of
coverage for the BSS. If the client's average
received signal power dips below this threshold,
clients must have roamed to another AP with a
stronger signal.rw Integer32 (-255..255) UNITS "dBm" .1.3.6.1.4.1.9.9.523.1.1.6 |
clcrDot11aHysteresisV2This object indicates how much stronger the signal
strength (dB) of a neighbor AP must be, in order
for the client to roam to it. The use of roaming
hysteresis is intended to reduce the amount of
clients roaming back and forth between BSSs if the
client is physically located on or near the border
between two BSSs.rw Integer32 .1.3.6.1.4.1.9.9.523.1.1.7 |
clcrDot11aAdaptiveScanThresholdV2This object configures the threshold for the
strength of the signals received(RSSI) from an AP,
as seen by an associated client, below which the
client must be able to roam to a neighbor AP within
the specified Transition Time configured through
clcrDot11aTransitionTime.rw Integer32 (-255..255) UNITS "dBm" .1.3.6.1.4.1.9.9.523.1.1.8 |
clcrDot11aTransitionTimeV2This object configures the maximum time duration
permitted for the client to detect a suitable
neighbor AP to roam to and to complete the roam,
whenever the RSSI from the clients associated AP
is below the adaptive scan threshold configured
through clcrDot11aAdaptiveScanThreshold. The time
is expressed in 100th of a second.rw TimeInterval .1.3.6.1.4.1.9.9.523.1.1.9 |
clcrRoamDot11bRfParamConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.523.1.2 |
clcrDot11bModeThis object represents how the controller chooses
the values of the RF parameters needed to manage
roaming in 802.11b/g networks.rw CLDot11RfParamMode (CISCO-LWAPP-TC-MIB) .1.3.6.1.4.1.9.9.523.1.2.1 |
clcrDot11bMinRssiThis object indicates the minimum Received Signal
Strength Indication (RSSI) in dBm required to
associate with the AP. It also defines the edge of
coverage for the BSS. If the client's average
received signal power dips below this threshold,
clients must have roamed to another AP with a
stronger signal.
This object is superceded by clcrDot11bMinRssiV2rwdeprecated Integer32 (-90..-80) UNITS "dBm" .1.3.6.1.4.1.9.9.523.1.2.2 |
clcrDot11bHysteresisThis object indicates how much stronger the signal
strength (dB) of a neighbor AP must be, in order
for the client to roam to it. The use of roaming
hysteresis is intended to reduce the amount of
clients roaming back and forth between BSSs if the
client is physically located on or near the border
between two BSSs.
This object is superceded by clcrDot11bHysteresisV2rwdeprecated Integer32 .1.3.6.1.4.1.9.9.523.1.2.3 |
clcrDot11bAdaptiveScanThresholdThis object configures the threshold for the
strength of the signals received(RSSI) from an AP,
as seen by an associated client, below which the
client must be able to roam to a neighbor AP within
the specified Transition Time configured through
clcrDot11bTransitionTime.
This object is superceded by clcrDot11bAdaptiveScanThresholdV2rwdeprecated Integer32 (-77..-70) UNITS "dBm" .1.3.6.1.4.1.9.9.523.1.2.4 |
clcrDot11bTransitionTimeThis object configures the maximum time duration
permitted for the client to detect a suitable
neighbor AP to roam to and to complete the roam,
whenever the RSSI from the client is associated AP
is below the adaptive scan threshold configured
through clcrDot11aAdaptiveScanThreshold. The
time is expressed in 100th of a second.
This object is superceded by clcrDot11bTransitionTimeV2rwdeprecated TimeInterval .1.3.6.1.4.1.9.9.523.1.2.5 |
clcrDot11bMinRssiV2This object indicates the minimum Received Signal
Strength Indication (RSSI) in dBm required to
associate with the AP. It also defines the edge of
coverage for the BSS. If the client's average
received signal power dips below this threshold,
clients must have roamed to another AP with a
stronger signal.rw Integer32 (-255..255) UNITS "dBm" .1.3.6.1.4.1.9.9.523.1.2.6 |
clcrDot11bHysteresisV2This object indicates how much stronger the signal
strength (dB) of a neighbor AP must be, in order
for the client to roam to it. The use of roaming
hysteresis is intended to reduce the amount of
clients roaming back and forth between BSSs if the
client is physically located on or near the border
between two BSSs.rw Integer32 .1.3.6.1.4.1.9.9.523.1.2.7 |
clcrDot11bAdaptiveScanThresholdV2This object configures the threshold for the
strength of the signals received(RSSI) from an AP,
as seen by an associated client, below which the
client must be able to roam to a neighbor AP within
the specified Transition Time configured through
clcrDot11bTransitionTime.rw Integer32 (-255..255) UNITS "dBm" .1.3.6.1.4.1.9.9.523.1.2.8 |
clcrDot11bTransitionTimeV2This object configures the maximum time duration
permitted for the client to detect a suitable
neighbor AP to roam to and to complete the roam,
whenever the RSSI from the client is associated AP
is below the adaptive scan threshold configured
through clcrDot11aAdaptiveScanThreshold. The
time is expressed in 100th of a second.rw TimeInterval .1.3.6.1.4.1.9.9.523.1.2.9 |
clcrRoamReasonReport OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.523.1.3 |
clcrRoamReasonReportTableThis table provides the reasons for CCX clients
roaming from one AP to another.
When a CCX client associates to an AP, it will always
send an IAPP information packet to the new AP listing
the characteristics of the previous AP.
An entry is added to this table when a roam reason
report is sent by a CCX client when it roams to a
new AP. SEQUENCE OF ClcrRoamReasonReportEntry .1.3.6.1.4.1.9.9.523.1.3.1 |
clcrRoamReasonReportEntryEach entry corresponds to the roam reason report
sent by a CCX client to the new AP to which client
associates. ClcrRoamReasonReportEntry .1.3.6.1.4.1.9.9.523.1.3.1.1 |
clcrRoamClientMacAddressThis object indicates the mac address of the
client which has roamed to a new AP. MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.523.1.3.1.1.1 |
clcrRoamClientTimeStampThis object indicates the time instance at which
this report was received by the new AP, to which
client roamed to. This represents number of
seconds elapsed since 00:00:00 on January 1, 1970,
Coordinated Universal Time (UTC). So a value of
'1131362704' means 'Mon Nov 7 16:55:04 2005'. TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.9.9.523.1.3.1.1.2 |
clcrRoamNewApMacAddressThis object indicates the mac address of the
current AP to which client has roamed to. This AP
receives the roam reason report.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.523.1.3.1.1.3 |
clcrRoamPrevApMacAddressThis object indicates the mac address of the
previous AP to which client was associated.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.523.1.3.1.1.4 |
clcrRoamPrevApChannelThis object indicates the channel number at which
the client was associated to the previous AP.ro CLDot11Channel (CISCO-LWAPP-TC-MIB) .1.3.6.1.4.1.9.9.523.1.3.1.1.5 |
clcrRoamPrevApSsidThis object indicates the SSID at which the client
was associated to the previous AP.ro OCTET STRING .1.3.6.1.4.1.9.9.523.1.3.1.1.6 |
clcrRoamDisassocTimeIntervalThis object indicates the time elapsed since the
client disassociated, in hundredth of a second.ro TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.9.9.523.1.3.1.1.7 |
clcrRoamReasonThis object indicates the reason for a client to
roam to a new AP.
The semantics are as follows.
clcrUnspecified - The reason is not known or can't
be found.
clcrPoorLink - Normal roam due to poor link
(excessive retries, too much interference, RSSI too
low, etc.)
clcrLoadBalancing - Normal roam due to load
balancing
clcrInsufficientCapacity - Roaming occured due to
the insufficient capacity on the previous AP
(TSPEC rejected)
clcrDirectedRoam - Roaming is directed by the
802.11 wireless Infrastructure
clcrFirstAssociation - This is the first
association to a particular WLAN
clcrRoamingIn - Roaming in from cellular or other
WAN
clcrRoamingOut - Roaming out to cellular or other
WAN
clcrBetterAp - Normal roam due to better AP found
clcrDisassociated - Deauthenticated or
Disassociated from the previous AP.ro Enumeration .1.3.6.1.4.1.9.9.523.1.3.1.1.8 |
clcrRoamDot11Stats OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.523.1.4 |
clcrDot11StatsTableThis table populates the statistics collected when
the client roamed in the WLAN.
There exists a row in this table for each conceptual
row in cLApDot11IfTable that represents a dot11
interface of an AP. SEQUENCE OF ClcrDot11StatsEntry .1.3.6.1.4.1.9.9.523.1.4.1 |
clcrDot11StatsEntryEach entry represents a conceptual row in
clcrDot11StatsTable and corresponds to the roam
reason report sent by a CCX client to the new AP
which the client associates to. ClcrDot11StatsEntry .1.3.6.1.4.1.9.9.523.1.4.1.1 |
clcrDot11NeighborRequestRxThis object indicates the count of the number
of requests received from an E2E client for
neighbor updates.ro Counter32 .1.3.6.1.4.1.9.9.523.1.4.1.1.1 |
clcrDot11NeighborReplySentThis object indicates the count of the number
of replies sent to the client in reply to the
request for neighbor updates received from the
client.ro Counter32 .1.3.6.1.4.1.9.9.523.1.4.1.1.2 |
clcrDot11RoamReasonReportRxThis object reports the count of the number
of roam reason reports received from CCX
clients.ro Counter32 .1.3.6.1.4.1.9.9.523.1.4.1.1.3 |
clcrDot11BcastUpdatesSentThis object indicates the count of the number of
broadcast neighbor updates sent by an AP.ro Counter32 .1.3.6.1.4.1.9.9.523.1.4.1.1.4 |
ciscoLwappClRoamMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.523.2 |
ciscoLwappClRoamMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.523.2.1 |
ciscoLwappClRoamMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.523.2.2 |