Welcome, Guest. Please login or register.

Author Topic: monitor ESX vSwitch virtual interfaces  (Read 5688 times)


  • Guest
monitor ESX vSwitch virtual interfaces
« on: June 04, 2012, 11:04:58 PM »

Looking for a nedi based solution to get the topology including port at vswitch and network side interface
monitoring (traffic,errors,discards) between esx vswitch and vm-guests.

Want to avoid the need for accessing vm-guests for monitoring,
because its normaly allmost impossible to organize that all servers get SNMP enabled and
Read community or v3 credetials provided across all sub organizations in a company in timly manner.

SNMP walking the ESX hosts you can see the physical vmnics only. So we need to access the vSwitch.

1. Is it possible to give the vswitch an IP-addresse and could it be SNMP activated?
2. is there a ready to use perl script or module to can fetch
vSwitch interface data via the Perl-SDK?
3. if not, does anybody know the SDK commands for accessing the vswitch?

thx for hints, Steffen
« Last Edit: June 04, 2012, 11:22:35 PM by steffen1 »


  • Administrator
  • Hero Member
  • *****
  • Posts: 2728
    • View Profile
    • NeDi
Re: monitor ESX vSwitch virtual interfaces
« Reply #1 on: June 05, 2012, 12:06:21 AM »
1. AFAIK, only Nexus1k is "smart" in that context.
2. There are quite some bits and pieces, I've found googling around. I put some relevant info in perldoc libcli-iopty.pm
3. esxcfg-vswitch

I noticed that seems to relate to the non-vendor part of the MAC address. This could be used to map nodes to VMs (represented as modules in NeDi). Unfortunately I haven't found any documentation on this yet...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!


  • Guest
Re: monitor ESX vSwitch virtual interfaces
« Reply #2 on: June 10, 2012, 09:39:43 AM »
thx for the hints, esp. for inlined in libcli-iopty.pm:esxcfg-vswitch

Found this nice site => http://vmware-land.com/esxcfg-help.html
But it seams to confirm that you can monitor virtual traffic only, if you replace the native ESX-vswitch by Cisco NX1K.

ps:  compliments for the good inline documentation throughout the overall v1.0.6/7 code.