<div>
You should be able to configure trunking on both ends at the same time, but having only ONE NIC active. If you manage to configure this, you should not have any problems as soon as you plug in the second NIC. But prepare to loose network connection for a short time.<br />
<br />
As long as you have configured trunking on one side only, but both NICs active, you will confuse either the switch or the NIC driver.<br />

</div>


<div>
Thanks. However I was looking for more specific information, like what the right settings are when creating the trunked ports on the switch. &nbsp;I need to know the following:<br />
<br />
&gt;Flow Control (enabled or disabled)<br />
&gt;LACP Status (disabled, active, or passive) for both ports<br />
&gt;Trunk Type (none, trunk, or LACP) for both ports<br />
&gt;Trunk Group (Both ports set to same group number?)
</div>


<div>
I suggest to use LACP, if NIC driver allow for it. Static trunking may work or not, it is proprietary - works in many cases, e.g. with Intel NIC and 3Com switches, but that's not guaranteed.<br />
LACP has to be configured on one device as active, on the other as passive. On the active side, I would set up the thresholds to &quot;always on&quot;, so the trunk is used all the time versus on demand.<br />
<br />
Flow control: always on!<br />
<br />
Both ports must be set to the same trunk group. Different groups = different trunks.<br />
<br />
&nbsp; 
</div>


<div>
I don't know why, but when I try to set the trunk port LACP status to ACTIVE or PASSIVE I get a message saying &quot;LACP Configuration Failed! Dynamic LACP not allowed on manual trunk port.&quot;.<br />
The ports are already set to Trunk Type LACP, so I dont know why it says they are manual. The current status of LACP is Disabled, so this is not going to work if I cannot set one to Active and the other to passive.
</div>


<div>
In the GUI, under configuration of ports in question, I have the choice of selecting LACP, Trunk, or none for each port, as well as the Trunk Group number, and LACP Status (Disable, Passive, or Active). In the selection of Trunk Group, (Trk1, Trk2, etc..) I don't have the option to select a Dynamic Group number (as defined in the manual as being Dyn1, Dyn2, etc..) so I think it can only be a static LACP trunk (selecting LACP Trunk type, and using Trk1 Group number). I tried selecting Trunk instead of LACP and it works with only one server NIC connected but if I connect the second server NIC of the team then I lose connectivity all together on the server. Would I need to specify a Team type selection in this case?, instead of automatic? Like 802.3ad?
</div>


<div>
Ok, as I understand Trunk is manual and LACP dynamic configuration. If using LACP, don't set trunks.<br />
<br />
Are you NICs allowing for LACP?<br />

</div>


<div>
Actually, it seems both Trunk and LACP are manual in my case. They both only have the option for Tk1, Tk2, etc.. for Trunk Group identifiers, which according to the manual means manual. Plus the fact that I receive that error message when I try to set Active or Passive regardless if picking Trunk or LACP. There must be both manual and dynamic versions of LACP according to what I am seeing. I don't see how I can use Trunk Group Dyn1, Dyn2, etc... for the Trunk Group identifier in the GUI. This tells the switch that it is a Dynamic LACP Trunk if the Trunk Group name starts with Dyn. Perhaps this can only be done via command line or telnet or something?<br />
The NICs are set to auto in the section that deals with 802.3ad (LACP?) and things. <br />

</div>


<div>
802.3ad = LACP.<br />
What about leaving trunk group settings emtpy?<br />
<br />

</div>


<div>
Actually, I think it is working. I must of thought incorrectly before that it was not working because it is now. I set the trunk to LACP and it is working. I see the NIC's are reporting that they are in 802.3ad Dynamic mode now. The switch still shows the LACP status for the trunk ports as Disabled, but I am not going to worry about that if it works. Thanks
</div>


<div>
You are correct.<br />
<br />
Here is an example of my Trunk:<br />
<br />

<blockquote>
Port(s): &nbsp;B13 &nbsp;B17<br />
Port Enabled: &nbsp; Yes &nbsp;<br />
Mode: Auto<br />
Flow Control: &nbsp; EnableDisable ????<br />
LACP Status: &nbsp;Disabled<br />
Trunk Type: &nbsp; LACP <br />
Trunk Group: &nbsp;Trk3 
</blockquote>
<br />
You manually set the LACP mode by selecting the trunk type. LACP status is labelled incorrectly. It should be something like &quot;Auto LACP: Yes\No&quot; Disabled would be the same as no.<br />
<br />
I haev a question for everyone that posted here - What should the flow control be? It wants to default to disabled.<br />
<br />
Should I enable it?<br />
&nbsp;<br />

</div>


<div>
My understanding is that flow control should be left to disabled unless you have an old piece of equipment connected to the switch that throwing a lot of errors on the switch. In that case you could try flow control to see if it helps.
</div>


<div>
<div class="content wysiwyg-content">
I have several HP servers that have dual gigabit NIC's. They are teamed together on each server, providing 2Gb/s outgoing ethernet connections to the HP Procurve 5400zl being used as a core switch. I think that in order to obtain 2Gb/sec for incoming date, the two ports per server on the HP switch need to be trunked together. Can someone tell me the proper way to do this? I tried it once and it resulted in no network access to the server.
</div>
</div>


I have several HP servers that have dual gigabit NIC's. They are teamed together on each server, providing 2Gb/s outgoing ethernet connections to the HP Procurve 5400zl being used as a core switch. I think that in order to obtain 2Gb/sec for incoming date, the two ports per server on the HP switch need to be trunked together. Can someone tell me the proper way to do this? I tried it once and it resulted in no network access to the server.

How to set up Trunk Ports properly on HP ProCurve 5400zl switch

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.

Networking Hardware-Other

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.

Server Hardware

A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.