CISCO-LWAPP-RRM-MIB: View SNMP OID List / Download MIB

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 study the RRM on the WLAN. 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. 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'. 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. Radio Resource Management ( RRM ) RRM is the system level control of co-channel interference and other radio transmission characteristics in wireless communication systems. Received Signal Strength Indicator ( RSSI ) A measure of the strength of the signal as observed by the entity that received it, expressed in 'dbm'. Coverage Hole Detection ( CHD ) If clients on an Access Point are detected at low RSSI levels, it is considered a coverage hole by the Access Points. This indicates the existence of an area where clients are continually getting poor signal coverage, without having a viable location to roam to. Dynamic Channel Assignment (DCA) Dynamic channel assignment (DCA) is used by the controller to minimize adjacent channel interference between access points. Dynamic Frequency Selection (DFS) Dynamic frequency selection (DFS) is used by the controller to detect radar signals and avoid interfering with them. RRM RF Grouping Radio Resource Management (RRM) allows the Cisco WLAN controllers to continuously analyze the existing RF environments, and automatically adjust the AP power and channel configurations in order to help alleviate overlapping channel interference, signal coverage problems, and so forth. An RF group is a cluster of Cisco wireless controllers that coordinates its RRM calculations on a per 802.11-network basis. An RF group exists for each 802.11 network type. Clustering controllers into RF groups enables the RRM algorithms to scale beyond a single controller. +....+ Auto-leader +....+ Auto-member + + <-------------> + C2 + + + (802.11a network) +....+ + C1 + + + + + Static-member +....+ Static-leader + + <-------------> + C3 + +....+ (802.11b network) +....+ With the help of above diagram, different aspects of RRM RF Grouping can be explained. Grouping can be configured for 3 modes. 1) Automatic 2) Static 3) Off If the mode is 'Automatic', the controllers automatically form groups and elect leaders to perform better dynamic parameter optimization. If the mode is 'Static', user can select one controller as the group leader and configure the group members manually. If the mode is 'Off', no dynamic grouping occurs. Each controller optimizes only its own APs' parameters. In the above diagram, controller C1 forms a RF group with controller C2 in 802.11a network. And with controller C3, it forms a different group in 802.11b network. For the 802.11a network, the gorup mode is selected as 'Automatic'. So between C1 and C2 controllers, one would be selected as group leader and the other controller as member automatically by the algorithm. In the above case C1 is the group leader and C2 is the group member. Now for 802.11b network, group mode is selected as 'Static'. Also the user has manually configured C3 as the leader in this group and C1 was added to this group as member. 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

This notification is generated when the AP receives at least 'packet count' packets, represented by clrRrmParametersVoicePktCount for voice or clrRrmParametersDataPktCount for data, from a client in any given 5 second interval and 'packet percent' of the packets, represented by clrRrmParametersVoicePktCount for voice and clrRrmParametersDataPktCount for data, from the client are below the 'RSSI threshold' represented by clrRrmParametersVoiceRssiThreshold for voice and clrRrmParametersDataRssiThreshold for data.

This notification would be generated, from the controller that is elected as the new leader, when RF Grouping is done. It has MAC address and details of the new Group Leader.

This notification is generated from the group leader when a new member is added to the RF group. This notification has MAC address and details of new group member.

The notification is generated from the group leader, when a member is removed from the RF group. This notification has MAC address and details of removed group member.

This table represents the RRM parameters for a 802.11 interface type. Entries are automatically created on the controller for each 802.11 interface type.

An entry in this table corresponds to a particular 802.11 interface type.

This object uniquely represents the 802.11 interface type for this entry.

This object specifies the 802.11 pico-cell mode. disable - pico-cell mode is disabled. picoCellv1 - legacy pico-cell mode is in use. picoCellv2 - in this mode the APs to use the tuple information from the clrRrmTupleTable. Object is deprecated since controller doesn't support Pico cell configuration anymore. Enumeration: 'picoCellv2': 3, 'picoCellv1': 2, 'disable': 1.

This object represents the state of CHD (Coverage Hole Detection) on the controller. A value of 'true' indicates that the detection is enabled. A value of 'false' indicates that the detection is disabled.

This object represents the minimum threshold on the Voice packet count required to trigger the CHD algorithm on the controller.

This object represents the threshold on the percent of Voice packets dropped, that is required to trigger the CHD algorithm on the controller.

This object represents the RSSI threshold value for Voice packets, that is required to trigger the CHD algorithm on the controller.

This object represents the minimum threshold on the Data packet count required to trigger the CHD algorithm on the controller.

This object represents the threshold on the percent of Data packets dropped, that is required to trigger the CHD algorithm on the controller.

This object represents the RSSI threshold value for Data packets, that is required to trigger the CHD algorithm on the controller.

This object specifies how the system performs DCA channel width selection min - Min channel width(20Mhz) the radio supports medium - Medium channel width(40Mhz) supported by this radio. max - Max channel width(80Mhz) supported by this radio. Enumeration: 'max': 3, 'medium': 2, 'min': 1.

This defines the upper limit of transmit power in dBm. For a 802.11a network, the system will only accept this configuration if the bsnGlobalDot11aDynamicTransmitPowerControl is set to 'automatic' or 'runOnce'. For a 802.11b network, the system will only accept this configuration if the bsnGlobalDot11bDynamicTransmitPowerControl is set to 'automatic' or 'runOnce'. The value of this attribute has to be greater than equal to value of clrRrmParametersMinTxPower.

This defines the lower limit of transmit power in dBm. For an 802.11a network, the system will only accept this configuration if the bsnGlobalDot11aDynamicTransmitPowerControl is set to 'automatic' or 'runOnce'. For an 802.11b network, the system will only accept this configuration if the bsnGlobalDot11bDynamicTransmitPowerControl is set to 'automatic' or 'runOnce'. The value of this attribute has to be less than equal to value of clrRrmParametersMaxTxPower.

This object represents the TPC(Transmission Power Control) version. If version 1 is selected, TPC would be in coverage optimal mode. If version 2 is selected, TPC would be in interference optimal mode. Enumeration: 'versionTwo': 2, 'versionOne': 1.

This object represents the maximum allowed clients per radio.

This object represents the state of RSSI low check on the controller. A value of 'true' indicates that the check is enabled. A value of 'false' indicates that the check is disabled.

This object represents the RSSI threshold value for RSSI low check.

This object represents the state of Optimized Roaming feature on the controller. A value of 'true' indicates that the feature is enabled. A value of 'false' indicates that the feature is disabled

This object represents the data rate threshold value for Optimized Roaming. A valid data rate in mbps must be entered.

This object represents the reporting interval value for Optimized Roaming.

A list of tuple tuning parameters that are advertised to all APs registered under this 802.11 interface type. This information is pushed down to to 802.11 clients by the APs to operate under high density. Entries in this table are automatically created by the controller with default values. Object is deprecated since controller doesn't support Pico cell configuration anymore.

Each entry represents the tuning parameters for an interface type. These entries are applicable only when object clrRrmParametersPicoCellMode is is set to 'picoCellv2'. Pico cell is no more supported so deprecating this attribute. It will be obsolete post 7.0 release. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object represents the minimum value configured for receiver's sensitivity threshold. This value must be less than the value configured for clrRrmTupleRxSenseThresholdMax object. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object represents the maximum value configured for receiver's sensitivity threshold. This value must be greater than the value configured for clrRrmTupleRxSenseThresholdMin object. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object represents the current value for receiver's sensitivity threshold. This value is sent to the APs that join the controller. The APs in turn propogate this value to the 802.11 clients. The client will either use this value or will tune receiver's sensitivity settings between the range of values configured by clrRrmTupleRxSenseThresholdMin and clrRrmTupleRxSenseThresholdMax objects. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object represents the minimum value configured for clear channel (CCA) sensitivity threshold. This value must be less than the value configured for clrRrmTupleCcaSenseThresholdMax object. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object represents the maximum value configured for clear channel (CCA) sensitivity threshold. This value must be greater than the value configured for clrRrmTupleCcaSenseThresholdMin object. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object represents the current value for clear channel (CCA) sensitivity. This value is sent to the APs that join the controller. The APs in turn propogate this value to the 802.11 clients. The client will either use this value or may tune CCA sensitivity settings between the range of values configured by clrRrmTupleCcaSenseThresholdMin and clrRrmTupleCcaSenseThresholdMax objects. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object represents the minimum value configured for transmit power level. This value must be less than the value configured for clrRrmTupleTransmitPowerLevelMax object. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object represents the maximum value configured for transmit power level. This value must be greater than the value for clrRrmTupleTransmitPowerLevelMin object. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object represents the current value for transmit power level. This value is sent to the APs that join the controller. The APs in turn propogate this value to the 802.11 clients. The client will either use this value or may tune the transmit power settings between the range of values configured by clrRrmTupleTransmitPowerLevelMin and clrRrmTupleTransmitPowerLevelMax objects. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This object restores the other objects in this table to default value. Setting this value to 'true' wil restore defaults as indicated by the DEFVAL clause. This object can only be set to 'true' and all other values are rejected. This object will always return 'false' for get operations. Object is deprecated since controller doesn't support Pico cell configuration anymore.

