[no] fc fc-name [create]
config>qos>network>ingress
Supported on all 7210 SAS platforms as described in this document
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.
Specifies the case-sensitive, system-defined FC name for which policy entries will be created.
Specifies that the FC is created. The create keyword requirement can be enabled in the environment>create context.
ingress
config>qos>network
Supported on all 7210 SAS platforms as described in this document
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.
default-action fc fc-name [profile {in | out}]
config>qos>network>ingress
Supported on all 7210 SAS platforms as described in this document
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.
default-action fc be profile out
Specifies the FC name. All packets with dot1p or dot1p bits that are not defined are placed in this FC.
Specifies an in or out of profile for all packets assigned to this FC. A value of 'in' defines the packet profile as 'in-profile' and a value of 'out' defines the packet profile to be 'out-of-profile.
[no] fc fc-name [create]
config>qos>network>ingress
Supported on all 7210 SAS platforms as described in this document
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.
Specifies the case-sensitive system-defined FC name for which policy entries are created.
Specifies that the FC is created. The create keyword requirement can be enabled in the environment>create context.
dot1p dot1p-priority fc fc-name profile {in|out}
no dot1p dot1p-priority
config>qos>network>ingress
Supported on all 7210 SAS platforms as described in this document
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.
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 FC is overridden by the new parameters.
A maximum of eight dot1p rules are allowed on a single policy.
Specifies a value that must be one of the predefined FCs in the system. Specifying the fc-name is optional. When a packet matches the rule, the FC is only overridden when the fc fc-name parameter is defined on the rule. If the packet matches and the FC is not explicitly defined in the rule, the FC is inherited based on previous rule matches.
Specifies an in or out of profile for all packets assigned to this FC. A value of 'in' defines the packet profile as 'in-profile' and a value of 'out' defines the packet profile to be 'out-of-profile.
meter meter-id [multipoint] [create]
no meter meter-id
config>qos>network>ingress
Supported on all 7210 SAS platforms as described in this document
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.
meter 1 (for unicast traffic)
meter 9 multipoint (for traffic other than unicast traffic)
Specifies the meter-id that uniquely identifies the meter within the policy. This is a required parameter each time the meter command is executed.
Specifies that this meter-id is for multipoint forwarded traffic only. This meter-id can only be explicitly mapped to the FC multicast, broadcast, or unknown unicast ingress traffic. If you attempt to map FC 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 does not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint meter to edit meter-id parameters.
Keyword to create the ingress network QoS policy meter.
meter meter-id
no meter
config>qos>network>ingress>fc
Supported on all 7210 SAS platforms as described in this document
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.
meter 1
Specifies the meter ID. 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 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.
9
Specifies the multicast meter. The specified parameter must be an existing multipoint meter defined in the config>qos>network>ingress context.
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
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.
adaptation-rule cir closest pir closest
Specifies the adaptation rule and defines the constraints enforced to adapt the CIR rate defined using the meter meter-id rate command. The cir parameter requires a qualifier that defines the constraint used to derive the operational CIR rate for the meter. When the pir command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive.
Specifies the adaptation rule and defines the constraints enforced to adapt the PIR rate defined using the meter meter-id rate command. The pir parameter requires a qualifier that defines the constraint used to derive the operational PIR rate for the meter. When the pir command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive.
cbs size [kbits | bytes | kbytes]
no cbs
config>qos>network>ingress>meter
Supported on all 7210 SAS platforms as described in this document
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 size to the default value.
32 kbits
Specifies the size parameter is an integer expression of the number of kilobits, kilobytes, or bytes reserved for the meter; for example, if a value of 100 kb is needed, then enter the value 100. The bucket size is rounded to the next highest 4096 bytes boundary.
Specifies that the value is in kilobits.
Specifies that the value is in kilobytes.
Specifies that the value is in bytes.
mbs size [kbits|bytes|kbytes]
no mbs
config>qos>network>ingress>meter
Supported on all 7210 SAS platforms as described in this document
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 size to the default value.
128 kbits
Specifies the size parameter is an integer expression of the number of kilobits reserved for the meter; for example, if a value of 100 kb is needed, then enter the value 100. The bucket size is rounded off to the next highest 4096 bytes boundary.
Specifies that the value is in kilobits.
Specifies that the value is in kilobytes.
Specifies that the value is in bytes.
mode {trtcm1|srtcm}
no mode
config>qos>network>ingress>meter
Supported on all 7210 SAS platforms as described in this document
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.
trtcm1
Specifies the policing algorithm defined in RFC2698 and meters the packet stream and marks its 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 example, for ingress policing of a service, where a peak rate needs to be enforced separately from a committed rate. Two token buckets are used, the CBS bucket and the MBS bucket. Tokens are added to the buckets based on the CIR and PIR rates. The algorithm deducts tokens from both the CBS and the MBS buckets to determine a profile for the packet.
Specifies that the mode is configured as a srTCM and meters a packet stream and marks the 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 does exceed the CBS but not the cir and red otherwise. The srTCM is useful, for example, 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
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.
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.
rate 0 pir max
Specifies that the default administrative CIR used by the meter will be overridden. 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 values must be a positive integer.
The actual CIR rate is dependent on the meter’s adaptation-rule parameters and the hardware.
Specifies the administrative PIR rate, 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.
Fractional values are not allowed and must be specified as a positive integer.
The actual PIR rate is dependent on the meter’s adaptation-rule parameters and the hardware.