6.6. Network QoS Policy Command Reference

This command creates or edits a QoS network policy. The network policy defines the treatment packets receive as they ingress and egress the network port and network IP interface in network mode of operation.

The QoS network policy consists of an ingress and egress component. The ingress component of the policy defines how packet header priority bits are mapped to internal forwarding class and profile state. The forwarding class and profile state define the Per Hop Behavior (PHB) or the QoS treatment through the 7210 SAS. The mapping on each network interface defaults to the mappings defined in the default network QoS policy until an explicit policy is defined for the network interface. It also defines the rate-limiting parameters for the traffic mapped to each forwarding classes. Traffic mapped to each forwarding class can be rate limited using separate meters for each uni-cast and multipoint traffic.

The egress component of the network QoS policy defines forwarding class and profile state to packet header priority bit values for traffic to be transmitted into the core network. If the egressing packet originated on an ingress SAP, the parameter is always enabled for the network port, the egress QoS policy also defines the dot1p bit marking based on the forwarding class and the profile state.

In network mode, network policy ID 2 exists as the default policy that is applied to all IP interface by default. The network policy ID 2 cannot be modified or deleted. It defines the default LSP EXP-to-FC mapping and default meters for unicast traffic and optional multipoint meters for BUM traffic on the, ingress MPLS packets. For the egress, it defines eight forwarding classes which defines LSP EXP values and the packet marking behavior.

In network mode, Network policy-id 1 exists as the default policy that is applied to all network ports by default. This default policy cannot be modified or deleted. It defined the default DSCP-to-FC mapping and default unicast meters for ingress IP traffic. For the egress, if defines the forwarding class to dot1p and DSCP values and the packet marking criteria.

In network mode, If a new network policy is created (for instance, policy ID 3), only the default action, default meters for unicast and multipoint traffic and egress forwarding class parameters are identical to the default policy. A new network policy does not contain the default LSP EXP-to-FC mapping for network QoS policy of type ip-interface or the DSCP-to-FC mapping (for network QoS policy of type port). The default network policy can be copied (use the copy command) to create a new network policy that includes the default ingress LSP EXP or DSCP to FC mapping (as appropriate). You can modify parameters or use the no modifier to remove an object from the configuration.

Any changes made to an existing policy, using any of the sub-commands, will be applied immediately to all network ports 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 entities where it is applied. The default network policy policy-id 1 cannot be deleted.

This command enables the context to create a new mpls-lsp-exp-profile-map policy. The policy specifies the profile to assign to the packet based on the MPLS LSP EXP bits value matched in the MPLS packet received on a network IP interface.

The assigned profile is available for use by the meter or policer associated with FC in the network policy attached to this IP interface.

The policy is associated with network policy attached to a network IP interface.

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

Ingress traffic that matches the specified LSP EXP bits will be assigned the corresponding profile.

Multiple commands can be entered to define the association of some or all eight LSP EXP bit values to the profile. For undefined values, packets are assigned the profile value out.

The no form of this command removes the association of the LSP EXP bit value to the profile value. The default profile value out then applies to that LSP EXP bit pattern.

This command enables the context to associate the mpls-lsp-exp-profile-map policy for use with LDP LSPs. When color-aware metering is in use for the IP interface, the policy specified here provides the profile to assign to the MPLS packets received on any of the network IP interface in use in the system. The MPLS EXP bits in the received packet are matched for assigning the profile.

On system boot-up, the policy ID is set to the default policy ID 1. The user can modify it to use the policy of their choice.

For LDP LSP traffic and segment routing (SR), the system always uses the global mpls-lsp-exp-profile-map policy. For RSVP LSP traffic, system uses the mpls-lsp-exp-profile-map policy associated with the network policy. For consistent QoS treatment, it is highly recommended to use a single mpls-lsp-exp-profile-map policy for all network policies when the FRR facility or a mix of LDP, SR, and RSVP is in use, or when the PHP is enabled.

The no form of this command reverts the policy to the default.

This command enables the context to specify the mpls-lsp-exp-profile-map policy to use for assigning profile values for packets received on this IP interface.

Note: For LDP LSP traffic, the system uses the global mpls-lsp-exp-profile-map policy. For RSVP LSP traffic, the system uses the mpls-lsp-exp-profile-map policy that is associated with the network policy. For consistent QoS treatment, Nokia highly recommends using a single mpls-lsp-exp-profile-map policy for all the network policies when FRR facility is in use.

The no form of this command removes the policy.

