7.6. Network QoS Policy Command Reference

This command creates a text description stored in the configuration file for a configuration context.

The description 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 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 the IP interface.

The policy is associated with the 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 is 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 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 the network mode of operation.

The QoS network policy consists of an ingress and egress component. The ingress component of the policy defines how bits are mapped to the internal FC and profile state. The FC 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 FC. Traffic mapped to each FC can be rate limited using separate meters for unicast and multipoint traffic.

The egress component of the network QoS policy defines FC and profile state to packet header priority bit values for traffic 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 FC and the profile state.

In network mode, network policy ID 2 exists as the default policy that is applied to all network interfaces. This default policy 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 FCs, which define 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. This default policy cannot be modified or deleted. It defines the default DSCP-to-FC mapping and default unicast meters for ingress IP traffic. For the egress, it defines the FC to dot1p and DSCP values and the packet marking criteria.

In network mode, if a new network policy is created (for example, policy-id), only the default action, default meters for unicast and multipoint traffic, and egress FC parameters are identical to the default policy. A new network policy does not contain the default LSP EXP-to-FC mapping for a network QoS policy of the ip-interface type or the DSCP-to-FC mapping (for a network QoS policy of the port type). The default network policy can be copied (using 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 form of the command to remove an object from the configuration.

Changes made to an existing policy using any of the subcommands, are applied immediately to all network ports where this policy is applied. For this reason, when many changes are required on a policy, Nokia highly recommends 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 configures the network policy scope as exclusive or template.

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

This command associates 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 using this command provides the profile to assign to the MPLS packets received on any of the network IP interfaces 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 value (policy ID 1). The user can choose a different policy.

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

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

This command creates a class instance of the FC. After the fc-name is created, classification actions can be applied, which can be used in match classification criteria.

By default, undefined FCs use the parameters configured in the default policy policy-id 1.

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 is used to enter the CLI node that creates or edits policy entries that specify the FC mapping packets.

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

This command configures the default action taken for packets that have undefined LSP EXP bits set. The default-action command specifies the FC to which the packets are assigned.

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

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

By default, undefined FCs use the parameters configured in the default network policy ID 1.

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 explicitly configures the FC or enqueuing priority and profile of the packet when a packet has the dot1p-priority specified. Adding a dot1p rule on the policy forces packets that match the dot1p-priority specified to be assigned to the FC and enqueuing priority and 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 eight Class-of-Service (CoS) values commonly used to map packets to per-hop QoS behavior.

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

This command configures 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 because of the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service is not 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. Any FC forwarding types that are mapped to the meter revert to their default meters. When a meter is removed, any pending accounting information is discarded for each port meter created, because of the definition of the meter in the policy.

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. After the FC 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 FC (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. After the FC mapping is executed, all multicast traffic on a port using this policy is forwarded using the meter-id.

This command can only be used with a network policy of the ip-interface type.

The no form of this command reverts the multicast forwarding type meter ID to the default value.

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

Ingress traffic that matches the specified DSCP is assigned to the corresponding FC. Multiple commands can be entered to define the association of some or all 64 DSCPs to the FC. For undefined code points, packets are assigned to the FC 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 creates a mapping between the LSP EXP bits of the network ingress traffic and the FC.

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

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

This command defines the method used by the system to derive the operational CIRs and PIRs 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.

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 rate and cir apply.

This command overrides 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, the packets are marked as in-profile by the meter to indicate that the traffic is complying with meter-configured parameters.

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

This command overrides 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, the packets are marked as in-profile by the meter to indicate that the traffic is complying with meter-configured parameters.

The no form of this command reverts the MBS 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 value.

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

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

The no form of this command reverts all meter instances created with this meter-id to the default.

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

This command specifies 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 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. Nokia highly recommends using a single mpls-lsp-exp-profile-map policy for all the network policies when FRR facility or PHP is in use, for consistent QoS treatment.

The no form of this command removes the policy.

This command creates or edits egress policy entries that specify the FC dot1p marking map to be instantiated when this policy is applied to the network port.

The FC and profile state mapping to EXP bits mapping for all packets are defined in this context.

All out-of-profile service packets are marked with the corresponding out-of-profile EXP bit value at network egress. All in-profile service ingress packets are marked with the corresponding in-profile EXP bit value based on the FC to which they belong.

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

The remarking policy ID can be associated with the network QoS policy associated with a network port or network IP interface. Remarking must be enabled in the network QoS policy to mark packets sent out of the network port or network IP interface. The user can use the following remarking policy types: dot1p, dscp, and dot1p-dscp when the remark policy is associated with a network QoS policy of the port type. The user should use remarking policies of the lsp-exp and dot1p-lsp-exp-shared type when the remark policy is associated with a network QoS policy of the ip-interface type.

Table 48 describes the remark policies, their attachment points supported on the node, and their uses.

The no form of this command removes the explicit association of the remark policy and associates the default remark policy. Therefore, if remarking is enabled and the no remark command is configured, the default remark policy is used to mark sent packets.

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

The remarking command specifies that 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 the network QoS policy is used to determine the FC-to-EXP marking for packets sent out of access ports.

Table 48 describes remark policies that you can use to configure FC-to-priority bit markings in different QoS policies associated with different service entities.

The no form of this command disables remarking. When remarking is disabled for MPLS LSR traffic, EXP values received at ingress are not modified at egress. For MPLS LER traffic, where the node adds the MPLS encapsulation, MPLS EXP bits are set based on the mapping specified in the policy associated with the IP interface. If the user does not attach an explicit policy, the default policy is used.