Queue Sharing and Redirection
Quality of Service Guide 413
b. One or more spoke-sdps can have their FCs redirected to use queues only or
queues and policers in the same queue-group instance.
The following are the constraints and rules of this provisioning model:
1. Queue-groups containing queues only or policers and queues can be instantiated in
the network egress context of an Ethernet port on IOM3/IMM.
2. When a port is a LAG, one instance of the queue-group is instantiated on each
member link.
3. One or more instances of the same queue-group name and/or a different queue-group
name can be created in the network egress context of an Ethernet port.
4. The queue-group-name must be unique within all network egress and access egress
queue groups in the system.
5. A user attempt to instantiate the queue-group on the network egress context of a POS
port or a TDM port will fail.
6. When a PW FC is redirected to use a queue or a policer and a queue in a queue-group
and the queue-group name does not exist, the association is failed at the time the user
associates the egress context of a spoke-SDP to the named queue-group. In such a
case, the PW packet is fed directly to the corresponding egress queue for that FC used
by the IP network interface the PW packet is forwarded on. This queue can be a
queue-group queue or the egress shared queue for that FC defined in the network-
queue policy applied to the egress of this port. This is the existing implementation
and default behavior for a PW packet.
7. When a PW FC is redirected to use a queue or a policer and a queue in a queue-group
and the queue-group name exists but the policer-id and/or the queue-id is not defined
in the queue-group template, the association is failed at the time the user associates
the egress context of a spoke-SDP to the named queue-group. In such a case, the PW
packet is fed directly to the corresponding egress queue for that FC used by the IP
network interface the PW packet is forwarded on.
8. When a PW FC is redirected to use a queue or a policer and a queue in a queue-group
and the queue-group name exists and the policer-id or policer-id plus queue-id exist,
it is not required to check that an instance of that queue-group exists in all egress
network ports which have network IP interfaces. The handling of this is dealt with in
the data path as follows:
a. When a PW packet for that FC is forwarded and an instance of the referenced
queue-group name exists on that egress port, the packet is processed by the
queue-group policer and is fed to the queue-group queue. If only a policer is
specified in the redirection command, then the packet is processed by the queue-
group policer and is then fed into the corresponding egress shared queue for that
FC defined in the network-queue policy applied to the egress of this port. If only
a queue is specified in the redirection command, the packet is fed to the queue-
group queue.
To Next Page
Loading...