This command creates or edits a QoS network policy. The network policy defines the treatment packets receive as they ingress and egress the access-uplink port. Only network-policy-type port is supported in access-uplink mode.

The QoS network policy consists of an ingress and egress component. The ingress component of the policy defines how dot1p bits are mapped to internal forwarding class and profile state. The forwarding class and profile state define the Per Hop Behavior (PHB) or the QoS treatment through the 7210 SAS. The mapping on each access-uplink port defaults to the mappings defined in the default network QoS policy until an explicit policy is defined for the port. It also defines the rate-limiting parameters for the traffic mapped to each forwarding classes. Traffic mapped to each forwarding class can be rate limited using separate meters for each uni-cast and multipoint traffic.

The egress component of the network QoS policy defines the queuing parameters associated with each forwarding class. There are eight queues per port on the egress. Each of the forwarding classes is associated with a queue on each access-uplink port. This queue gets all the parameters defined within the default network QoS policy 1 until an explicit policy is defined for the network interface access-uplink port. If the egressing packet originated on an ingress SAP, the parameter is always enabled for the access-uplink port, the egress QoS policy also defines the dot1p bit marking based on the forwarding class and the profile state.

The network policy ID 1 cannot be modified or deleted. It defines the default dot1p-to-FC mapping and default meters for unicast traffic and optional multipoint meters for the ingress. For the egress, it defines eight forwarding classes which represent individual queues and the packet marking criteria.

If a new network policy is created (for instance, policy ID 2), only the default action and default meters for unicast and multipoint traffic and egress forwarding class parameters are identical to the default policy. A new network policy does not contain the default dot1p-to-FC mapping for network QoS policy of type port. The default network policy can be copied using the copy command to create a new network policy that includes the default ingress dot1p or DSCP to FC mapping (as appropriate).

You can modify parameters or use the no modifier to remove an object from the configuration.

Any changes made to an existing policy, using any of the sub-commands, will be applied immediately to all access-uplink ports 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 entities where it is applied. The default network policy ID1 cannot be deleted.

Note: The config>qos>network>egress context is only supported on the 7210 SAS-M (access-uplink and network mode) and 7210 SAS-T (access-uplink mode).

This command creates a class instance of the forwarding class. Once the fc-name is created, classification actions can be applied and it can be used in match classification criteria.

The no form of this command removes all the explicit meter mappings for fc-name forwarding types. The meter mappings revert to the default meters for fc-name.

This command creates or edits policy entries that specify the lsp-exp-value to forwarding class mapping for all MPLS packets.

When pre-marked packets ingress on a network port, the QoS treatment through the 7210 SAS-based on the mapping defined under the current node.

This command defines or edits the default action to be taken for packets that have an undefined LSP EXP (only when devices is operating in network mode) or dot1p bits (for 7210 SAS-M and 7210 SAS-T in access-uplink mode) 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 explicitly sets the forwarding class or enqueuing priorityand profile of the packet when a packet is marked with a dot1p-priority specified. Adding a dot1p rule on the policy forces packets that match the dot1p-priority specified to overridebe assigned to the forwarding class and enqueuing priorityand profile of the packet based on the parameters included in the dot1p rule.

The dot1p-priority is derived from the most significant three bits in the IEEE 802.1Q or IEEE 802.1P header. The three dot1p bits define 8 Class-of-Service (CoS) values commonly used to map packets to per-hop Quality-of-Service (QoS) behavior.

The no form of this command removes the explicit dot1p classification rule from the policy. Removing the rule on the policy immediately removes the rule on all ingress SAPsports using the policy.

This command enables the context to configure an ingress Network QoS policy meter. The meter command allows the creation of multipoint meters. Only multipoint meters can receive ingress packets that need to be sent to multiple destinations

Multipoint meters are for traffic bound to multiple destinations. Within non-multipoint services, such as Epipe services, all traffic is considered unicast due to the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service will not be mapped to a multipoint service meter.

The no form of this command removes the meter-id from the Network ingress QoS policy and from any existing ports using the policy. If any forwarding class forwarding types are mapped to the meter, they revert to their default meters. When a meter is removed, any pending accounting information for each port meter created due to the definition of the meter in the policy is discarded.

This command overrides the default unicast forwarding type meter mapping for fc fc-name. The specified meter-id must exist within the policy as a non-multipoint meter before the mapping can be made. Once the forwarding class mapping is executed, all unicast traffic on a port using this policy is forwarded using the meter-id.

