Skip to main content

How to change VMware Network Adapter Type from E1000 to VMXnet3?

Once I've migrate my vSphere 4 to 5, I got need to change some Server NIC from E1000 to VMXNET3 as they are not touched while migrating to avoid unnecessary issue and delay in project period.

But after migrated, I start noticed that some server like File Server, SAP or other server those need high user access definitely need to convert to VMXNET3 to get better performance.

So, I've decided to convert and follow is my steps in converting process.

That will be the easy guide for you too.

Actually, you will see two method to covert the adapter type.
- Shutdown the server and add new NIC. Uninstall old NIC and update NIC setting of old to New.
- Using VMware PowerCLI for live converting without touching server.

Here, I'm using second method, PowerCLI, to make conversion.

You need to download and install the VMware PowerCLI into your machine before start.

OK. Let's start now.
-          Check the Network Adapter Type and Adapter Number 1 or 2.
-          In this example, we are going to change Network Adapter 2 to VMXNET3 from E1000.


-          Check the Host where the Guest OS located on.
-          Here Guest OS “xxxx xxxx” is located on Host “xxxxesxi52”.



-          Open the VMware PowerCLI and key in “Connect-VIServer –Server hostname or ip address of host –Protocol https” without double quote to connect to the “Host”.


-          Key in username and password for “Host” to login.


-          You will see as below once you login successfully.
-          Host Server Name, Port Using and Login User.



-          Double check the network adapter by key in “Get-VM 'xxxx xxxx' |Get-Networkadapter” without double quote.


-          Key in “Get-VM  'xxxx xxxx' |Get-Networkadapter |Set-Networkadapter -type vmxnet3” without double quote to change adapter type.
-          You will be asked to perform the changing action with network adapter. Just choose “Yes” or “No” for correct network adapter number that you wish to change the adapter type.


-          You will see the new network adapter type as below if you change its type successfully without any errors.


-          Double confirm the network adapter type from Web Console or vSphere Client as below.


-          Cheer! You’ve done.

(You may google or search in VMware Website depends on version)

To read deepth about VMware Network Adapter Type, please go this link http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805

To read deepth about details instruction and requirement for VMXNET3, please go this link http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805

May you all be happy.
(Be knowledgeable, pass it on then)
 

Comments

  1. There are some great tips on this blog that I plan to use.cloud hosting is best compared to all other type of hosting.Use minecraft server hosting with better hardware support.

    ReplyDelete

Post a Comment

Popular posts from this blog

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. services.sh restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)