MPLS QoS - SUP720BXL GE Port not supporting Strict Priority & Priority %

Question

Hi Sir,
My customer have few C7609s with SUP720 3BXL and running IOS image s72033-advipservicesk9_wan-mz.122-18.SXF6.bin within the MPLS network.
What I experienced is that I can't configured the built-in GE port of the SUP720 for Strict Priority & Priority Percent QoS.
Is there anyone outside there know what is the equivalent or alternative to above mentioned two QoS features ? This is mainly to priortize the voice traffic.
Thanks in advance.
Ray.

Answer 1

The below has been recommended for a customer using 7600 in the
Core with GiGs as normal core facing links.
The implementation goes as below:
i) Enabling the MLS on the 7600 chassis.
mls qos
ii) Configuring Trust Boundary on all Interfaces.
interface GigabitEthernet1/1
mls qos trust
<--By default the Trust Command trusts the incoming DSCP/TOS.
When the ports are configured with the Trust Boundary as given above,
all incoming packets are mapped into Initial Internal DSCP values.
These values are used purely as a reference MAP for Internal QOS
processing on the 7600.
Internal DSCP Output COS
DSCP 0 7 COS 0
DSCP 8 15 COS 1
DSCP 16 23 COS 2
DSCP 24 31 COS 3
DSCP 32 39 COS 4
DSCP 40 47 COS 5
DSCP 48 55 COS 6
DSCP 56 63 COS 7
This deafault mapping can be modified by modifying the DSCP-COS MAP
within the MLS QOS. The the default mapping are as per standards,
and hence it is not recommended to change the mapping.
iii) Directing Traffic into the appropriate Egress Queue.
Once the incoming traffic is mapped to the Initial Internal DSCP,
and the same gets mapped to the Output COS, these values need to
be directed to the appropriate Queues for the desired QOS behavior
on the MPLS EXP packets.
interface x/x
wrr-queue cos-map
priority-queue cos-map
For Eg:
interface gigabitethernet 1/10
wrr-queue cos-map 2 threshold 2 0
wrr-queue cos-map 3 threshold 2 1 2
wrr-queue cos-map 4 threshold 2 3 4
priority-queue cos-map 1 5 6 7
iv) Defining Queue Bandwidth Limits.
After directing the COS to appropriate queues and then assigning them
to appropriate drop threshold values, it is required to define the
bandwidth allocation per queue. This can be done as below.
!<-- To Set minimum assured bandwidth to COS Queue 1,2 & 3
Use the Bandwdith Percentage command as below.
interface GigabitEthernet 1/1
wrr-queue bandwidth percent !
<--Total of Queue Weights should be =100%
To evenly distribute the available bandwidth during congestion for
all the 4 queues, it is required to set the Queue Scheduling Weights
between all the four Queues. This is done by assigning the queues
weights which are used during WRR scheduling.
!<--Set the Queue-Limit Weights of WRR Scheduling as below
interface GigabitEthernet 1/1
wrr-queue queue-limit
priority-queue queue-limit xx
!<--For Example:
interface GigabitEthernet 1/1
wrr-queue queue-limit 25 20 22
priority-queue queue-limit 33
!<-- The example above does a Queue scheduling for Queue 1 for 25% of BW,
Queue 2 for 20% and Queue 3 for 22 % and Priority Queue has 33 %.
To conclude if you want to use the conventional MQC based toggles,
you will need to use FlexWans with WAN ports or OSM's. Where you can
apply the conventional MQC based toggles.
FOr all the LAN ports in 7600 only hardware queues are supported which
can be controlled using MLS, the difference between SUP and Module based
LAN ports is withing the Scheduling alogirthms supported, the Egress and Ingress
buffers, and the number of queues and drop thresholds available.
For Reference use this link:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/software/122sr/swcg/qos.htm
HTH-Cheers,
Swaroop
PS:
Policy Map Class Command Restrictions
PFC QoS does not support these policy map class commands:
?bandwidth
?priority
?queue-limit
?random-detect
?set qos-group
?service-policy