Skip to main content

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

By
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)
 
Labels:

Comments

  1. UnknownDecember 11, 2014 at 9:13 AM

    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

Fortigate guide for Begineer - 6

By
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...
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
144 comments
Read more

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

By
Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...
7 comments
Read more