The no form of this command sets the unicast (point-to-point) meter-id back to the default meter for the forwarding class (meter 1).

This command overrides the default multicast forwarding type meter mapping for fc fc-name. The specified meter-id must exist within the policy as a multipoint meter before the mapping can be made. Once the forwarding class mapping is executed, all multicast traffic on a port using this policy is forwarded using the meter-id.

This command can be used with a network policy of type ip-interface, and on a network port when multicast is enabled.

The no form of this command reverts the multicast forwarding type meter-id to the default meter for the forwarding class.

This command creates a mapping between the DiffServ Code Point (DSCP) of the network ingress traffic and the forwarding class.

Ingress traffic that matches the specified DSCP will be assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all sixty-four DiffServ code points to 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 DiffServ code point to forwarding class association. The default-action then applies to that code point value.

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 eight LSP EXP bit values to 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 to the forwarding class. The default-action then applies to that LSP EXP bit pattern.

This command defines the method used by the system to derive the operational CIR and PIR rates when the meter is provisioned in hardware. For the cir and pir parameters, the system attempts to find the best operational rate depending on the defined constraint.

Note: The adaptation rule configured for the rate influences the step-size used for the burst. See Adaptation Rule for Meters for information.

The no form of this command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for cir and pir apply.

This command provides a mechanism to override the default CBS for the meter. The committed burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the CBS value then the packets are marked as in-profile by the meter to indicate that the traffic is complying meter configured parameters.

Note: The adaptation rule configured for the rate influences the step-size used for the burst. See Adaptation Rule for Meters for information.

The no form of this command reverts the size to the default value.

This command provides a mechanism to override the default MBS for the meter. The maximum burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the MBS value then the packets are marked as in-profile by the meter to indicate that the traffic is complying meter configured parameters.

Note: The adaptation rule configured for the rate influences the step-size used for the burst. See Adaptation Rule for Meters for information.

The no form of this command reverts the size to the default value.

This command defines the mode of the meter. The mode can be configured as Two Rate Three Color Marker (trTCM) or Single Rate Three Color Marker (srTCM). The mode command can be executed at any time.

The no form of this command reverts to the default.

This command defines the administrative PIR and CIR parameters for the meter.

The rate command can be executed at any time, altering the PIR and CIR rates for all meters created through the association of the Network QoS policy with the meter-id.

The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir-rate value.

The no form of this command reverts all meter instances created with this meter-id to the default PIR (max) and CIR (0) parameters.

Note: The value of rates are represented as 1000 kilobits per second and bursts are represented as 1024 kilobits per second.

This command creates or edits egress policy entries that specify the forwarding class map to be instantiated when this policy is applied to the network IP interface, or access-uplink port

The forwarding class and profile state mapping to appropriate marking values for all packets are defined in this context.

In network mode of operation, the system supports use of forwarding class mapping to EXP bits for IP interface, forwarding class mapping to DSCP and dot1p bits for network ports. In access-uplink mode of operation it allows the user to specify the FC mapping to dot1p bits for access-uplink ports.

This command specifies the forwarding class name. The forwarding class name represents an egress queue. The fc fc-name represents a CLI parent node that contains sub-commands or parameters describing the marking criteria of packets flowing through it. The fc command overrides the default parameters for that forwarding class to the values defined in the network default policy. Appropriate default parameters are picked up based on whether the network-policy-type is port or ip-interface.

The no form of this command removes the forwarding class LSP EXP/dot1p/DSCP map associated with this fc, as appropriate. The forwarding class reverts to the defined parameters in the default network policy. If the fc-name is removed from the network policy that forwarding class reverts to the factory defaults.

This command explicitly defines the marking of the DEI bit for fc fc-name according to the in and out of profile status of the packet (fc-name may be used to identify the dot1p-value).

If no de-value is present, the default values are used for the marking of the DEI bit, as defined in the IEEE 802.1ad-2005 standard. For example 0 for in-profile packets, 1 for out-of-profile ones.

If the de-value is specifically mentioned in the command line it means this value is to be used for all the packets of this forwarding class regardless of their in/out of profile status.

This command explicitly defines the egress IEEE 802.1P (dot1p) bits marking for fc-name. When the marking is set, all packets of fc-name that have either an IEEE 802.1Q or IEEE 802.1P encapsulation use the explicitly defined dot1p-value. If the egress packets for fc-name are not IEEE 802.1Q or IEEE 802.1P encapsulated, the dot1p command has no effect.

