egress
config>qos>network policy-id
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
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.
[no] fc fc-name
config>qos>network>egress
7210 SAS-T (access-uplink mode)
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.
Undefined forwarding classes default to the configured parameters in the default network policy policy-id 1.
Specifies a case-sensitive, system-defined forwarding class name for which policy entries will be created.
[no] de-mark [force de-value]
config>qos>network>egress>fc
7210 SAS-T (access-uplink mode)
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.
Specifies the DEI value to use for this forwarding class.
[no] dot1p dot1p-value
config>qos>network>egress>fc
7210 SAS-T access-uplink mode
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.
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.
no dot1p
Specifies the 802.1p value to set for in-profile frames in this forwarding class.
dot1p-in-profile dot1p-priority
no dot1p-in-profile
config>qos>network>egress>fc
7210 SAS-T access-uplink mode
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.
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.
0
Specifies the 802.1p value to set for in-profile frames in this forwarding class.
dot1p-out-profile dot1p-priority
no dot1p-out-profile
config>qos>network>egress>fc
7210 SAS-T access-uplink mode
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.
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.
0
Specifies the 802.1p value to set for in-profile frames in this forwarding class.
dscp-in-profile dscp-name
no dscp-in-profile
config>qos>network >egress>fc
7210 SAS-T (access-uplink mode)
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.
Specifies a system- or user-defined, case-sensitive dscp-name.
dscp-out-profile dscp-name
no dscp-out-profile
config>qos>network>egress>fc
7210 SAS-T (access-uplink mode)
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.
Specifies a system- or user-defined, case-sensitive dscp-name.
remarking {use-dot1p | use-dscp | all}
no remarking
config>qos>network>egress
7210 SAS-T(access-uplink mode)
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.
On access-uplink port egress, the behavior is as follows:
If the use-dot1p keyword is configured in the access-egress policy, then the dot1p bits are marked in the packet header for all traffic sent out of all SAPs configured on that access-uplink port.
If the use-dscp keyword is configured in the access-egress policy, then the IP DSCP bits are marked in the packet header for IPv4 traffic sent out of all SAPs configured on that access port.
DSCP marking also marks the IPv4 packets associated with SAPs configured in an Layer 2 VPN service. If this is not required, to avoid this it is recommended to use only dot1p marking on access-uplink ports.
If the all keyword is configured is configured in the access-egress policy, then the dot1p bits are marked in the packet header for all traffic (Layer 2 and IPv4) sent out of all SAPs and the IP DSCP bits are marked in the packet header for all IPv4 traffic sent out of all SAPs configured on that access port.
DSCP marking also marks the packets associated with SAPs configured in an Layer 2 VPN service. If this is not required, to avoid this it is recommended to use only dot1p marking on access-uplink ports.
If remarking is enabled in access-egress policy, by default use-dot1p is used. If no marking values are specified, the default FC-to-dot1p marking values are used.
The no form of this command disables remarking.
no remarking
remark policy-id
no remark
config>qos>network>egress
7210 SAS-T (network mode), 7210 SAS-Sx 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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. Table: 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 Table: Summary of remark policy and attachment points for 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 describe 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. For example, if remarking is enabled and the no remark command is configured, 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.
Specifies the remark policy ID.
[no] remarking
config>qos>network>egress
7210 SAS-T (network mode), 7210 SAS-Sx 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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-EXP 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 Table: 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 Table: Summary of remark policy and attachment points for 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12.
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.
no remarking
scope {exclusive | template}
no scope
config>qos>network policy-id
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
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.
template
Specifies that the policy can only be applied to one interface. If a policy with an exclusive scope is assigned to a second interface an error message is generated. If the policy is removed from the exclusive interface, it will become available for assignment to another exclusive interface. The system default policies cannot be put into the exclusive scope. An error will be generated if scope exclusive is executed in any policies with a policy ID equal to 1.
Specifies that the policy can be applied to multiple interfaces on the router.
Default QoS policies are configured with template scopes. An error is generated if you try to modify the template scope parameter to exclusive scope on default policies.