fc fc-name [create]
no fc fc-name
config>qos>network>ingress
config>qos>network>egress
Supported on all 7210 SAS platforms as described in this document
The config>qos>network>egress context is only supported on the 7210 SAS-T (access-uplink mode).
This command creates a class instance of the forwarding class. After 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.
Undefined forwarding classes default to the configured parameters in the default policy policy-id 1.
Specifies a case-sensitive, system-defined forwarding class name for which policy entries will be created.
Creates the forwarding class. The create keyword requirement can be enabled or disabled in the environment>create context.
ingress
config>qos>network policy-id
Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode
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.
default-action fc fc-name [profile {in | out | use-dei}]
config>qos>network>ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode
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-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.
default-action fc be profile out
Specifies the forwarding class name. All packets with LSP EXP (only when devices is operating in network mode) or dot1p bits (for 7210 SAS-T in access-uplink mode) that are not defined will be placed in this forwarding class.
Specifies that all packets assigned to this forwarding class are considered in or out of profile based on this command. A value must be specified when the profile keyword is used in the command. If the profile is not assigned to a forwarding class, the packets of that FC are treated as out-of-profile packets.
dot1p dot1p-priority fc fc-name profile {in | out | use-dei}
no dot1p
config>qos>network>ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode
This command explicitly sets the forwarding class or enqueuing priorityand 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 forwarding class 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.1 q 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 on the policy immediately removes the rule from all ingress SAP ports using the policy.
Specifies the unique IEEE 802.1p value that will match the dot1p rule. If the command is executed multiple times with the same dot1p-priority value, the previous forwarding class is completely overridden by the new parameters.
A maximum of eight dot1p rules are allowed on a single policy.
Specifies a predefined forwarding classes in the system. Specifying the fc-name is optional. When a packet matches the rule, the forwarding class is only overridden when the fc fc-name parameter is defined on the rule. If the packet matches and the forwarding class is not explicitly defined in the rule, the forwarding class is inherited based on previous rule matches.
Specifies that all packets that are assigned to this forwarding class will be considered in-profile or out-of-profile based on this command or to use the default. In case of congestion, the in-profile packets are preferentially queued over the out-of-profile packets.
meter meter-id [multipoint] [create]
no meter meter-id
config>qos>network>ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode
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 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.
meter 1 (for unicast traffic)
meter 9 multipoint (for all other traffic, other than unicast traffic)
Specifies the meter within the policy. The value 9 is reserved for the default multipoint meter.
Specifies that this meter-id is for multipoint forwarded traffic only. This meter-id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown unicast ingress traffic. If you attempt to map forwarding class unicast traffic to a multipoint queue, an error is generated and no changes are made to the current unicast traffic queue mapping.
The meter must be created as multipoint. The multipoint designator cannot be defined after the meter is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated and the command will not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint meter to edit meter-id parameters.
meter meter-id
no meter
config>qos>network>ingress>fc
Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode
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 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).
meter 1
Specifies the meter. The specified parameter must be an existing, non-multipoint meter defined in the config>qos>network>ingress context.
multicast-meter meter-id
no multicast-meter
config>qos>network>ingress>fc
Supported on all 7210 SAS platforms as described in this document
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 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.
9
Specifies the multicast meter. The specified parameter must be an existing, multipoint meter defined in the config>qos>network>ingress context.
dscp dscp-name fc fc-name profile {in | out}
no dscp
config>qos>network policy-id>ingress
Supported on all 7210 SAS platforms as described in this document
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 64 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 DSCP-to-FC association. The default-action then applies to that code point value.
Specifies the name of the DiffServ code point to be associated with the forwarding class. DiffServ code point can only be specified by its name and only an existing DiffServ code point can be specified. The software provides names for the well known code points.
Table: Default DSCP names to DSCP value mapping table shows the available system-defined names. The system-defined names must be referenced as all lowercase exactly as listed in the first column in Table: Default DSCP names to DSCP value mapping table and Table: Default class selector code points to DSCP value mapping table below.
Additional names to code point value associations can be added using the dscp-name dscp-name dscp-value command.
The actual mapping is being done on the dscp-value, not the dscp-name that references the dscp-value. If a second dscp-name that references the same dscp-value is mapped within the policy, an error will occur. The second name will not be accepted until the first name is removed.
| DSCP name | DSCP value decimal | DSCP value hexadecimal | DSCP value binary |
|---|---|---|---|
nc1 |
48 |
0x30 |
0b110000 |
nc2 |
56 |
0x38 |
0b111000 |
ef |
46 |
0x2e |
0b101110 |
af41 |
34 |
0x22 |
0b100010 |
af42 |
36 |
0x24 |
0b100100 |
af43 |
38 |
0x26 |
0b100110 |
af31 |
26 |
0x1a |
0b011010 |
af32 |
28 |
0x1c |
0b011100 |
af33 |
30 |
0x1d |
0b011110 |
af21 |
18 |
0x12 |
0b010010 |
af22 |
20 |
0x14 |
0b010100 |
af23 |
22 |
0x16 |
0b010110 |
af11 |
10 |
0x0a |
0b001010 |
af12 |
12 |
0x0c |
0b001100 |
af13 |
14 |
0x0e |
0b001110 |
default |
0 |
0x00 |
0b000000 |
| DSCP name | DSCP value decimal | DSCP value hexadecimal | DSCP value binary |
|---|---|---|---|
cs7 |
56 |
0x38 |
0b111000 |
cs6 |
48 |
0X30 |
0b110000 |
cs5 |
40 |
0x28 |
0b101000 |
cs4 |
32 |
0x20 |
0b100000 |
cs3 |
24 |
0x18 |
0b011000 |
cs2 |
16 |
0x10 |
0b010000 |
cs1 |
08 |
0x8 |
0b001000 |
Specifies the fc-name with which the code point will be associated.
Keyword to indicate whether the DiffServ code point value is the in-profile or out-of-profile value. For every DSCP value defined, the profile must be indicated. If a DSCP value is not mapped, the default-action forwarding class and profile state will be used for that value.
DSCP values mapping to forwarding classes Expedited (ef), High-1 (h1) and Network-Control (nc) can only be set to in-profile.
DSCP values mapping to forwarding class be can only be set to out-of-profile.
lsp-exp lsp-exp-value fc fc-name
no lsp-exp lsp-exp-value
config>qos>network policy-id>ingress
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 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.
Specifies the LSP EXP values to be associated with the forwarding class.
Specifies the fc-name that the EXP bit pattern will be associated with.
adaptation-rule [cir adaptation-rule] [pir adaptation-rule]
no adaptation-rule
config>qos>network>ingress>meter
Supported on all 7210 SAS platforms as described in this document, including those operating in the access-uplink mode
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 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.
adaptation-rule cir closest pir closest
Specifies the adaptation rule and defines the constraints enforced to adapt the CIR defined using the meter meter-id rate command. The cir parameter requires a qualifier that defines the constraint used to derive the operational CIR for the meter. When the cir command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive.
See Table: Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T and Table: Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Sx 10/100GE for more information about supported hardware step-size rates.
Specifies the adaptation rule and defines the constraints enforced to adapt the PIR defined using the meter meter-id rate command. The pir parameter requires a qualifier that defines the constraint used to derive the operational PIR for the meter. When the rate command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive.
See Table: Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T and Table: Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Sx 10/100GE for information about supported hardware step-size rates.
cbs size [kbits | bytes | kbytes]
no cbs
config>qos>network>ingress>meter
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
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 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 to the default value.
32 kbits
Specifies the number of kilobits or kilobytes or bytes reserved for the meter. For example, if a value of 100 kbits is desired, then enter the value 100. The bucket size is rounded off to the next highest 4096 bytes boundary.
Specifies the unit of measure for the size of the CBS.
mbs size [kbits | bytes | kbytes]
no mbs
config>qos>network>ingress>meter
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
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 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 to the default value.
512 kbits
Specifies the number of kilobits or kilobytes or bytes reserved for the meter. For example, if a value of 100 kbits is desired, then enter the value 100. The bucket size is rounded off to the next highest 4096 bytes boundary.
Specifies the unit of measure for the size of the MBS.
mode mode
no mode
config>qos>network>ingress>meter
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
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.
trtcm
Keyword to meter the packet stream and mark the packets green, yellow, or red. A packet is marked red if it exceeds the PIR. Otherwise, it is marked yellow or green depending on whether it exceeds or does not exceed the CIR. The trTCM1 is useful for ingress policing of a service, where a peak rate needs to be enforced separately from a committed rate.
Keyword to meter a packet stream and mark its packets green, yellow, or red. Marking is based on a CIR and two associated burst sizes, a CBS and an MBS. A packet is marked green if it does not exceed the CBS, yellow if it exceeds the CBS but not the CIR, and red otherwise. The srTCM is useful for ingress policing of a service, where only the length, not the peak rate, of the burst determines service eligibility.
rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]
no rate
config>qos>network>ingress>meter
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
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 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 PIR (max) and CIR (0) parameters.
The value of rates are represented as 1000 kilobits per second and bursts are represented as 1024 kilobits per second.
rate 0 pir max
Specifies the administrative CIR, in kilobits, for the meter. The cir parameter overrides the default administrative CIR used by the meter. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.
Fractional values are not allowed and must be given as a positive integer.
The actual CIR is dependent on the meter’s adaptation-rule parameters and the hardware.
Specifies the administrative PIR, in kilobits, for the meter. When this command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. When the rate command is executed, a PIR setting is optional.
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.
Fractional values are not allowed and must be given as a positive integer.
The actual PIR is dependent on the meter’s adaptation-rule parameters and the hardware.
If the meter mode is configured as trtcm2, the system configures the policer EIR rate, based on the value of the PIR rate configured by the user.