Jasmine McTigue

Network Computing Blogger

Upcoming Events

Where the Cloud Touches Down: Simplifying Data Center Infrastructure Management

Thursday, July 25, 2013
10:00 AM PT/1:00 PM ET

In most data centers, DCIM rests on a shaky foundation of manual record keeping and scattered documentation. OpManager replaces data center documentation with a single repository for data, QRCodes for asset tracking, accurate 3D mapping of asset locations, and a configuration management database (CMDB). In this webcast, sponsored by ManageEngine, you will see how a real-world datacenter mapping stored in racktables gets imported into OpManager, which then provides a 3D visualization of where assets actually are. You'll also see how the QR Code generator helps you make the link between real assets and the monitoring world, and how the layered CMDB provides a single point of view for all your configuration data.

Register Now!

A Network Computing Webinar:
SDN First Steps

Thursday, August 8, 2013
11:00 AM PT / 2:00 PM ET

This webinar will help attendees understand the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging. It will also help users decide whether SDN makes sense in their environment, and outline the first steps IT can take for testing SDN technologies.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

See more from this blogger

Updating ESX To vSphere 4

It's no secret that the latest version of VMware's virtual infrastructure is bigger, better, faster and more capable than ever, but along with the new feature set comes a whole load of complexity. vSphere 4.0 has a ton of features designed to bring system performance to the next level, but it requires a little tweaking to get the most out of them.

Upgrading vSphere is cake, but your job is not necessarily finished. Virtual machines are not automatically updated to the new machine format when you update your hosts. A word of caution: vSphere virtual machines can only run on vSphere hosts. Don't complete the steps below until you are committed to bringing your entire cluster up to current. 

To get started:

  • Take a backup of your virtual machines.
  • Open the vSphere client and shut down the guest virtual machine in question.
  • Right click the guest machine and click upgrade virtual hardware.
  • Agree to the warning and watch the task complete in the task pane.
Now that your machines have up-to-date virtual hardware, you can take advantage of the new networking and SCSI adapter types in virtual hardware. VMware made a number of enhancements to virtual networking with vSphere 4. While you're taking advantage of the networking enhancements, read Scott Lowe's awesome post on enabling jumbo frames for vDS, if you haven't already. The virtual networking adapter has performance increases of up to 85 percent over ESX 3.5, especially when multiple VMs are transmitting. I'm not sure if there is an easier way, but you can't seem to upgrade the network adapters to VMXNET3 directly.

To get around this:

  • Right click the VM in question and edit settings.
  • Click the add button for hardware, select Ethernet adapter.
  • From the adapter type box select VMXNET3, leave the adapter connected at power on.
  • Click next, finish and then OK to the settings dialog and allow the configuration task to finish.
  • Power on the VM.
You'll notice as soon as you login that a whole bunch of new hardware is going to be detected. Some machines also request a disk consistency check on startup prior to login. I let these run and have yet to run into problems. Once new hardware is finished installing, give the machine a reboot or answer in the affirmative to the reboot prompts.

After a successful restart on windows machines, you should see the original network adapters plus any new ones. Reassign any static IP addresses to the new VMXNET3 network interface and disable the original one. Bring the machine down for one more reboot and remove the original Ethernet adapter. When you power your server on, you are officially on VMXNET3. Just remember, VMXNET3 performance increases depend on all of your machines making use of the new networking technology, so get cracking and get the rest of those machines up to date.

Jasmine McTigue is the IT manager for Carwild Corp. She is responsible for IT infrastructure and has worked on numerous customer projects as well as ongoing network management and support throughout her 10-plus-year career.

Related Reading

More Insights

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.
Vendor Comparisons
Network Computing’s Vendor Comparisons provide extensive details on products and services, including downloadable feature matrices. Our categories include:

Research and Reports

Network Computing: April 2013

TechWeb Careers