User guide

QoSPolicies for the FX20 Interface Quality of Service (QoS) Network Management
6-123
AlliedView NMS Administration Guide (Configuring Network Services)
The administrator can also set the priority of traffic packets for the entire iMAP by setting the priority (usually through
VLANs) and mapping them to system-wide queues before forwarding. (This is done on the NMS by creating a profile for the
Allied Telesis device. By doing this, the administrator can set a queue number (0 = lowest priority; higher numbers = higher
priority) and match it to the p-bit value in the packet.
In the 11.0 release of iMAP software, there was an enhancement to provisioning egress interfaces for the FX20 interfaces; a
QosPolicy, which defines data stream attributes, could be associated with a specific queue on the FX20 interface. This was
an enhancement over other interfaces, where rate and burst attributes are defined for the entire interface (when using the
attribute EGRESSLIMITER), or where a QOSPOLICY defined data stream attributes on a VLAN basis (when provisioning
EPON).
On the NMS, there is already a GUI framework for creating the QoS Policies for the EPON/ONU configuration, as detailed
in 6.11.11.
In NMS 11.0 SP4, this FX20 QoS feature is added; using (for the most part) the NMS GUI that is used to configure QoSPol-
icies, the administrator can engineer traffic going through the FX20 by creating an NMS Policy that is a set of QosPolicies
that tie together the queues and their data stream attributes. This policy is then included in a Profile that is for the FX20 port.
The same QosPolicy can be shared with multiple ports and queues since the configuration is applied on a per port and per
queue basis.
The following figure summarizes this feature. The iMG/RG is connected to the iMAP over an FX20 interface. Packets from
the network have a priority based on service (usually set through VLANs), and the iMAP-level profile will map the priorities
to queues. At the egress for an FX20 interface, a QoSPolicy is made up of a set of rules that tie together for each queue the
attributes of its data stream.
FIGURE 6-104 Summary of FX20 QoS per Queue Feature
6.11.12.2 Overview of GUI
This feature uses the GUI framework that is used to configure SLA bandwidth parameters for ONU interfaces, as detailed in
6.11.11, but instead of defining QoSPolicies for each VLAN on an ONU, an NMS Policy consists of a set of rules in which
each rule maps a queue to a specific traffic action. The GUI is updated as follows when creating a rule:
• QoS Packet Flow - Each flow represents a queue, and there are already in the pull-down for flows the selections for
queues, [Queue0] through [Queue7].
• Traffic Priority - The rules that make up a QoSPolicy for the FX20 do not use these (if the administrator chooses a Queue
for a Flow, and then a Priority, the Priority will be ignored).