DEI marking can be enabled using the de-mark command along with this command for the command to take effect. When de-mark command is configured along with this command, then the DEI bit is marked in the packet to indicate the profile of the packet. The DEI bit is marked to 0 to indicate in-profile/green packet and 1 to indicate out-of-profile/yellow packet. If the force de-value parameter is specified then the DEI bit is set to specified value for all packets.

If the no form of this command is executed then software will use the dot1p-in-profile and dot1p-out-profile if configured, else it will use default values.

Note: The following rules are applied to determine the dot1p values when both the dot1p command, and the dot1p-in-profile and dot1p-out-profile commands are specified: If de-mark is not configured, dot1p [in | out]-profile values are considered. Even if dot1p value is configured it is ignored and if dot1p [in | out]-profile value is not configured, default values are considered for that FC. If de-mark is configured and the dot1p value is configured, it is considered. If the dot1p [in | out]-profile value is configured, it is considered. In this case, the dot1p value takes precedence over the dot1p [in | out]-profile.

The command adds the capability to mark on an egress the in and out of profile status through a certain dot1p combination, similarly with the DEI options. It may be used when the internal in and out of profile status needs to be communicated to an adjacent network/customer device that does not support the DEI bit.

This command explicitly defines the egress IEEE 802.1P (dot1p) bits marking for fc-name. When the marking is set, all packets with in-profile status (or green color) of fc-name that have either an IEEE 802.1Q or IEEE 802.1P encapsulation use the explicitly defined dot1p-value. If the egress packets for fc-name are not IEEE 802.1Q or IEEE 802.1P encapsulated, the dot1p command has no effect.

If DEI marking is enabled using the de-mark command and the command dot1p dot1p-value is used to configure the dot1p value, then this command has no effect. In other words, enabling DEI marking has precedence over this command and the system ignores this command.

When this command is used the DEI Bit is left unchanged by the egress processing if a tag exists. If a new tag is added, the related DEI bit is set to 0.

The no form of this command sets the IEEE 802.1P or IEEE 802.1Q priority bits to 0.

Note: The following rules are applied to determine the dot1p values when both the dot1p command and the dot1p-in-profile and dot1p-out-profile commands are specified: If de-mark is not configured, dot1p [in|out]-profile values are considered. Even if dot1p command value is configured, it is ignored, and if the dot1p [in|out]-profile value is not configured, default values are considered for that FC. If de-mark is configured and if the dot1p command value is configured, it is considered. Otherwise, if the dot1p [in|out]-profile value is configured, it is considered. In this case, the dot1p command value has the precedence over the dot1p [in|out]-profile. If marking is enabled and both the dot1p command value and the dot1-[in|out]-profile commands are not specified, the default values are used.

The command adds the capability to mark on an egress the in and out of profile status via a certain dot1p combination, similarly with the DEI options. It may be used when the internal in and out of profile status needs to be communicated to an adjacent network/customer device that does not support the DEI bit.

This command explicitly defines the egress IEEE 802.1P (dot1p) bits marking for fc-name. When the marking is set, all packets with out-of-profile status (or yellow color) of fc-name that have either an IEEE 802.1Q or IEEE 802.1P encapsulation use the explicitly defined dot1p-value. If the egress packets for fc-name are not IEEE 802.1Q or IEEE 802.1P encapsulated, the dot1p command has no effect.

If DEI marking is enabled using the de-mark command and the dot1p-value is configured, then this command has no effect. In other words, enabling DEI marking has precedence over this command and the system ignores this command.

When this command is used the DEI Bit is left unchanged by the egress processing if a tag exists. If a new tag is added, the related DEI bit is set to 0.

The no form of this command reverts the IEEE 802.1P or IEEE 802.1Q priority bits to the default.

Note: The following rules are applied to determine the dot1p values to when both the dot1p command and dot1p-in-profile and dot1p-out-profile commands are specified: If de-mark is not configured, the dot1p [in|out]-profile values are considered. Even if the dot1p command value is configured, it is ignored, and if the dot1p [in|out]-profile value is not configured, default values are considered for that FC. If de-mark is configured and if the dot1p command value is configured, it is considered. Otherwise, if the dot1p [in|out]-profile value is configured, it is considered. In this case, the dot1p command value, has the precedence over the dot1p [in|out]-profile value. If marking is enabled and the dot1p command value and the dot1p-[in|out]-profile command are not specified, the default values are used.

This command specifies the in-profile DSCP name for the forwarding class.

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

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

