Hi all

I will move servers into Hyper-V environment and I need to ask a question
about virtual network configuration. Below are the current and projected
network schemas:

http://img32.imageshack.us/img32/705/networkga.png



In Hyper-V, I've got 3 network cards. Can you advice any configuration,
where should I begin then what would be the next steps.

Thanks in advance.

Hi Nime,

ok - as you have 3 networks cards that would be for now enough and cover
your current needs - 1xManagement, 1x Internal LAN (Switch), 1x External WAN
(Router).

I would not add the management adapter to Hyper-V networks and let it
dedicated for management OS. Then you need to configure 2 "external"
networks which you name like where the physical adapter is connected
(Internal/External) and uncheck "Allow management OS to share this
adapter...". With that you configure the physical NICs dedicated for Hyper-V
and all well known protocols (TCP/IP, Client for MS Networks...) will be
removed from this adapter and an "Microsoft Virtual Network Switch" Protocol
installed. Do not change this configuration ! Then you only need to add 2
vNICs within your VMs and connect them to each network via the Hyper-V
Manager -> VM Settings -> Network.

I addition i would also recommend to you the following 2 links :
Understand Hyper-V Networking
http://www.microsoft.com/downloads/d...4-62b925ed7eea

Understanding Networking in Hyper-V
http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx

PS : This design does rely on Windows 2008 R2 Hyper-V, where you can
dedicate an adapter to Hyper-V via the GUI -> Hyper-V Manager -> Network
Settings.

If you have any further questions please let me know.

Regards
Ramazan




"Nime" <eminakbulut@newsgroup> wrote in message
news:E2272D4F-DCE3-4D5F-8F81-56720E331A99@newsgroup

> Hi all
>
> I will move servers into Hyper-V environment and I need to ask a question
> about virtual network configuration. Below are the current and projected
> network schemas:
>
> http://img32.imageshack.us/img32/705/networkga.png
>
> In Hyper-V, I've got 3 network cards. Can you advice any configuration,
> where should I begin then what would be the next steps.
> Thanks in advance.

Hi Florian,

yes you got it :-)

If you have 8 pNICs (I believe 2 x intel quadport) in your system available
I would work with teaming if supported by your hardware vendor
(intel/broadcom works like a charm) for the external networks. Please read
the hardware vendors documentation here about installing teaming in
combination with Hyper-V there are normally some add. steps to take.

> So if virtual servers must be able to communicate with i.e. clients on the
> LAN, VMs must be connected to the 'external' NIC, right?

correct.

> Let's say I have one DC, one Exchange Server. Each of them must be
> reachable by clients. So I connect each VM to the same 'external' NIC?

correct (you should use here a teamed adapter as your external network and
connect the VMs to it).

Steps by Step:
1. Create Teaming for Hyper-V comm + 1 x management adapter (check with
Hardware vendor about installation order here)
2. Configure Hyper-V Networks
2a. Create external network and bind to teamed external adapter
2b. uncheck "Allow management OS to share this adapter"
2c. Bind your VMs which do need external communication (like exchange,DC..)
to this network
2d. Hyper-V will not add an additional NICs to your hosts network and will
uninstall the protocolls. do not change/configure anything on this network
(teamed external adaper) properties !

If you have any further questions please let me know.

Regards
Ramazan

"Florian Brenner" <fbrenner@newsgroup> wrote in message
news:0F15902B-2390-4794-A070-D529CA168E07@newsgroup

> So if virtual servers must be able to communicate with i.e. clients on the
> LAN, VMs must be connected to the 'external' NIC, right?
> When using 'external' NICs, Is network traffic sent from one VM to another
> going through the physical switch/network infrastructure or does it route
> internally? Let's say I have one DC, one Exchange Server. Each of them
> must be reachable by clients. So I connect each VM to the same 'external'
> NIC?
>
> I have 8 NICs in my Hyper-V host and til now connected each virtual NIC to
> a physical. That' nonsense as I understand now
>
> Thanks,
> Florian
>
>
> "RCan" <noospam@newsgroup> wrote in message
> news5E12675-41A9-4EE6-AF3A-02C5F4D0678F@newsgroup