This table represents the channel information for an AP's 802.11 interface. Based on the country that an AP operates in, it gets assigned to a regulatory domain. For a given regulatory domain a fixed number of channels are assigned automatically to an AP for a given interface. This table represents this information. Entries are automatically created on the controller as APs associate. Entries are removed when the APs disassociate.

Each entry in this table provides the channel information for an 802.11 interface in an AP.

The channel nubmer for this entry. This value represents the unique channel number on this 802.11 interface for this regulatory domain.

This object indicates whether this channel is part of the dynamic channel allocation (DCA) list. A value of 'true' indicates that the DCA for this channel is enabled. A value of 'false' indicates that the DCA for this channel is disabled.

This table contains the information about the RRM grouping corresponding to the dot11 band of the APs that have joined the controller. This table has a one-to-one dependent relationship on the clrRrmParametersTable.

An entry in this table represents the RRM RF grouping on a dot11 band of an AP that has joined the controller. For each dot11 band an entry will be created.

This object indicates the group leader's address type for the dot11 group containing this controller. The only one address type supported is ipv4(1).

This object indicates the configured group leader's address for the dot11 group containing this controller.

This object denotes the name of the current group leader.

This object indicates the mode for the RRM algorithm for the band. 'automatic' - the controller form groups and elect leaders to perform better dynamic parameter optimization. 'leader' - the user can manually configure the group. 'off' - no dynamic grouping occurs. Each controller optimizes only its own APs' parameters. Enumeration: 'off': 2, 'automatic': 1, 'leader': 3.

This object indicates the group role with respect to RRM RF grouping. The controller can be either group member or group leader while being in automatic or static grouping, for a particular band. If grouping is off , the value of the group role would be 'none'. 'none' - RRM RF Grouping is off 'auto-leader' - leader of automatic RRM RF Group 'auto-member' - member in automatic RRM RF Group 'static-leader' - leader of static RRM RF Group 'static-member' - member in static RRM RF Group. Enumeration: 'static-member': 5, 'none': 1, 'auto-member': 3, 'auto-leader': 2, 'static-leader': 4.

This object denotes if the grouping algorithm needs a restart. If a value of 'true' is set, the RRM grouping algorithm is restarted for the dot11 band. This will always return 'false' when retrieved

This object indicates the last time the dot11 grouping was updated on this controller. This is valid only if the controller is not a static member in the group. If it is a static member (i.e the value of the variable ,'clrRrmDot11BandGrpMode' is 'static-member(4)'), a value of '0' would be returned always.

This object indicates the period used by the grouping algorithm. The grouping algorithm runs when the group contents changes and automatic grouping is enabled. The system administrator can start grouping on demand.

This table contains the information about the RRM grouping members corresponding to the dot11 band of the APs that have joined the controller. The entries are members of the group represented by clrRrmDot11BandGrpTable.

An entry describes the grouping members on a dot11 band of an AP that has joined the controller. An entry will be created/deleted when members are added/deleted to/from the gorup.

This object indicates the address type of the dot11 group member for the dot11 grouping containing this controller.

This object specifies the address of the dot11 group member for the dot11 grouping containing this controller.

This object represents the name of the dot11 group member for the dot11 grouping containing this controller.

This object indicates whether the member has joined this RRM RF Group yet.If not the value would be 'false'. Else it would be true.This field is significant only if the current group is a static RRM RF Group. In all other cases a value of 'true' would be shown. true - member has joined the group successfully false - member has not joined the group yet.

