11. Access Egress QoS Policies

This chapter provides information to configure access egress QoS policies using the CLI.

11.1. Overview

This section provides an overview of access egress QoS policies.

11.1.1. Access Egress QoS Policies on 7210 SAS-R6 and 7210 SAS-R12

On the 7210 SAS-R6 and 7210 SAS-R12 platforms, an access egress policy allows users to define the marking values for the traffic sent out of the access ports towards the customer. Access egress QoS policies map FC flows to marking values. In addition, based on the queuing mode used on access egress, these policies also define the per-port queue parameters.

11.1.2. Access Egress QoS Policies for SAP-based Queuing Mode on 7210 SAS-R6 and 7210 SAS-R12

In SAP-based queuing mode,the 7210 SAS-R6 and 7210 SAS-R12 support SAP-based marking for access SAPs and port-based egress marking on access ports. SAP-based marking is only supported for L2 SAPs, that is, SAPs configured in Epipe and VPLS services. If users enable remarking in the SAP egress policy attached to the SAP, then the remark policy configured is used to mark the packets sent out of the SAP. If remarking is disabled in the SAP egress policy attached to the SAP, remark policy configured under the access-egress policy associated with the egress access port is used to mark all packets sent out of the L2 SAP configured on the access port. This is known as port-based marking.

Port-based marking is supported primarily for L3 SAPs (that is, SAPs configured in VPRN services and IES services). SAP based marking is not supported for L3 SAPs.

On 7210 SAS-R6 and 7210 SAS-R12, no explicit CLI command is provided to choose between port-based marking and SAP-based marking for L2 SAPs. The user can configure SAP-based marking by enabling remarking in the SAP egress policy attached to the L2 SAP, or configure port-based marking by disabling remarking in the SAP egress policy attached to the SAP and enabling remarking in the access-egress policy associated with the access port on which the L2 SAP is configured.

A remarking policy can be defined for each access-egress policy and remarking is disabled by default. Only remarking policies of the type dot1p, dot1p-lsp-exp-shared, dscp, or dot1p-dscp can be used with access-egress policies. The following is the marking behavior with different remark policy types.

  1. If the remark policy type is dot1p or dot1p-lsp-exp-shared, all traffic sent out of L2 SAPs and L3 SAPs configured on that port has the dot1p bits marked.
  2. If the remark policy type is dscp, all traffic sent out of L2 SAPs and L3 SAPs configured on that port has the IP DSCP bits marked (assuming L2 SAPs are carrying IP traffic).
  3. If the remark policy type is dot1p-dscp, all traffic sent out of L2 SAPs and L3 SAPs configured on that port has the IP DSCP bits (assuming L2 SAPs are carrying IP traffic) and dot1p bits marked.
Note:

  1. If remarking is enabled for the SAP egress policy and port based marking is enabled, the values configured in the SAP egress policy are used. For L3 SAPs the values configured in the access-egress policy are used.
  2. If remarking is disabled for the SAP egress policy and port-based marking is enabled, IP DSCP values get marked even for the traffic egressing out of the L2 SAPs configured on the port. To avoid this, Nokia recommends using only FC-to-dot1p values when both L2 and L3 SAPs are configured on the same access port.

11.1.3. Access Egress QoS Policies for Port-based Queuing Mode on 7210 SAS-R6 and 7210 SAS-R12

On the 7210 SAS-R6 and 7210 SAS-R12, in addition to marking values, the access-egress QoS policy provides an option to define port-based queues and scheduling. when per-port egress queues are used for SAPs configured on access ports.

Users can configure either port-based egress queuing and shaping or SAP-based egress queuing and shaping for SAPs configured on access ports or hybrid ports. The config system global-resource-profile qos port-scheduler-mode command allows the user to select the mode used for SAPs configured on all the ports of the node.

When port-scheduler-mode is enabled, eight egress queues are used per access port, and all the SAPs configured on the port share the eight egress queues for traffic sent out of that port. In this mode, SAPs configured on hybrid ports share the egress queues with network port traffic. Enabling port-scheduler-mode affects the behavior for all the SAPs configured on either access or hybrid ports. This means that port-based egress queues are mutually exclusive to the use of SAP-based egress queues. When port-scheduler-mode is enabled, per-port egress queues are defined using the access egress policies.