>> Hi Nime,
>>
>> ok - as you have 3 networks cards that would be for now enough and cover
>> your current needs - 1xManagement, 1x Internal LAN (Switch), 1x External
>> WAN (Router).
>>
>> I would not add the management adapter to Hyper-V networks and let it
>> dedicated for management OS. Then you need to configure 2 "external"
>> networks which you name like where the physical adapter is connected
>> (Internal/External) and uncheck "Allow management OS to share this
>> adapter...". With that you configure the physical NICs dedicated for
>> Hyper-V and all well known protocols (TCP/IP, Client for MS Networks...)
>> will be removed from this adapter and an "Microsoft Virtual Network
>> Switch" Protocol installed. Do not change this configuration ! Then you
>> only need to add 2 vNICs within your VMs and connect them to each network
>> via the Hyper-V Manager -> VM Settings -> Network.
>>
>> I addition i would also recommend to you the following 2 links :
>> Understand Hyper-V Networking
>> http://www.microsoft.com/downloads/d...4-62b925ed7eea
>>
>> Understanding Networking in Hyper-V
>> http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
>>
>> PS : This design does rely on Windows 2008 R2 Hyper-V, where you can
>> dedicate an adapter to Hyper-V via the GUI -> Hyper-V Manager -> Network
>> Settings.
>>
>> If you have any further questions please let me know.
>>
>> Regards
>> Ramazan
>>
>>
>>
>>
>> "Nime" <eminakbulut@newsgroup> wrote in message
>> news:E2272D4F-DCE3-4D5F-8F81-56720E331A99@newsgroup

>>> Hi all
>>>
>>> I will move servers into Hyper-V environment and I need to ask a
>>> question
>>> about virtual network configuration. Below are the current and projected
>>> network schemas:
>>>
>>> http://img32.imageshack.us/img32/705/networkga.png
>>>
>>> In Hyper-V, I've got 3 network cards. Can you advice any configuration,
>>> where should I begin then what would be the next steps.
>>> Thanks in advance.

>>

Hi Florian,

as MS would say here, please release first the teaming and check if the
problem persists :-)
At teaming with Hyper-V it is really important to read the 3rd party vendors
documentation for support and setting up teaming with Hyper-V.

Like I know from HP to install first hyper-v before you install /configure
teaming software like.
http://www.google.com/url?sa=t&sourc...jH9F3h9bc-G8uw

Genereal Support Policy for Teaming with Hyper-V
http://support.microsoft.com/kb/968703

Can you contact Dell for getting docs about how to setup their broadcom
adapters with teaming and Hyper-V ? I'm sure (99%) is is the same example
that the hyper-v NDIS drivers must be installed first before you configure
broadcom teaming.

Regards
Ramazan

"Florian Brenner" <fbrenner@newsgroup> wrote in message
news:9C72E2EE-41B0-41CF-8BB4-8A0908B3A543@newsgroup

> Hi RCan,
>
> I installed several VMs according to your recommendations using the two
> Broadcom onboard NICs for management and 3 Intel Dualport NICs for the
> VMs. Unfortuanately I can't ping anything outside the Hyper-V host
> (destination unreachable). Before I setup the VMs I installed all recent
> drivers from the Dell Homepage to be able to configure NIC teaming which
> is not possible with the built in drivers.
>
> Can this be a configuration issue or are those drivers buggy? I don't
> think there is something that can be misconfigured.
>
> BTW: It's a Dell PowerEdge 2900III with 3 Intel MT1000 Dual Port NICs.
>
> I'm going to reinstall the server to check if it works with the original
> drivers.
>
> Thanks,
> Florian
>
>
>
> "RCan" <noospam@newsgroup> wrote in message
> news:853569D2-2235-4D0D-9FC3-018D59F4D9F8@newsgroup

>> Hi Florian,
>>
>> yes you got it :-)
>>
>> If you have 8 pNICs (I believe 2 x intel quadport) in your system
>> available I would work with teaming if supported by your hardware vendor
>> (intel/broadcom works like a charm) for the external networks. Please
>> read the hardware vendors documentation here about installing teaming in
>> combination with Hyper-V there are normally some add. steps to take.
>>

