Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1443
  • Last Modified:

HP Nic Teaming and Cisco Switch

HI
Im looking at teaming together the two NIC that come with a HP DL380. I know Microsoft frowns on teaming on some servers ie DC's and exchange but i was wondering if anyone had successfully achieved this both at the server end windows 2003/8 and at the switch end ie Cisco 2960.
I dont see any point in teamng at the server side only surely the switch must also be sonfigured in some way.

Also would this be similar on a Hyper V environment?

Ta
0
kingcastle
Asked:
kingcastle
  • 2
1 Solution
 
vtopchievCommented:
I have done the teaming on these and it works fine - but only used the fault tolerance method - in this case each card is connected to a separate switch so in case one fails, the other one picks up.
Use the HP team application that should be in the server once all soft packs are installed to team it and that's it
0
 
Handy HolderSaggar makers bottom knockerCommented:
I wasn't aware MS frowned on teaming, would like to see link.

Switch assisted load balancing is the way to go if you've only got one switch, I would use Etherchannel rather than LACP since that doesn't need any negotiation protocol, but you do have to set it on both the server and the switch or it really misbehaves.
0
 
kingcastleAuthor Commented:
i assume i would simply use the hp teaming software to bind the nics and then pick switch assisted load balancing so that would be the server side done but how would i do the switch is it dificult to do on a Cisco 2960.

sorry not MS as such directly,  but some stuff on the net saying teaming not really a good way to go on Windows DCs and exchange as it may casuse problems and lead to difficult troubleshooting arising from hardware vendor/software and switch maker.

cheers


0
 
Handy HolderSaggar makers bottom knockerCommented:
Here's an example. HP's teaming was initially based on Cisco fast etherchannel (some is now open standard) so there shouldn't be vendor/software problems, but there again it can be fiddly and the drivers have to be setup properly.

http://www.cisco.com/en/US/tech/tk389/tk213/technologies_configuration_example09186a008089a821.shtml 
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now