Migrate an Existing Virtual Adapter to a vSphere Distributed Switch & vice versa

Migrate an Existing Virtual Adapter to a vSphere Distributed Switch

You can migrate an existing virtual adapter from a vSphere standard switch to a vSphere distributed switch.
Procedure
1 Log in to the vSphere Client and select the Hosts and Clusters inventory view.

2 Select the host in the inventory pane.
3 On the host Configuration tab, click Networking.
4 Select the vSphere Distributed Switch view.

5 Click Manage Virtual Adapters.

6 Click Add.

7 Select Migrate existing virtual network adapters and click Next.

8 Select one or more virtual network adapters to migrate.

9 For each selected adapter, choose a port group from the Select a port group drop-down menu.

10 Click Next.

11 Click Finish.

---

Migrate an existing virtual adapter from a vSphere distributed switch to a vSphere standard switch.

Procedure
1 Log in to the vSphere Client and select the Hosts and Clusters inventory view.
2 Select the host in the inventory pane.
3 On the host Configuration tab, click Networking.
4 Select the vSphere Distributed Switch view.

5 Click Manage Virtual Adapters.

6 Select the virtual adapter to migrate, and click Migrate.

7 Select the standard switch to migrate the adapter to and click Next.

8 Enter a Network Label and optionally a VLAN ID for the virtual adapter, and click Next.

9 Click Finish to migrate the virtual adapter and complete the wizard.

migration FROM CLASSIC ESX4.0 TO ESXI5.0 SCREEN CAST-post 02

NETWORKING CHANGES

AFTER MIGRATION SERVICE CONSOLE IS CHANGED TO MANAGEMENT NETWORK

---

DNS & ROUTING CHANGES

DOMAIN INFORMATION WAS LOST DURING MIGRATION

---

FIREWALL CHANGES

 

ALL CHANGES MADE IN FIREWALL GUI GETS CARRIED OVER E.G. NFS CLIENT, SSH CLIENT

---

HOST SUMMARY SCREEN CHANGES

MEMORY UTILIZATION FOUND INCREASED

migration FROM CLASSIC ESX4.0 TO ESXI5.0 SCREEN CAST-post 01

CONFIGURATION –> PROCESSOR CHANGES (NO CHANGE)

---

CONFIGURATION –> MEMORY  CHANGES (changes in memory as it was ESX before and it comes ESXi after)

 

---

Datastore of ESX before migration

Datastore of ESXi after migration (Partition changed little bit)

---

DATASTORE SIZE BEFORE MIGRATION

LITERALLY NOT CHANGE IN SIZE AFTER MIGRATION

Migration to ESXi5.0 from classic esx

Files and Configuration Settings Affected by the Migration or Upgrade to ESXi 5.0

The migration from ESX 4.x to ESXi 5.0 does not migrate all host configuration files and settings. After the upgrade, you must reconfigure some host settings.

Migrating ESX 4.x Files and Settings to ESXi 5.0

The upgrade process preserves as much of the ESX host configuration as possible. However, because of the architectural differences between ESX 4.x and ESXi 5.0 architecture, many configuration files cannot be migrated when you select the Migrate option in the ESXi installation or upgrade wizard. Pertinent VMware files, such as /etc/vmware/esx.conf are migrated, but many existing settings such as third party agents and scripts, cannot be migrated. In fact you can imagine these 3rd party agents & scripts are no longer needed in ESXi. Most of the 3rd party agents are backup agents, monitoring agent and scripts are generally doing same functions. All these scripts can still run if you use vMA. Agents no longer needed.

---

NOTE If a host contains customizations, such as third-party VIBS or drivers, upgrading with the standard VMware installer ISO will result in the loss of those customizations, and possibly an unstable system. Use ESXi Image Builder CLI to create a customized ESXi installer ISO file that includes the VIBs or drivers. See the information on Image Builder in the vSphere Installation and Setup documentation.

---

Files not Migrated	Comments
/etc/logrotate.conf	Not migrated, ESXi has different log rotation scheme. Need to re-configure log setting mentioned at page:18 of vSphere Upgrade Guide
/etc/localtime & /etc/sysconfig/clock	Not migrated. Timezones are not supported in ESXi
/etc/syslog.conf	Not migrated.
/etc/sysconfig/ntp	Not migrated
/etc/sysconfig/console/*	Not migrated
/etc/sysconfig/xinetd & /etc/xinetd.conf /etc/sysconfig/i18n	Not migrated as not supported in ESXi
/etc/sysconfig/crond	Not migrated
/etc/sysconfig/syslog	Not migrated, as it is not compatible with new version
/etc/sysconfig/mouse	Not migrated, as mouse is not supported in ESXi
/etc/ssh & /etc/vmware/pci*	Not migrated
/etc/yp.conf	NIS is not supported & not needed as we have AD integration
/etc/login.defs & /usr/local/etc/	Not migrated.
/etc/hosts.allow & /etc/hosts.deny	Not migrated
/etc/ldap.conf & /etc/openldap, /etc/sudoers	Not migrated as it is not supported in ESXi
/etc/rc.d/rc*.d/*	Not migrated as ESXi & ESX rc scripts are not compatible
/etc/vmware/init/*	Not migrated as scripts are incompatible
/etc/vmware/license.cfg & /etc/vmware/license.lic	Not migrated.
/etc/vmware/hostd/config.xml & /etc/vmware/hostd/proxy.xml	Not migrated as these files are not compatible with ESXi
/usr/lib/vmware	Not migrated
/etc/fstab	only NFS entries migrated
/etc/passwd & /etc/shadow	Partially migrated, only root password saved if possible
/etc/groups	not migrated