4.4. Network QoS Policy Command Reference

This command associates a text string with a configuration context to help identify the context in the configuration file.

The no form of this command removes any description string from the context.

This command creates or edits a QoS network policy. The network policy defines the treatment that GRE, IP, or MPLS packets receive as they ingress and egress the network port.

The network-policy-type keyword defines the type of network policy that will be created. The ip-interface type network policy is assigned to router interfaces. The ring type network policy is assigned to bridging domain ports on a ring adapter card.

Using the network-policy-type keyword is optional. If network-policy-type is not used, a default ip-interface policy is created.

Note: With the addition of ring ports on the 2-port 10GigE (Ethernet) Adapter card, the network-policy-type keyword allows the creation of network QoS policies for IP interfaces in the IP domain (that is, ingress and egress network ports) and for ring policies in the bridging domain.

Network policy-id 1 exists as the default policy that is applied to all network interfaces by default. Network policy-id 1 cannot be modified or deleted, and is reapplied when the network-policy-type default keyword is used.

If a new network policy is created for the IP domain (for instance, policy-id 2), only the default action and egress forwarding class parameters are identical to the default policy-id 1. A new network policy does not contain the default DSCP-to-FC or MPLS EXP-to-FC mapping. To create a new network policy that includes the default ingress DSCP-to-FC or MPLS EXP-to-FC mapping, the default network policy-id 1 can be copied (using the copy command). You can modify parameters or use the no modifier to remove an object from the configuration. Similarly, the copy and modify process is used to create a new ring type network policy, where the dot1p-to-queue and profile state mapping are available for use in the new policy.

Any changes made to an existing policy, using any of the sub-commands, will be applied immediately to all network interfaces where this policy is applied. For this reason, when many changes are required on a policy, it is highly recommended that the policy be copied to a work area policy-id. That work-in-progress policy can be modified until complete and then written over the original policy-id. Use the config qos copy command to maintain policies in this manner.

The no form of this command deletes the network policy. A policy cannot be deleted until it is removed from all services where it is applied. The default network policy policy-id 1 cannot be deleted.

This command configures the network policy scope as exclusive or template. The policy’s scope cannot be changed if the policy is applied to an interface.

The no form of this command sets the scope of the policy to the default of template.

This command is used to enter the CLI mode that creates or edits egress policy entries that specify the forwarding class to be instantiated when this policy is applied to the network port.

The forwarding class and profile state mapping to in-profile and out-of-profile DSCP and MPLS EXP bits mapping for all labeled packets are also defined under this node.

For MPLS tunnels, if network egress Ethernet ports are used, dot1p bit marking can be enabled in conjunction with EXP bit marking. In this case, the tunnel and pseudowire EXP bits do not have to be the same as the dot1p bits.

For GRE and IP tunnels, dot1p marking and pseudowire EXP marking can be enabled, and DSCP marking can also be enabled.

The service packets are transported over an MPLS LSP, GRE tunnel, or IP tunnel.

All out-of-profile service packets are marked with the corresponding DSCP (for GRE or IP packets) or EXP (for MPLS packets) bit value at network egress. All in-profile service packets are marked with the corresponding in-profile DSCP or EXP bit value based on the forwarding class they belong to.

This command specifies the forwarding class name. The fc fc-name represents a CLI parent node that contains sub-commands or parameters describing the marking criteria for that forwarding class. The fc command overrides the default parameters for that forwarding class defined in the network default policy-id 1.

The no form of this command reverts to the defined parameters in the default network policy policy-id 1. If the fc-name is removed from the default network policy policy-id 1, that forwarding class reverts to the factory defaults.

This command is used to enter the CLI mode that creates or edits policy entries that specify the DSCP to forwarding class mapping for all GRE or IP packets and define the MPLS EXP bits to forwarding class mapping for all labeled packets.

When pre-marked GRE, IP, or MPLS packets ingress on a network port, they get a per-hop behavior (that is, the QoS treatment through the 7705 SAR based on the mapping defined under the current node).

This command defines or edits the default action to be taken for packets that have  undefined DSCP or MPLS EXP bits set. The default-action command specifies the forwarding class to which such packets are assigned.

Multiple default-action commands will overwrite each previous default-action command.

