Avaya P882 manual Introduction

Page 2

1. Introduction

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 Load- Sharing 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:

Solution & Interoperability Test Lab Application Notes

2 of 31

WCH 7/7/2003

©2003 Avaya Inc. All Rights Reserved.

intel-lag-notes.doc

Page 1 Page 3
Image 2
Page 1 Page 3
Contents Abstract Introduction Create the Virtual LAN Avaya P882 Switch Web Agent AdministrationEquipment and Software Validated Configure Module 2 M8024R-100TX Switch Port Parameters Vlan ConfigurationModule Information Configure Module 3 M8024R-100TX Switch Port Parameters Switch Port Configuration for PortModule Information Switch Port Configuration for Port Configure Module 4 M8008R-1000T Switch Port Parameters Switch Ports reduced for brevitySwitch Port Configuration for Port Create and Assign an IP Interface to the Vlan IP InterfacesCreate the Hunt Groups Create Hunt GroupDisable Module 3 Ports Being Added to the Hunt Group Disable Module 4 Ports Being Added to the Hunt Group Physical Port Configuration Module 3 reduced for brevityPhysical Port Configuration Module Add Module 3 Ports to the Hunt GroupModule Information Switch Port Configuration for Port Add Module 3 Ports to the Hunt Group Switch Port Configuration for Port Enable the Module 3 Hunt Group Member Ports Enable the Module 4 Hunt Group Member Ports Physical Port Configuration Module 4 WindowIntel PRO/1000MT Dual Port Server Adapter Configuration Creating an Intel Link Aggregation Adapter TeamTeaming Wizard LAG Type Teaming Wizard Notification Teaming Wizard Membership Selection Popup PROSet II with GEC/LA/802.3adstatic Mode Team #0 Intel Adapter 802.1Q Trunk Configuration Adding Vlan to LAG via PROSet II GUIAdd New Vlan Popup Verification Steps Screen Shot of Adapters in Windows 2000 ServerConclusion Additional ReferencesAvaya Inc. All Rights Reserved
Top Page Image Contents