CISCO-LWAPP-MESH-STATS-MIB
AI MIB Summary
The CISCO-LWAPP-MESH-STATS-MIB provides statistical monitoring for Cisco Central Controllers managing LWAPP-based Wireless Mesh Networks, specifically tracking performance metrics for Root Access Points (RAPs), Mesh Access Points (MAPs), and associated Mobile Stations. This module enables the collection of backhaul link statistics, including Signal-to-Noise Ratio (SNR), mesh link states, and roaming events (intra- and inter-controller) to assess the health and throughput of the wireless mesh topology.
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
Main OID:
ciscoLwappMeshStatsMIB.1.3.6.1.4.1.9.9.617
83
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
83 total| Object Name |
|---|
ciscoLwappMeshStatsMIBThis 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 MODULE-IDENTITY .1.3.6.1.4.1.9.9.617 |
ciscoLwappMeshStatsMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.0 |
ciscoLwappMeshQueueOverflowThis 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.. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.617.0.1 |
ciscoLwappMeshExcessiveAssociationThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.617.0.2 |
ciscoLwappMeshSecBackhaulChangeThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.617.0.3 |
ciscoLwappMeshStatsMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.1 |
ciscoLwappMeshNodeStats OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.1.1 |
clMeshNodeStatsTableThis 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. SEQUENCE OF ClMeshNodeStatsEntry .1.3.6.1.4.1.9.9.617.1.1.1 |
clMeshNodeStatsEntryAn (conceptual) entry in this table represents statistics
for a mesh node. ClMeshNodeStatsEntry .1.3.6.1.4.1.9.9.617.1.1.1.1 |
clMeshNodeMalformedNeighPktsThis object represents total number of packets
received from neighbor mesh nodes which could
not be decoded.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.1.1.1 |
clMeshNodePoorNeighSnrPktsThis object represents total number of packets
received from neighbor mesh nodes which were below
SNR threshold value.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.1.1.2 |
clMeshNodeExcludedPktsThis object represents total number of packets
received from excluded neighbor mesh nodes.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.1.1.3 |
clMeshNodeRxNeighReqThis object represents total number of request
received from neighbor mesh node APs. Requests
can be either broadcast or unicast from neighbor
mesh nodes.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.1.1.4 |
clMeshNodeRxNeighRspThis object represents total number of response
received from neighbor mesh node APs.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.1.1.5 |
clMeshNodeTxNeighReqThis object represents total number of request
sent to neighbor mesh node APs. Requests can be
broadcast or unicast to neighbor mesh node.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.1.1.6 |
clMeshNodeTxNeighRspThis object represents total number of response
sent to neighbor mesh node APs.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.1.1.7 |
clMeshNodeParentChangesThis object represents total number of times
this mesh node has changed its parent.ro Counter32 UNITS "parent-switches" .1.3.6.1.4.1.9.9.617.1.1.1.1.8 |
clMeshNodeSecBackhaulCountThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.1.1.9 |
clMeshNodeAssociationCountThis object specifies the number of association attempts
of children nodes at a parent node and is also sent as a part
of the ciscoLwappMeshExcessiveAssociation notificationro Counter32 .1.3.6.1.4.1.9.9.617.1.1.1.1.10 |
clMeshNodePktQueueStatsTableThis 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. SEQUENCE OF ClMeshNodePktQueueStatsEntry .1.3.6.1.4.1.9.9.617.1.1.2 |
clMeshNodePktQueueStatsEntryEach entry in this table represents average queue size
and peak packets queue reached. ClMeshNodePktQueueStatsEntry .1.3.6.1.4.1.9.9.617.1.1.2.1 |
clMeshNodePktQueueIndexThis 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 .1.3.6.1.4.1.9.9.617.1.1.2.1.1 |
clMeshNodePktQueueAvgThis object represents average number of
packets waiting in the queue during interval
defined by object 'clMeshNodeStatsTimeInterval'.ro Gauge32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.2.1.2 |
clMeshNodePktQueuePeakThis object represents peak number of
packets waiting in the queue during interval
defined by object 'clMeshNodeStatsTimeInterval'.ro Gauge32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.2.1.3 |
clMeshNodePktQueuePktsDroppedThis object represents total number of packets
dropped due to queue overflow.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.2.1.4 |
clMeshNodePktQueueTimeStampThis object represents when the queue statistics
was last collected. This value is represented as a
instance of sysUp time.ro TimeStamp UNITS "seconds" .1.3.6.1.4.1.9.9.617.1.1.2.1.5 |
clMeshNodePktQueueSizeThis object represents max number of packets a
queue can hold.ro Unsigned32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.2.1.6 |
clMeshNodeSecStatsTableThis 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. SEQUENCE OF ClMeshNodeSecStatsEntry .1.3.6.1.4.1.9.9.617.1.1.3 |
clMeshNodeSecStatsEntryEach (conceptual) entry in this table represents count of
security packets a mesh node exchange with its parent mesh
node. ClMeshNodeSecStatsEntry .1.3.6.1.4.1.9.9.617.1.1.3.1 |
clMeshNodeSecTxPktsThis object indicates total number of packets
transmitted by this mesh node during security
negotiations.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.1 |
clMeshNodeSecRxPktsThis object indicates total number of packets
received by this mesh node during security
negotiations.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.2 |
clMeshNodeAssocReqFailuresThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.3 |
clMeshNodeAssocReqTimeoutsThis object indicates total number of
association request sent by this node, as a
child mesh node to a parent mesh node, that
timed out.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.4 |
clMeshNodeAssocReqSuccessThis object indicates total number of association
request sent by this node, as a child mesh
node to a parent mesh node, that completed.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.5 |
clMeshNodeAuthReqFailuresThis object indicates total number of
authenticaton request sent by this node, as a child
mesh node to a parent mesh node, that failed.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.6 |
clMeshNodeAuthReqTimeoutsThis object indicates total number of
authentication request sent by this node, as a child
mesh node to a parent mesh node, that timed out.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.7 |
clMeshNodeAuthReqSuccessThis object indicates total number of
authentication request sent by this node, as a child
mesh node to a parent mesh node, that completed.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.8 |
clMeshNodeReassocReqFailuresThis object indicates total number of
re-association request sent by this node, as a child
mesh node to a parent mesh node, that failed.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.9 |
clMeshNodeReassocReqTimeoutsThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.10 |
clMeshNodeReassocReqSuccessThis object indicates total number of
re-association request sent by this node, as a child
mesh node to a parent mesh node, that completed.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.11 |
clMeshNodeReauthReqFailuresThis object indicates total number of
re-authentication request sent by this node, as a child
mesh node to a parent mesh node, that failed.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.12 |
clMeshNodeReauthReqTimeoutsThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.13 |
clMeshNodeReauthReqSuccessThis object indicates total number of
re-authentication request sent by this node, as a child
mesh node to a parent mesh node, that completed.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.14 |
clMeshNodeUnknownAssocReqThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.15 |
clMeshNodeInvalidAssocReqThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.16 |
clMeshNodeUnknownReauthReqThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.17 |
clMeshNodeInvalidReauthReqThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.18 |
clMeshNodeUnknownReassocReqThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.19 |
clMeshNodeInvalidReassocReqThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.1.3.1.20 |
ciscoLwappMeshNeighStats OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.1.2 |
clMeshNeighStatsTableThis table represents information about packets
transmitted to neighbor mesh node in wireless mesh
network. SEQUENCE OF ClMeshNeighStatsEntry .1.3.6.1.4.1.9.9.617.1.2.1 |
clMeshNeighStatsEntryAn (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. ClMeshNeighStatsEntry .1.3.6.1.4.1.9.9.617.1.2.1.1 |
clMeshNeighAsParentTxPktsThis object provides number of packets
transmitted as a parent to a neighbor mesh node.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.2.1.1.1 |
clMeshNeighAsParentRxPktsThis object indicates total number of packets
received as a parent to a neighbor mesh node.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.2.1.1.2 |
clMeshNeighTotalTxPktsThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.2.1.1.3 |
clMeshNeighSuccessTxPktsThis object indicates total number of packets successfully
transmitted to a neighbor mesh node.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.2.1.1.4 |
clMeshNeighRetriesTxPktsThis object indicates total number of retries were
made at MAC layer to send the packet to a neighbor
mesh node.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.2.1.1.5 |
clMeshNeighPoorSnrRxPktsThis 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.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.2.1.1.6 |
ciscoLwappMeshStatsMIBNotifObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.1.3 |
clMeshInitiatingApNameThis object specifies the name of the AP that initiated the
backhaul Change.ro SnmpAdminString .1.3.6.1.4.1.9.9.617.1.3.1 |
ciscoLwappMeshAccessClass OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.1.4 |
clMeshAccessClassTableThis 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. SEQUENCE OF ClMeshAccessClassEntry .1.3.6.1.4.1.9.9.617.1.4.1 |
clMeshAccessClassEntryAn (conceptual) entry in this table represents mesh backhaul
access class statistics for a mesh node. ClMeshAccessClassEntry .1.3.6.1.4.1.9.9.617.1.4.1.1 |
clMeshAccessClassTotalTxPktsThis object represents total number of packets transmitted.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.4.1.1.1 |
clMeshAccessClassSuccTxPktsThis object represents total number of packets successfully
transmitted.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.4.1.1.2 |
clMeshAccessClassRetryPktsThis object represents total number of retried packets.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.4.1.1.3 |
clMeshAccessClassRTSAttemptsThis object represents total number of RTS attempts.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.4.1.1.4 |
clMeshAccessClassRTSSuccessThis object represents total number of successful RTS packets.ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.4.1.1.5 |
ciscoLwappMeshDataRateStats OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.1.5 |
clMeshDataRateStatsTableThis 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. SEQUENCE OF ClMeshDataRateStatsEntry .1.3.6.1.4.1.9.9.617.1.5.1 |
clMeshDataRateStatsEntryAn (conceptual) entry in this table represents mesh backhaul
data Rate statistics for a mesh node. ClMeshDataRateStatsEntry .1.3.6.1.4.1.9.9.617.1.5.1.1 |
cLMeshDataRateIndexThis object represents supported data rates of the access
point. Unsigned32 UNITS "Mbps" .1.3.6.1.4.1.9.9.617.1.5.1.1.1 |
clMeshDataRateSuccTxPktsThis object represents total number of successfully transmitted packets .ro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.617.1.5.1.1.2 |
clMeshDataRateTxAttemptsThis object represents total number of transmitted attempts.ro Counter32 .1.3.6.1.4.1.9.9.617.1.5.1.1.3 |
ciscoLwappMeshStatsMIBConfigObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.2 |
clMeshNodeQueueOverflowNotifEnabledThe 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.617.2.1 |
clMeshNodeStatsTimeIntervalThe object represents the time interval after
which statistics are populated for each mesh node.rw TimeInterval .1.3.6.1.4.1.9.9.617.2.2 |
clMeshNodeSecBackhaulChangeNotifEnabledThis 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.617.2.3 |
clMeshNodeExcessiveAssociationNotifEnabledThis 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.617.2.4 |
clMeshNodeExcessiveAssociationThresholdThis object represents cumulative association
at parent by different child mesh nodes. Notification
'ciscoLwappMeshExcessiveAssociation' is raised
when this number is crossed in one hour.rw Unsigned32 .1.3.6.1.4.1.9.9.617.2.5 |
ciscoLwappMeshStatsMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.3 |
ciscoLwappMeshStatsMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.3.1 |
ciscoLwappMeshStatsMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.617.3.2 |