CISCO-LWAPP-MESH-STATS-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 (LWAPP) tunnel from Light-weight Access Points. This MIB represents statistics collected for mesh node in Wireless Mesh Network. The deployment of the controller (referred to as CC in the diagram), mesh nodes (RAP and MAP) LWAPP APs, client(MS) and NMS appear as follows. +.......+ +.......+ + + + + + NMS + + NMS + + + + + +.......+ +.......+ . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + RAP + + RAP + + RAP + + RAP + + RAP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MAP + + MS + + MAP + + MAP + + MAP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . .. . . . . .. . . . . .. . . . . . . +......+ +......+ +......+ +......+. +......+ + + + + + + + + + + + MAP + + MAP + + MAP + + MAP + + MS + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ 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 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'. Mobile Station ( MS ) A roaming 802.11 wireless device in a wireless network associated with an access point. Mobile Station and client are used interchangeably. Network Management System ( NMS ) The station from which the administrator manages the wired and wireless networks. Mesh Node A mesh node is defined as a physical or logical entity in the mesh network participating in forming the mesh backhaul. RAP and MAP are two types of mesh nodes supported in mesh network. Root AP (RAP) The AP forming the bridge between a wired and a mesh network with an Ethernet interface to the wired network and a 802.11 radio interface to the mesh network Mesh AP (MAP). The AP extending wireless coverage similar to a repeater in a mesh network and consists of a 802.11 uplink and a 802.11 downlink. On a single-radio backhaul, both uplink and downlink exist on the same radio and are logical links only. On a multi-radio backhaul, they may exist on different radios. Mesh Network Network starting with the wireless backhaul downlink of the RAP and all the entities below except any attached network to the Ethernet link of MAPs. A mesh network below a single RAP is also referred to as a 'Mesh Sector'.A mesh network consists of mesh nodes. A single mesh network is always augmented to a single wired network. Mesh Link A logical 802.11 link between two mesh nodes. A single link is point-to-point. All point-to-multipoint links are considered as multiple mesh links. Often referred to as mesh backhaul link. Mesh Backhaul A Mesh backhaul consists of mesh nodes and mesh links terminating at a RAP. This necessarily creates a one- to-one relationship between a 'mesh network', 'mesh sector' and a 'mesh backhaul' where these terms can be used interchangeably. SNR Signal to Noise ratio on the 802.11 radio. Bridged network The bridged network is defined as the network(s) attached to the Ethernet port of any MAP. There can be multiple such networks attached to a single mesh network. Mesh Node Roaming A mesh node may change its parent mesh node naturally when the RF/network condition changes. Child Mesh node will re-associate and re-authenticate to new parent mesh node. Mesh Security supports two types of mesh node roaming. Intra-controller - LWAPP session is not lost. Inter-controller - LWAPP session is lost. 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 sent by the agent when a queue overflows and as a result packets get dropped. After each time interval, defined by object 'clMeshNodeStatsTimeInterval', mesh node sends its queue statistics to the controller which also includes cumulative number of packets dropped, defined by object 'clMeshNodePktQueuePktsDropped'. If the packets dropped is higher than the previous time notification generated then this notification is raised..

This notification is sent by the agent when cumulative association counter at parent mesh node exceeds value configured in 'clMeshNodeExcessiveAssociationThreshold'. cLApName is the name of the parent mesh node.

This notification is sent by the agent when the MAP identified by clApName intiates the backhaul change from primary to secondary. cLApName identifies the AP that receives the change. The MAC address of the initiating AP is sent as a part of the index of clMeshNodeBackhaul. clMeshNodeBackhaul identifies the secondary backhaul channel used. The MAC address of the receiving AP is sent as a part of the index of cLApName.

This table represents statistics information about a mesh node such as the number of that were transmitted to or received from the mesh node, number association attempts, packets transmitted on secondary backhaul etc. An entry in this table gets added when a mesh node associates to the controller and entry gets removed when mesh node disassociates from the controller.

An (conceptual) entry in this table represents statistics for a mesh node.

This object represents total number of packets received from neighbor mesh nodes which could not be decoded.

This object represents total number of packets received from neighbor mesh nodes which were below SNR threshold value.

