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.
[no
] fc
{be
| l2
| af
| l1
| h2
| ef
| h1
| nc
}
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 egress characteristics of the queue and the marking criteria of packets flowing through it. The
fc command overrides the default parameters for that forwarding class defined in the network default policy
policy-id 1.
See Default Shared Queue Policy Values for undefined forwarding class values.
This command configures the broadcast forwarding type queue mapping for fc fc-name. The specified
queue-id must exist within the policy as a multipoint queue before the mapping can be made. Once the forwarding class mapping is executed, all broadcast traffic on a SAP using this policy will be forwarded using the
queue-id.
The no form of the command sets the broadcast forwarding type
queue-id back to the default of tracking the multicast forwarding type queue mapping.
The queue-id parameter must be an existing, multipoint queue defined in the
config>qos>sap-ingress context .
This command configures the multicast forwarding type queue mapping for fc fc-name. The specified
queue-id must exist within the policy as a multipoint queue before the mapping can be made. Once the forwarding class mapping is executed, all multicast traffic on a SAP using this policy is forwarded using the
queue-id.
The multicast forwarding type includes the unknown unicast forwarding type and the
broadcast forwarding type unless each is explicitly defined to a different multipoint queue. When the unknown and broadcast forwarding types are left as default, they will track the defined queue for the multicast forwarding type.
The no form of the command sets the multicast forwarding type
queue-id back to the default queue for the forwarding class. If the
broadcast and
unknown forwarding types were not explicitly defined to a multipoint queue, they will also be set back to the default multipoint queue (queue 11).
The queue-id parameter specified must be an existing, multipoint queue defined in the the
config>qos>sap-ingress context.
This command overrides the default unicast forwarding type queue mapping for fc fc-name. The specified
queue-id must exist within the policy as a non-multipoint queue before the mapping can be made. Once the forwarding class mapping is executed, all unicast traffic (this includes all traffic, even broadcast and multicast for services) on a SAP using this policy is forwarded using the
queue-id.
The no form of this command sets the unicast (point-to-point)
queue-id back to the default queue for the forwarding class (queue 1).
The queue-id parameter specified must be an existing, non-multipoint queue defined in the
config>qos>sap-ingress context.
queue queue-id [queue-type] [profile-mode | priority-mode
] [multipoint
] pool
pool-name
queue queue-id [queue-type] [multipoint
] pool
pool-name
Explicit definition of an ingress queue’s hardware scheduler status is supported. A single ingress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or non-expedited nature of the queue based on the forwarding classes mapped to it. As long as all forwarding classes mapped to the queue are expedited (nc, ef, h1 or h2), the queue is treated as an expedited queue by the hardware schedulers. When any non-expedited forwarding classes are mapped to the queue (be, af, l1 or l2), the queue is treated as best effort (be) by the hardware schedulers. The expedited hardware schedulers are used to enforce expedited access to internal switch fabric destinations. The hardware status of the queue must be defined at the time of queue creation within the policy.
The queue-id for the queue, expressed as an integer. The
queue-id uniquely identifies the queue within the policy. This is a required parameter each time the queue command is executed.
The expedite,
best-effort and
auto-expedite queue types are mutually exclusive to each other. Each defines the method that the system uses to service the queue from a hardware perspective. While parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for bandwidth with other queues associated with the same scheduler hierarchy. An internal mechanism that provides access rules when the queue is vying for bandwidth with queues in other virtual schedulers is also needed. A keyword must be specified at the time the queue is created in the SAP ingress policy. If an attempt to change the keyword after the queue is initially defined, an error is generated.
expedite — This keyword ensures that the queue is treated in an expedited manner independent of the forwarding classes mapped to the queue.
best-effort — This keyword ensures that the queue is treated in a non-expedited manner independent of the forwarding classes mapped to the queue.
auto-expedite — This keyword allows the system to auto-define the way the queue is serviced by the hardware. When auto-expedite is defined on the queue, the queue is treated in an expedited manner when all forwarding classes mapped to the queue are configured as expedited types nc, ef, h1 or h2. When a single non-expedited forwarding class is mapped to the queue (be, af, l1 and l2) the queue automatically falls back to non-expedited status.
This keyword specifies that this queue-id is for multipoint forwarded traffic only. This queue-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.
A queue must be created as multipoint. The multipoint designator cannot be defined after the queue 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 queue to edit queue-id parameters.
This command configures the unknown unicast forwarding type queue mapping for fc fc-name. The specified
queue-id must exist within the policy as a multipoint queue before the mapping can be made. Once the forwarding class mapping is executed, all unknown traffic on a SAP using this policy is forwarded using the
queue-id.
The no form of this command sets the unknown forwarding type
queue-id back to the default of tracking the multicast forwarding type queue mapping.
The queue-id must be an existing, multipoint queue defined in the the
config>qos>sap-ingress context .
The Committed Burst Size (cbs) command specifies the relative amount of reserved buffers for a specific ingress network MDA forwarding class queue or egress network port forwarding class queue. The value is entered as a percentage.
The cbs forwarding class defaults are listed in the table below:
The high-prio-only command allows the reservation of queue buffers for use exclusively by high priority packets as a default condition for access buffer queues for this shared queue policy.
Modifying the current MBS for the queue through the mbs command will cause the default
high-prio-only function to be recalculated and applied to the queue. The
high-prio-only command as defined for the specific queue can be used to override the default
high-prio-only setting as defined in the network queue policy. This prevents the
high-prio-only command for the shared queue policy from having an affect on the queue.
The high-prio-only forwarding class defaults are listed in the table below.
The mbs forwarding class defaults are listed in the table below.
The no pool command is used to remove a named pool association for the queue. When the pool name is removed, the queue will be placed on the appropriate default pool.
rate [percent] [cir
percent]
This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the percentage that the queue can transmit packets through the switch fabric (for SAP ingress queues) or out an egress interface (for SAP egress queues). 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 over-subscription factors or available egress bandwidth.
The CIR can be used by the queue’s parent commands cir-level and
cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.
The rate command can be executed at anytime, altering the PIR and CIR rates for all queues created through the association of the SAP ingress or SAP egress QoS policy with the
queue-id.
A:ALA-1>config>qos# show qos shared-queue default
===============================================================================
QoS Network Queue Policy
===============================================================================
-------------------------------------------------------------------------------
Shared Queue Policy (default)
-------------------------------------------------------------------------------
Policy : default
Description : Default Shared Queue Policy
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
A:ALA-1>config>qos#