>>> So if virtual servers must be able to communicate with i.e. clients on
>>> the LAN, VMs must be connected to the 'external' NIC, right?

>>
>> correct.
>>

>>> Let's say I have one DC, one Exchange Server. Each of them must be
>>> reachable by clients. So I connect each VM to the same 'external' NIC?

>>
>> correct (you should use here a teamed adapter as your external network
>> and connect the VMs to it).
>>
>> Steps by Step:
>> 1. Create Teaming for Hyper-V comm + 1 x management adapter (check with
>> Hardware vendor about installation order here)
>> 2. Configure Hyper-V Networks
>> 2a. Create external network and bind to teamed external adapter
>> 2b. uncheck "Allow management OS to share this adapter"
>> 2c. Bind your VMs which do need external communication (like
>> exchange,DC..) to this network
>> 2d. Hyper-V will not add an additional NICs to your hosts network and
>> will uninstall the protocolls. do not change/configure anything on this
>> network (teamed external adaper) properties !
>>
>> If you have any further questions please let me know.
>>
>> Regards
>> Ramazan
>>
>> "Florian Brenner" <fbrenner@newsgroup> wrote in message
>> news:0F15902B-2390-4794-A070-D529CA168E07@newsgroup

>>> So if virtual servers must be able to communicate with i.e. clients on
>>> the LAN, VMs must be connected to the 'external' NIC, right?
>>> When using 'external' NICs, Is network traffic sent from one VM to
>>> another going through the physical switch/network infrastructure or does
>>> it route internally? Let's say I have one DC, one Exchange Server. Each
>>> of them must be reachable by clients. So I connect each VM to the same
>>> 'external' NIC?
>>>
>>> I have 8 NICs in my Hyper-V host and til now connected each virtual NIC
>>> to a physical. That' nonsense as I understand now
>>>
>>> Thanks,
>>> Florian
>>>
>>>
>>> "RCan" <noospam@newsgroup> wrote in message
>>> news5E12675-41A9-4EE6-AF3A-02C5F4D0678F@newsgroup
>>>> Hi Nime,
>>>>
>>>> ok - as you have 3 networks cards that would be for now enough and
>>>> cover your current needs - 1xManagement, 1x Internal LAN (Switch), 1x
>>>> External WAN (Router).
>>>>
>>>> I would not add the management adapter to Hyper-V networks and let it
>>>> dedicated for management OS. Then you need to configure 2 "external"
>>>> networks which you name like where the physical adapter is connected
>>>> (Internal/External) and uncheck "Allow management OS to share this
>>>> adapter...". With that you configure the physical NICs dedicated for
>>>> Hyper-V and all well known protocols (TCP/IP, Client for MS
>>>> Networks...) will be removed from this adapter and an "Microsoft
>>>> Virtual Network Switch" Protocol installed. Do not change this
>>>> configuration ! Then you only need to add 2 vNICs within your VMs and
>>>> connect them to each network via the Hyper-V Manager -> VM Settings ->
>>>> Network.
>>>>
>>>> I addition i would also recommend to you the following 2 links :
>>>> Understand Hyper-V Networking
>>>> http://www.microsoft.com/downloads/d...4-62b925ed7eea
>>>>
>>>> Understanding Networking in Hyper-V
>>>> http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
>>>>
>>>> PS : This design does rely on Windows 2008 R2 Hyper-V, where you can
>>>> dedicate an adapter to Hyper-V via the GUI -> Hyper-V Manager ->
>>>> Network Settings.
>>>>
>>>> If you have any further questions please let me know.
>>>>
>>>> Regards
>>>> Ramazan
>>>>
>>>>
>>>>
>>>>
>>>> "Nime" <eminakbulut@newsgroup> wrote in message
>>>> news:E2272D4F-DCE3-4D5F-8F81-56720E331A99@newsgroup
>>>>> Hi all
>>>>>
>>>>> I will move servers into Hyper-V environment and I need to ask a
>>>>> question
>>>>> about virtual network configuration. Below are the current and
>>>>> projected
>>>>> network schemas:
>>>>>
>>>>> http://img32.imageshack.us/img32/705/networkga.png
>>>>>
>>>>> In Hyper-V, I've got 3 network cards. Can you advice any
>>>>> configuration,
>>>>> where should I begin then what would be the next steps.
>>>>> Thanks in advance.
>>>>