Additionally, the marking values used to mark traffic from different forwarding classes is defined by the remark policy in the access-egress policy. Per-SAP marking cannot be used when port-based queuing mode is used. A remarking policy can be defined for each access-egress policy, and remarking is disabled by default. Only remarking policies of the type dot1p, dot1p-lsp-exp-shared, dscp, or dot1p-dscp can be used with access-egress policies. The following is the marking behavior with different remark policy types.

  1. If the remark policy type is dot1p or dot1p-lsp-exp-shared, all traffic sent out of L2 SAPs and L3 SAPs configured on that port has the dot1p bits marked.
  2. If the remark policy type is dscp, all traffic sent out of L2 SAPs and L3 SAPs configured on that port has the IP DSCP bits marked (assuming L2 SAPs are carrying IP traffic).
  3. If the remark policy type is dot1p-dscp, all traffic sent out of L2 SAPs and L3 SAPs configured on that port has the IP DSCP bits (assuming L2 SAPs are carrying IP traffic) and dot1p bits marked.
Note:

  1. When port-scheduler-mode is disabled, per-SAP egress queues are available for use. Per-SAP egress queues are configured using service egress policies.
  2. On the 7210 SAS-R6 and 7210 SAS-R12, when port-based queuing mode is enabled, RVPLS SAPs use the port-based egress queues for both unicast and BUM traffic. All the SAPs, including RVPLS SAPs, share the eight egress queues created per port.

On the 7210 SAS-R6 and 7210 SAS-R12, access-egress QoS policies define egress queues and map FC flows to queues, if port-scheduler-mode is enabled. In port-scheduler-mode, the system allocates eight egress queues to access port egress by default. To define a basic access-egress QoS policy, the following are required:

  1. unique access egress QoS policy ID
  2. QoS policy scope of template or exclusive

The parameters that can be configured for a queue are described in Queue Parameters.

Optional service egress QoS policy elements include:

  1. specifying a remark policy that defines IEEE 802.1p priority value remarking based on FC

On the 7210 SAS-R6 and 7210 SAS-R12, when port-based queuing is used, the FC-to-queue map is fixed and the queue priority is determined by the queue number, where higher queue numbers have higher priority. The user can configure a queue as a strict queue and change the scheduling behavior for that queue. See Port-based Scheduling and Queuing on Access Ports for more information.

The following is a sample configuration output showing a default access-egress policy for the 7210 SAS-R6 and 7210 SAS-R12.

*A:sasr_dutb>config>qos>access-egress# info detail
----------------------------------------------
            description "Default Access egress QoS policy."
            no remarking
            remark 2
            scope template
            queue 1
                adaptation-rule cir closest pir closest
                rate cir 0 pir max
                queue-mgmt "default"
                queue-mode weighted
                weight 1
            exit
A:sasr_dutb>config>qos>access-egress# 

11.1.4. Access Egress QoS Policy Queue Override

The following QoS policy queue parameters can be overridden using the configure port ethernet access egress queue-override command:

  1. adaptation rule
    Specifies the criteria used to compute the operational PIR and CIR values for this queue (min, max, or closest)).
  2. percent rate
    Enables the configuration of queue PIR and CIR as a percentage of the egress port line rate rather that the values set by the rate parameter.
  3. queue management
    Associates a queue management policy with the queue.
  4. queue mode
    Sets strict or weighted mode for the queue.
  5. rate
    Defines the administrative PIR and CIR for the queue.
  6. weight
    Determines the proportion of available bandwidth that is given to this queue.

Refer to the “Port Ethernet QoS Commands” section in the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Interface Configuration Guide for command description details for the 7210 SAS-R6 and 7210 SAS-R12.

11.2. Basic Configurations

A basic access-egress QoS policy must conform to the following:

  1. have a unique access egress QoS policy ID
  2. have a description of the policy features

11.2.1. Modifying Access Egress QoS Queues

The following is a sample port-scheduler-mode policy configuration output for the 7210 SAS-R6 and 7210 SAS-R12.

*A:sasr_dutb>config>system>glob-res# info detail
----------------------------------------------
         qos
                no port-scheduler-mode
            exit
----------------------------------------------
*A:sasr_dutb>config>system>glob-res#

11.2.2. Applying Access Egress QoS Policies

Apply access egress policies to the following entities:

  1. Ethernet ports

A policy can be applied to the ports that are in access mode.

11.2.2.1. Ethernet Ports

Use the following syntax to apply an access-egress policy to an Ethernet port.

