Home > Hyper-V, Virtualization, Windows 2008 R2 > Configuring Hyper-V network with HP Teaming software and VirtualConnect

Configuring Hyper-V network with HP Teaming software and VirtualConnect

Source

This is a very useful article so I translated it to English

Hello

These are the two basic documents

* HP Teaming
or Using HP ProLiant Network Teaming Software with Microsoft ® Windows ® Server 2008 with Hyper-V or Microsoft ® Windows ® Server 2008 R2 Hyper-V: http://h20000.www2.hp.com/bc/docs/support/SupportManual/ c01663264/c01663264.pdf

* Virtual Connect
HP Virtual Connect Ethernet or Cookbook: Single and Multi Enclosure Domain (Stacked) Scenarios: http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01990371/c01990371.pdf

My comments:

* Always Active Hyper-V role before installing the software Teaming (NCU). If this advice comes too late, simply rename cpqteam.dll (http://support.microsoft.com/kb/950792)
* In Server Core, or simply run HPTeam.cpl CPQTeam.cpl (older versions) to set the Teaming easily through graphical interface.
* As Team is generated and VLANs are added, they begin to proliferate NICs in the system. It is more than advisable to go renowned for having control at all times who is every thing (physical ports that make up the Team, associated with each VLAN NICs and switches that make up virtual, virtual NICs that are generated in Hyper-V parent partition and connected to virtual switches, etc.).
* There is a much easier way of doing things. That is only the Virtual Switch Hyper-V VLAN Tagging who does, for which either the Team or Virtual Connect we set these options (To do that, the Virtual Connect domain must be in “VLAN Tunneling” )
* The Proliant Support Pack, SmartStart, CD of the firmware, etc. are good traveling companions. The behavior of this may be very dependent on firmware versions, drivers and software

Regards

Advertisements
  1. November 16, 2010 at 5:14 pm

    You can simply boot the machine after virtualisation and deactivate the network. So you’re able to install new / additional drivers after virtualisation.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: