Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

VMTools Upgrade Behavior

Posted on 2016-09-26
5
80 Views
Last Modified: 2016-09-29
We have had issues where upgrading VMtools causes the existing NIC to be replaced by another NIC and all settings are lost. We are running ESXi 5.5 U3b and upgrading tools from various versions to version 10. We need to understand the circumstances under which this can happen and also how to prevent it, if possible.  We are using VMXNET3 NICs.

I have researched online and reviewed release notes, but cannot find anything which clarifies the expected behavior.

Thanks,
Rick
0
Comment
Question by:Virene
  • 3
  • 2
5 Comments
 
LVL 119
ID: 41817043
We have had issues where upgrading VMtools causes the existing NIC to be replaced by another NIC and all settings are lost.

This can happen, when the network interface, changes PCI slot in the virtual machine, and the effect as you describe is the removing of the current network interface, and the insertion of a new network interface.

We are running ESXi 5.5 U3b and upgrading tools from various versions to version 10.

I think you may be getting confused here. There are two changes being discussed here

1. updating VMware Tools.
2. changing and upgrading the virtual machine version to version 10.

There is NO real reason to rush and upgrade VMware Tools or Upgrade virtual machine version. Upgrading the virtual machine version just gives you the benefit of using newer virtual machine version 10 features.

Although recommended to be on the latest version of VMware Tools compatible with the Host OS, it's not an absolute MUST DO!

So which order did you do these changes, BECAUSE order is important.

1. VMware Tools Upgrade first.
2. Upgrade Virtual machine version second.

and always have a backup before you start, so you can rollback, any changes to production machines.
0
 

Author Comment

by:Virene
ID: 41819969
Hi Andrew,

Thanks for your response.

I was actually referring to Tools version 10240 here. However, I do have the same  question about expected behavior of the vNICs after a hardware version upgrade (we are going from either v4 or v7 to v10), and found multiple warnings about ensuring tools are upgraded first, so we've been doing that.

I can find articles about both Tools and Hardware upgrades causing NICs to be replaced, thus losing configuration, but nothing about predicting this result, except the issue about upgrading hardware before tools. My goal is to get proactive so the team knows what result to expect.
0
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 41820695
It can happen and does happen.
0
 

Author Comment

by:Virene
ID: 41822436
That's exactly what VMware support said. They have almost no details and suggested backing up the config before upgrading.
0
 
LVL 119
ID: 41822496
Unfortunately, it's the OS which does it plug and play.
0

Featured Post

Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

HOW TO: Upload an ISO image to a VMware datastore for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere Host Client, and checking its MD5 checksum signature is correct.  It's a good idea to compare checksums, because many installat…
In this step by step tutorial with screenshots, we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 6.5 (ESXi 6.5). This is important if you need to enable SSH remote access for additional troubleshooting of the ESXi hos…
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question