Example 6 is similar to Example 5, except that FCs in use from the port policy and the override policy are considered. The following configuration shows the policy association with two SAPs configured in the routed VPLS, with one SAP on the access port and the other SAP on the hybrid port.
*A:dut-a>config>qos>dscp-classification 23 create
*A:dut-a>config>qos>dscp-classification# info detail
----------------------------------------------
description "dscp-classification-23"
default-dscp-fc "be" profile in
dscp cs3 fc "be"
dscp cs4 fc "ef" profile out
dscp af31 fc "af" profile in
dscp af33 fc "l1" profile in
dscp af41 fc "nc"
dscp cp25 fc "l2"
dscp cp31 fc "h2" profile out
dscp cp33 fc "h1" profile in
----------------------------------------------
*A:dut-a>config>qos>dscp-classification 24 create
*A:dut-a>config>qos>dscp-classification# info detail
----------------------------------------------
description "dscp-classification-24"
default-dscp-fc "be" profile in
dscp cs4 fc "ef" profile out
dscp af31 fc "af" profile in
----------------------------------------------
*A:dut-a# configure qos sap-ingress 24
*A:dut-a>config>qos>sap-ingress# info
----------------------------------------------
description "sap-Ingress-Policy-24"
num-qos-classifiers 26
meter 1 create
mode trtcm2
rate cir 5000 pir 7000
mbs 200 kbits
cbs 100 kbits
exit
meter 9 create
mode trtcm2
rate cir 3000 pir 5000
mbs 200 kbits
cbs 100 kbits
exit
meter 10 create
mode trtcm2
rate cir 4000 pir 6000
mbs 200 kbits
cbs 100 kbits
exit
meter 11 multipoint create
mode trtcm2
rate cir 2000 pir 5000
mbs 200 kbits
cbs 100 kbits
exit
meter 12 create
mode trtcm2
rate cir 3500 pir 6000
mbs 200 kbits
cbs 100 kbits
exit
meter 13 create
mode trtcm2
rate cir 5000 pir 7000
mbs 200 kbits
cbs 100 kbits
exit
meter 14 create
mode trtcm2
rate cir 5000 pir 6000
mbs 200 kbits
cbs 100 kbits
exit
meter 15 create
mode trtcm2
rate cir 4000 pir 5000
mbs 200 kbits
cbs 100 kbits
exit
meter 20 multipoint create
mode trtcm2
rate cir 0 pir 5
mbs 50 kbits
cbs 50 kbits
exit
meter 21 multipoint create
mode trtcm2
rate cir 0 pir 10
mbs 100 kbits
cbs 100 kbits
exit
meter 22 multipoint create
mode trtcm2
rate cir 0 pir 50
mbs 100 kbits
cbs 100 kbits
exit
fc "af" create
meter 11
broadcast-meter 22
exit
fc "be" create
meter 9
exit
fc "ef" create
meter 14
broadcast-meter 22
exit
fc "h1" create
meter 15
broadcast-meter 22
exit
fc "h2" create
meter 13
broadcast-meter 22
exit
fc "l1" create
meter 12
broadcast-meter 22
unknown-unicast 21
exit
fc "l2" create
meter 10
broadcast-meter 20
exit
fc "nc" create
meter 1
exit
dscp-classification 24
----------------------------------------------
The following are sample IES service and routed VPLS service configuration outputs.
----------------------------------------------
ies 7 customer 1 vpn 7 create
description "Default Ies service id 7"
interface "int1IES201" create
address 10.43.44.1/24
vpls "rvpls607"
ingress
enable-table-classification
routed-override-qos-policy 24
exit
exit
exit
service-name "XYZ Ies 7"
no shutdown
----------------------------------------------
----------------------------------------------
vpls 607 customer 1 r-vpls svc-sap-type any create
description "Default tls service id 607"
allow-ip-int-bind
exit
stp
shutdown
exit
service-name "rvpls607"
sap 1/1/24:201 create // SAP on hybrid port
description "Default sap service id 607"
ingress
qos 24 enable-table-classification
exit
egress
exit
exit
sap 1/1/3:201 create // SAP on access port
description "Default sap service id 607"
ingress
qos 24 enable-table-classification
exit
egress
exit
exit
no shutdown
----------------------------------------------
The configuration of the network port policy for a hybrid port, followed by associating the policy with hybrid port 1/1/3 is shown below. This configuration is used for classifying RVPLS SAP bridged packets and also for classifying IP traffic received and processed in the context of the network port IP interface.
**A:dut-a >config>qos# network 123
**A:dut-a >config>qos>network# info
----------------------------------------------
ingress
default-action fc be profile in
meter 1 create
exit
dscp cs4 fc ef profile out
dscp af31 fc af profile in
dscp af33 fc l1 profile in
dscp af41 fc nc profile in
dscp cp25 fc l2 profile out
dscp cp31 fc h2 profile out
dscp cp33 fc h1 profile in
exit
egress
exit
----------------------------------------------
*A:dut-a #/configure port 1/1/24
A:NS1543C2102>config>port# info
----------------------------------------------
shutdown
ethernet
mode hybrid
access
exit
encap-type dot1q
network
queue-policy "_tmnx_hybrid_default"
qos 123
exit
exit
----------------------------------------------
*A:NS1543C2102>config>port#
The configuration of the DSCP classification policy associated with the access port, which is the port that the RVPLS SAP is configured on, is shown below. The policy is used for classifying bridged packets.
*A:dut-a# configure port 1/1/3
*A:dut-a>config>port# info
----------------------------------------------
ethernet
mode access
enable-table-classification
access
ingress
dscp-classification 24
untagged-fc ef
exit
exit
encap-type dot1q
mtu 9212
exit
no shutdown
----------------------------------------------
To determine the resources needed for RVPLS SAP 1/1/3:201 consider the FCs configured in the DSCP classification policy configured in access port 1/1/3 context—there are three FCs (be, af, ef) configured. In addition, consider the FCs configured in the DSCP classification policy configured in the context of IES IP interface—there are three FCs (be, af, ef) configured. The total number of resources for RVPLS SAP 1/1/3:201 is computed as follows using the meter configuration under SAP ingress policy 24.
FC (ef) = 1 + 1 + 1 + 0 = 3 (one for unicast, one for broadcast, and one for both multicast & unknown-unicast) FC (af) = 1 + 1 + 1 + 0 = 3 (one for unicast, one for broadcast, and one for both multicast and unknown-unicast) FC (be) = 1 +0 +1 +0 = 2 (one for unicast and one for all of BUM) FC (default-fc) = 1 + 0 + 1 + 0 = 2 (one for unicast and one for all of BUM)
TP = Total meters used is 4 (meter 11, meter 9, meter 22, and meter 14).
Hence, to use the available resources efficiently for the RVPLS SAP 1/1/3:201 we need a policy with num-qos-classifiers set to (maximum (10, (4*2)) = 10.
To determine the resources needed for RVPLS SAP 1/1/24:201 consider the FCs configured in the network port policy 123, which is associated with network port 1/1/24—all eight FCs are configured. In addition, consider the FCs configured in the DSCP classification policy configured in the context of IES IP interface—three FCs (be, af, ef) are configured. The total number of resources for RVPLS SAP 1/1/24:201 is computed as follows, using the meter configuration under the SAP ingress policy 24:
FC (nc) = 1 + 0 + 1 + 0 = 2 (one for unicast and one for all of BUM) FC (h1) = 1 + 1 + 1 + 0 = 3 (one for unicast, one for broadcast, and one for both multicast & unknown-unicast) FC (ef) = 1 + 1 + 1 + 0 = 3 (one for unicast, one for broadcast, and one for both multicast & unknown-unicast) FC (h2) = 1 + 1 + 1 + 0 = 3 (one for unicast, one for broadcast, and one for both multicast & unknown-unicast) FC (l1) = 1 + 1 + 1 + 1 = 4 (one for unicast, one for broadcast, one for unknown-unicast & one for multicast) FC (af) = 1 + 1 + 1 + 0 = 3 (one for unicast, one for broadcast, and one for both multicast and unknown-unicast) FC (l2) = 1 + 1 + 1 + 0 = 3 (one for unicast, one for broadcast, and one for both multicast and unknown-unicast) FC (be) = 1 + 0 + 1 + 0 = 2 (one for unicast and one for all of BUM) FC (default-fc) = 1 + 0 + 1 + 0 = 2 (one for unicast and one for all of BUM, because default-dscp-fc is configured to be FC 'be' in the dscp-classification policy)
TP = Total meters used is 11.
Hence, for RVPLS SAP /1/124:201, we need a policy with num-qos-classifiers in the policy is calculated to be (maximum (25, (11*2)) = 25, but is set to 26 after rounding off to the next highest even number.