It has always been my understanding that if I configure multiple External
networks in Hyper-V R2 that virtual hosts on these networks can freely
communicate with each other and the LAN (assuming same subnet obviously) -
is this correct ? So for example host 192.168.30.3/24 on Virtual-network-1
can communicate with host 192.168.30.4/24 on Virtual-network-2 where each
virtual network/switch is bound to a specific physical NIC in the server.

Ian

Hi Ian,

"Ian Moran" <ianm@newsgroup> wrote
< .....where each virtual network/switch is bound to a specific physical NIC
in the server.

That is the point, when both pNICs are bound to the same subnet
(192.168.30.0/24) then they would be able to communicate to each other.
Why not team the adapters and bound all VMs to teamed adapter ? of course it
depends if your hardware vendor does support teaming for Hyper-V !

Regards
Ramazan

Good, I'm not going mad then :-)

I ask because PSS tell me otherwise and we're in the middle of attempting to
investigate why sometimes my virtual hosts on the same or different virtual
networks are unable to communicate.

All pointing to a Hyper-V/Broadcom NIC mess. No way will I attempt teaming
until basic comms works

Thanks Ramazan

"RCan" <noospam@newsgroup> wrote in message
news:85B7443D-9F6C-49B9-865F-8D03EA54DA50@newsgroup

> Hi Ian,
>
> "Ian Moran" <ianm@newsgroup> wrote
> < .....where each virtual network/switch is bound to a specific physical
> NIC in the server.
>
> That is the point, when both pNICs are bound to the same subnet
> (192.168.30.0/24) then they would be able to communicate to each other.
> Why not team the adapters and bound all VMs to teamed adapter ? of course
> it depends if your hardware vendor does support teaming for Hyper-V !
>
> Regards
> Ramazan

"Ian Moran" <ianm@newsgroup> wrote

> All pointing to a Hyper-V/Broadcom NIC mess. No way will I attempt teaming
> until basic comms works

Oh yes the good old broadcom drivers :-) I had also so much pain in the past
with it but newer releases are really good developed and work fine with
virtualization environments.

Would be great if you can share the outcome of the PSS investigation here.

Thanks
Ramazan

Well I've one more card to play re Broadcom. I have already installed the
latest drivers from the Dell web site but on the Broadcom site they have
newer ones again - they do say though to use the drivers form the hardware
vendor - so I've held back installing the newer drivers.

I knew something was up with the initial Hyper-v R2 install. Running
ipconfig from the parent partition showed full IP details of NICS that had
been added to Virtual networks (with Management unchecked). These NICS
should only have the Virtual Switch protocol bound to them so should not
show up in the parent partition when running ipconfig.

Ian



"RCan" <noospam@newsgroup> wrote in message
news:4A9C4B3F-8859-43EC-8E30-8D47241A7A7D@newsgroup

> "Ian Moran" <ianm@newsgroup> wrote

>> All pointing to a Hyper-V/Broadcom NIC mess. No way will I attempt
>> teaming until basic comms works

>
> Oh yes the good old broadcom drivers :-) I had also so much pain in the
> past with it but newer releases are really good developed and work fine
> with virtualization environments.
>
> Would be great if you can share the outcome of the PSS investigation here.
>
> Thanks
> Ramazan

Hi Ian,

