Hierarchical Class of Service in ACX Series Routers
Scheduling properties can be applied at physical as well as logical interface and logical interface set levels. Service providers can support hierarchical class of service (HCoS) at multiple levels to meet the service level agreements and bandwidth allocations for subscribers.
Hierarchical Scheduling on the Physical Interface
By default, the queuing mode on all the physical interfaces in ACX routers that support HCoS is 4 queues per physical interface (port). In the hierarchical scheduler mode, you can configure up to 3 levels (physical interface, logical interface, and queues) or 4 levels (including logical interfaces sets) of scheduling, depending on the platform.
You can enable hierarchical scheduling by including the
hierarchical-scheduler CLI command under the [edit interfaces
interface-name] hierarchy:
[edit]
interfaces xe-0/0/1 {
hierarchical-scheduler;
}
If you change the physical interface queuing mode from default to hierarchical scheduler mode or vice-versa, the traffic flowing out of the physical interface during the mode change results in a transient loss of traffic data.
Traffic Control Profiles
Traffic control profiles hold parameters for levels above the queue level of the scheduler hierarchy. You configure the scheduling and shaping on the scheduler nodes using traffic control profiles and scheduler maps for the queue level. The traffic control profile defines the following characteristics of a scheduler node:
-
Scheduler-map
-
Shaping rate
-
Guaranteed rate
You attach traffic control profiles at the physical interface, logical interface set, and
logical interface level. You define scheduling and shaping characteristics for the scheduler
node using shaping-rate and guaranteed-rate. The following
is a sample traffic control profile configuration:
[edit class-of-service traffic-control-profiles]
tcp-500m-shaping-rate {
shaping-rate 500m;
}
tcp-vlan0 {
shaping-rate 200m;
guaranteed-rate 100m;
scheduler-map tcp-map-vlan0; # Applies scheduler maps to customer VLANs.
}
tcp-vlan1 {
shaping-rate 100m;
guaranteed-rate 40m;
scheduler-map tcp-map-vlan1; # Applies scheduler maps to customer VLANs.
}
Schedulers
A scheduler defines scheduling and queuing characteristics of a queue and holds the information about the queues, the last level of the hierarchy. The following is a sample scheduler configuration:
[edit class-of-service schedulers]
sched-vlan0-q0 {
priority low;
transmit-rate 20m;
buffer-size temporal 100ms;
drop-profile loss-priority low dp-low;
drop-profile loss-priority high dp-high;
}
sched-vlanl-q1 {
priority strict-high;
shaping-rate 20m;
}
We do not support transmit-rate with priority queues on ACX Series
routers.
Deep Buffer Control
With deep buffer control, also known as fine-grained buffer control, you can configure buffers on a per-queue basis.
On ACX routers running Junos OS Evolved, by default all queues on HQoS enabled logical interfaces have a dedicated buffer of 4KB and a shared buffer of 10msec. Table 1 and Table 2 show the guaranteed and shared per queue default buffers on ACX routers running Junos OS Evolved.
|
Interface Speed (GB) |
Minimum Guaranteed Buffer (KB) |
|---|---|
|
1/10 |
125 |
|
25/40/50 |
625 |
|
100 |
1250 |
|
200 |
2500 |
|
400 |
5000 |
|
Interface Speed (GB) |
Shared buffer size (MB) |
Shared buffer size (ms) |
|---|---|---|
|
1 |
5 |
40 |
|
10 |
50 |
40 |
|
25 |
250 |
80 |
|
40 |
250 |
50 |
|
50 |
250 |
40 |
|
100 |
500 |
40 |
|
200 |
500 |
20 |
|
400 |
500 |
10 |
You can configure the shared and guaranteed buffers for each queue on HCoS-enabled ports and logical interfaces. See buffer-size (Schedulers).
Use the temporal option to configure shared buffers.
Drop Profiles
Drop profiles allow you to specify queue specific behavior to drop packets based on WRED profile under congestion. The following is a sample drop profile configuration:
[edit class-of-service drop-profiles]
dp-low {
fill-level 80 drop-probability 0;
fill-level 100 drop-probability 100;
}
dp-high {
fill-level 60 drop-probability 0;
fill-level 80 drop-probability 100;
}
Scheduler Maps
A scheduler map is referenced by traffic control profiles to define queues. The scheduler map establishes the number of queues over a scheduler node, associating a forwarding-class with a scheduler. The following is a sample scheduler map configuration:
[edit class-of-service scheduler-maps]
tcp-map-vlan0 {
forwarding-class voice scheduler sched-vlan0-q0;
forwarding-class video scheduler sched-vlan0-q1;
forwarding-class data scheduler sched-vlan0-q2;
}
tcp-map-vlan1 {
forwarding-class voice scheduler sched-vlan1-q0;
forwarding-class video scheduler sched-vlan1-q1;
forwarding-class data scheduler sched-vlan1-q2;
}Applying the Traffic Control Profiles
You can attach output-traffic-control-profile and
output-traffic-control-profile-remaining at various levels of the
scheduler hierarchy to achieve hierarchical class of service. On an interface set,
output-traffic-control-profile-remaining is active if there is at least
one member logical interface with an attached
output-traffic-control-profile and at least one without.
Although a shaping rate can be applied directly to the physical interface, hierarchical schedulers must use a traffic control profile to hold this parameter.
All logical interfaces that are part of an interface set inherit the traffic control profile of the interface set.
The following is a sample configuration to apply traffic control profiles:
[edit class-of-service interfaces]
ge-1/0/0 {
output-traffic-control-profile tcp-500m-shaping-rate;
output-traffic-control-profile-remaining tcp-500m-shaping-rate;
unit 0 {
output-traffic-control-profile tcp-cvlan0;
}
unit 1 {
output-traffic-control-profile tcp-cvlan1;
}
}
interface-set svlan0 {
output-traffic-control-profile tcp-svlan0;
}
interface-set svlan1 {
output-traffic-control-profile tcp-svlan1;
}HCoS on Aggregated Ethernet Interfaces
Configuring HCoS on aggregated Ethernet (AE) interfaces is exactly the same as configuring HCoS on physical interfaces. Apply all HCoS configuration to the AE interface.
You cannot apply HCoS configuration to a physical interface that is a member of an AE interface. To apply HCoS to an AE interface, do not configure HCoS on a physical interface and then add the physical interface to the AE interface. First configure the AE interface, then configure HCoS on the AE interface.
HCoS configuration on an AE interface is automatically applied to each member interface. How the system applies the configuration to each member interfaces (that is, whether the configuration is normalized or not) depends on the AE interface configuration mode:
-
Link protection mode — system applies configuration directly to each member interface without normalization.
-
Non-link protection replica mode — system applies configuration directly to each member interface without normalization.
-
Non-link protection scale mode (default mode) — system does normalize the configuraiton before applying to each member interface.
HCoS configuration has the following requirements when the configuration must be normalized across member interfaces:
-
transmit-rateat scheduler/queue level — both percent and absolute configuration allowed -
shaping-rateat scheduler/queue level — both percent and absolute configuration allowed -
guaranteed-rateat traffic control profile level — only absolute configuration allowed -
shaping-rateat traffic control profile level — only absolute configuration allowed -
shaping-rateat port level — only absolute configuration allowed
If the configuration must be normalized, rates configured as a percent require no normalization. If the configuration must be normalized, rates configured as absolute must be normalized. You can calculated the normalized value for each interface by deviding the absolute configured value by the number of member interfaces in the AE interface.
Subscriber Services
Supported ACX routers support hierarchical class of service functionality for subscriber services such as Layer 3 VPN, Layer 2 VPN, Ethernet pseudowire (VPWS), and VPLS for logical interface instance on the AC (Access Port).
Hierarchical class of service is not supported for Layer 2 bridging (bridge domain VLAN) service.
The following sections explain the hierarchical class of service configuration for subscriber services:
- Configuring hierarchical class of service for Layer 3 VPN Service
- Configuring hierarchical class of service for Layer 2 VPN (Ethernet Pseudowires) Service
- Configuring hierarchical class of service for VPLS Service
- Verifying the hierarchical class of service configurations
Configuring hierarchical class of service for Layer 3 VPN Service
Supported ACX routers can be configured to provide Layer 3 VPN services to subscribers by connecting the UNI port to a CE device. The physical port can be configured to provide Layer 3 VPN services to multiple subscribers. You can schedule traffic for different Layer 3 VPN instances based on the SLA parameters agreed with the subscriber.
The following is a sample UNI and NNI logical interface configuration on the PE router providing the Layer 3 VPN service:
[edit interfaces]
xe-0/0/1 {
description “NNI IFL”;
unit 0 {
family inet {
address 100.1.1.1/24;
}
family mpls;
}
}
ge-0/0/1 {
description “UNI IFL”;
hierarchical-scheduler;
flexible-vlan-tagging;
unit 0 {
vlan-id 100;
family inet {
address 20.20.0.1/24;
}
}
unit 1 {
vlan-id 101;
family inet {
address 20.20.1.1/24;
}
}
unit 2 {
vlan-id 2;
family inet {
address 20.20.2.1/24;
}
}
unit 3 {
vlan-id 3;
family inet {
address 20.20.3.1/24;
}
}
unit 4 {
vlan-id 4;
family inet {
address 20.20.4.1/24;
}
}
...
}
Scheduling can be enabled on the interfaces to achieve hierarchical class of service support for traffic flowing from NNI towards UNI direction.
Configuring hierarchical class of service for Layer 2 VPN (Ethernet Pseudowires) Service
Supported ACX routers can be configured to provide Layer 2 VPN services to subscribers based on Ethernet pseudowires where the UNI port is connected to a CE device. The physical port can be configured to provide Layer 2 VPN services to multiple subscribers. You can schedule traffic for different pseudowires based on the SLA parameters agreed with the subscriber. Hierarchical class of service can be enabled per UNI logical interface represented as the attachment point of the Ethernet pseudowire to achieve the functionality.
The following is a sample to configure the UNI logical interface on the PE router providing the Layer 2 VPN service based on Ethernet pseudowire:
[edit interfaces]
ge-0/0/1 {
hierarchical-scheduler;
vlan-tagging;
unit 0 {
encapsulation vlan-ccc;
vlan-id 0;
}
unit 1 {
encapsulation vlan-ccc;
vlan-id 1;
}
unit 2 {
encapsulation vlan-ccc;
vlan-id 2;
}
unit 3 {
encapsulation vlan-ccc;
vlan-id 3;
}
unit 4 {
encapsulation vlan-ccc;
vlan-id 4;
}
}
You can enable scheduling on the interfaces to achieve hierarchical class of service for traffic flowing from NNI towards UNI direction.
Configuring hierarchical class of service for VPLS Service
Supported ACX routers can be configured to provide Layer 2 VPN services to subscribers based on VPLS where the UNI port can be connected to a CE device. Subscriber network is attached to UNI logical interface at the PE router and have a VPLS instance. The same physical port can service multiple VPLS instances for various subscribers. The service provider can schedule traffic for different VPLS instances based on the SLA parameters agreed with the subscriber. You can enable hierarchical class of service per UNI logical interface representing the VPLS instance for the subscriber to achieve the functionality.
The following is a sample to configure the UNI logical interface on the PE router providing the VPLS service:
[edit interfaces]
ge-0/0/1 {
hierarchical-scheduler;
vlan-tagging;
encapsulation vlan-vpls;
unit 0 {
encapsulation vlan-vpls;
vlan-id 0;
}
unit 1 {
encapsulation vlan-vpls;
vlan-id 1;
}
unit 2 {
encapsulation vlan-vpls;
vlan-id 2;
}
unit 3 {
encapsulation vlan-vpls;
vlan-id 3;
}
unit 4 {
encapsulation vlan-vpls;
vlan-id 4;
}
}
Scheduling can be enabled on the interfaces to achieve hierarchical class of service for the traffic flowing from NNI towards UNI direction.
Verifying the hierarchical class of service configurations
You can use the following CLI commands to verify the configuration:
-
show interfaces queue—Shows physical interface aggregate, physical interface remaining, and logical interface traffic statistics to monitor the traffic received and transmitted. The following are some sample outputs ofshow interfaces queueCLI command:user@host# run show interfaces queue ge-0/0/4.2 Logical interface ge-0/0/4.2 (Index 555) (SNMP ifIndex 671) Forwarding classes: 16 supported, 8 in use Egress queues: 8 supported, 8 in use Burst size: 0 Queue: 0, Forwarding classes: 8q0 Queued: Packets : 1121476 7642 pps Bytes : 587885024 32237416 bps Transmitted: Packets : 594964 3160 pps Bytes : 304621568 12946280 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 526512 4482 pps Total-dropped bytes : 283263456 19291136 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 1, Forwarding classes: 8q1 Queued: Packets : 1121476 7642 pps Bytes : 587885154 32237416 bps Transmitted: Packets : 594959 3160 pps Bytes : 304619008 12946280 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 526517 4482 pps Total-dropped bytes : 283266146 19291136 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 2, Forwarding classes: 8q2 Queued: Packets : 1119456 7321 pps Bytes : 595127702 31122568 bps Transmitted: Packets : 274601 1500 pps Bytes : 140595712 6144000 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 844855 5821 pps Total-dropped bytes : 454531990 24978568 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 3, Forwarding classes: 8q3 Queued: Packets : 1119464 7303 pps Bytes : 595131980 31122568 bps Transmitted: Packets : 274602 1500 pps Bytes : 140596224 6144000 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 844862 5803 pps Total-dropped bytes : 454535756 24978568 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 4, Forwarding classes: 8q4 Queued: Packets : 1121476 7642 pps Bytes : 587885024 32237416 bps Transmitted: Packets : 594964 3160 pps Bytes : 304621568 12946280 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 526512 4482 pps Total-dropped bytes : 283263456 19291136 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 5, Forwarding classes: 8q5 Queued: Packets : 1121476 7660 pps Bytes : 587885024 32310560 bps Transmitted: Packets : 594964 3178 pps Bytes : 304621568 13019424 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 526512 4482 pps Total-dropped bytes : 283263456 19291136 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 6, Forwarding classes: 8q6 Queued: Packets : 1121476 7017 pps Bytes : 587190842 29535136 bps Transmitted: Packets : 621684 3589 pps Bytes : 318302208 14701712 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 499792 3428 pps Total-dropped bytes : 268888634 14833424 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 7, Forwarding classes: 8q7 Queued: Packets : 1121477 6481 pps Bytes : 586036910 27137704 bps Transmitted: Packets : 666066 3660 pps Bytes : 341025792 14994280 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 455411 2821 pps Total-dropped bytes : 245011118 12143424 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytesuser@host# run show interfaces queue ge-0/0/4 aggregate Physical interface: ge-0/0/4, Enabled, Physical link is Up Interface index: 648, SNMP ifIndex: 1763 Description: UNI side - connected to ixia 6/9 Forwarding classes: 16 supported, 8 in use Egress queues: 8 supported, 8 in use Queue: 0, Forwarding classes: 8q0 Queued: Packets : 16762731 33205 pps Bytes : 8738362264 139058280 bps Transmitted: Packets : 8779233 13724 pps Bytes : 4494967296 56220880 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7983498 19481 pps Total-dropped bytes : 4243394968 82837400 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 52 pkts 10816 bytes Queue: 1, Forwarding classes: 8q1 Queued: Packets : 16762732 33237 pps Bytes : 8738359966 139190408 bps Transmitted: Packets : 8779363 13756 pps Bytes : 4495033856 56353008 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7983369 19481 pps Total-dropped bytes : 4243326110 82837400 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 43 pkts 8944 bytes Queue: 2, Forwarding classes: 8q2 Queued: Packets : 16754769 30221 pps Bytes : 8826383526 127522040 bps Transmitted: Packets : 4052168 6369 pps Bytes : 2074710016 26095472 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 12702601 23852 pps Total-dropped bytes : 6751673510 101426568 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 24232 pkts 5040256 bytes Queue: 3, Forwarding classes: 8q3 Queued: Packets : 16754937 30328 pps Bytes : 8826406908 127965968 bps Transmitted: Packets : 4052173 6378 pps Bytes : 2074646336 26134456 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 12702764 23950 pps Total-dropped bytes : 6751760572 101831512 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 24205 pkts 5034640 bytes Queue: 4, Forwarding classes: 8q4 Queued: Packets : 16762735 33406 pps Bytes : 8738360722 139886136 bps Transmitted: Packets : 8779404 13828 pps Bytes : 4495054848 56648672 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7983331 19578 pps Total-dropped bytes : 4243305874 83237464 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 46 pkts 9568 bytes Queue: 5, Forwarding classes: 8q5 Queued: Packets : 16762734 33285 pps Bytes : 8738359924 139389112 bps Transmitted: Packets : 8779416 13788 pps Bytes : 4495060992 56485136 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7983318 19497 pps Total-dropped bytes : 4243298932 82903976 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 52 pkts 10816 bytes Queue: 6, Forwarding classes: 8q6 Queued: Packets : 16762732 27688 pps Bytes : 8721917186 115931832 bps Transmitted: Packets : 9618678 12111 pps Bytes : 4924763136 49614432 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7144054 15577 pps Total-dropped bytes : 3797154050 66317400 bps Queue Buffer Usage: Reserved buffer : 24 pkts 4992 bytes Shared buffer : 0 pkts 0 bytes Queue: 7, Forwarding classes: 8q7 Queued: Packets : 16762733 26045 pps Bytes : 8710804790 108947832 bps Transmitted: Packets : 10187546 11805 pps Bytes : 5216023552 48359208 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 6575187 14240 pps Total-dropped bytes : 3494781238 60588624 bps Queue Buffer Usage: Reserved buffer : 21 pkts 4368 bytes Shared buffer : 0 pkts 0 bytesuser@host# run show interfaces queue ge-0/0/4 remaining-traffic Physical interface: ge-0/0/4, Enabled, Physical link is Up Interface index: 648, SNMP ifIndex: 1763 Description: UNI side - connected to ixia 6/9 Forwarding classes: 16 supported, 8 in use Egress queues: 8 supported, 8 in use Queue: 0, Forwarding classes: 8q0 Queued: Packets : 77501 6106 pps Bytes : 41609646 26235344 bps Transmitted: Packets : 3206 243 pps Bytes : 1641472 999248 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 74295 5863 pps Total-dropped bytes : 39968174 25236096 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1495 pkts 310960 bytes Queue: 1, Forwarding classes: 8q1 Queued: Packets : 77489 6100 pps Bytes : 41444318 26107008 bps Transmitted: Packets : 9330 732 pps Bytes : 4776960 3002344 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 68159 5368 pps Total-dropped bytes : 36667358 23104664 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1435 pkts 298480 bytes Queue: 2, Forwarding classes: 8q2 Queued: Packets : 77485 6099 pps Bytes : 41362188 26054080 bps Transmitted: Packets : 12417 975 pps Bytes : 6357504 3996992 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 65068 5124 pps Total-dropped bytes : 35004684 22057088 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1507 pkts 313456 bytes Queue: 3, Forwarding classes: 8q3 Queued: Packets : 77547 6114 pps Bytes : 41609314 26271632 bps Transmitted: Packets : 3261 243 pps Bytes : 1646862 999248 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 74286 5871 pps Total-dropped bytes : 39962452 25272384 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1381 pkts 287248 bytes Queue: 4, Forwarding classes: 8q4 Queued: Packets : 77502 6105 pps Bytes : 41450894 26131200 bps Transmitted: Packets : 9349 732 pps Bytes : 4786688 3002344 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 68153 5373 pps Total-dropped bytes : 36664206 23128856 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1366 pkts 284128 bytes Queue: 5, Forwarding classes: 8q5 Queued: Packets : 77480 6094 pps Bytes : 41358904 26032304 bps Transmitted: Packets : 12444 975 pps Bytes : 6371328 3996992 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 65036 5119 pps Total-dropped bytes : 34987576 22035312 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1552 pkts 322816 bytes Queue: 6, Forwarding classes: 8q6 Queued: Packets : 77970 6099 pps Bytes : 41151002 25749384 bps Transmitted: Packets : 30585 2440 pps Bytes : 15659520 9997088 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 47385 3659 pps Total-dropped bytes : 25491482 15752296 bps Queue Buffer Usage: Reserved buffer : 3 pkts 624 bytes Shared buffer : 0 pkts 0 bytes Queue: 7, Forwarding classes: 8q7 Queued: Packets : 77971 6099 pps Bytes : 41151540 25749384 bps Transmitted: Packets : 30585 2440 pps Bytes : 15659520 9997088 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 47386 3659 pps Total-dropped bytes : 25492020 15752296 bps Queue Buffer Usage: Reserved buffer : 3 pkts 624 bytes Shared buffer : 0 pkts 0 bytes -
show class-of-service packet-buffer usage—Shows the total buffer usage of the system. The following is a sample output of theshow class-of-service packet-buffer usageCLI command:user@host# run show class-of-service packet-buffer usage Egress: Total Buffer Bytes : 10652.89 KB in use out of 12480.00 KB Total Buffer Pkts : 52445 in use out of 61440 Dedicated Buffer Bytes : 48.14 KB in use out of 738.16 KB Dedicated Buffer Pkts : 237 in use out of 3634 Shared Buffer Bytes : 10604.75 KB in use out of 11741.84 KB Shared Buffer Pkts : 52208 in use out of 57806 -
For interface sets, you can run the following commands:
-
show interfaces interface-set voq—Show VOQ statistics for the interface-set. -
show interfaces interface-set detail—Display detailed output for the interface set. -
show interfaces interface-set voq remaining-traffic—Show remaining traffic queue statistics for the interface set.
-
You can use the syslog to view the log messages and error reports.