This command specifies the out-of-profile DSCP name for the forwarding class.

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

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

This command specifies the in-profile LSP EXP value for the forwarding class.

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

The no form of this command reverts to the factory default in-profile EXP value.

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

The no form of this command reverts to the factory default out-of-profile EXP value.

This command enables the context to modify Queue parameters associated with a particular queue.

The no form of this command deletes the queue.

This command enables the system to remark egress packets sent out of access-uplink ports. The user can specify if dot1p or dscp or both dot1p and dscp to be used for marking the packets sent out of the port.

When 7210 is operated in access-uplink mode, marking support is available as given below.

The no form of this command disables remarking.

This command enables the system to remark egress packets sent out of network ports, hybrid ports and network port IP interfaces. The user can specify if dot1p or DSCP or both dot1p and DSCP are to be used for marking the packets sent out of the port. It is also possible to configure MPLS EXP bits to use for marking the MPLS packets sent out of a network IP interface.

When 7210 SAS-M is operated in network mode, marking support is available as given below.

Note: If remarking is enabled in network QoS policy of type port, by default, use-dot1p is used. If no marking values are specified, then the default FC to dot1p marking values are used. If remarking is enabled in network Qos policy of type port and associated with hybrid port, then by default all is used. Both dot1p and DSCP values are marked. See DSCP and Dot1p Marking for more information If remarking is enabled in network qos policy of type ip-interface and associated with an IP interface, then the default FC to MPLS EXP values are used for marking MPLS packets.

The no form of this command disables remarking.

This command specifies the remarking policy ID to use for marking packets on network port and network IP interface egress.

The remarking policy ID must be associated with the appropriate network QoS policy associated with the network port and or network IP interface and remarking must be enabled in the network QoS policy to enable marking of packets sent out of network port and or network IP interface egress. Remarking policy of type dot1p, dscp, and dot1p-dscp is allowed to be used when the remark policy is associated with network qos policy of type port. Remarking policy of type lsp-exp and dot1p-lsp-exp-shared is allowed to be used when the remark policy is associated with network qos policy of type ip-interface. See Summary of Remark Policy and Attachment Points for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE (Network Mode) for different remark policies supported on the node and its use.

The no form of this command removes the explicit association of the remark policy and associates the default remark policy. For example, if remarking is enabled and no remark policy is executed, then the default remark policy is used to mark packets sent out. If no remark policy is executed and remarking is disabled, then packets are not remarked at all.

This command enables the system to remark egress packets sent out of network ports and hybrid ports.

When remarking is enabled, the remark policy configured in the QoS policy context is used to determine the FC to QoS bit mapping. For example, when remarking is enabled in the network QoS policy, the remark policy associated with network QoS policy is used to determine the FC to dot1p mapping to use for marking packets sent out of access ports.

See Remark Policies for the remark policy that can be used to configure FC to priority bit markings in different QoS policies associated with different service entities. For more information, see Summary of Remark Policy and Attachment Points for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE (Network Mode) and Summary of Remark Policy and Attachment Points for 7210 SAS-Mxp.

The no form of this command disables remarking.

This command configures the network policy scope as exclusive or template.

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

This command enables the context to configure DSCP/dot1p re-marking for select self-generated traffic.

This command configures DSCP/dot1p re-marking for self-generated application traffic. When an application is configured using this command, then the specified DSCP name/value is used for all packets generated by this application within the router instance it is configured. The instances can be base router or VPRN service.

Using the value configured in this command does the following.

Only one DSCP name/value can be configured per application. If multiple entries are configured then the subsequent entry overrides the previously configured entry.

The no form of this command reverts to the default value.

This command creates a mapping between the DiffServ Code Point (DSCP) of the self-generated traffic and the forwarding class.

Self-generated traffic for configured applications that matches the specified DSCP will be assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all 64 DSCPs to a forwarding class.

All DSCP names that define a DSCP value must be explicitly defined.

The no form of this command removes the DSCP-to-forwarding class association.

This command copies existing QoS policy entries for a QoS policy-id to another QoS policy-id. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.

This command displays network policy information.

This command displays profile policy information.

This command displays DSCP name and DSCP value mappings.

This command enables the contexts to show router information.

This command displays QoS information about self-generated traffic. In the output, the value “none” indicates that the default value is used; it does not indicated that there is no value set. See Table 43 for a list of application defaults.

This command displays application QoS settings.

This command displays DSCP-to-FC mappings.