Hi Florian,

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 helds

Regards
Ramazan

"Florian Brenner" <fbrenner@newsgroup> wrote in message
news:#KwI7imsKHA.1352@newsgroup

> Thanks for the reply but neither the teamed NICs worked nor the not-teamed
>
>
> Florian
>
> "RCan" <noospam@newsgroup> wrote in message
> news:793635AA-492B-44BD-934B-125C2F393149@newsgroup

>> Hi Florian,
>>
>> as MS would say here, please release first the teaming and check if the
>> problem persists :-)
>> At teaming with Hyper-V it is really important to read the 3rd party
>> vendors documentation for support and setting up teaming with Hyper-V.
>>
>> Like I know from HP to install first hyper-v before you install
>> /configure teaming software like.
>> http://www.google.com/url?sa=t&sourc...jH9F3h9bc-G8uw
>>
>> Genereal Support Policy for Teaming with Hyper-V
>> http://support.microsoft.com/kb/968703
>>
>> Can you contact Dell for getting docs about how to setup their broadcom
>> adapters with teaming and Hyper-V ? I'm sure (99%) is is the same example
>> that the hyper-v NDIS drivers must be installed first before you
>> configure broadcom teaming.
>>
>> Regards
>> Ramazan
>>
>> "Florian Brenner" <fbrenner@newsgroup> wrote in message
>> news:9C72E2EE-41B0-41CF-8BB4-8A0908B3A543@newsgroup

