Why would this be?

After an upgrade from ESX4.x to ESX5.x you notice that when you run the following command via the vMA: “esxcfg-vswif-I” you notice that there are no configure vswif interfaces listed. Why would this be?

A.
the service console is no longer available with vSphere 5. All vswif interfaces are removed during the upgrade

B.
during the upgrade process, vswif interfaces are disable by default, they’ll need to be enable before they will be listed

C.
the wrong command is being used. “vicfg-vswif-I” is the correct command to display all vswif interfaces

D.
during the upgrade process all vswif interfaces are migrated to vmk interfaces

Explanation:

For example, if the version 4.x ESX host has virtual NICs vmk0, vmk1, and vswif0, after the migration the new ESXi configuration will be vmk0, vmk1, and vmk2, where vmk2 is the management interface.


When you upgrade from ESXi 4.x to ESXi 5.x, the default maximum number of ports for a virtual switch changes from 64 to 128.
ESX hosts have two IP stacks, one for the vmkernel and one for the Service Console. Because ESXi hosts have only one IP stack, the migration cannot preserve both ESX default routes. After migration, the ESX Service Console default route becomes the single ESXi default route, replacing the vmkernel route. The change to a single ESXi default route might cause loss of connectivity for routed non-management traffic that originates from vmkernel. To restore vmkernel networking, you can configure static routes in addition to the default route.
All vswif interfaces are migrated to vmk interfaces. If a conflict is detected between two interfaces, one is left in disabled state. The upgrade disables any conflicting kernel IP addressing in favor of the management interface.
The migration to ESXi 5.0 disables any existing vmk virtual NIC that meets the following conditions.

  • The vmk virtual NIC has a manually configured (static) IP address.
  • The IP address is in the same subnet as a vswif virtual NIC that is being migrated to a switch containing the vmk virtual NIC.
  • The vmk and vswif NICs are both on the same virtual switch.

2 Comments on “Why would this be?

    1. admin says:

      When you upgrade from ESXi 4.x to ESXi 5.x, the default maximum number of ports for a virtual switch changes from 64 to 128.
      ESX hosts have two IP stacks, one for the vmkernel and one for the Service Console. Because ESXi hosts have only one IP stack, the migration cannot preserve both ESX default routes. After migration, the ESX Service Console default route becomes the single ESXi default route, replacing the vmkernel route. The change to a single ESXi default route might cause loss of connectivity for routed non-management traffic that originates from vmkernel. To restore vmkernel networking, you can configure static routes in addition to the default route.
      All vswif interfaces are migrated to vmk interfaces. If a conflict is detected between two interfaces, one is left in disabled state. The upgrade disables any conflicting kernel IP addressing in favor of the management interface.
      The migration to ESXi 5.0 disables any existing vmk virtual NIC that meets the following conditions.
      + The vmk virtual NIC has a manually configured (static) IP address.
      + The IP address is in the same subnet as a vswif virtual NIC that is being migrated to a switch containing the vmk virtual NIC.
      + The vmk and vswif NICs are both on the same virtual switch.


Leave a Reply

Your email address will not be published. Required fields are marked *