In the last post here, I provided some basic information on SNMP and also shared which networking MIB modules are supported in vSphere 5.1. Before I describe how to use these MIB modules, there is one correction I would like make to the last post. I had mentioned that network related Trap is not supported, but that is not correct. SNMP agent on the host does send SNMP Trap when a physical link goes UP or DOWN. The Trap is like an interrupt. Instead of polling the values of the different network parameters, specific trap tells the user which network parameter needs attention.
Let’s take a look how you can use Networking MIBs to monitor virtual switch parameters.
In earlier releases of ESXi, a VMkernel interface could transport three types of traffic: Management, vMotion and Fault Tolerance. To enable a particular traffic type, one would use either the vSphere Web/C# Client or the vSphere API. Some of you may have recalled using an undocumented command-line tool called vim-cmd in the ESXi Shell to enable vMotion and Fault Tolerance traffic. An issue with this tool is it does not support the Management traffic type. This made it a challenge to completely automate the provisioning of VMkernel interfaces from a scripted installation (kickstart) perspective and required the use of remote CLI/APIs to enable the Management traffic type.
Luckily in vSphere 5.1, we now have an easy way of tagging these various traffics types for a VMkernel interface using the new ESXCLI 5.1.
VMware is looking for customer feedback on the which VMware and third party plugins are commonly used within the virtual infrastructure client. We have compiled a short 6 question survey asking for your feedback on which plugins you use. Please complete the survey so that your input can help make VMware products better.
We are arranging a special preview of the next generation vSphere client to a limited audience at this year’s Partner Exchange in Las Vegas 02/13-16th. Selected attendees will be able to listen to VMware Product Managers discuss the future vision of VMware user interaction as well as have the ability to try out the new client in real time with common day to day VMware administration tasks. All we ask is for you to provide feedback on usability, navigation, performance etc during this one of a kind event.
You must be attending (or planning to attend) PEX 2012 in Las Vegas 02/13-16th,
A Partner with an actively signed VMware Non Disclosure Act,
Available Monday, 13th 5:30pm-8:00pm
If you are interested in participating in this one time private preview and have valuable input into making VMware products better, please email firstname.lastname@example.org with subject of ‘PEX 2012 NGC Private Preview’ and include your company name, your name and names attending with you no later than close of business, Friday February 10th. Invites will be sent soon after.