VMware vSphere

 View Only
Expand all | Collapse all

No Network Connection after Migration

  • 1.  No Network Connection after Migration

    Posted Jan 22, 2019 04:47 PM

    Dear Community

    We are operating several ESXI Hosts with various servers.

    We have an infrastructure counting 7 servers in a separate VLAN. We have recently introduced a new host an wanted to migrate all 7 servers on the new host.

    When migrating the DomainController, we do not manage to have Internet Connection; "unknown network" is displayed. When leaving the domain controller on the old ESXI host and migrating the other 6 servers, we have made the experience that 2 servers have network and the other 4 have not.

    Versions used:

    New Host: VMware ESXi, 6.5.0, 8294253

    Old Host: VMware ESXi, 6.0.0, 3620759

    Servers:

    Domain Controller: Server 2012R2, VM-Version 11

    Other Servers: Server 2012R2, VM-Version 8

    One Server: Server 2016, VM-Version 11

    We have already checked our infrastructure regarding VLAN configuration. It seems all ok there, especially as two servers are running.

    Is this a known issue?

    Many thanks,

    Marianne



  • 2.  RE: No Network Connection after Migration

    Posted Jan 22, 2019 04:57 PM

    Is there a portgroup on the new host for that vlan, and if your check that configuration does it show the correct vlan tag. Look at the "

    To configure a VLAN on the portgroup using the VMware Infrastructure/vSphere Client:"

    in the kb article if you aren't sure where to look.

    VMware Knowledge Base



  • 3.  RE: No Network Connection after Migration

    Posted Jan 22, 2019 05:08 PM

    Dear Sjesse

    Yes, we have a port group configured with the correct VLAN tag. An two servers are operational in this VLAN, which wouldn't be the case otherwise.



  • 4.  RE: No Network Connection after Migration

    Posted Jan 22, 2019 05:15 PM

    On the vmware host where your not getting a connection, sorry I just want to be clear, I'm only referring to the virtual switches in vmware. Where is "unknown network" coming from?



  • 5.  RE: No Network Connection after Migration

    Posted Jan 23, 2019 04:10 PM

    Thanks for your inputs.

    The unknown network ist on the Network configuration on the VM (Server 2012R2 and Server 2016); as we are operating servers in German, maybe the correct wording is different. A ping isn’t possible tot he DC nor to the Default Gateway.



  • 6.  RE: No Network Connection after Migration

    Posted Jan 22, 2019 05:21 PM

    Are all 7 VMs configured to use the same port group name?

    Do each of the VMs only have a single network adapter?

    Can you post a screenshot of the virtual switch configuration from the new ESXi host and the old ESXi host?

    Have you got the physical switch ports configured correctly for the VLAN? If you have multiple NICs from the virtual switch to the physical switch what load balancing method are you using? 



  • 7.  RE: No Network Connection after Migration

    Posted Jan 23, 2019 04:12 PM

    Thanks for your inputs.

    All 7 VMs are in the same port group, named «KIT 3119 Cloud» on the Print Screen.
    The virtual switch details of both hosts are documented as per attachment. The difference is, that the old host has one active nic (10GB) and 2 Standy-Adapters (1GB) für VM network, the new host has only one active nic (10GB).
    Do we have an issue with load balancing in the settings «teaming and failover»? It is set on «Route based on the originating virtual port» on both hosts, also on the one with only one nic.
    The physical switch ports of both hosts are configured the same, however not on the same hardware. The old host ist attached to a Layer 3 ZYXEL switch (10GB), the new host on a Layer 2 Cisco switch (10GB).



  • 8.  RE: No Network Connection after Migration

    Posted Jan 22, 2019 05:49 PM

    ... and migrating the other 6 servers, we have made the experience that 2 servers have network and the other 4 have not.

    Are the migrated VMs - which are on the same port group - able to reach each other?

    For me this looks like some kind of an enabled port security on the physical switch. In case you have multiple network adapters (vmnics) connected to the vSwitch, please ensure that all the physical ports are configured identically.

    What may also help with troubleshooting the isse is to run esxtop from the host's command line. This will show you, which vmnic is used for each of the VMs (press "n" for "network" in esxtop).

    André.



  • 9.  RE: No Network Connection after Migration

    Posted Jan 23, 2019 04:12 PM

    Thanks for your input.

    Yes, the two servers which have been migrated can reach each other. I will check the physical switch setup with the provider tomorrow; we cannot see any errors.



  • 10.  RE: No Network Connection after Migration

    Posted Jan 22, 2019 11:47 PM

    Something I've run in to before is setting a VLAN tag on the port group when the native VLAN is the VLAN you want.  If that's the case, double check to see if the portgroup native VLAN is the same as the one you tagged.  If so, try removing the tag from the portgroup configuration.  Also check to see if there's a limit on the number of ports available on the virtual switch.  That can do it as well.  If you didn't touch it to start with, then I wouldn't see why that would be an issue, but always good just to double-check.



  • 11.  RE: No Network Connection after Migration

    Posted Jan 23, 2019 04:14 PM

    Thanks for your inputs.

    I think the attached screenshots to cjsol’s input will also answer your questions.



  • 12.  RE: No Network Connection after Migration

    Posted Jan 23, 2019 04:13 PM

    The unknown network ist on the Network configuration on the VM

    Can you change this to what its support to be, if its unknown the port group its expects isn't available.



  • 13.  RE: No Network Connection after Migration

    Posted Jan 23, 2019 04:56 PM

    It is configured manually with IP, subnet and default gateway. It returns "unknown" as the DC ist not reachable. The configuration is the same on the two servers that are working, only another IP, of course. Same VLAN.