This command creates a mapping between the DSCP of the network ingress traffic and the forwarding class for GRE or IP packets.

Ingress traffic that matches the specified DSCP is assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all 64 DSCP values with the forwarding class. For undefined code points, packets are assigned to the forwarding class specified under the default-action command.

The no form of this command removes the DSCP-to-FC association. The default-action then applies to that code point value.

This command is used to override tunnel QoS mapping on all ingress network IP interfaces that the network-policy-id is associated with. The command may be defined at any time after the network QoS policy has been created.

For IP traffic riding over MPLS or GRE tunnels that will be routed to the base router, a VRPN interface, or an IES interface at the tunnel termination point (the eLER), this command makes it possible for the 7705 SAR to ignore the EXP/DSCP bits in the tunnel header when the packets arrive at the eLER. This is useful when the mapping for the tunnel QoS marking does not completely reflect the required QoS handling for the IP routed packet. When the command is enabled on an ingress network IP interface, the IP interface will ignore the tunnel’s QoS mapping and will derive the internal forwarding class and associated profile state based on the DSCP values of the IP header ToS field. This command applies only on the eLER where the tunnel or service is terminated and the next header in the packet is IP.

The default state is to not enforce customer DSCP at the tunnel-termination point, IP-routed QoS override within the network QoS policy.

The no form of the command removes use of customer DSCP at tunnel-termination, IP-routed QoS override from the network QoS policy and all ingress network IP interfaces associated with the policy.

This command creates a mapping between the LSP EXP bits of the network ingress traffic and the forwarding class.

Ingress traffic that matches the specified LSP EXP bits will be assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all of the eight LSP EXP bit values with the forwarding class. For undefined values, packets are assigned to the forwarding class specified under the default-action command.

The no form of this command removes the association of the LSP EXP bit value with the forwarding class. The default-action then applies to that LSP EXP bit pattern.

This command is used to enter the CLI context that creates or edits policy entries that specify the dot1p-to-queue mapping for all packets.

This command defines or edits the default action to be taken for packets that have undefined dot1p bits set. The default-action command specifies the queue to which received packets are assigned as well as their profile state.

Multiple default-action commands will overwrite each previous default-action command.

This command creates a mapping between the dot1p bits of the ingress traffic and the queue and profile state. A maximum of eight dot1p entries are allowed on a single policy.

The no form of the command removes the association of the dot1p bit value with the queue and profile state. The default-action then applies to that dot1p bit pattern.

This command explicitly defines the egress dot1p priority bits values for the forwarding class.

Note: When a single dot1p-priority is specified, it is applied to both in-profile and out-of-profile packets. The other forms of the command described below (dot1p-in-profile and dot1p-out-profile) allow different dot1p values for in-profile or out-of-profile packets to be specified.

The no form of the command sets the dot1p priority bits value to 0.

This command specifies dot1p in-profile mappings.

The no form of the command reverts to the factory default in-profile dot1p-priority setting for policy-id 1.

This Command Specifies Dot1p Out-profile Mappings.

The No Form Of The Command Reverts To The Factory Default Out-profile Dot1p-priority Setting For Policy-id 1.

This command specifies the in-profile DSCP name for the forwarding class. The corresponding DSCP value is used for all in-profile GRE or IP packets that require marking at egress on this forwarding class.

IP traffic from network interfaces is always trusted. There is no re-marking performed on network egress for global routing table (GRT) forwarded IP traffic (with the exception of GRE and IPSec tunnels).

When multiple DSCP names are associated with the forwarding class at network egress, the last name entered overwrites the previous value.

The no form of this command reverts to the factory default in-profile dscp-name setting for policy-id 1.

This command specifies the out-of-profile DSCP name for the forwarding class. The corresponding DSCP value is for all out-of-profile GRE or IP packets that require marking at egress on this forwarding class.

IP traffic from network interfaces is always trusted. There is no re-marking performed on network egress for global routing table (GRT) forwarded IP traffic (with the exception of GRE and IPSec tunnels).

When multiple DSCP names are associated with the forwarding class at network egress, the last name entered overwrites the previous value.

The no form of this command reverts to the factory default out-profile dscp-name setting for policy-id 1.

This command specifies the in-profile LSP EXP value for the forwarding class. The EXP value will be used for all in-profile LSP labeled packets requiring marking at egress on this forwarding class.

When multiple EXP values are associated with the forwarding class at network egress, the last name entered overwrites the previous value.

The no form of this command reverts to the factory default in-profile EXP setting for policy-id 1.

This command specifies the out-of-profile LSP EXP value for the forwarding class. The EXP value will be used for all out-of-profile LSP labeled packets requiring marking at egress on this forwarding class queue.

When multiple EXP values are associated with the forwarding class at network egress, the last name entered overwrites the previous value.

The no form of this command reverts to the factory default out-of-profile EXP setting for policy-id 1.

This command enables the context to configure DSCP or dot1p re-marking for self-generated traffic (SGT).

This set of commands configures DSCP marking for self-generated IP traffic or dot1p marking for self-generated non-IP traffic (specifically, IS-IS and ARP traffic).

When an IP or Layer 3 application is configured using the dscp-app-name parameter, the specified DSCP name or DSCP value is used for all packets generated by this application within the router instance in which it is configured. The value set in this command sets the DSCP value in the egress IP header. The egress QoS policy will not overwrite this value.

When a Layer 2 application is configured using the dot1p-app-name parameter, the specified dot1p priority value is used for all packets generated by this application within the router instance in which it is configured.

Only one name or value can be configured per application. If multiple entries are configured, a subsequent entry overrides the previously configured entry.

The fc-queue option redirects SGT applications to egress data queues rather than the default control queue by assigning them to a forwarding class. If this option is configured, the profile state must be set. All packets that are assigned to this forwarding class will be considered in-profile or out-of-profile based on the configuration. In case of congestion, the in-profile packets are preferentially queued over the out-of-profile packets.

If the fc-queue option is used with the dscp-app-name application, any configuration done using the sgt-qos>dscp command is ignored for packets generated by this application, as illustrated in the following examples:

sgt-qos>application telnet dscp cp1

sgt-qos>dscp cp1 fc af

sgt-qos>application ftp dscp cp1 fc-queue be profile out

sgt-qos>dscp cp1 fc af

In the first example, all packets generated by the Telnet application use DSCP CP1 and map to FC AF as configured in the dscp command. The dot1p bits of the outgoing packets are marked from the value that FC AF points to in the egress QoS policy.

In the second example, all packets generated by the FTP application use DSCP CP1 and map to FC BE as dictated by the fc-queue redirection. The dot1p bits of the outgoing packets are marked from the value that FC BE points to in the egress QoS policy. Because redirection is configured, the mapping configured with the dscp command is ignored.

Note: The above behavior applies to all SGT IP applications with the exception of VRRP, where the dot1p value is always set to 7, regardless of the value in the FC egress QoS policy.

If the fc-queue option is used with the dot1p-app-name application, the dot1p bits of the outgoing packets are marked with the value set with the dot1p-priority parameter, regardless of the value in the FC egress queue policy.

The no form of this command resets the DSCP or dot1p value for the application to its default value and resets the application to use the egress control queue.

This command creates a mapping between the DSCP of the self-generated traffic and the forwarding class. The forwarding class dot1p network QoS policy mapping is used to mark the dot1p bits of the Layer 3 or IP application. For example, configuring the dscp-name parameter as be and the fc-name parameter as l1 results in marking the dot1p bits of the outgoing Ethernet frame, which is transporting self-generated IP traffic with DSCP bits set to BE, to the value that FC L1 points to in the network QoS policy (as configured in the config>qos>network>egress>fc context).

Note: The dot1p class of service may not apply to all IP traffic and is dependent on the egress port encapsulation type.

Based on this configured FC, the network QoS policy for the egress forwarding complex sets the IEEE 802.1 dot1p bits.

Multiple commands can be entered to associate some or all of the 64 DSCP values with the forwarding class. For undefined code points, packets are assigned to the default forwarding class for the DSCP value. This value can be seen in the show>router>sgt-qos>dscp-map output under the Default FC Value column.

The no form of the command resets the DSCP value to its default forwarding class.

Note: If the fc-queue option is configured in the sgt-qos>application dscp-app-name command, the mapping created with this command is ignored for packets generated by the applications that are configured with the option.

Table 32 lists the default FC value for each DSCP value.