Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) User Manual
Page 154

140
Multi-Service IronWare QoS and Traffic Management Configuration Guide
53-1003037-02
Traffic manager statistics display
4
TABLE 34
Traffic manager statistics
This field...
Displays...
Ingress Statistics
Total Ingress Pkt Count
A count of all packets entering into this traffic manager. A traffic manager contains a
specific number of ports depending on the Interface module as described in
.
EnQue Pkt Count
A count of all packets entering Ingress queues on this traffic manager. A traffic manager
contains a specific number of ports depending on the Interface module as described in
.
EnQue Byte Count
A count of all bytes entering Ingress queues on this traffic manager. A traffic manager
contains a specific number of ports depending on the Interface module as described in
.
DeQue Pkt Count
A count of all packets dequeued from Ingress queues and forwarded on this traffic
manager. A traffic manager contains a specific number of ports depending on the
Interface module as described in
DeQue Byte Count
A count of all bytes dequeued from Ingress queues and forwarded on this traffic
manager.
TotalQue Discard Pkt
Count
A count of all packets failing to enter Ingress queues on this traffic manager. This may
be due to:
•
the queue reaching its maximum depth, WRED, or other reasons.
•
the network processor deciding to drop packets for reasons including: an unknown
Layer-3 route, RPF, or segment filtering.
A traffic manager contains a specific number of ports depending on the Interface
module as described in
TotalQue Discard Byte
Count
A count of all bytes failing to enter Ingress queues on this traffic manager. This may be
due to:
•
the queue reaching its maximum depth, WRED, or other reasons.
•
the network processor deciding to drop packets for reasons including: an unknown
Layer-3 route, RPF, or segment filtering.
A traffic manager contains a specific number of ports depending on the Interface
module as described in
Oldest Discard Pkt
Count
A count of all packets entering Ingress queues on this traffic manager, but deleted
afterwards due to buffer full. A traffic manager contains a specific number of ports
depending on the Interface module as described in
.
Oldest Discard Byte
Count
A count of all bytes entering Ingress queues on this traffic manager, but deleted
afterwards due to buffer full. A traffic manager contains a specific number of ports
depending on the Interface module as described in
.
Egress statistics
EnQue Pkt Count
A count of all packets entering egress queues and forwarded out on this traffic manager.
A traffic manager contains a specific number of ports depending on the Interface
module as described in
EnQue Byte Count
A count of all bytes entering egress queues and forwarded out on this traffic manager. A
traffic manager contains a specific number of ports depending on the Interface module
as described in
.
Discard Pkt Count
A count of all packets failing to enter egress queues on this traffic manager. A traffic
manager contains a specific number of ports depending on the Interface module as
described in
Discard Byte Count
A count of all bytes failing to enter egress queues on this traffic manager. A traffic
manager contains a specific number of ports depending on the Interface module as
described in