User guide

Overview Quality of Service (QoS) Network Management
6-91
AlliedView NMS Administration Guide (Configuring Network Services)
Usage Notes:
Classifiers on LAGs only support filtering and remarking; not metering.
LAGs do not support egress port rate limiting.
Ingress Meters (TRAFFIC DESCRIPTORs) are limited to 1 per classifier. Their actions on out-of-profile packets are
NCFORWARD (the default), NCDROP, an NCCOUNT.
All interfaces support p-bit mapping to queues.
All interfaces support only Strict Priority, Tail-drop queuing discipline.
FE2/GE2/FE10/FX10/ADSL24 - Not supported with double tagging of 802.3 packets. Rejects classifiers with ETHFOR-
MAT=802.3x if the classifier contains an INNERVID or INNERVPRIORITY rule. Rejects classifiers with ETHFOR-
MAT=802.3x if the classifier contains is an HVLAN configured on that port. Any generic classifier that does not specify
an EthFormat of 802.3 will NOT match 802.3 packets. In other words, classifiers with no ETHFORMAT rule or a rule of
ETHFORMAT=ANY will not match 802.3 packets.
GE3 - Not supported with double tagging of 802.3 packets. Rejects classifiers with ETHFORMAT=802.3x if the classi-
fier contains an INNERVID or INNERVPRIORITY rule. Rejects classifiers with ETHFORMAT=802.3x if the classifier
contains is an HVLAN configured on that port.
FE2, GE2, FE10, FX10, ADSL24, GE3 - If a classifier contains a rule that specifies one of the 802.3 EthFormats, a filter
will be created that will match 802.3 packets. The iMAP system assumes that if the user specifies 802.3x and IP-related
fields, that this is an indicator that IP uses LLC-SNAP and as a result the system allows for an 8-byte SNAP header. The
system does NOT support 802.3 headers of any size other than 8 bytes when matching IP-related fields.
FE2, GE2, FE10, FX10, ADSL24, GE3 - Rejects classifiers containing INNERVID or INNERVIDPRIORITY rule(s) if
there is NOT a HVLAN configured on that interface/port.
FE2, GE2, FE10, FX10, ADSL24, GE3 - If a classifier fails to be installed due to any reason related to the configuration
of other features on that port (such as, an HVLAN being configured on that port), the system will keep the data related to
the specified classifier. When the condition(s) preventing the classifiers installation is corrected (such as, HVLAN is
Number of Egress
Queues
4 8 4 8 8 4 8
Number of Classifiers
d
(d) (d) 128 128 1024 128 128
Number of Ingress Traf-
fic Meters
63 256 127 2048 1024
Number of Ingress Traf-
fic Counters
32 255 128 4096 16384
Number of Out-of-pro-
file Packet Meter
Counters
63 255 127 127 127
a. Not the interface for traffic management; this is done by the ONU, which is the UNI interface port. The EPON2 mod-
els the ONU as an Network Access product extension.
b. For ETHFORMAT=ANY or no ETHFORMAT, the rule will result in a match for either EthII or 802.3 formats.
c. QoS policies (SLAs) allow limiting of services at specific rates.
d. Classifier capacity is an approximation. The features enabled on a port or interface, such as such as IGMP,
DHCPRELAY, VLAN (for per-VLAN UFO and HVLAN), EPSR, INTERFACE (TAGALL option for HVLAN),
ACCESSLIST, and CLASSIFIER, classifiers on surrounding ports, content of the user classifiers, and many other fac-
tors influence the number of classifiers available on a given port or interface.
TABLE 6-11 Traffic Management Summary Table - Ethernet-based Cards (Continued) - iMAP and SBx3112
Classifier Match Fields
FE10/
FX10
FX20 GE2 GE3 XE1 GE4/
GE2RJ
GE8 EPON2
a
GE24POE XE4