Sap Egress Qos Policy - Alcatel-Lucent 7450 Quality Of Service Manual

To negate the issue between SAP type and LAG port membership, the config>lag>port-type
{standard | hsmda-ports} command has must be executed prior to adding any ports to the
LAG. This command allows the type ports that will be added to the LAG to be predefined.
Without executing this command, HSMDA ports cannot be added to the LAG and after
execution, the LAG may only be populated with HSMDA ports.
The LAG port type restriction can only be changed prior to adding SAPs or binding network
IP interfaces to the LAG. If the port type for the LAG must be changed, all ports, SAPs and
IP interfaces must be removed from the LAG.
A LAG with HSMDA member ports cannot be configured as mode network.
A LAG with HSMDA member ports can only operate in link-level SLA distribution. Since
hierarchical QoS is only supported for queues within a single queue group and a queue group
is limited to a single egress port, it cannot spread a SAP's ingress or egress queue CIR and
PIR parameters over multiple LAG links. Each SAP created on an HSMDA LAG is assigned
a queue group for each link within the LAG. The CIR and PIR defined in the SAP ingress or
SAP egress QoS policy is replicated for the queue ID in each queue group.
Billing
The HSMDA SAP and subscriber queue billing statistics collection process supports the same
information as non-HSMDA objects with the addition of the exception counter information.
Statistics from queues within a queue group that are not currently mapped to forwarding
classes are removed. Since the queues always exist, the counter information for the unused
queues will be presented by the underlying collection mechanisms. Because of a large amount
of data that could potentially exist, longer statistics collection intervals can occur.
Resource Management
The HSMDA presents a different set of resource management features to the system than with
non-HSMDAs. Since the HSMDA does not manage a pool of queues that are individually
mapped to SAPs or subscribers, it cannot run out of queues on the XMA or MDA. Instead, a
pool of available queue groups are managed and allocated on a per SAP or subscriber basis.
Each SAP and subscriber created is managed against a system wide maximum. The
maximum for SAPs and subscribers are each 64K within a single chassis.
Quality of Service Guide
High Scale Ethernet MDA Capabilities
787