VMware


NIC teaming can be used in virtual switches to improve reliability and performance.
You may be familiar with NIC teaming on a server where you have two NICs and give them both the same IP using a special driver to create a virtual NIC.
On ESX servers you can use NIC teaming also to take advantage of multiple physical NICs you have. The NIC teaming is however done at the virtual switch (vSwitch) level rather than in the VM itself. This way everything using that vSwitch benefits.

I had created a host profile from an identical server (NICs etc) and applied to a fresh install of ESX 4. However it failed for a couple of reasons half way though applying. At this point it had converted the standard virtual switch (SVS) to several DVS distributed virtual switches (DVS), and moved the pNICs as part of this. After correcting the problem I went back to continue to apply the profile to the server to complete the remaining parts (firewall etc) however I received the following error:

 

"IP Address <ip.add.re.ss> is used for multiple virtual nics" 

Read more ...

Before deploying hundreds of desktops its best to test everything is working correctly with an individual desktop.
 
Individual desktops are generally provisioned for users with specific desktop requirements. For example this might be an application used by one or two users and is licensed for one machine.
 
Here will will access a Windows 7 virtual desktop on an old physical desktop running Windows XP.


Notably the biggest difference between ESX and ESXi, is the fact ESXi does not have a service console. There is now a remote CLI that can be run from a windows system to perform the majority of commands available from the similar ESX service console.
However lacking the service console has some drawbacks that may restrict some from running ESX server based backups, 3rd party monitoring and other custom applications from the red hat based service console.

 

When powering on a virtual machine you may get the following error relating to resources:

"Insufficient memory resources"

Read more ...

Share this blog post on social media:

Latest Blog Posts

Popular

Social Links

Disclaimer

All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.

Copyright ©2008-2021 Andy Barnes - Please do not copy any content including images without prior consent!

Designed and Hosted by Andy Barnes

We use cookies

We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this site and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.

Ok Decline