This object represents total number of packets received from excluded neighbor mesh nodes.

This object represents total number of request received from neighbor mesh node APs. Requests can be either broadcast or unicast from neighbor mesh nodes.

This object represents total number of response received from neighbor mesh node APs.

This object represents total number of request sent to neighbor mesh node APs. Requests can be broadcast or unicast to neighbor mesh node.

This object represents total number of response sent to neighbor mesh node APs.

This object represents total number of times this mesh node has changed its parent.

This object specifies the number of packets sent on the secondary backhaul after the change, and is also sent as a part of the 'ciscoLwappMeshSecBackhaulChange' notification.

This object specifies the number of association attempts of children nodes at a parent node and is also sent as a part of the ciscoLwappMeshExcessiveAssociation notification

This table represents information about different packet queues of a mesh node. Queues are maintained in a mesh node based on quality of service and packets wait for its turn in queue before it is sent to network. An (conceptual) entry in this table is created when a mesh node associates with controller and start sending packets to neighbor mesh node or controller Entries are removed when the mesh node disassociates from controller.

Each entry in this table represents average queue size and peak packets queue reached.

This object represents different types of queues in a mesh node. silver - queue for Best Effort packets. gold - queue for Video Application. platinum - queue for Voice Application. bronze - queue for Background. management - queue for management frames. Enumeration: 'platinum': 3, 'management': 5, 'bronze': 4, 'silver': 1, 'gold': 2.

This object represents average number of packets waiting in the queue during interval defined by object 'clMeshNodeStatsTimeInterval'.

This object represents peak number of packets waiting in the queue during interval defined by object 'clMeshNodeStatsTimeInterval'.

This object represents total number of packets dropped due to queue overflow.

This object represents when the queue statistics was last collected. This value is represented as a instance of sysUp time.

This object represents max number of packets a queue can hold.

This table represents information about packets transmitted to or received from a mesh node during association or authentication of a child mesh node to parent mesh node. An (conceptual) entry in this table is created when a mesh node associates or authenticates with a parent mesh node. Entries are removed when the mesh node disassociates from controller.

Each (conceptual) entry in this table represents count of security packets a mesh node exchange with its parent mesh node.

This object indicates total number of packets transmitted by this mesh node during security negotiations.

This object indicates total number of packets received by this mesh node during security negotiations.

This object indicates total number of association request sent by this node as a child mesh node to a parent mesh node, that resulted in a failure.

This object indicates total number of association request sent by this node, as a child mesh node to a parent mesh node, that timed out.

This object indicates total number of association request sent by this node, as a child mesh node to a parent mesh node, that completed.

This object indicates total number of authenticaton request sent by this node, as a child mesh node to a parent mesh node, that failed.

This object indicates total number of authentication request sent by this node, as a child mesh node to a parent mesh node, that timed out.

This object indicates total number of authentication request sent by this node, as a child mesh node to a parent mesh node, that completed.

This object indicates total number of re-association request sent by this node, as a child mesh node to a parent mesh node, that failed.

This object indicates total number of re-association request sent by this node, as a child mesh node to a parent mesh node, that timed out.

This object indicates total number of re-association request sent by this node, as a child mesh node to a parent mesh node, that completed.

This object indicates total number of re-authentication request sent by this node, as a child mesh node to a parent mesh node, that failed.

This object indicates total number of re-authentication request sent by this node, as a child mesh node to a parent mesh node, that timed out.

This object indicates total number of re-authentication request sent by this node, as a child mesh node to a parent mesh node, that completed.

This object indicates total number of unknown association request received by this node, as a parent mesh node from a child mesh node. This may happen when child is a unknown neighbor.

This object indicates total number of invalid association request that were received by this node, as a parent mesh node from a child mesh node. This may happen when child is a valid neighbor but is in a wrong state to be associated.

This object indicates total number of unknown re-authentication request received by this node, as a parent mesh node from a child mesh node. This may happen when child is a unknown neighbor.

This object indicates total number of invalid re-authentication request received by this node, as a parent mesh node from a child mesh node. This may happen when child is a valid neighbor but is in a wrong state to be re-authenticated.

This object indicates total number of unknown re-association request received by this node, as a parent mesh node from a child mesh node. This may happen when child is a unknown neighbor.

This object indicates total number of invalid re-association request received by this node, as a parent mesh node from a child mesh node. This may happen when child is a valid neighbor but is in a wrong state to be re-associated.

This table represents information about packets transmitted to neighbor mesh node in wireless mesh network.

An (conceptual) entry in this table is created when a mesh node transmit packets to another neighbor mesh node. Neighbor mesh node can be parent, child or neighbor. Entries are removed when the mesh node does not see another mesh node as neighbor.

This object provides number of packets transmitted as a parent to a neighbor mesh node.

This object indicates total number of packets received as a parent to a neighbor mesh node.

This object indicates total number of packets transmitted to a neighbor mesh node. Total Tx packets is the sum of success Tx and retry Tx packets.

This object indicates total number of packets successfully transmitted to a neighbor mesh node.

This object indicates total number of retries were made at MAC layer to send the packet to a neighbor mesh node.

This object indicates total number of packets received from a neighbor mesh node whose SNR value were lower than threshold value. The threshold value is fixed at 8.

This object specifies the name of the AP that initiated the backhaul Change.

This table represents mesh backhaul access class statistics for a mesh node. An entry in this table gets added when a mesh node associates to the controller and entry gets removed when mesh node disassociates from the controller.

An (conceptual) entry in this table represents mesh backhaul access class statistics for a mesh node.

This object represents total number of packets transmitted.

This object represents total number of packets successfully transmitted.

This object represents total number of retried packets.

This object represents total number of RTS attempts.

This object represents total number of successful RTS packets.

This table represents statistics information of a mesh node for each of the supported data rates. An entry in this table gets added when a mesh node associates to the controller and entry gets removed when mesh node disassociates from the controller.

An (conceptual) entry in this table represents mesh backhaul data Rate statistics for a mesh node.

This object represents supported data rates of the access point.

This object represents total number of successfully transmitted packets .

This object represents total number of transmitted attempts.

The object to control the generation of 'ciscoLwappMeshQueueOverflow' notification. A value of 'true' indicates that the agent generates 'ciscoLwappMeshQueueOverflow' notification. A value of 'false' indicates that the agent doesn't generate ciscoLwappMeshQueueOverflow notification.

The object represents the time interval after which statistics are populated for each mesh node.

This object controls the generation of 'ciscoLwappMeshSecBackhaulChange' notification. A value of 'true' indicates this notification will be generated. A value of 'false' indicates this notification will not be generated.

This object controls the generation of 'ciscoLwappMeshExcessiveAssociation' notification. A value of 'true' indicates notification will be generated. A value of 'false' indicates notification will not be generated.

This object represents cumulative association at parent by different child mesh nodes. Notification 'ciscoLwappMeshExcessiveAssociation' is raised when this number is crossed in one hour.

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

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

This collection of objects represents statistics information about a mesh node such as the number of that were transmitted to or received from the mesh node, number association attempts, packets transmitted on secondary backhaul etc.

This collection of objects represent packets is different types of queues to be transmitted to neighbor meshnode or to controller.

This collection of objects represent packets that were transmitted or received by a child mesh node or a parent mesh node during security negotiations.

This collection of objects represent configuration objects for statistics of mesh network.

This collection of objects represent the mesh network statistics related notifications sent by the agent to a network management station.

This collection of objects represent packets transmitted or received by a mesh node to or from a neighbor mesh node.

This collection of objects represent the information carried by the mesh network statistics related notifications sent by the agent to a network management station.

Thia collection of objects represents statistics information about a meshnode such as the number of that were successful transmitted, number of dropped packets, retried packets.

Thia collection of objects represents statistics information about a mesh node the number of that were successful transmitted packets, of each data rate.

This collection of objects represent statistics information of a mesh node such as the number of packets that were transmitted to or received from the mesh node, number association attempts, packets transmitted on secondary backhaul.

This collection of objects represent configuration objects for statistics of mesh network.

This collection of objects represent the mesh network statistics related notifications sent by the agent to a network management station.