7.4. Command descriptions

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 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 remarks egress packets sent out of access ports and access-uplink ports. Remarking can be enabled or disabled. On access port and access-uplink port egress, the behavior is as follows.

If remarking is enabled without specifying one of the options, by default 'use-dot1p' is used for access-egress and “all” is used for network-egress (that is, access-uplink port egress).

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 to the default value.

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 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 dot1p 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 the FC and profile to packet header priority bits (for example: dot1p bits).

The network policy 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 BUM traffic on the, ingress. For the egress, it defines eight FCs which represent individual queues and the packet marking behavior.

If a new network policy is created (for instance, policy 2), only the default action and egress FC parameters are identical to the default policy. A new network policy does not contain the default dot1p to FC mapping for network QoS policy. The default network policy can be copied (use the copy command) to create a new network policy that includes the default ingress dot1p to FC mapping (as appropriate). You can modify parameters or use the no modifier to remove an object from the configuration.

Changes made to an existing policy, using any of the sub-commands, are applied immediately to all access uplink 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. 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 1 cannot be deleted.

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.

Commands in this context create or edit policy entries that specify the dot1p to FC mapping for all 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 dot1p bits set. The default-action command specifies the FC to which such packets are assigned.

Multiple default-action commands will 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 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 sets 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 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 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 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 FC forwarding types are mapped to the meter, they 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 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. 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 reverts the unicast (point-to-point) meter ID back to the default meter for the FC.

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.

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

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.

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.

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 CBS size 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.

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 MBS size to the default value.

This command defines the mode of the meter. The mode can be configured as Two Rate Three Color Marker (trTCM1) 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 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.

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

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

This command creates or edits egress policy entries that specify the FC to marking values map to be instantiated when this policy is applied to the access-uplink port.

The FC and profile state mapping to marking values (for example: IEEE 802.1p bits, etc.) bits mapping for all packets are defined in this context.

This command specifies the FC name. The FC name represents an egress queue. The fc fc-name represents a CLI parent node that contains subcommands or parameters describing the marking criteria of packets flowing through it. The fc command overrides the default parameters for that FC to the values defined in the network default policy.

The no form of this command removes the FC to marking value association. The FC reverts to the mapping defined in the default network policy.

This command defines the method used by the system to derive the operational CIR and PIR rates when the queue 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. See Table 17 and Table 18 for information about supported hardware step-size rates for 7210 SAS-D and 7210 SAS-Dxp.

This command overrides the default slope policy configuration for the queue. The specified slope policy name must exist as a current slope policy name. If the slope policy does not exist, the slope-policy command fails. If a slope policy is currently associated with a queue, the slope policy cannot be removed from the system.

The slope policy contains the ring and non-ring high and low WRED slope definitions that will be used by the queue. The non-ring slopes are used by the traffic received on access SAP ingress and sent out of access SAP egress queues. The ring slopes are used by the traffic received on access-uplink port ingress and sent out of access-uplink port egress queues.

If the slope-policy command is not executed or the no slope policy command is executed, the default slope policy is associated with the queue.

The no form of the command reverts the default slope policy to the queue.

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

The no form of this command deletes the queue.

This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets through the port. Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth. The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth.

The rate command can be executed at anytime, altering the PIR and CIR rates for all queues created on the access ports.

The no form of the command reverts all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters.

The command enables the context to mark on an egress the in and out of profile status through a certain dot1p combination (similar to DEI option). 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, this command has no effect.

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

The command enables the context to mark on an egress the in and out of profile status via a certain dot1p combination (similar to DEI option). 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-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, this command has no effect.

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

This command specifies the in-profile DSCP name for the FC. When marking is set, the corresponding DSCP value is used to mark all IP packets with in-profile status, on the egress of this FC queue.

When multiple DSCP names are associated with the FC 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 setting for policy-id 1.

This command specifies the out-of-profile DSCP name for the FC. When marking is set, the corresponding DSCP value is used to mark all IP packets with out-of-profile status, on the egress of this FC queue.

When multiple DSCP names are associated with the FC 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 setting for policy-id 1.

This command displays network policy information.