that is correct - if the adapter were added dedicated (unchecked "Allow mgmt
OS to share adapter"), they should not be listed in the hosts ipconfig as
they should not have TCP/IP protocol, only the MS Virtual Switch protocol is
enabled here.

MS has released a really great command line tool from Keith M. which does
check/repair the protocol bindings on your NICs. Possibly you want to have a
look on this ->
http://blogs.technet.com/virtualizat...xternally.aspx
http://blogs.technet.com/jhoward/arc...-nvspbind.aspx

Regards
Ramazan

"Ian Moran" <ianm@newsgroup> wrote in message
news:e0gP2H0rKHA.4948@newsgroup

> Well I've one more card to play re Broadcom. I have already installed the
> latest drivers from the Dell web site but on the Broadcom site they have
> newer ones again - they do say though to use the drivers form the hardware
> vendor - so I've held back installing the newer drivers.
>
> I knew something was up with the initial Hyper-v R2 install. Running
> ipconfig from the parent partition showed full IP details of NICS that had
> been added to Virtual networks (with Management unchecked). These NICS
> should only have the Virtual Switch protocol bound to them so should not
> show up in the parent partition when running ipconfig.
>
> Ian
>
>
>
> "RCan" <noospam@newsgroup> wrote in message
> news:4A9C4B3F-8859-43EC-8E30-8D47241A7A7D@newsgroup

>> "Ian Moran" <ianm@newsgroup> wrote

>>> All pointing to a Hyper-V/Broadcom NIC mess. No way will I attempt
>>> teaming until basic comms works

>>
>> Oh yes the good old broadcom drivers :-) I had also so much pain in the
>> past with it but newer releases are really good developed and work fine
>> with virtualization environments.
>>
>> Would be great if you can share the outcome of the PSS investigation
>> here.
>>
>> Thanks
>> Ramazan

>

That looks fantastic, and along with the Hyper-V Powershell library I'd say
was pretty indispensable. Thanks.

"RCan" <noospam@newsgroup> wrote in message
news:OYvxzM0rKHA.4048@newsgroup

> Hi Ian,
>
> that is correct - if the adapter were added dedicated (unchecked "Allow
> mgmt OS to share adapter"), they should not be listed in the hosts
> ipconfig as they should not have TCP/IP protocol, only the MS Virtual
> Switch protocol is enabled here.
>
> MS has released a really great command line tool from Keith M. which does
> check/repair the protocol bindings on your NICs. Possibly you want to have
> a look on this ->
> http://blogs.technet.com/virtualizat...xternally.aspx
> http://blogs.technet.com/jhoward/arc...-nvspbind.aspx
>
> Regards
> Ramazan
>
> "Ian Moran" <ianm@newsgroup> wrote in message
> news:e0gP2H0rKHA.4948@newsgroup

>> Well I've one more card to play re Broadcom. I have already installed the
>> latest drivers from the Dell web site but on the Broadcom site they have
>> newer ones again - they do say though to use the drivers form the
>> hardware vendor - so I've held back installing the newer drivers.
>>
>> I knew something was up with the initial Hyper-v R2 install. Running
>> ipconfig from the parent partition showed full IP details of NICS that
>> had been added to Virtual networks (with Management unchecked). These
>> NICS should only have the Virtual Switch protocol bound to them so should
>> not show up in the parent partition when running ipconfig.
>>
>> Ian
>>
>>
>>
>> "RCan" <noospam@newsgroup> wrote in message
>> news:4A9C4B3F-8859-43EC-8E30-8D47241A7A7D@newsgroup

>>> "Ian Moran" <ianm@newsgroup> wrote
>>>> All pointing to a Hyper-V/Broadcom NIC mess. No way will I attempt
>>>> teaming until basic comms works
>>>
>>> Oh yes the good old broadcom drivers :-) I had also so much pain in the
>>> past with it but newer releases are really good developed and work fine
>>> with virtualization environments.
>>>
>>> Would be great if you can share the outcome of the PSS investigation
>>> here.
>>>
>>> Thanks
>>> Ramazan

>>

Well did a clean install of Windows 2008 Server R2 Standard and imported my
two virtual servers.
Installed Broadcom drivers from Dell
Removed all virtual NIC's from the servers and removed all virtual networks
in Hyper-V.
Rebooted virtual host
Created 2 virtual networks, one server on each, "Allow Management ..."
unchecked as I have a dedicated NIC for that
Fired up the two virtual servers (took ages to logon, understandably, no
networking) and installed Integration Services.
Rebooted Virtual servers.
Logon to virtual servers and configured networking, putting both on same
subnet.

Result:
Virtual servers can ping lan clients
Lan clients cannot ping virtual servers
Virtual host cannot ping virtual servers
Virtual servers cannot ping virtual host
Virtual servers cannot ping each other

