For feedback, use the following: |
ipd_online_feedback@alcatel-lucent.com |
Queue sharing and redirection is supported on the SR and ESS platforms with the following IOM types:Queue sharing is also supported if the High Scale MDA (HSMDA) is used. On ingress, HSMDA queues are bypassed, and the queue group on the IOM forwarding plane is used. On egress, it is possible to redirect forwarding classes from multiple SAPs to an HSMDA queue group. Note that the HSMDA also uses the term queue group to describe a group of 8 pre-configured hardware queues on its egress port. When queue sharing and redirection is configured on egress, a set of 8 HSMDA queues could be configured as a part of the queue group template. These correspond to 8 hardware queues on the HSMDA. When all eight (8) egress fcs are mapped to the queue-group instantiated in the egress port, the per-sap hsmda queue-group resource is freed.Once an ingress queue group template is defined, a forwarding plane queue group with the same name may be created on an ingress forwarding plane of an IOM/IMM/XMA. Forwarding plane queue groups are named objects that act as a container for a group of policers. Queues are not supported in forwarding plane queue groups. Only hierarchical policers are supported in the forwarding plane queue group, rather than queues. These policers may be configured to use profile-aware behavior. The policers are created based on the defined policer IDs within the associated queue group template. Multiple forwarding plane queue groups of the same template name may be created on ingress if they have a different instance identifier. These are termed queue group instances. Each instance of a named queue group created on a forwarding plane is an independent set of policers structured as per the queue group template. Forwarding plane queue groups are only supported with Ethernet ports and may be created on IOM/IMM/XMAs with ports in a LAG.Two models are supported for forwarding class redirection. In the first, the actual instance of a queue group to use for forwarding class redirection is named in the QoS policy. This is termed policy-based redirection.
2. Create an ingress or egress queue group instance with the same name as the template on the port associated with the SAP. Examples are as follows:
On ingress ports:
config>port>ethernet>access>ingress>queue-group queue-group-name
On egress ports:
config>port>ethernet>access>egress>queue-group queue-group-name [instance instance-id]
Queue parameter overrides can also be applied at this time.
3. Redirect the SAP ingress or SAP egress QoS policy forwarding class policer or queue to the queue group name and desired queue ID (Steps 2 and 3 may be done in opposite order). Examples are as follows:
On ingress:
config>qos>sap-ingress policy-id
fc fc-name
queue queue-id group queue-group-name
On egress:
config>qos>sap-egress policy-id
fc fc-name
queue queue-id group queue-group-name instance instance-id
config>qos>sap-egress policy-id
fc fc-name
policer policer-id group queue-group-name instance instance-id
2. Create an ingress queue group instance on the forwarding plane of the IOM/IMM/XMA, or an egress port queue group with the same name as the template on the port associated with the SAP.
On ingress:
config>card>fp>ingress>access>queue-group queue-group-name instance instance-id [create]
On egress:
config>port>ethernet>access>egress>queue-group queue-group-name [instance instance-id]
3. Redirect the SAP ingress forwarding class policer in the SAP-ingress QoS policy using the keyword fp-redirect-group keyword on the policer, or SAP egress forwarding class queue or policer using the port-redirect-group keyword. (Steps 2 and 3 may be done in opposite order.)
On ingress:
config>qos>sap-ingress policy-id
fc fc-name
queue queue-id fp-redirect-group
On egress:
config>qos>sap-egress policy-id
fc fc-name
queue queue-id port-redirect-group-queue
config>qos>sap-egress policy-id
fc fc-name
policer policer-id port-redirect-group-queue
4. Finally, the SAP ingress or SAP egress QoS policy must be applied to the SAP. The named queue group instance that was created on the ingress forwarding plane or the egress port must be specified at this time.
On ingress:
config>service>epipe>sap sap-id
ingress
qos sap-ingress-policy-id fp-redirect-group queue-group-name instance instance-id
On egress:
config>service>epipe>sap sap-id
egress
qos sap-egress-policy-id port-redirect-group queue-group-name instance instance-idNote that redirection to a queue group on the HSMDA supports the SAP-based provisioning model, only.Note that if the user enables the packet-byte-offset {add bytes | subtract bytes} option under the ingress queue-group policer, the byte counters of that policer will reflect the adjusted packet size.The set of statistics per queue are eligible for collection in a similar manner to SAP queues. The collect-stats command enables or disables statistics collection in to a billing file based on the accounting policy applied to the queue group.The user applies a network QoS policy to the ingress context of a spoke-SDP1 to redirect the mapping of a Forwarding Class (FC) to a policer defined in a queue-group template which is instantiated on the ingress Forwarding Plane (FP) where the PW packets are received.config>service>vprn>interface>spoke-sdp>ingress>qos network-policy-id fp-redirect-group queue-group-name instance instance-idLet us refer to a queue-group containing policers as a policer queue-group. The user must instantiate this queue-group by applying the following command:config>qos>network>ingress>fc>fp-redirect-group policer policer-id
config>qos>network>ingress>fc>fp-redirect-group multicast-policer policer-idWhen the FC of a PW is redirected to use a policer in the named queue-group, the policer feeds the existing per-FP ingress shared queues referred to as policer-output-queues. These queues are shared by both access and network policers configured on the same ingress FP. The shared queue parameters are configurable using the following command:
a.
b. a queue-group policer followed by the per-FP ingress shared queues referred to as policer-output-queues if the ingress context of the network IP interface from which the packet is received is redirected to a queue-group. The only exceptions to this behavior are for packets received from a IES/VPRN spoke interface and from a R-VPLS spoke-SDP, which is forwarded to the R-VPLS IP interface. In these two cases, the ingress network shared queue for the packet FC defined in the network-queue policy applied to the ingress of the MDA/FP is used.When a PW is redirected to use a policer queue-group, the classification of the packet for the purpose of FC and profile determination is performed according to default classification rule or the QoS filters defined in the ingress context of the network QoS policy applied to the PW. This is true regardless if an instance of the named policer queue-group exists on the ingress FP the PW packet is received on. The user can apply a QoS filter matching the dot1.p in the VLAN tag corresponding to the Ethernet port encapsulation, the EXP in the outer label when the tunnel is an LSP, the DSCP in the IP header if the tunnel encapsulation is GRE, and the DSCP in the payload’s IP header if the user enabled the ler-use-dscp option and the PW terminates in IES or VPRN service (spoke-interface).config>service>vprn>interface>spoke-sdp>egress>qos network-policy-id port-redirect-group queue-group-name instance instance-idconfig>qos>network>egress>fc>port-redirect-group {queue queue-id | policer policer-id [queue queue-id]}
• The user can redirect a FC to use a queue in a queue-group and in which case there are no policers used.
config>qos>network>egress>fc>port-redirect-group queue queue-id
• The user can redirect a FC to use a policer-id in a queue-group without specifying a queue-id and in which case the policer is feeding the egress shared queue for that FC defined in the network-queue policy applied to the egress of this port.
config>qos>network>egress>fc>port-redirect-group policer policer-id
• The user can redirect a FC to use a policer feeding a queue both of which are defined in the named queue-group.
config>qos>network>egress>fc>port-redirect-group policer policer-id
queue queue-idconfig>qos>network>egress>prec ip-prec-value [fc fc-name] [profile {in | out}]
config>qos>network>egress>dscp dscp-name [fc fc-name] [profile {in | out}]config>service>vprn>interface>spoke-sdp>egress>qos network-policy-id port-redirect-group queue-group-name instance instance-idconfig>service>ies>interface>spoke-sdp>egress>qos network-policy-id port-redirect-group queue-group-name instance instance-idSimilar to the SDP binding stats, the ingress policer stats for a spoke-SDP does not count the label stack. When the spoke-SDP is part of a L2-service, they will count the L2-encapsulation, minus CRC and VLAN tag if popped out, and they also count the PW CW, if included in the packet. When the spoke-SDP is part of a L3-service, the policer stats only count the IP payload and do not count the PW CW. Unlike the ingress SDP binding stats, if the user enables the packet-byte-offset {add bytes | subtract bytes} option under the queue-group policer, then the policer stats reflect the adjusted packet size in both L2 and L3-spoke-SDPs.The egress queue-group policer and/or queue counts the full label stack of the PW packet including the CW. If the user enables the packet-byte-offset {add bytes | subtract bytes} option under the queue-group policer and queue-group queue, then the policer and queue stats reflect the adjusted packet size.*A:Dut-T>cfg>qos>qgrps# info----------------------------------------------ingressqueue-group "QG_ingress_1" createqueue 1 best-effort creatembs 100exitqueue 2 best-effort creatembs 100exitqueue 3 best-effort creatembs 100exitqueue 4 best-effort creatembs 100exitexitexit----------------------------------------------*A:Dut-T>cfg>qos>qgrps#
*A:Dut-T>cfg>qos>qgrps# info----------------------------------------------...egressqueue-group "QG_egress_1" createdescription "Egress queue group"queue 1 best-effort creatembs 100exitqueue 2 best-effort creatembs 100exitqueue 3 best-effort creatembs 100exitqueue 4 best-effort creatembs 100exitexitexit----------------------------------------------*A:Dut-T>cfg>qos>qgrps#*A:Dut-T>config>qos>sap-ingress# info----------------------------------------------queue 1 createexitqueue 11 multipoint createexitfc "af" createqueue 2 group "QG_ingress_1"exitfc "be" createqueue 1 group "QG_ingress_1"exitfc "ef" createqueue 3 group "QG_ingress_1"exitfc "nc" createqueue 4 group "QG_ingress_1"exitdot1p 0 fc "be"dot1p 2 fc "af"dot1p 4 fc "ef"dot1p 6 fc "nc"----------------------------------------------*A:Dut-T>config>qos>sap-ingress#A:Dut-T>config>qos>sap-egress# info----------------------------------------------queue 1 createexitfc af createqueue 2 group "QG_egress_1"exitfc be createqueue 1 group "QG_egress_1"exitfc ef createqueue 3 group "QG_egress_1"exitfc nc createqueue 4 group "QG_egress_1"exit----------------------------------------------A:Dut-T>config>qos>sap-egress#*A:Dut-A# configure qos sap-egress 3*A:Dut-A>config>qos>sap-egress# info----------------------------------------------queue 1 createexitqueue 2 createexitpolicer 8 createrate 50000exitfc af createqueue 3 port-redirect-group-queuehsmdaqueue 3 port-redirect-group-queueexitexitfc be createqueue 3 port-redirect-group-queuehsmdaqueue 3 port-redirect-group-queueexitexitfc ef createpolicer 8 port-redirect-group-queuehsmdaqueue 3 port-redirect-group-queueexitexitfc h1 createqueue 3 port-redirect-group-queuehsmdaqueue 3 port-redirect-group-queueexitexitfc h2 createqueue 3 port-redirect-group-queuehsmdaqueue 3 port-redirect-group-queueexitexitfc l1 createqueue 3 port-redirect-group-queuehsmdaqueue 3 port-redirect-group-queueexitexitfc l2 createqueue 3 port-redirect-group-queuehsmdaqueue 3 port-redirect-group-queueexitexitfc nc createqueue 3 port-redirect-group-queuehsmdaqueue 3 port-redirect-group-queueexitexit----------------------------------------------This is to be in-conjunction with:*A:Dut-A# configure service vpls 1*A:Dut-A>config>service>vpls# info----------------------------------------------stpshutdownexitsap 9/1/2:1 createegressqos 3 port-redirect-group qg1 instance 101exitexit*A:Dut-T>config>port# /configure port 9/2/1*A:Dut-T>config>port# info----------------------------------------------ethernetmode accessaccessingressqueue-group "QG_ingress_1" createexitexitegressqueue-group "QG_egress_1" createexitexitexitexitno shutdown----------------------------------------------*A:Dut-T>config>port#*A:Dut-T>config>port# /configure port 9/2/2*A:Dut-T>config>port# info----------------------------------------------ethernetmode accessaccessingressqueue-group "QG_ingress_1" createexitexitegressqueue-group "QG_egress_1" createexitexitexitexitno shutdown----------------------------------------------*A:Dut-T>config>port#*A:Dut-T>config>port>ethernet>access# /configure port 9/2/1*A:Dut-T>config>port# info----------------------------------------------ethernetmode accessaccessingressqueue-group "QG_ingress_1" createqueue-overridesqueue 2 createrate 800000 cir 20000exitexitexitexitegressqueue-group "QG_egress_1" createexitexitexitexitno shutdown----------------------------------------------*A:Dut-T>config>port# /configure port 9/2/2*A:Dut-T>config>port# info----------------------------------------------ethernetmode accessaccessingressqueue-group "QG_ingress_1" createexitexitegressqueue-group "QG_egress_1" createqueue-overridesqueue 3 createrate 1500000 cir 2000exitexitexitexitexitexitno shutdown----------------------------------------------*A:Dut-T>config>port#configqosqueue-group-templatesingressqueue-group "Ingress_QG_1" createpolicer 2 createrate 9000exitexitexitegressqueue-group "Egress_QG_1" createqueue 1 best-effort createexitpolicer 2 createrate 9000exitexitexitexitnetwork 2 createingressfc befp-redirect-group policer 2exitexitegressfc beport-redirect-group policer 2exitexitexitcard 1card-type xcm-x20mda 1 mda-type cx20-10g-sfp no shutdownexitfp 1ingressnetworkqueue-group "Ingress_QG_1" instance 550 createexitexitexitexitno shutdownport 1/1/3ethernetmtu 1514networkegressqueue-group "Egress_QG_1" instance 550 createexitexitexitexitno shutdownexitrouterinterface “to-D”address 10.10.11.3/24port 1/1/3qos 2 egress-port-redirect-group "Egress_QG_1" egress-instance550 ingress-fp-redirect-group "Ingress_QG_1" ingress-instance550no shutdownconfigure#--------------------------------------------------echo "QoS Policy Configuration"#--------------------------------------------------qosqueue-group-templatesingressqueue-group "QGIng1" createpolicer 1 createexitpolicer 2 createexitpolicer 3 createexitpolicer 4 createexitexitexitegressqueue-group "QGEgr1" createqueue 1 best-effort createexitpolicer 1 createexitpolicer 2 createexitpolicer 3 createexitpolicer 4 createexitexitexitexitexitnetwork 10 createingresslsp-exp 0 fc be profile outlsp-exp 1 fc be profile outlsp-exp 2 fc be profile outlsp-exp 3 fc be profile outlsp-exp 4 fc be profile outlsp-exp 5 fc be profile outlsp-exp 6 fc be profile outlsp-exp 7 fc be profile outfc affp-redirect-group policer 4exitfc befp-redirect-group policer 1exitfc l1fp-redirect-group policer 2exitfc l2fp-redirect-group policer 3exitexitegressfc afport-redirect-group policer 4exitfc beport-redirect-group policer 1exitfc l1port-redirect-group policer 2exitfc l2port-redirect-group policer 3exitexitexitexit#--------------------------------------------------echo "Card Configuration"#--------------------------------------------------card 3fp 1ingressnetworkqueue-group "QGIng1" instance 1 createexitqueue-group "QGIng1" instance 2 createexitexitexitexitexit#--------------------------------------------------echo "Port Configuration"#--------------------------------------------------port 3/2/1ethernetencap-type dot1qnetworkegressqueue-group "QGEgr1" instance 1 createexitqueue-group "QGEgr1" instance 2 createexitexitexitexitno shutdown*A:Dut-T>config>service#customer 1 createdescription "Default customer"exitsdp 1 mpls createdescription "Default sdp description"far-end 2.2.2.2ldppath-mtu 9000keep-aliveshutdownexitno shutdownexitvpls 1 customer 1 vpn 1 createdescription "Default tls description for service id 1"service-mtu 9000stpshutdownexitservice-name "XYZ Vpls 1"sap 9/2/1:1.* createdescription "Default sap description for service id 1"static-mac 00:00:1e:00:01:02 createingressqos 10exitexitspoke-sdp 1:101 vc-type vlan createdescription "Description for Sdp Bind 1 for Svc ID 1"ingressqos 10 fp-redirect-group "QGIng1" instance 1exitegressqos 10 port-redirect-group "QGEgr1" instance 1exitstatic-mac 00:00:28:00:01:02 createno shutdownexitno shutdownexitrouterinterface "ip-12.1.1.1"address 12.1.1.1/24port 3/2/1:1exitinterface "system"address 1.1.1.1/32exit#---------------------------------------------*A:Dut-T>config>service>vpls# info----------------------------------------------stpshutdownexitsap 9/2/1 createingressqos 10exitegressqos 10exitexitsap 9/2/2 createingressqos 10exitegressqos 10exitexitno shutdown----------------------------------------------*A:Dut-T>config>service>vpls#