network network-policy-id [create] [network-policy-type {ip-interface | port}]
no network network-policy-id
config>qos
Supported on all 7210 SAS platforms as described in this document
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 unicast 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 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 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, 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.
system default network policy 1
Specifies the policy on the interface or port.
Specifies the type of the policy. This parameter defines where this network policy can be applied.
mpls-lsp-exp-profile-map policy-id [create]
no mpls-lsp-exp-profile-map
config>qos
Supported on all 7210 SAS platforms as described in this document
This command creates 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.
1 (default mpls-lsp-exp-profile-map policy ‟1”)
Specifies the policy ID on the 7210 SAS.
Keyword to create a policy.
lsp-exp lsp-exp-value
no lsp-exp
config>qos> mpls-lsp-exp-profile-map
Supported on all 7210 SAS platforms as described in this document
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.
Specifies a 3-bit LSP EXP bit value, expressed as a decimal integer.
use-global-mpls-lsp-exp-profile policy-id
no use-global-mpls-lsp-exp-profile
config>qos
Supported on all 7210 SAS platforms as described in this document
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 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, Nokia highly recommends using 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.
1
Specifies the mpls-lsp-exp-profile-map policy to use.
mpls-lsp-exp-profile policy-id [create]
no mpls-lsp-exp-profile
config>qos>network>ingress
Supported on all 7210 SAS platforms as described in this document
This command specifies the mpls-lsp-exp-profile-map policy to use for assigning profile values for packets received on this IP interface.
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.
Specifies the policy.
Keyword to create a policy.