- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Re: Teaming Network Cards
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2009 03:01 PM
08-27-2009 03:01 PM
does anyone know how to team nic's in windows 2003 standard server SP 2 that is installed as a guest OS on ESX 3.5u4. the windows server see's 4 VMware Accelerated AMD PCNet Adapter network cards. The physical hardware is HP BL680c G5 blade server.
Is there a driver/configuration steps that need to be followed to get teaming to work.
Thanks for your help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2009 08:10 AM
08-28-2009 08:10 AM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2009 11:15 PM
09-01-2009 11:15 PM
Re: Teaming Network Cards
you can check with below link.
http://download.cnet.com/HP-Network-Teaming-Virtual-Miniport-Driver/3000-2112_4-80628.html
OR
you can check with post
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=1137825&prodNameId=3288122&swEnvOID=1005&swLang=8&taskId=135&swItem=MTX-7270a56016c04f62a3a5f1a56e&mode=3
Good Luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2009 09:04 AM
09-02-2009 09:04 AM
Re: Teaming Network Cards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2009 01:33 AM
09-03-2009 01:33 AM
Re: Teaming Network Cards
the windows server see's 4 VMware Accelerated AMD PCNet Adapter network cards
<<<
IMO the "hardware" vendor must supply support for teaming. so that would be VMWare not HP.
Furthermore these virtual adapters are connected to VMWare virtual switches. For this to work, they must support teaming (or link aggregation) too!
In the first post there is a reference to a thread that states communication is at bus-speed (for VMWare it's memory-to-memory ) even though windows reports 1GB link.
so there's no need to combine two NICs so windws can report 2GB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2009 04:12 AM
11-24-2009 04:12 AM
Re: Teaming Network Cards
The basic command syntax is:
vimsh -n -e "hostsvc/net/vswitch_setpolicy --nicteaming-policy [load balance option] [vSwitch#]"
For each of the 4 load balancing options there is a different command option:
Load Balance Type Command Option
Port ID loadbalance_srcid
IP Hash loadbalance_ip
MAC loadbalance_srcmac
Failover Only failover_explicit
For example to change vSwitch1 from the default Port ID to IP address load balancing the command line would look like this:
vimsh -n -e "hostsvc/net/vswitch_setpolicy --nicteaming-policy loadbalance_ip vSwitch1"
This should help those who like to run automated scripted ESX builds. Note that if using in conjunction with esxcfg commands to create and bind vSwtiches you'll need to run a service management restart and put a 20 second or so sleep to allow background processes to complete, eg: this script creates a vSwitch, labels it Production, binds vmnic 1 & 2 to it, restarts hostd, pauses for 20 seconds then modifies loadbalancing of the vSwitch to the MAC based option.
esxcfg-vswitch -a vSwitch2
esxcfg-vswitch -A Production vSwitch2
esxcfg-vswitch -L vmnic2 vSwitch2
esxcfg-vswitch -L vmnic1 vSwitch2
vimsh -n -e "/internalsvc/refresh_network"
vimsh -n -e "hostsvc/net/vswitch_setpolicy --nicteaming-policy loadbalance_srcmac vSwitch2"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2009 06:55 AM
12-11-2009 06:55 AM