Is my Team set up correctly or is it creating a Broadcast Storm?

How is the team configured, NFT, SLB, etc?

adaptive load balancing

With a team, you're only showing one, or possibly two IP addresses depending on the configuration - this would be no different then connecting two individual devices to your switch.  That being said, I've never found the HP Teaming software to work all that well for load balancing - so you may want to try turning that off and just putting them into failover mode to see if things clear up a bit.  So really the team should in no way be causing a broadcast storm.

Are you sure the traffic is actually coming OUT of the team and not going to it?  How do you know the traffic is goingi to the broadcast address?  If you've capturred some packets, could you show the dumps?

This is actually Intel Teaming software.  Its running on a Dell server.  why would i be seeing ALOT of broadcast coming from the Team?  i can see the traffic when i run ethereal.  It actually shows broadcast and the MAC address goes to to the team.

Should I undo the team or leave as is?  Ill run ethereal again and post back.

thanks

I'm assuming you have the switch setup to do etherchannel or some other protocol?  How did you configure the switch?  

to make it easier, i changed the team over to link aggregation and did the same on the switch.

all seems well for now.  i guess i can close this case.

thanks

Interesting - if you're actually looking at the packets and confirming they're linked to the team, coming out of the team, and going to the broadcast IP then you're certainly correct that this type of traffic shouldn't be happening.  What was configured on the switch before since you mention "did the same on the switch"?

I'm wondering if somehow you created a loop in the network - which would absolutely cause a broadcast storm and explain the traffic you were seeing.  Does your switch support Spanning Tree?  If so, try turning that on and putting the configuration back the way it was when you were seeing the broadcast storm.  It may take a minute or two, but if you did end up creating a loop then Spanning Tree will find it and shut down one of the problem ports on the switch.

the switch had broadcast storm turned on and stp turned on.  i ran 3com's network supervisor and it didnt detect any loops in the network.

OK, well I know it's been a while but the question is still open and a final thought came to my mind.  Make sure your NICs are set to auto negotiation and not set directly to a particular speed/duplex setting (i.e. 100/full).  If they're set to auto, are they negotiating to the correct speed and duplex setting?

Is there that much traffic that an AFT is required?
I would think a gig card could handle most traffic and would use network fault tolerance for the nic teaming.