>>> Hi RCan,
>>>
>>> I installed several VMs according to your recommendations using the two
>>> Broadcom onboard NICs for management and 3 Intel Dualport NICs for the
>>> VMs. Unfortuanately I can't ping anything outside the Hyper-V host
>>> (destination unreachable). Before I setup the VMs I installed all recent
>>> drivers from the Dell Homepage to be able to configure NIC teaming which
>>> is not possible with the built in drivers.
>>>
>>> Can this be a configuration issue or are those drivers buggy? I don't
>>> think there is something that can be misconfigured.
>>>
>>> BTW: It's a Dell PowerEdge 2900III with 3 Intel MT1000 Dual Port NICs.
>>>
>>> I'm going to reinstall the server to check if it works with the original
>>> drivers.
>>>
>>> Thanks,
>>> Florian
>>>
>>>
>>>
>>> "RCan" <noospam@newsgroup> wrote in message
>>> news:853569D2-2235-4D0D-9FC3-018D59F4D9F8@newsgroup
>>>> Hi Florian,
>>>>
>>>> yes you got it :-)
>>>>
>>>> If you have 8 pNICs (I believe 2 x intel quadport) in your system
>>>> available I would work with teaming if supported by your hardware
>>>> vendor (intel/broadcom works like a charm) for the external networks.
>>>> Please read the hardware vendors documentation here about installing
>>>> teaming in combination with Hyper-V there are normally some add. steps
>>>> to take.
>>>>
>>>>> So if virtual servers must be able to communicate with i.e. clients on
>>>>> the LAN, VMs must be connected to the 'external' NIC, right?
>>>>
>>>> correct.
>>>>
>>>>> Let's say I have one DC, one Exchange Server. Each of them must be
>>>>> reachable by clients. So I connect each VM to the same 'external' NIC?
>>>>
>>>> correct (you should use here a teamed adapter as your external network
>>>> and connect the VMs to it).
>>>>
>>>> Steps by Step:
>>>> 1. Create Teaming for Hyper-V comm + 1 x management adapter (check with
>>>> Hardware vendor about installation order here)
>>>> 2. Configure Hyper-V Networks
>>>> 2a. Create external network and bind to teamed external adapter
>>>> 2b. uncheck "Allow management OS to share this adapter"
>>>> 2c. Bind your VMs which do need external communication (like
>>>> exchange,DC..) to this network
>>>> 2d. Hyper-V will not add an additional NICs to your hosts network and
>>>> will uninstall the protocolls. do not change/configure anything on this
>>>> network (teamed external adaper) properties !
>>>>
>>>> If you have any further questions please let me know.
>>>>
>>>> Regards
>>>> Ramazan
>>>>
>>>> "Florian Brenner" <fbrenner@newsgroup> wrote in message
>>>> news:0F15902B-2390-4794-A070-D529CA168E07@newsgroup
>>>>> So if virtual servers must be able to communicate with i.e. clients on
>>>>> the LAN, VMs must be connected to the 'external' NIC, right?
>>>>> When using 'external' NICs, Is network traffic sent from one VM to
>>>>> another going through the physical switch/network infrastructure or
>>>>> does it route internally? Let's say I have one DC, one Exchange
>>>>> Server. Each of them must be reachable by clients. So I connect each
>>>>> VM to the same 'external' NIC?
>>>>>
>>>>> I have 8 NICs in my Hyper-V host and til now connected each virtual
>>>>> NIC to a physical. That' nonsense as I understand now
>>>>>
>>>>> Thanks,
>>>>> Florian
>>>>>
>>>>>
>>>>> "RCan" <noospam@newsgroup> wrote in message
>>>>> news5E12675-41A9-4EE6-AF3A-02C5F4D0678F@newsgroup
>>>>>> Hi Nime,
>>>>>>
>>>>>> ok - as you have 3 networks cards that would be for now enough and
>>>>>> cover your current needs - 1xManagement, 1x Internal LAN (Switch), 1x
>>>>>> External WAN (Router).
>>>>>>
>>>>>> I would not add the management adapter to Hyper-V networks and let it
>>>>>> dedicated for management OS. Then you need to configure 2 "external"
>>>>>> networks which you name like where the physical adapter is connected
>>>>>> (Internal/External) and uncheck "Allow management OS to share this
>>>>>> adapter...". With that you configure the physical NICs dedicated for
>>>>>> Hyper-V and all well known protocols (TCP/IP, Client for MS
>>>>>> Networks...) will be removed from this adapter and an "Microsoft
>>>>>> Virtual Network Switch" Protocol installed. Do not change this
>>>>>> configuration ! Then you only need to add 2 vNICs within your VMs and
>>>>>> connect them to each network via the Hyper-V Manager -> VM
>>>>>> Settings -> Network.
>>>>>>
>>>>>> I addition i would also recommend to you the following 2 links :
>>>>>> Understand Hyper-V Networking
>>>>>> http://www.microsoft.com/downloads/d...4-62b925ed7eea
>>>>>>
>>>>>> Understanding Networking in Hyper-V
>>>>>> http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
>>>>>>
>>>>>> PS : This design does rely on Windows 2008 R2 Hyper-V, where you can
>>>>>> dedicate an adapter to Hyper-V via the GUI -> Hyper-V Manager ->
>>>>>> Network Settings.
>>>>>>
>>>>>> If you have any further questions please let me know.
>>>>>>
>>>>>> Regards
>>>>>> Ramazan
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> "Nime" <eminakbulut@newsgroup> wrote in message
>>>>>> news:E2272D4F-DCE3-4D5F-8F81-56720E331A99@newsgroup
>>>>>>> Hi all
>>>>>>>
>>>>>>> I will move servers into Hyper-V environment and I need to ask a
>>>>>>> question
>>>>>>> about virtual network configuration. Below are the current and
>>>>>>> projected
>>>>>>> network schemas:
>>>>>>>
>>>>>>> http://img32.imageshack.us/img32/705/networkga.png
>>>>>>>
>>>>>>> In Hyper-V, I've got 3 network cards. Can you advice any
>>>>>>> configuration,
>>>>>>> where should I begin then what would be the next steps.
>>>>>>> Thanks in advance.
>>>>>>