Overview
720 Quality of Service Guide
The named pool policy is applied at the XMA or MDA ingress and egress level and at the
ingress and egress port level. Each XMA or MDA within the system is associated with a
forwarding plane traffic manager that has support for a maximum of 57 buffer pools. The
following circumstances affect the number of named pools that can be created per XMA or
MDA (these circumstances may be different between ingress and egress for the XMA or
MDA):
• The forwarding plane can be associated with multiple XMAs or MDAs (each XMA
or MDA has its own named pools).
• A single system level pool for system created queues is allocated.
• Each system must have default pools for queues that are not explicitly mapped or are
incorrectly mapped to a named pool.
• Default pools for most IOM types (separate for ingress and egress).
• Access pool.
• Network pool.
• The number of named per-port pools is dependent on the number of ports the XMA
or MDA supports which is variable per XMA or MDA type.
• Per-port named pools cannot be used by ingress network queues, but pools defined
in a named pool policy defined on an ingress all network port are still created.
→ Ingress network queues use the default network pool or XMA or MDA named
pools.
→ Ingress port buffer space allocated to network mode ports is included in the
buffers made available to ingress XMA or MDA named pools.
→ Ingress port buffer space on channelized ports associated with network
bandwidth is included in the buffers made available to ingress XMA or MDA
named pools
→ Ingress port named pools are only allocated buffers when the port is associated
with some access mode bandwidth
• Per-port named pools on ports aggregated into a LAG are still created per physical
port
• Default, named XMA or MDA and named per-port pools are allocated regardless of
queue provisioning activity associated with the pool
If the named pool policy is applied to an XMA or MDA or port that cannot create every pool
defined in the policy, the policy application attempt will fail. Any pre-existing named pool
policy on the XMA, MDA, or port will not be affected by the failed named pool policy
association attempt.
To Next Page
Loading...
