CISCO-LWAPP-REAP-MIB: View SNMP OID List / Download 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. Information represented by this MIB is passed by the controller to those Cisco LWAPP APs, that can operate in stand-alone mode. 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, 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. 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. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Native VLAN ID A switch port and/or AP can be configured with a 'native VLAN ID'. Untagged or priority-tagged frames are implicitly associated with the native VLAN ID. The default native VLAN ID is '1' if VLAN tagging is enabled. The native VLAN ID is '0' or 'no VLAN ID' if VLAN tagging is not enabled. Remote Edge Access Point ( REAP ) The LWAPP AP that can also act as a stand-alone AP when it loses communication with the controller it was associated with. When REAP can reach the controller (connected state), it gets help from controller to complete client authentication. When a controller is not reachable by REAP, it goes into standalone state and does client authentication by itself. All data packets from clients are either bridged locally (local-switch) or forwarded to the controller (central-switch) depending on the WLAN configuration. Virtual LAN VLAN defined in the IEEE 802.1Q VLAN standard supports logically segmenting of LAN infrastructure into different subnets or workgroups so that packets are switched only between ports within the same VLAN. VLAN ID Each VLAN is identified by a 12-bit 'VLAN ID'. A VLAN ID of '0' is used to indicate 'no VLAN ID'. Valid VLAN IDs range from '1' to '4095'. Home AP A REAP AP can be installed at end-user home. Home AP ethernet port will be connected to DSL or cable modem at home. Home AP will be primed with Controller IP Address so that it will join with controller. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol

This table represents the WLAN configuration sent by the controller to REAPs so that the APs can operate in stand-alone mode. LWAPP APs operating in REAP mode locally switch the data frames of the associated clients, rather than tunneling them through to the LWAPP controller as LWAPP data packets. The LWAPP controller passes this configuration set to the LWAPP AP during the AP initialization so that the AP can operate in stand-alone mode when it fails to reach the controller. The configuration is also passed to the REAP when they are individually modified through separate LWAPP messages. The REAP updates itself with the information received through these LWAPP messages. This table has a one-to-one relationship with cLWlanConfigTable of the CISCO-LWAPP-WLAN-MIB. There exist a row in this table corresponding to each row representing a WLAN in cLWlanConfigTable. Note that the configuration represented by this table is applicable only for REAPs. The controller will send this configuration set only to the REAP APs for their operation in standalone mode.

Each entry represents a conceptual row in cLReapWlanConfigTable and corresponds to the packet switching configuration for a particular WLAN.

This object indicates the behavior of the REAP when switching the data frames of the clients associated to it through the WLAN identified by cLWlanIndex. A value of 'true' indicates that the AP, on which this WLAN is configured, may locally switch the data packets of the clients in the WLAN instead of tunneling them to the central controller for switching. A value of 'false' indicates that the AP should tunnel all the data packets of the wireless clients in the WLAN to the central controller for switching. Note that the value of 'true' will be effective only if the WLAN is configured on a REAP.

This object indicates whether Client IP Address learning is enabled on the controller. When layer two tunneling is employed the IP learning on controller has to be disabled. Otherwise, the controller is unable to learn the client's IP address and cannot move it to the associated state. A value of 'true' indicates the controller does checks for IP sent by the HREAP AP. A value of 'false' indicates the controller does not check for IP from the locally switch HREAP AP.

This object specifies the behavior of the REAP, on where to handle the authentication of the client associated to the WLAN indicated by cLWlanIndex. A value of 'true' indicates that the AP, on which this WLAN is configured, will do the authentication of the clients in the WLAN locally instead of of sending them to the central controller. A value of 'false' indicates that the AP should send the information to the central controller to do the authentication of the client. Note that the value of 'true' will be effective only if the WLAN is configured on a REAP and WLAN is configured for local switching of the data.

This table represents the VLAN configuration of REAPs. The agent adds a row to this table corresponding to each row representing a REAP in cLApTable of the CISCO-LWAPP-AP-MIB. The agent deletes the row either when the AP dissociates from the controller or moved out of the remote mode.

Each entry represents a conceptual row in cLReapApConfigTable and corresponds to the VLAN configuration of a REAP.

This object defines the Native VLAN ID for the particular AP identified by cLApSysMacAddress. Note that this particular object can be modified through a Set request only if the AP is a REAP. The agent is expected to reject the attempt to set this object for APs in other modes.

This object indicates the availability of Native VLAN configured through cLReapApNativeVlanId on this REAP. A value of 'true' indicates that the VLAN configured as native through cLReapApNativeVlanId is enabled on the REAP and that the REAP can reach the controller through the native VLAN. A value of 'false' indicates that the VLAN configured as native through cLReapApNativeVlanId is disabled and the REAP can't reach the controller.

