13. Remark Policies

This chapter provides information to configure remark policies using the command line interface.

13.1. Overview of Remark Policies for 7210 SAS-K 2F1C2T

The remark policies configure the marking behavior for the system at the egress of access SAP or access uplink port. These policies allow the user to define the forwarding class to egress marking values and to use the available hardware resources efficiently. Based on the packet encapsulation used, the remark policy allows the user to define and associate service egress policies to service egress, and network QoS policies to access-uplink port. The following types of remark policies are available

  1. dot1p — used for service egress policy, and network QoS
  2. dscp — used for service egress and network QoS
  3. dot1p-dscp — used for service egress and network QoS

The type of the remark policy identifies the bits marked in the packet header. Each of these remark policy types can be associated with only appropriate QoS policies. Service entities as listed in Table 48.

Table 48:  Summary of Remark Policy and Attachment Points for 7210 SAS-K 2F1C2T  

Remark Policy Type

Qos Policy

Attachment Point

Packet Header Bits Marked

dot1p

Service Egress Policy

Access SAP egress

Dot1p bits and optionally the DEI bits, in the L2 header for service packets sent out of an Access SAP.

Network policy

Access-uplink Port

Dot1p bits and optionally the DEI bits, in the L2 header for service packets sent out of an access-uplink port (all packets sent out of all access-uplink SAPs are marked).

dscp

service egress policy

Access SAP egress

IP DSCP bits in the IP header (if present) for service packets sent out of an Access SAP.

Network policy

Access-uplink Port

IP DSCP bits in the IP header (if present) for service packets sent out of an Access-uplink port Marking is done for packets sent out of all the access-uplink SAPs configured on the access-uplink port.

dot1p-dscp

service egress policy

Access SAP egress

Dot1p bits and optionally the DEI bits, in the L2 header for service packets sent out of access SAP. In addition to the dot1p bits, the IP DSCP bits in the IP header (if present) are marked for service packets sent out of an Access SAP.

Network policy

Access-uplink Port

Dot1p bits and optionally the DEI bits, in the L2 header for service packets sent out of access uplink port. In addition to the dot1p bits, the IP DSCP bits in the IP header (if present) are marked for service packets sent out of an access-uplink port. Marking is done for packets sent out of all the access-uplink SAPs configured on the access-uplink port.

13.1.1. Configuration Guidelines for 7210 SAS-K 2F1C2T

  1. The 7210 SAS-K 2F1C2T marks the Dot1p configured in the marking policy, only if the node adds one or two tags or if it replaces existing tags. It does not touch the VLAN tag which represents customer payload (for example, the 7210 SAS-K 2F1C2T does not implement marking for packets when forwarding traffic out of dot1q range SAP or a null SAP).
  2. A limited number of unique remark policies are available to be shared among all the different types of remark policies. In other words, dot1p, dscp and dot1p-dscp remark policy types share the available resources and scaling one type of remark policy reduces the amount policies allowed for other type of remark policy.
  3. The user also has an option to preserve the Dot1p values in the received packet. See the CLI description for the config>service>sap>egress>dot1p-inner and config>service>sap>egress>dot1p-outer commands in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Services Guide.

13.2. Overview of Remark Policies for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C

The remark policies are used to configure the marking behavior for the system at the egress of access SAPs, network port, hybrid ports, and access uplink ports. These policies allow the user to define the forwarding class to egress marking values and allow them to use the available hardware resources efficiently. Based on the packet encapsulation used, the remark policy allows the user to define and associate service egress policies to access SAP egress, and network QoS policies applied to network ports, hybrid ports, and access-uplink ports. The following type of remark policies are available:

  1. dot1p — used for service egress and network QoS policies
  2. dscp — used for service egress and network QoS policies
  3. dot1p-dscp — used for service egress and network QoS policies
  4. lsp-exp — used for network QoS policies (only network ports and hybrid ports)
  5. dot1p-lsp-exp — used for network QoS policies (only network ports and hybrid ports)
  6. dot1p-lsp-exp-dscp — used for network QoS policies (only network ports and hybrid ports)
  7. dscp-lsp-exp — used for network QoS policies (only network ports and hybrid ports)

The type of the remark policy identifies the bits marked in the packet header. Each of these remark policy types can be associated with only appropriate QoS policies. Service entities as listed in Table 49.

Table 49:  Summary of Remark Policy and Attachment Points for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C 

Remark Policy Type

QoS Policy

Attachment Point

Packet Header Bits Marked

dot1p

Service egress policy

Access SAP egress (applicable to SAPs configured on access ports or hybrid ports)

Dot1p bits, and optionally the DEI bits, in the outermost Ethernet header for service packets sent out of an Access SAP

Network policy

Network port

Hybrid port

Dot1p bits, and optionally the DEI bits, in the outermost Ethernet header for all MPLS and IP packets sent out of a network IP interface configured on a network port or hybrid port

Network policy

Access-uplink port

Dot1p bits, and optionally the DEI bits, in the Ethernet header for service packets sent out of an access-uplink port (all packets sent out of all access-uplink SAPs are marked)

dscp

Service egress policy

Access SAP egress (applicable to SAPs configured on access ports or hybrid ports)

IP DSCP bits in the IP header (if present) for service packets sent out of an Access SAP

Network policy

Network port

Hybrid port

IP DSCP bits in the IP header (if present) for all IP packets sent out of a network IP interface configured on a network port or hybrid port

Access-uplink port

IP DSCP bits in the IP header (if present) for service packets sent out of an Access-uplink port. Marking is done for packets sent out of all access-uplink SAPs configured on the access-uplink port.

dot1p-dscp

Service egress policy

