Motorola Solutions WiNG 5.2.6 Reference Manual page 569

Access point
Table of Contents

Advertisement

Good Pkts
Describes the number of good packets received.
Received
Mcast Pkts Sent
Displays the number of multicast packets sent through the selected interface.
Mcast Pkts
Displays the number of multicast packets received through the selected
Received
interface.
Bcast Pkts Sent
Displays the number of broadcast packets sent through the interface.
Bcast Pkts
Displays the number of broadcast packets received through the interface.
Received
Packet
Displays the number of packet fragments transmitted or received through the
Fragments
interface.
Jabber Pkts
Displays the number of packets transmitted through the interface that are
larger than the MTU through the interface.
8. The
Errors
field displays the following information for the selected access point interface:
Bad Pkts
Displays the number of bad packets received through the interface.
Received
Collisions
Displays the number of collisions on the interface.
Late Collisions
A late collision is any collision that occurs after the first 64 octets of data
have been sent by the sending client. Late collisions are not normal, and are
usually the result of out-of-specification cabling or a malfunctioning device.
Excessive
Displays the number of excessive collisions. Excessive collisions occur when
Collisions
the traffic load increases to the point that a single Ethernet network cannot
handle it efficiently.
Drop Events
Displays the number of dropped packets transmitted or received through the
interface.
Tx Undersize
Displays the number of undersize packets transmitted through the interface.
Pkts
Oversize Pkts
Displays the number of oversize packets.
MAC Transmit
Displays the number of transmits that failed because of an internal MAC
Error
sublayer error that is not a late collision, excessive collision count, or a carrier
sense error.
MAC Receive
Displays the number of received packets failed because of an internal MAC
Error
sublayer that is not a late collision, excessive collision count, or a carrier
sense error.
Bad CRC
Displays the CRC error. The Cyclical Redundancy Check (CRC) is the 4 byte
field at the end of every frame. The receiving station uses it to interpret if the
frame is valid. If the CRC value computed by the interface does not match the
value at the end of the frame, it's considered a bad CRC.
Statistics 12 - 67

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents