A Sample 802.1Q Hunt Group Trunk Configuration
Between an Avaya™ P882 Gigabit Ethernet Switch and
Servers with Intel Dual Port Server Adapters - Issue 1.0
Abstract
These Application Notes describe a sample Link Aggregation Group (LAG) configuration
between two Windows 2000 Servers: one equipped with an Intel PRO/100+ Dual Port Server
Adapter and the other an Intel PRO/1000MT Dual Port Server Adapter. Each adapter is
connected to an Avaya™ P882 Gigabit Ethernet switch via a separate 802.1Q Hunt Group
Trunk. A sample configuration diagram has been included along with all of the necessary
provisioning steps. These Application Notes were created as a result of field requests for
information on interoperability with Intel Dual Port Server Adapters.
GAK; Reviewed:
WCH 7/7/2003
Solution & Interoperability Test Lab Application Notes
The Avaya™ P580/P882 Gigabit Ethernet Switch Hunt Group feature aggregates multiple switch
ports together, combining the bandwidth into a single connection. This feature is normally
deployed between switches to provide added bandwidth and fault tolerance. These Application
Notes describe a configuration where a hunt group is deployed between a switch and a server to
provide similar bandwidth and fault tolerance advantages. If one segment in the hunt group fails,
the remaining active members will service the failed segment traffic. The Hunt Group LoadSharing feature (enabled by default) distributes traffic load amongst the hunt group members for
improved performance. A hunt group can be configured as an 802.1Q trunk or as a clear access
link and associated with or without a router interface address.
The Avaya Hunt Group feature is a manual (or static) implementation of link aggregation. This
means the feature does not support dynamic LAG configuration or binding via some standard or
proprietary protocol. Examples of such protocols include Link Aggregation Control Protocol
(LACP) for dynamic 802.3ad and Cisco’s Port Aggregation Protocol (PAgP) for dynamic
EtherChannel negotiation. It is possible to configure Avaya Hunt Groups to interoperate with
third-party vendors. Forcing a LAG to be formed statically with a third-party vendor device
without dynamic protocol negotiation is normally used for interoperability.
Enterprise-level servers are often deployed with a dual port Network Interface Card (NIC), also
referred to as an adapter, to improve application response time and availability. Most dual port
adaptor vendors provide the option to team both ports together for link aggregation via 802.3ad,
EtherChannel or other proprietary mechanism.
These Application Notes discuss how the Avaya Hunt Group feature and load-sharing algorithm
can be combined with Intel Dual Port Server Adapters implementing either static
FastEtherChannel (FEC)/LAG or static GigabitEtherChannel(GEC)/LAG with 802.1Q enabled.
The specific Intel NIC cards validated were the Intel PRO/100+ Dual Port Server Adapter and
PRO/1000MT Dual Port Server Adapter. Figure 1 shows the sample configuration that was
verified.
GAK; Reviewed:
WCH 7/7/2003
Solution & Interoperability Test Lab Application Notes
The following equipment and software were used for the sample configuration provided:
Equipment Software
Server with Intel PRO/100+ Dual
Port Server Adapter
Server with Intel PRO/1000MT Dual
Port Server Adapter
Avaya™ P882 Gigabit Ethernet
Switch
Microsoft Windows 2000 Server with Intel
Adapter Driver 6.4 with PROSet
Microsoft Windows 2000 Server with Intel
Adapter Driver 6.4 with PROSet
Version 5.4 Gigabit Ethernet Switch
Software
2 - M8024-100TX modules
1 - M8008R-1000T modules
Two Target PC’s equipped with
Microsoft Windows 2000 Professional
3Com 100BaseTX Adapters
3. Avaya™ P882 Switch Web Agent Administration
3.1. Create the Virtual LAN
1. Select Cajun Router ! L2 Switching !!!! VLANs !!!! Configuration from the Web Agent.
The VLAN Configuration window opens (Figure 2).
GAK; Reviewed:
WCH 7/7/2003
Solution & Interoperability Test Lab Application Notes
4. Select vlan100 from the Port VLAN drop-down menu.
5. Select IEEE 802.1Q from the Trunk Mode drop-down menu.
6. Click the APPLY button.
Notes: It is only necessary to configure VLAN information for the first port that will be
added to the Hunt Group. When the first port is added to the Hunt Group, it is designated as
the “Base Port” and all other member ports will assume the identity of the base port.
Unknown unicast and broadcast traffic is flooded on the base port only. If multiple VLANs
are being statically mapped (via the CLI) to Hunt Group member ports, then each member
port must be configured with the VLANs individually before configuring them as Hunt
Group members.
GAK; Reviewed:
WCH 7/7/2003
Solution & Interoperability Test Lab Application Notes
3. Select port name Port 4.4 under the Name column. The Switch Port Configuration for
Port 4.4 window opens (Figure 12).
Figure 12: Switch Port Configuration for Port 4.4
4. Select vlan100 from the Port VLAN drop-down menu.
5. Select IEEE 802.1Q from the Trunk Mode drop-down menu.
6. Click the APPLY button.
Notes: Configure the first port in the Hunt Group with VLAN information. The first port
will be added to the Hunt Group and is designated as the “Base/Root Port”. All other ports
will assume the identity of the base port.
GAK; Reviewed:
WCH 7/7/2003
Solution & Interoperability Test Lab Application Notes