Hunt Group Configuration Considerations - Avaya Cajun P882 User Manual

Chapter 4
Optimizing
Hunt Group
Throughput

Hunt Group Configuration Considerations

4-34
To Optimize Hunt Group throughput follow these considerations.
Forwarding Engines in the Hunt group ports should be separate
from the ports involved in the modules traffic flows.
The greater the number of non-member Forwarding Engines in
the system, the greater the ability of the system to load-share.
Distribute the hunt group across more than one Fabric Port per
slot
Distribute the hunt group across media modules
Consider the following before creating hunt groups:
Hunt group end to end physical connections must be
configured with the hunt group ports connected to hunt group
ports.
All ports of the hunt group must be of the same bandwidth and
all layer 2 or all layer 3 ports (but not a mix)
Can have a mix of 80 and 50 series as long as they are the same
bandwidth and all layer 2 or all layer 3. (but not a mix)
A hunt group cannot be distributed between more than two
switches.
You must disable or disconnect the ports in a hunt group until
both ends of the link are configured.
All ports in the hunt group take on the configuration of the
base port
Both sides of the hunt group have the same configuration
Any change to a port in the hunt group will be reflected on all
ports.
When removing a port from a hunt group with the Web Agent,
it must be removed before its VLAN assignment is changed.
If 48-port mode is enabled on the switch, only the first thirteen
hunt groups are retained and all others are discarded. However,
the ports associated with the discarded hunts groups lose their
hunt group bindings, but still retain their VLAN bindings, and
are still active as VLAN bridges. Spanning tree may or may not,
due to the topology or spanning tree settings on those ports,
decide to forward traffic over unwanted trunks.
Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, Version 5.3.1