Entrar
 
HomeBibliotecaWikiAprenderGaleriaDownloadsSuporte ComunidadeFóruns
Recursos para Profissionais de TI >
> 
> 
Virtual Hyper-V NIC not connected even when physically connected

已答覆 Virtual Hyper-V NIC not connected even when physically connected

  • quinta-feira, 24 de abril de 2008 06:24
     
     
    Entrar para Votar
    0

    I am using a Windows Server Core installation.

     

    I have got 4 NICs.

    1. 2x OnBoard Intel with I/O Acceleration

    2. 1x Intel PT Dual Port adapter

     

    For testing I have now connected the LAN to the onBoard Port 1 and configured a new external network in the Hyper-V manager and named it LAN. This seems to work the guest system has network connection.

    Now I connected my VDSL modem to the first port of the Intel PT Pro adapter. I added a new external network in the Hyper-V manager and named it "T-Com". Now the problem is he is not changing the status to connected. If I type ipconfig /all I see the interface "T-Com" but it shows me that it is disconnected. When I connect the cable in the second Port I see that it is connected. This is a port which is not used by Hyper-V. I also recognized in the taskmanager that the interface is connected with 100 MBit /s. But switching to the configured "T-Com" interface it is not conencted anymore at any interface. Why?

     

    The device behind the interface is a device for my broadband connection. I need to deactivate the Client for Microsoft Networks and TCP/IP for this. But how do I realize this on Windows Server 2008 Core installation. By the way should this fix the problem?

    Does the Hyper-V virtual switch only marks the nic as connected when a ip address is given?

     

    Further configuration details:

    Because of the VDSL technology it is necessary to use VLANs. I need VLAN1 for the communication from modem to Router and VLAN7 for the connection.

    I tried to realize it with doeing following steps. As mentioned above I bound the interface which is connected to the VDSL modem to an extra external network. Then I added this interface, called "T-Com" to the virtual machine as new nic. Once as VLAN1 and second as VLAN7. So I added the same configured interface twice. But only with different VLAN configurations. I don't think that there should be any problems with the configuration? Or am I wrong?

     

Todas as Respostas

  • quinta-feira, 24 de abril de 2008 15:33
    Moderador
     
     Respondido
    Entrar para Votar
    0

    Okay..

     

    If I follow your post corrently  you have 4 NICs - 2 virtual switches.

     

    Virtual Switch "LAN" connected to your internal network workes fine.

    Virtual Switch "T-Com" does not work when any VMs are attached to it??  - do I have that right?

     

    Let's back up a bit

     

    First of all - the physical adapter being used by a Virtual Network cannot have an IP address

    (if your DSL modem requires that this physical interface has an IP address, then this will not work) it can only have the Virtual Network Switch Protocol turned on (turning on any other protocol at the physical NIC level will 'break' the interface and any virtual switch attached.

     

    A physical NIC can only have one virtual switch attached.

     

    Are you working with virtual machines attached to these switches?  or is all of your work at the Host VM partition?

     

    Your interface might show as disconnected at the console because if this physical adapter is a virtual switch and it does not 'see' a router or network traffic the OS might consider it disconnected.  (I am assuming that you checked the NIC indicator lights and they show connectivity)

    Attach a VM to this virtual network and see what that VM reports.  (if your DSL is running DHCP then the VM should pick up an address, etc.)

     

    the other way is to create a proxy VM that has a virtual NIC on an internal virtual switch (for vm to vm and host traffic) and a virtual NIC on the External T-Com Virtual Switch (to get the IP from the DSL connection).

     

    Also - if you set VLAN at the Virtual Network Switch level - that setting only pertains to the Parent Partition communication on that switch, not the VMs (each VM has it own VLAN setting on its own NIC).

     

    I know this is all a bit confusing.

    A background on networking: http://itproctology.blogspot.com/2008/04/networking-under-hyper-v-my-network.html