broadcast-queue queue-id
no broadcast-queue
config>qos>sap-ingress>fc
This command maps the broadcast forwarding type queue to the fc fc-name. The specified queue-id must already have been created within the policy 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 no mapping to an FC.
no broadcast-queue
an existing queue defined in the config>qos>sap-ingress context.
[no] de-1-out-profile
config>qos>sap-ingress>fc
This command, when enabled on a parent forwarding class, applies a color profile mode to the packets stored in the queue associated with this forwarding class.
When this QoS policy is applied to the ingress of an FR VLL SAP, DE=1 frames are classified as out-of-profile and are not subject to the CIR marking.
All received DE=0 frames that exceed the CIR are marked as out-of-profile and have the DE set to 1, regardless of whether this command is enabled or disabled.
The priority option, if used, has no effect. All FR VLL DE=1 frames have their priority automatically set to low; DE=0 frames have their priority set to high.
All other capabilities of the Fpipe service are maintained. These capabilities include re-marking of the DE bit on egress SAP, and FR PW control word on egress network port for the packets that were classified as out-of-profile at the ingress SAP.
The de-1-out-profile command has an effect only when it is applied to the ingress of a SAP that is part of an Fpipe service.
The no form of the command disables the color profile mode of operation on all SAPs to which this ingress QoS policy is applied.
no de-1-out-profile
multicast-queue queue-id
no multicast-queue
config>qos>sap-ingress>fc
This command maps the multicast forwarding type queue to the fc fc-name. The specified queue-id must already have been created within the policy before the mapping can be made. Once the forwarding class mapping is executed, all multicast traffic on a SAP using this policy will be forwarded using the queue-id.
The no form of the command sets the multicast forwarding type queue-id back to the default of no mapping to an FC.
no multicast-queue
an existing queue defined in the config>qos>sap-ingress context.
profile {in | out}
no profile
config>qos>sap-ingress>fc
This command specifies that ingress access data packets mapped to this forwarding class are either in-profile or out-of-profile.
Usually, at SAP ingress an access packet’s state is defined as in-profile or out-of-profile based on the dynamic rate of the ingress queue prior to being forwarded to the fabric. Explicitly defining a forwarding class as in-profile or out-of-profile overrides this function by handling each packet according to the defined profile state; however, the forwarding class must be mapped to a queue configured for profile-mode. If the forwarding class is mapped to a queue configured for priority-mode, the forwarding class profile setting is ignored and the packet’s state is defined as in-profile or out-of-profile based on the dynamic rate of the ingress queue.
When the profile in command is executed on a forwarding class that is mapped to a queue operating in profile mode, all packets associated with the class are handled as in-profile. When the profile out command is executed on a forwarding class that is mapped to a queue operating in profile mode, all packets associated with the class are handled as out-of-profile.
When the no profile command is executed on a forwarding class that is mapped to a queue operating in profile mode, the data packets using the forwarding class are marked as in-profile or out-of-profile based on the dynamic rate of the ingress queue relative to its CIR.
Packets explicitly handled as in-profile or out-of-profile flow through the same ingress service queue associated with the forwarding class to preserve order within flows. In-profile packets count against the CIR of the queue, reducing the amount of CIR available to forwarding classes using the queue that are not configured with an explicit profile. Out-of-profile packets do not count against the CIR of the queue, allowing classes using the queue that are not configured with an explicit profile to be measured against the full CIR.
A queue operating in profile mode can support in-profile, out-of-profile, and non-profiled packets simultaneously because multiple forwarding classes with different forwarding class profiles can be assigned to a single queue. In addition, a queue operating in profile mode is classified as high-priority or low-priority based on the configuration of the forwarding class profile rather than on the high-priority or low-priority configuration specified for DSCP or dot1p. Packets mapped to a forwarding class configured with profile in or no profile are marked as high priority. Packets mapped to a forwarding class configured with profile out are marked as low priority.
The no form of this command removes the explicit in-profile or out-of-profile configuration on a forwarding class.
no profile
specifies that all packets associated with the forwarding class will be handled as in-profile
specifies that all packets associated with the forwarding class will be handled as out-of-profile
queue queue-id
no queue
config>qos>sap-ingress>fc
This command overrides the default forwarding type queue mapping for fc fc-name.
The no form of this command sets the queue-id back to the default queue for the forwarding class (queue 1).
an existing queue defined in the config>qos>sap-ingress context
unknown-queue queue-id
no unknown-queue
config>qos>sap-ingress>fc
This command maps the unknown forwarding type queue to the fc fc-name. The specified queue-id must already have been created within the policy before the mapping can be made. Once the forwarding class mapping is executed, all unknown forwarding type traffic on a SAP using this policy will be forwarded using the queue-id.
The no form of the command sets the unknown forwarding type queue-id back to the default of no mapping to an FC.
no unknown-queue
an existing queue defined in the config>qos>sap-ingress context.