So, moved both virtual servers to same External virtual network, no
difference.
Unchecked TCP/IP in Virtual NIC properties and re-checked - can now ping
virtual server from lan, virtual server can now ping host and LAN
Repeated for second server, same result, full connectivity to LAN, from LAN
and to/from virtual host and other virtual server

Anyone like to guess what on earth is going on ?

"RCan" <noospam@newsgroup> wrote in message
news:4A9C4B3F-8859-43EC-8E30-8D47241A7A7D@newsgroup

> "Ian Moran" <ianm@newsgroup> wrote

>> All pointing to a Hyper-V/Broadcom NIC mess. No way will I attempt
>> teaming until basic comms works

>
> Oh yes the good old broadcom drivers :-) I had also so much pain in the
> past with it but newer releases are really good developed and work fine
> with virtualization environments.
>
> Would be great if you can share the outcome of the PSS investigation here.
>
> Thanks
> Ramazan

Hi Ian,

here is a post from a other tread which has helped in a similar case :

--------------------------------------------
look I try to give you here a short overview how to setup your networking
environment with dedicated physical NICs (R2) without teaming :

1. Confgure Host networking (Public Interface = Management, others which are
dedicated for VMs can be ignored here)
1a. Add Public IP for your management adapter and connect hyper-v dedicated
(2 nd) NIC physically to the same public network
2. Install Hyper-V Role
3. Configure Hyper-V networking
3a. Add "External" network and bind this to 2nd physical NIC ! which hasn't
configured an IP and uncheck "allow management OS to share adapter"

With HP teaming it works like that way but again broadcom can has a
different implementation - check your hardware vendors docs :

1. Install OS
2. Install Hyper-V with OS installed NIC drivers
3. Install teaming software and configure OS & Hyper-V networking
4. Add your VMs vNICs and connect them to the created networks (3)
5. At VMs ceck in device manager when additions are installed that all
devices are ok
6. Configure IP from same physical network as OS in your and try to ping
------------------------------------------------------

Hope that helps to resolve your issues, cause hyper-v networking is really
rock solid when you configure it on the right way ;-)

Regards
Ramazan

"Ian Moran" <ianm@newsgroup> wrote in message
news:eO1sCFhsKHA.1476@newsgroup

> Well did a clean install of Windows 2008 Server R2 Standard and imported
> my two virtual servers.
> Installed Broadcom drivers from Dell
> Removed all virtual NIC's from the servers and removed all virtual
> networks in Hyper-V.
> Rebooted virtual host
> Created 2 virtual networks, one server on each, "Allow Management ..."
> unchecked as I have a dedicated NIC for that
> Fired up the two virtual servers (took ages to logon, understandably, no
> networking) and installed Integration Services.
> Rebooted Virtual servers.
> Logon to virtual servers and configured networking, putting both on same
> subnet.
>
> Result:
> Virtual servers can ping lan clients
> Lan clients cannot ping virtual servers
> Virtual host cannot ping virtual servers
> Virtual servers cannot ping virtual host
> Virtual servers cannot ping each other
>
> So, moved both virtual servers to same External virtual network, no
> difference.
> Unchecked TCP/IP in Virtual NIC properties and re-checked - can now ping
> virtual server from lan, virtual server can now ping host and LAN
> Repeated for second server, same result, full connectivity to LAN, from
> LAN and to/from virtual host and other virtual server
>
> Anyone like to guess what on earth is going on ?
>
> "RCan" <noospam@newsgroup> wrote in message
> news:4A9C4B3F-8859-43EC-8E30-8D47241A7A7D@newsgroup

>> "Ian Moran" <ianm@newsgroup> wrote

>>> All pointing to a Hyper-V/Broadcom NIC mess. No way will I attempt
>>> teaming until basic comms works

>>
>> Oh yes the good old broadcom drivers :-) I had also so much pain in the
>> past with it but newer releases are really good developed and work fine
>> with virtualization environments.
>>
>> Would be great if you can share the outcome of the PSS investigation
>> here.
>>
>> Thanks
>> Ramazan

