Read the HP press release? Still wondering what we’ve added to HP Network Automation software? Here’s the straight talk. HP NA now supports ESX vSwitch devices. What does that mean? Well, we’ve had available for a while now a beta driver (www.hp.com/go/BSAEssentialsNetwork) that allows you to find and manage vSwitch devices using the same HP NA you’ve come to know and love to manage NCCM in your conventional network infrastructure. That means HP Network Automation software allows you to mange thousands of types of physical network devices, virtual devices such as Cisco FWSM and ACE modules, and now vSwitch devices as well.

Why does that matter? I’ll be writing more on this hot topic in future posts, but did you know that every ESX server has and embedded vSwitch? These virtual switches connect VMs and they connect also to the physical network. You know, the one you’re responsible for keeping up. Yup, that one. So now, let me ask you this – how many vSwitches are currently deployed in your IT environment? How many will be deployed next month? How about during the last week of your fiscal quarter? How are they configured? Are they compliant? What is the default CDP setting on vSwitches?

What does your policy call for? How will you enforce that policy with vSwtiches )? Okay, sorry, didn’t mean to scare you like that. But hey, it’s happening, so you might as well get  a grip on it.

Want to take the first step? Download an excellent independent Impact Brief written by Jim Frey at Enterprise Management Associates (http://www.enterprisemanagement.com/about/team/Jim_Frey.php). You can buy it at EMA’s website, or read it from our website, www.hp.com/go/NAsoftware.

I’ll be back soon, giving you more to worry about. Unless, of course, you’re one of the many happy HP Network Automation customers. In that case, I’ll be giving you more reasons to be thrilled with your HP Network Automation software.

Using Opsware NAS? Might be a good time to consider upgrading to HP NA 7.5, virtually speaking.