This object indicates the reason the member could not join the RRM RF Group. This field is relevant only if the corresponding instance for 'clrRrmDot11BandMemberIsJoined' is 'false'. joinedSuccessfully - member has joined the group successfully invalidIp - invalid ip groupSizeExceeded - group size is exceeded invalidGroupOrder - group order is invalid nonMatchingGroupID - group id doesn't match unexpectedError - unexpected error has occurred weakSignalStrength - signal strength is weak joinPending - group join is pending notAManager - not a manager groupingDelayed - grouping is delayed groupingDisabled - grouping is disabled invalidProtocolVersion - protocol version is invalid countryCodeMismatch - country code doesn't match invalidHierarchy - invalid grouping hierarchy alreadyAStaticLeader - already a static leader memberOfAnotherGroup - member of another group unconfiguredAsStaticMember - unconfigured static member cntlrNameAndIpMismatch - controller name and ip doesn't match unexpectedMemoryError - an unexpected memory error has happened rfDomainMismatch - RF domain doesn't match. splitForInvalidStateRequest - split for invalid state request transitioningToStaticFromAuto - transitioning to static from auto splitDueToUserAction - split due to user action. Enumeration: 'rfDomainMismatch': 20, 'joinedSuccessfully': 1, 'transitioningToStaticFromAuto': 22, 'countryCodeMismatch': 13, 'notAManager': 9, 'splitDueToUserAction': 23, 'invalidGroupOrder': 4, 'groupingDisabled': 11, 'invalidHierarchy': 14, 'invalidIp': 2, 'cntlrNameAndIpMismatch': 18, 'joinPending': 8, 'groupingDelayed': 10, 'splitForInvalidStateRequest': 21, 'unexpectedMemoryError': 19, 'groupSizeExceeded': 3, 'nonMatchingGroupID': 5, 'invalidProtocolVersion': 12, 'alreadyAStaticLeader': 15, 'unconfiguredAsStaticMember': 17, 'memberOfAnotherGroup': 16, 'unexpectedError': 6, 'weakSignalStrength': 7.

This object specifies the status of the row.

This object specifies whether check for non-DFS channel should be done on DCA channel list or not. Generally at least one non-DFS channel should be present in DCA channel list. But there are locations like EU(European Union) where there is no non-DFS channel available for outdoor deployment. Customers deploying outdoor APs in EU or regions with similar regulations should set this variable to 'true'. When set to 'true' Controller will not perform check for non-DFS channels in DCA list.

This object indicates the priority assigned to controller with respect to RRM RF Grouping. When groups are formed, the priorities of the member controllers would be checked. Priority of the member controller should be less than or equal to priority of the leader controller.

This object represents the state of Packet RSSI location feature. A value of 'true' indicates that PRL is enabled. A value of 'false' indicates that PRL is disabled.

This object represents the threshold value for Packet RSSI location feature. Valid range is -100 dbm to -50 dbm.

This object represents the trigger threshold value for Packet RSSI location feature. Valid range is 1 dbm to 100 dbm.

This object represents the NTP server IP address type for Packet RSSI location feature.

This object represents the NTP server IP for Packet RSSI location feature.

This indicates represents the transmit power level for the AP.

This object indicates the time when coverage pre alarm was first reported to controller by an access point. After receiving this alert, controller will try to mitigate the coverage hole by increasing the transmit power of that access point. After doing above step for stipulated time, if coverage hole cannot be corrected by controller, a final notification would be generated from controller , informing the administrator about the existence of a coverage hole.

This object indicates the client type for which this notification was sent. data(1) - coverage hole has been detected for a data client(client which is meant for data services). voice(2) - coverage hole has been detected for a voice client(client which is meant for voice services). Enumeration: 'voice': 2, 'data': 1.

This object represents the number of values on the histogram. At present it is 31 entries.

This object represents the maximum value on the histogram.

This object represents the minimum value on the histogram.

This object returns a comma seperated string of histogram values. The number of values sent out is represented by the clrRrmRssiHistogramLength.

This object represents the number of 'clrRrmNeighborApMac, clrRrmNeighborApRssi' appended to this notification. This count is 5 and includes the AP itself.

This object represents the neighbor MAC address for this client. This is a comma sperated values for clrRrmNeighborApCount values.

This object represents the neighbor RSSI values for this client. This is a comma sperated values for clrRrmNeighborApCount values.

This object represents the neighbor AP radio type for this client. This is a comma sperated values for clrRrmNeighborApCount values.

This object represents the MAC Address of the controller.

This object represents the IPv4 and IPv6 address of the controller.

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

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

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

This collection of objects represent the RRM configuration on the controller.

This collection of objects represents the RRM configuration for Voice and Data packets on the controller.

This collection of objects represent the RRM configuration on the controller.

This collection of objects represent the Transmission Power Control(TPC) configuration on the controller, when the same is enabled on the controller.

This collection of objects represent the RRM RF Grouping configuration on the controller, when the same is enabled on the controller.

This collection of objects represent the status of RRM RF Groping on the controller, when the same is enabled on the controller.