>

Thanks Ramazan. Reading through the description below I can confirm that it
follows pretty much what I did. There's no rocket science here as far as I
can see, dedicate one NIC to Management and configure the other ports to
provide virtual networks for your guests as needed. With all virtual
networks using the same subnet then all guests should be able to see each
other and the Host if External network is chosen. Unfortunately I'm not
seeing this expected behavior - yet.

Ian

"RCan" <noospam@newsgroup> wrote in message
news:#Nww3PzsKHA.4752@newsgroup

> Hi Ian,
>
> here is a post from a other tread which has helped in a similar case :
>
> --------------------------------------------
> look I try to give you here a short overview how to setup your networking
> environment with dedicated physical NICs (R2) without teaming :
>
> 1. Confgure Host networking (Public Interface = Management, others which
> are
> dedicated for VMs can be ignored here)
> 1a. Add Public IP for your management adapter and connect hyper-v
> dedicated
> (2 nd) NIC physically to the same public network
> 2. Install Hyper-V Role
> 3. Configure Hyper-V networking
> 3a. Add "External" network and bind this to 2nd physical NIC ! which
> hasn't
> configured an IP and uncheck "allow management OS to share adapter"
>
> With HP teaming it works like that way but again broadcom can has a
> different implementation - check your hardware vendors docs :
>
> 1. Install OS
> 2. Install Hyper-V with OS installed NIC drivers
> 3. Install teaming software and configure OS & Hyper-V networking
> 4. Add your VMs vNICs and connect them to the created networks (3)
> 5. At VMs ceck in device manager when additions are installed that all
> devices are ok
> 6. Configure IP from same physical network as OS in your and try to ping
> ------------------------------------------------------
>
> Hope that helps to resolve your issues, cause hyper-v networking is really
> rock solid when you configure it on the right way ;-)
>
> Regards
> Ramazan
>
> "Ian Moran" <ianm@newsgroup> wrote in message
> news:eO1sCFhsKHA.1476@newsgroup

>> Well did a clean install of Windows 2008 Server R2 Standard and imported
>> my two virtual servers.
>> Installed Broadcom drivers from Dell
>> Removed all virtual NIC's from the servers and removed all virtual
>> networks in Hyper-V.
>> Rebooted virtual host
>> Created 2 virtual networks, one server on each, "Allow Management ..."
>> unchecked as I have a dedicated NIC for that
>> Fired up the two virtual servers (took ages to logon, understandably, no
>> networking) and installed Integration Services.
>> Rebooted Virtual servers.
>> Logon to virtual servers and configured networking, putting both on same
>> subnet.
>>
>> Result:
>> Virtual servers can ping lan clients
>> Lan clients cannot ping virtual servers
>> Virtual host cannot ping virtual servers
>> Virtual servers cannot ping virtual host
>> Virtual servers cannot ping each other
>>
>> So, moved both virtual servers to same External virtual network, no
>> difference.
>> Unchecked TCP/IP in Virtual NIC properties and re-checked - can now ping
>> virtual server from lan, virtual server can now ping host and LAN
>> Repeated for second server, same result, full connectivity to LAN, from
>> LAN and to/from virtual host and other virtual server
>>
>> Anyone like to guess what on earth is going on ?
>>
>> "RCan" <noospam@newsgroup> wrote in message
>> news:4A9C4B3F-8859-43EC-8E30-8D47241A7A7D@newsgroup

>>> "Ian Moran" <ianm@newsgroup> wrote
>>>> All pointing to a Hyper-V/Broadcom NIC mess. No way will I attempt
>>>> teaming until basic comms works
>>>
>>> Oh yes the good old broadcom drivers :-) I had also so much pain in the
>>> past with it but newer releases are really good developed and work fine
>>> with virtualization environments.
>>>
>>> Would be great if you can share the outcome of the PSS investigation
>>> here.
>>>
>>> Thanks
>>> Ramazan

>>