Access SAP egress (applicable to SAPs configured on access ports or hybrid ports)

Dot1p bits, and optionally the DEI bits, in the L2 header for service packets sent out of access SAP. In addition to the dot1p bits, the IP DSCP bits in the IP header (if present) are marked for service packets sent out of an Access SAP.

Network policy

Network port

Hybrid port

Dot1p bits, and optionally the DEI bits, in the outermost Ethernet header for all MPLS and IP packets sent out of a network IP interface configured on a network port or hybrid port

IP DSCP bits in the IP header (if present) for all IP packets sent out of a network port IP interface configured on a network port or hybrid port

Access-uplink port

Dot1p bits, and optionally the DEI bits, in the Ethernet header for service packets sent out of access uplink port. In addition to the dot1p bits, the IP DSCP bits in the IP header (if present) are marked for service packets sent out of an access-uplink port. Marking is done for packets sent out of all the access-uplink SAPs configured on the access-uplink port.

lsp-exp

Network policy

Network port

Hybrid port

MPLS EXP bits for the outermost MPLS labels for all MPLS packets sent out of a network IP interface configured on a network port or hybrid port

dot1p-lsp-exp

Network policy

Network port

Hybrid port

Dot1p bits, and optionally the DEI bits, in the outermost Ethernet header for all MPLS and IP packets sent out of a network port

MPLS EXP bits for the outermost MPLS labels for all MPLS packets sent out of a network IP interface configured on a network port or hybrid port

dot1p-lsp-exp-dscp

Network policy

Network port

Hybrid port

Dot1p bits, and optionally the DEI bits, in the outermost Ethernet header for all MPLS and IP packets sent out of a network IP interface configured on a network port or hybrid port

IP DSCP for all IP packets sent out of a network IP interface configured on a network port or hybrid port

MPLS EXP bits for the outermost MPLS labels for all MPLS packets sent out of a network IP interface configured on a network port or hybrid port

dscp-lsp-exp

Network Policy

Network port

Hybrid port

IP DSCP for all IP packets sent out of a network IP interface configured on a network port or hybrid port

MPLS EXP bits for the outermost MPLS labels for all MPLS packets sent out of a network IP interface configured on a network port or hybrid port

13.2.1. Configuration Guidelines for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C

  1. The 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C mark the dot1p configured in the marking policy only if the node adds one or two tags or if it replaces existing tags. The platforms do not modify the VLAN tag which represents customer payload; for example, the platforms do not mark the packets when forwarding traffic out of dot1q range SAP or a null SAP.
  2. A limited number of unique remark policies are available to be shared among all the different types of remark policies. In other words, dot1p, dscp, dot1p-dscp, lsp-exp, dot1p-lsp-exp, dot1p-dscp-lsp-exp remark policy types share the available resources and scaling one type of remark policy reduces the amount policies allowed for other type of remark policy.
  1. The user also has an option to preserve the dot1p values in the received packet. Refer to the CLI description for the config>service>sap>egress>dot1p-inner and config>service>sap>egress>dot1p-outer commands in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Services Guide.
  2. When marking is enabled without explicitly associating the desired remark policy, then the default remark policy is used for marking packets.
  3. Any remark-policy that specifies MPLS lsp-exp values cannot be associated with access-uplink port. The association is blocked by the system.
  4. MPLS packets sent out of a network IP interface configured on a network port or hybrid port can be marked with MPLS lsp-exp values and dot1p, DEI values if both are configured.
  5. IP packets sent out of a network IP interface configured on a network port or hybrid port can be marked with IP DSCP values and dot1p, DEI values if both are configured.
  6. The dot1p bits of the packets sent out of a network IP interface configured on a network port or hybrid port are always marked by default, even when remarking is disabled.

13.3. Basic Configurations

A basic remark policy must confirm to the following:

  1. Each remark policy must have a unique policy ID.
  2. The remark policy type must be specified.
  3. The forwarding class to egress marking values must be specified.

13.3.1. Creating a Remark Policy

To create a new remark policy, define the following:

  1. A remark policy name and type is optional and by default it is “dot1p”.
  2. Provide a brief description of the policy features.
  3. Specify the forwarding class to egress marking values.

Use the following syntax to configure a remark policy.

----------------------------------------------
*A:7210SAS>config>qos>remark# info detail (applicable to SAS-K devices)
----------------------------------------------
            no description
                fc af
                    de-mark-outer
                    dot1p-inner 4
                    dot1p-outer in-profile 2 out-profile 3
                exit
                fc be
                    de-mark-outer force 0
                    dot1p-inner in-profile 4 out-profile 2
                    dot1p-outer 4
                exit
                fc ef
                    no de-mark-outer
                    dot1p-inner in-profile 4 out-profile 5
                    dot1p-outer in-profile 3 out-profile 1
                exit
                fc h1
                    de-mark-outer
                    dot1p-inner 1
                    dot1p-outer in-profile 1 out-profile 2
                exit
                fc h2                 
                    de-mark-outer
                    dot1p-inner in-profile 4 out-profile 4
                    dot1p-outer in-profile 6 out-profile 3
                exit
                fc l1
                    de-mark-outer force 1
                    dot1p-inner in-profile 2 out-profile 6
                    dot1p-outer 4
                exit
                fc l2
                    de-mark-outer
                    dot1p-inner 7
                    dot1p-outer 3
                exit
                fc nc
                    no de-mark-outer
                    dot1p-inner in-profile 2 out-profile 4
                    dot1p-outer in-profile 5 out-profile 6
                exit
*A:7210SAS>config>qos>remark#
 

13.3.2. 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 applicable.

To prevent configuration errors perform the following:

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