when you run the following command via the vMA: “esxcfg-vswif -l” you notice that their are no con

After an upgrade from ESX4.X to ESXi5.0 you notice that when you run the following command via the vMA: "esxcfg-vswif -l" you notice that their 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 -l" is the correct command to display all vswif interfaces.

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

One Comment on “when you run the following command via the vMA: “esxcfg-vswif -l” you notice that their are no con

  1. Scuall says:

    Some ESX 4.x and ESXi 4.x network settings stored in /etc/sysconfig/network are migrated in the upgrade or migration to ESXi 5.0. In the migration to ESXi 5.0, ESX Service Console virtual NICs (vswifs) are converted to ESXi virtual NICs (vmks).
    The distributed port group or dvPort that the virtual NICs connect to is also migrated. The Service Console port group is renamed as the Management Network port group. When vswifs are migrated to vmks, they are numbered to follow any existing vmk in sequence. 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.
    vSphere Upgrade – vSphere 5.0 page 77.


Leave a Reply

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