CISCO-LWAPP-DOT11-LDAP-MIB
AI MIB Summary
The CISCO-LWAPP-DOT11-LDAP-MIB enables monitoring and management of Lightweight Directory Access Protocol (LDAP) integration parameters on Cisco Centralized Controllers (CC) that terminate Light Weight Access Point Protocol (LWAPP) tunnels from lightweight access points. This module specifically tracks LDAP authentication configurations, directory service connectivity states, and associated security settings required for centralized user management within the LWAPP 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 used to manage LDAP features 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.
Gratuitous Probe Response (GPR)
The Gratuitous Probe Response feature aids in conserving battery power of WLAN-enabled cell phones by providing a high rate packet on the order of tens of milliseconds such that these kind of phones can wake up and wait at predefined intervals, to reduce battery power. The GPR packet is transmitted from the AP at a predefined time interval.
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.
Lightweight Directory Access Protocol ( LDAP )
LDAP is a protocol used for obtaining directory services and runs over TCP/IP.
Transport Layer Security ( TLS )
This is a cryptographic protocol which provides secure communication over the network.
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:
ciscoLwappDot11LdapMIB.1.3.6.1.4.1.9.9.614
30
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
30 total| Object Name |
|---|
ciscoLwappDot11LdapMIBThis 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 used to manage
LDAP features 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.
Gratuitous Probe Response (GPR)
The Gratuitous Probe Response feature aids in conserving
battery power of WLAN-enabled cell phones by providing
a high rate packet on the order of tens of milliseconds
such that these kind of phones can wake up and wait at
predefined intervals, to reduce battery power. The
GPR packet is transmitted from the AP at a predefined
time interval.
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.
Lightweight Directory Access Protocol ( LDAP )
LDAP is a protocol used for obtaining directory services
and runs over TCP/IP.
Transport Layer Security ( TLS )
This is a cryptographic protocol which provides secure
communication over the network.
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.614 |
ciscoLwappDot11LdapMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.614.0 |
ciscoLwappDot11LdapMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.614.1 |
cldlConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.614.1.1 |
cldlServerTableThis table lists the information about LDAP servers
configured on the controller. Entries are added or deleted
by the user through the use of cldlServerRowStatus. SEQUENCE OF CldlServerEntry .1.3.6.1.4.1.9.9.614.1.1.1 |
cldlServerEntryEach entry corresponds to a row in cldlServerTable and
represents the information about an LDAP server the
controller would contact for its operations. CldlServerEntry .1.3.6.1.4.1.9.9.614.1.1.1.1 |
cldlServerIndexThis object uniquely identifies an entry in
cldlServerTable. Unsigned32 .1.3.6.1.4.1.9.9.614.1.1.1.1.1 |
cldlServerAddressTypeThis object represents the type of the network
address made available through cldlServerAddress.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.614.1.1.1.1.2 |
cldlServerAddressThis object represents the address of the LDAP server
that can be contacted by the controller for the purpose
of authentication, authorization and accounting.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.614.1.1.1.1.3 |
cldlServerPortNumThis object represents the port number at which the
controller contacts the LDAP server.rw InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.614.1.1.1.1.4 |
cldlServerStateThis object indicates whether the LDAP server is currently
in use by the controller. A value of 'true' indicates that
the LDAP server is in use. A value of 'false' indicates that
the LDAP server is not in use.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.614.1.1.1.1.5 |
cldlServerTimeoutThis object represents the retransmit time-out value for
this LDAP server. If there is no response from the LDAP
server, the controller will wait for this duration,
before retransmitting.rw Unsigned32 .1.3.6.1.4.1.9.9.614.1.1.1.1.6 |
cldlServerUserBaseThis object represents the name of the sub-tree in
the LDAP server that contains the information about all
the users in that sub-tree.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.614.1.1.1.1.7 |
cldlServerUserNameAttributeThis object represents the attribute that stores
the name of the user.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.614.1.1.1.1.8 |
cldlServerUserNameThis object represents the name of the user.
This is the value for the attribute identified by
cldlServerUserNameAttribute.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.614.1.1.1.1.9 |
cldlServerSecurityEnableThis object indicates whether the LDAP transactions are
secured. A value of 'true' indicates that all the
LDAP transactions of the controller are secured the use
of TLS tunnel. A value of 'false' indicates that the LDAP
transactions are not secured.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.614.1.1.1.1.10 |
cldlServerStorageTypeThis object represents the storage type for this conceptual
row.rw StorageType (SNMPv2-TC) .1.3.6.1.4.1.9.9.614.1.1.1.1.11 |
cldlServerRowStatusThis object represents the status column for a
conceptual row in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.614.1.1.1.1.12 |
cldlServerBindTypeThis object represents the kind of authentication the
Controller does with the LDAP server.rw CldlBindType .1.3.6.1.4.1.9.9.614.1.1.1.1.13 |
cldlServerAuthBindUserNameThis object represents the name used by the Controller
for the authentication with the LDAP server.
For values other than 'authenticated', as identified through
cldlServerBindType, this object will be populated with an
empty string.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.614.1.1.1.1.14 |
cldlServerAuthBindPasswordThis object represents the password used by the Controller
for authentication with the LDAP server.
For security purposes, this object will be populated with
the string '****', when a valid password has been configured.
For values other than 'authenticated', as identified through
cldlServerBindType, this object will be populated with an
empty string.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.614.1.1.1.1.15 |
cldlWlanLdapTableThis table helps to map LDAP servers for WLANs
from cldlServerTable through the use of
cldlServerIndex. When a client gets associated to a WLAN,
the controller uses those LDAP servers that are
mapped to that WLAN for access to information about
the clients.
The creation of a new row in cLWlanConfigTable,
through an explicit network management action,
results in creation of an entry in this table.
Similarly, deletion of a row in
cLWlanConfigTable through user action causes the
deletion of corresponding row in this table.
This table has an one-to-one relationship with
cLWlanConfigTable of CISCO-LWAPP-WLAN-MIB. There
exists an entry in this table for each corresponding
entry in the cLWlanConfigTable. SEQUENCE OF CldlWlanLdapEntry .1.3.6.1.4.1.9.9.614.1.1.2 |
cldlWlanLdapEntryEach entry represents a conceptual row in
cldlWlanLdapTable and represents the LDAP
configuration for a particular WLAN
identified by cLWlanIndex. CldlWlanLdapEntry .1.3.6.1.4.1.9.9.614.1.1.2.1 |
cldlWlanLdapPrimaryServerIndexThe object represents the value that maps to the
primary LDAP server for this WLAN. A value of 0
indicates that the primary LDAP server is not
configured for this WLAN.rw Unsigned32 .1.3.6.1.4.1.9.9.614.1.1.2.1.1 |
cldlWlanLdapSecondaryServerIndexThe object represents the value that maps to the
secondary LDAP server for this WLAN. A value of 0
indicates that the primary LDAP server is not
configured for this WLAN.rw Unsigned32 .1.3.6.1.4.1.9.9.614.1.1.2.1.2 |
cldlWlanLdapTertiaryServerIndexThe object represents the value that maps to the
tertiary LDAP server for this WLAN. A value of 0
indicates that the primary LDAP server is not
configured for this WLAN.rw Unsigned32 .1.3.6.1.4.1.9.9.614.1.1.2.1.3 |
cldlStatus OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.614.1.2 |
ciscoLwappDot11LdapMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.614.2 |
ciscoLwappDot11LdapMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.614.2.1 |
ciscoLwappDot11LdapMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.614.2.2 |