This chapter provides information to configure remark policies using the CLI.
The remark policies are used to configure the marking behavior for the system at the egress of access SAP or access uplink port, network ports, hybrid ports, ports and network IP interfaces on network ports or hybrid 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 appropriate policies to service egress, and network QoS policies. The following remark policies are available:
The type of the remark policy typically identifies the bits marked in the packet header, with some exceptions, as noted in Table 48. Each of these remark policy types can be associated with only appropriate QoS policies and service entities, as listed in Table 48.
Remark Policy Type | Qos Policy | Attachment Point | Packet Header Bits Marked |
dot1p | SAP-egress policy | Service/SAP egress | Dot1p bits in the L2 Ethernet header for service packets sent out of a SAP egress |
Access-egress policy | Access port | Dot1p bits in L2 Ethernet header for service packets sent out of all access SAPs configured on access ports 1 | |
Network policy (port type) | Network port and hybrid port | Dot1p bits in the L2 Ethernet header for IP packets sent out of network port and hybrid port | |
dscp | Access egress policy | Access port | IP DSCP bits in the IP header for service packets sent out of access SAPs configured on access ports 1 |
Network policy (port type) | Network port and hybrid port | IP DSCP bits in the IP header for IP packets sent out of network port and hybrid port 1 | |
lsp-exp | Network policy (IP-interface type) | Network IP interface | EXP bits in the MPLS header for MPLS packets sent out of IP interface configured on network port and hybrid port |
dot1p-lsp-exp-shared | Access egress policy | Access port | Dot1p bits in L2 Ethernet header for service packets sent out of access SAPs configured on access ports 1 |
Network policy (IP-interface type or port type) | Network IP interface or network port | EXP bits in the MPLS header for MPLS packets sent out of IP interface configured on network port and hybrid port Dot1p bits in the L2 Ethernet header for MPLS packets sent out of network port and hybrid port | |
SAP egress policy | Service/SAP egress | Dot1p bits in the L2 Ethernet header for service packets sent out of a SAP egress | |
dot1p-dscp | Access egress policy | Access port | Dot1p bits in L2 Ethernet header and IP DSCP bits in the IP header for service packets sent out of access SAPs configured on access ports 1 |
Network policy (port type) | Network port and hybrid port | Dot1p bits in the L2 Ethernet header for MPLS and IP packets and IP DSCP bits in the IP header for IP packets sent out of network port and hybrid port 1 |
Note:
For access port and access SAP marking functionality (SAP-based and port-based), the 7210 SAS-R6 and 7210 SAS-R12 support SAP-based egress marking and port-based egress marking on only access ports when using access SAP-based egress queuing. Users have an option to use either SAP-based marking or port-based marking. In SAP-based marking, the remark policy defined in the SAP egress policy associated with each SAP is used to mark the packets egressing out of the SAP, if marking is enabled. In port-based marking, the remark policy defined in the access-egress policy associated with the access port determines the marking values to use for all the SAPs defined on that port. See Access Egress QoS Policies for more information.
The 7210 SAS-R6 and 7210 SAS-R12 support only access port-based marking when port-based egress queues are configured. See Access Egress QoS Policies for more information.
A basic remark policy must conform to the following.
To create a new remark policy, define the following:
Use the following CLI syntax to configure a remark policy.
The following is a sample remark policy configuration output.
Existing policies and entries can be edited using the CLI or NMS. The changes are applied immediately to all services where the policy is applicable.
To prevent configuration errors, perform the following.