Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
VMware tools upgrade to 10.5 causing major outage ?
Hi People,
When performing the previous VMware tools upgrade, I usually don't expect to do any major outage at all, normally only 1-2 ping packet loss. But today it has caused my some big issue where the production terminal server patch network adapter lost (not appearing in Network adapter folder) ?
The VMware tools was upgraded from earlier version to the latest v10.5 by double clicking on the setup64.exe file and it was taking so long time stuck in VMXNet3 driver update. eventually it finished successfully with the below error logged:
Therefore I have to perform reboot which cause some grief and frustration from the users !
Can anyone please assist me in troubleshooting what the root cause of the issue as the management and the change management team now demands some explanation from me ?
Please help me.
When performing the previous VMware tools upgrade, I usually don't expect to do any major outage at all, normally only 1-2 ping packet loss. But today it has caused my some big issue where the production terminal server patch network adapter lost (not appearing in Network adapter folder) ?
The VMware tools was upgraded from earlier version to the latest v10.5 by double clicking on the setup64.exe file and it was taking so long time stuck in VMXNet3 driver update. eventually it finished successfully with the below error logged:
Level:Log Name: System
Source: vmxnet3ndis6
Date: 8/01/2016 1:20:57 PM
Event ID: 5001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PRODTS47-VM.domain.com
Description:
vmxnet3 Ethernet Adapter #2 : Could not allocate the resources necessary for operation.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="vmxnet3ndis6" />
<EventID Qualifiers="49152">5001</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords >
<TimeCreated SystemTime="2016-01-08T02:20:57.1057 30500Z" />
<EventRecordID>139469</EventRecordID >
<Channel>System</Channel>
<Computer>PRODTS47-VM.domain.com</Co mputer>
<Security />
</System>
<EventData>
<Data>\Device\NDMP14</Data>
<Data>vmxnet3 Ethernet Adapter #2</Data>
<Binary>00001C0002004C00000000008913 00C0000000 0000000000 0000000000 0000000000 0000000000 009A0000C0 436D230072 6563767175 6575652E63 00CD000000 06000000</ Binary>
</EventData>
</Event>
Therefore I have to perform reboot which cause some grief and frustration from the users !
Can anyone please assist me in troubleshooting what the root cause of the issue as the management and the change management team now demands some explanation from me ?
Please help me.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
1. We always test any changes to Production VMs, this includes the upgrading of VMware Tools.
2. We always perform any changes to schedule Production VMs, out of core hours.
3. We always ensure we have full backups before we many any changes to production machines.
All of the above are agreed with our Change Boards and Change Management Teams before we commence any work.
So did you test it ?
You did this change with users logged on ?
The error message looks like, running out of memory or resources, do you regularly reboot your terminal servers every 24 hours ?
2. We always perform any changes to schedule Production VMs, out of core hours.
3. We always ensure we have full backups before we many any changes to production machines.
All of the above are agreed with our Change Boards and Change Management Teams before we commence any work.
So did you test it ?
You did this change with users logged on ?
The error message looks like, running out of memory or resources, do you regularly reboot your terminal servers every 24 hours ?
Hi Andrew,
No I don't regularly reboot it.
The only test that I did was the other IT Management server which doesn't cause any outage.
No I don't regularly reboot it.
The only test that I did was the other IT Management server which doesn't cause any outage.
We've always regularly rebooted our terminal servers after 24 hours, every day at 3AM, to clear all the sessions out, and clears out all the memory leaks and resource issues. Which seems to be with many users logging on and off, and running apps.
Hi Andrew,
Yes that does make sense.
But my case here is different. I got 55 VMs that server as Win2008R2 Terminal Servers RDSH for multiple different office in across several continents, so it is 24/7 used by the users.
The load balancer here is Riverbed Steel App
Restarting every 24 hours randomly is just going to cause some problem when there is some users logged on.
Yes that does make sense.
But my case here is different. I got 55 VMs that server as Win2008R2 Terminal Servers RDSH for multiple different office in across several continents, so it is 24/7 used by the users.
The load balancer here is Riverbed Steel App
Restarting every 24 hours randomly is just going to cause some problem when there is some users logged on.
But you have to install windows updates.
We schedule vm tools update at host reboot that happens sunday after patch tuesday.
We schedule vm tools update at host reboot that happens sunday after patch tuesday.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial