Nic Teaming and Cisco switch

[Ayman Altounji]

We have several servers configured with NIC teaming. The Primary and Secondary cards are connected to different Cisco Switches in different 6500 Catlysts . A bad fiber port caused us to install a new blade for our secondary connections. After installing the new blade and re-connecting the fiber we started to receive read and write errors on all of the servers. There were no errors in the event log or on Insight manager. What did we miss to reactivate the secondary NIC into the team. The only way to resolve this situation was to deactivate the switch for our secondary NIC's, which is where we are at this point with no secondary NIC connection.

Can someone help with the proper procedure to activate the NIC into the team.

[Ayman Altounji]

Make sure the common VLAN for the IP segment is presented on both switches. The primary and secondary connections need to talk to each other, especially if heatbeat is enabled.

[Seth Cohen]

I am having the same problems, with either the latest teaming software/nic driver, or the SS 5.40 set of drivers. We have many servers (360, 380, 580) with 1 100meg port on each 6509, and they intermittently and unpredictably lose connectivity unless there is a lot of activity.

Could really use some help in troubleshooting, we've tried just about everything.

[Tony Glynn_1]

What sort of teaming are you running? Cisco FEC? If you are connected to different switches then check are they trunked properly in the switch. I would try not to use Cisco FEC and run ALB - It doesn't rely on protocol support in the switches, gives you full transmit bandwith (most apps are >80% read)