CLI Syntax:
config>port#
ethernet access egress
qos access-egress-policy-id
sap-qos-marking disable

The following is a sample port configuration output for 7210 SAS-R6 and 7210 SAS-R12.

*A:Dut-B>config>port# ethernet mode access 
*A:Dut-B>config>port# info detail 
----------------------------------------------
        shutdown
        description "10/100/Gig Ethernet SFP"
        ptp-hw-timestamp
        access
            egress
                pool default
                    slope-policy "default"
                exit
            exit
        exit
        network
            egress
                pool default
                    no amber-alarm-threshold
                    no red-alarm-threshold
                    resv-cbs default
                    slope-policy "default"
                exit
            exit
        exit
        ethernet                      
            mode access 
            no enable-table-classification
            access
                no accounting-policy
                no     collect-stats
                egress
                    qos 1
                exit
            exit
            encap-type null
            no mtu
            no mac
            crc-monitor
                no sd-threshold
                no sf-threshold
                no window-size
            exit
            symbol-monitor
                shutdown
                no sd-threshold
                no sf-threshold
                no window-size        
            exit
            down-when-looped
                shutdown
                no keep-alive
                no retry-timeout
                no use-broadcast-address
            exit
            no accounting-policy
            no collect-stats
            access
                egress
                exit
            exit
            dot1x
                port-control force-auth
                no radius-plcy
                no re-authentication
                re-auth-period 3600
                max-auth-req 2
                transmit-period 30
                quiet-period 60
                supplicant-timeout 30 
                server-timeout 30
                no tunneling
            exit
            lldp
                no tunnel-nearest-bridge-dest-mac
                dest-mac nearest-bridge
                    admin-status disabled
                    no notification
                    no tx-tlvs
                    no tunnel-nearest-bridge
                    no tx-mgmt-address
                    port-id-subtype tx-local
                exit
                dest-mac nearest-non-tpmr
                    admin-status disabled
                    no notification
                    no tx-tlvs
                    no tx-mgmt-address
                    port-id-subtype tx-local
                exit
                dest-mac nearest-customer
                    admin-status disabled
                    no notification
                    no tx-tlvs
                    no tx-mgmt-address
                    port-id-subtype tx-local
                exit
            exit
            no down-on-internal-error
            no hold-time
            eth-cfm
            exit
            speed 1000
            no enable-dei
            autonegotiate
            ssm
                shutdown
                code-type sdh
                no tx-dus
            exit
            no egress-rate
            no loopback
            no dot1q-etype
            no qinq-etype             
            no lacp-tunnel
            efm-oam
                shutdown
                mode active
                no accept-remote-loopback
                transmit-interval 10 multiplier 5
                no hold-time
                no ignore-efm-state
                grace-tx-enable
                discovery
                    advertise-capabilities
                        link-monitoring
                    exit
                exit
                peer-rdi-rx
                    critical-event local-port-action out-of-service
                    dying-gasp local-port-action out-of-service
                    event-notification local-port-action log-only
                    link-fault local-port-action out-of-service
                exit
                no tunneling
            exit                      
            no multicast-egress
            no multicast-ingress
            no port-clock
        exit
        ddm-events
----------------------------------------------

11.2.3. Editing QoS Policies

Existing policies and entries can be edited through the CLI or NMS. The changes are applied immediately to all services where the policy is used.

To prevent configuration errors perform the following.

  1. Copy the policy to a work area.
  2. Edit the policy.
  3. Over write the original policy.

11.2.4. Deleting QoS Policies

Every access Ethernet port is associated, by default, with the default access-egress policy (policy-id 1). You can replace the default policy with a customer-configured policy, but you cannot entirely remove the policy from the port configuration. When you remove a non-default access-egress policy, the association reverts to the default policy-id 1.

A QoS policy cannot be deleted until it is removed from all access ports where it is applied.

When a QoS policy is in use, the following error occurs.

*A:7210-SAS>config>qos# no access-egress 30
MINOR: CLI Could not remove Access egress policy "30" because it is in use.

11.2.5. Removing a Policy from the QoS Configuration

Use the following syntax to remove a policy from the QoS configuration.

CLI Syntax:
config>qos# no access-egress policy-id

The following example shows the command usage to remove a policy from the QoS configuration.

Example:
config>qos# no access-egress 100
config>qos# no access-egress 1010