This object represents if this REAP AP is used as Home AP. A value of 'true' indicates that this REAP AP is a Home AP. A value of 'false' indicates that this REAP AP is not a Home AP.

This object represents if this REAP AP should join controller which has least latency. A value of 'true' indicates that this REAP AP will join controller which has least latency. A value of 'false' indicates that this REAP AP will not consider latency in selecting controller to join.

This object can be used to reset local SSID on a Home AP. A value of true indicates that the local SSID is to be reset. A value of false on this during set will return error. A value of false will be returned on get.

This table defines the WLAN / VLAN Id mappings to be configured for the REAP identified by cLApSysMacAddress. VLAN Id configured through this table is passed to the respective REAP through the 'Add WLAN' LWAPP message, sent as part of the 'Configure Response message from the controller to the REAP, during the initialization of the REAP. The REAP maps the VLAN to the particular WLAN to locally switch the data packets when those APs are in standalone mode. Thus, the information added through this table is applicable for REAPs only. VLANs are configured on WLANs for which local switching of packets is enabled through cLReapWlanEnLocalSwitching. This means that a row is added to this table only if there are WLANs available on the controller with local switching enabled and the AP is a REAP.

Each entry represents a conceptual row that corresponds to one WLAN / VLAN Id mapping to be applied to the REAP identified by cLApSysMacAddress.

This object represents the VLAN ID to be mapped to the WLAN identified by cLWlanIndex.

This table represents the configuration for REAPs so that the APs can be configured as a group. Entries are added or deleted by the user through the use of cLReapGroupRowStatus.

Each entry represents a conceptual row in cLReapGroupConfigTable.

This object uniquely identifies an entry in cLReapGroupConfigTable.

The object represents the value that maps to the primary RADIUS server for this group. A value of 0 indicates that the primary RADIUS server is not configured for this group.

The object represents the value that maps to the secondary RADIUS server for this group. A value of 0 indicates that the primary RADIUS server is not configured for this group.

This object represents the storage type for this conceptual row.

This object represents the status column for a conceptual row in this table.

This object represents timeout value for the PAC (protected access credentials). Superceded by cLReapGroupRadiusPacTimeoutCtrl

This object configures the authority ID.

This object represents the authority information.

This object represents the RADIUS server key. For security the key always returns '****'.

This parameter represents whether anonymous provisioning is enabled. A value of 'true' indicates the controller will ignore the key configured in cLReapGroupRadiusServerKey anonymous requests. A value of 'false' indicates that the controller will use the key configured by cLReapGroupRadiusServerKey.

This parameter represents whether RADIUS is enabled. A value of 'true' indicates that RADIUS is enabled. A value of 'false' indicates that RADIUS is disabled.

This parameter represents whether LEAP is enabled. A value of 'true' indicates that LEAP is enabled. A value of 'false' indicates that LEAP is disabled.

This parameter represents whether EAP-FAST is enabled. A value of 'true' indicates that EAP-FAST is enabled. A value of 'false' indicates that EAP-FAST is disabled.

This parameter represents timeout value for the PAC (protected access credentials). Valid range of timeout is 2 to 4095, and value 0 stands for disable.

This table represents the group associated with an AP. Entries are added or deleted by the user through the use of cLReapGroupApRowStatus.

Each entry represents a conceptual row in cLReapGroupApConfigTable.

This object represents the storage type for this conceptual row.

This object represents the status column for a conceptual row in this table.

This table represents the group associated with an User. Entries are added or deleted by the application through the use of cLReapGroupUserRowStatus.

Each entry represents a conceptual row in cLReapGroupUserConfigTable.

This object represents the user name for this group. user name is used for authenticating a client associated to an AP within the group.

This object represents the password for this user.

This object represents the storage type for this conceptual row.

This object represents the status column for a conceptual row in this table.

The compliance statement for the SNMP entities that implement the ciscoLwappReapMIB module.

The compliance statement for the SNMP entities that implement the ciscoLwappReapMIB module.

The compliance statement for the SNMP entities that implement the ciscoLwappReapMIB module.

The compliance statement for the SNMP entities that implement the ciscoLwappReapMIB module.

The compliance statement for the SNMP entities that implement the ciscoLwappReapMIB module.

The compliance statement for the SNMP entities that implement the ciscoLwappReapMIB module.

This collection of objects represent the WLAN configuration to be passed to the REAP.

This collection of objects represent the information needed by the REAP AP to locally switch the client data packets. The collection also includes the VLAN configuration on the REAP.

This collection of objects represent the information needed by the REAP APs to configure REAP groups.

This collection of objects represent the RADIUS information needed by the REAP APs in a REAP group.

This collection of objects represent the information needed for user authentication.

This supplemental collection of objects represents objects related to Home AP configuration for REAP AP.

This collection of objects represent the RADIUS information needed by the REAP APs in a REAP group.

This collection of objects represent additional WLAN configuration to be passed to the REAP.