• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2347
  • Last Modified:

ESXi: upgrade e1000 to vmxnet3 in bulk (powershell)?

Hi,

Is it possible to upgrade e1000 to vmxnet3 in bulk (powershell to multiple vm's)?

Thanks.
J.
0
janhoedt
Asked:
janhoedt
  • 4
  • 3
  • 2
  • +1
1 Solution
 
Paul SolovyovskySenior IT AdvisorCommented:
It may be possible but a secondary issue may arise with the IP addresses.  Since you're placing a new nic into each guest there needs to be process to re-ip the nic with the same setting as the previous nic and I"m not sure that there is a simple way to do this.
0
 
Neil RussellTechnical Development LeadCommented:
In short, no.
As Paul says, you will have a brand new NIC in each of your hosts that will need configuring INSIDE the OS.

On a brighter note, performance will be MUCH better with the VMXNet3 when you have finished :D
0
 
janhoedtAuthor Commented:
Thanks, I know that. Therefore the question indeed how to "copy" nic-settings from old to new nic. F.e. add new nic disabled, then copy within windows the settings and enabling the new nic ....
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
what OS?

Windows 2008 R2 ?

this script will change the IP Address

Get-VM VMName | Get-VMGuestNetworkInterface -GuestUser Administrator -GuestPassword <password> -HostUser root -HostPassword <password> | Set-VMGuestNetworkInterface -IPPolicy Static -Ip <IPAddress> -Netmask 255.255.252.0 -Gateway <Gateway> -GuestUser Administrator -GuestPassword <password> -HostUser root -HostPassword <password> 

Open in new window

0
 
janhoedtAuthor Commented:
Mostly Windows 2008 R2 indeed, some Windows 2003 also.
So this could work in my scenario, only problem is vm's with 2 nics ...
0
 
janhoedtAuthor Commented:
Note: a company I know mentions "why do we need vmxnet3, bandwith now isn't heavily used at all,  so why the effort migrating to vmxnet3?
Indeed, what other advantages vmxnet gives versus e1000 and how can I explain/prove this in human understandable format?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
E1000 is a legacy network adaptor, which should only be used for initial installation, it has a higher overhead on the host that the virtualised VMXNET3, and therefore is generally recommended to switch from e1000 to vmxnet3.

That's always been the recommendation.
0
 
Neil RussellTechnical Development LeadCommented:
Also the E1000 is prone to drop outs and the mysterious "Dissapearing" network. This is never the case with the VMXNET3 virtual NIC.
As hanccocka says, Always use the VMXNET3 in any OS that supports it.
0
 
janhoedtAuthor Commented:
Thanks, I'm already convinced but that won't convince "them" ....
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Using VMXNET interface has always been the recommendation, since version 1.0!

Well just park it, if they have network issues, it's likely to be related to E1000.

Just make sure all templates are updated, and in the future they deploy on VMXNET3.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now