Add esx 4 to orion NPM

I've problems adding a new esx4 to orion NPM.

I've several esx 3.5 added to orion and they work perfectly, list all machines and resources.

Last week i add my new esx 4 server and i notice something diferent, snmp is no longer as in esx 3.5 i configur the new snmp on esx4 and already have the node listed on orion but i can't see any of the virtual machines on it as i saw in esx 3.5.

Also the esx3.5 is recognized as esx machine type and the esx4 is as net-snmp - Linux

Thoose any one knows how to solve this.

the next print's show the esx 3.5 with all vm machines and the esx4 without anything.

[View:/cfs-file.ashx/__key/CommunityServer.Components.UserFiles/00.00.03.10.31/esx3_5F00_orion.TIF]

[View:/cfs-file.ashx/__key/CommunityServer.Components.UserFiles/00.00.03.10.31/esx3_5F00_orion1.TIF]

Thanks for the help

Find more posts tagged with

esx_3

advanced_node_details

add_resources

esx

esx_virtual_machine_physical

esx_host

vsphere_4_snmp_orion_esx

add_node

esx_4

add_snmp_devices

esx_server

esx_vmware

Accepted answers

cnbest01

I had just asked this question as well. It seems that NPM does not currently support ESX 4.x. It is in the works BUT there is no timeframe as to when it will.

All comments

pbrass

Please see the existing thread on this issue. Unfortunately, there doesn't appear to be any solution currently.

They think it will be fixed in 9.6, but (and i quote) their "rules around accounting don't allow [them] to provide specific dates that far in advance."

We've tried just about everything we could think of on our end to get this working but to date have had no luck.

cnbest01

I had just asked this question as well. It seems that NPM does not currently support ESX 4.x. It is in the works BUT there is no timeframe as to when it will.

bshopp

These threads are correct. VMWare is no longer populating their MIB's as they did in ESX 3.5. To address this, we are going to have to change our method of getting to the data and use their API.

kupjones

Brandon, the vSphere Basic Admin indicates that the HOSTD process on ESX 4 exposes a new set of MIBs that appear to be fully populated with the data that was originally populated into the HOST-RESOURCES MIB. (see page 55 in the doc www.vmware.com/.../vsp_40_admin_guide.pdf).

So the question is -- is it really necessary to go after the API (uggg)???

An alternative given by VMware is to enable Net-SNMP and setup a proxy to HOSTD -- which I consider to be a hokey solution.

I've already banged on our VMware channel SE about the abandonment of Net-SNMP -- something i consider to be be very short-sighted.

John.Taylor

The problem with using their "hokey" solution is that some of the important OIDs including the VM's interfaces bytes sent and received were removed and no new OIDs where added in their place.

John Taylor

kupjones

BTW, "hokey" is a technical term.

Yes, they no longer expose the vnic interface statistics. VMware really mucked this one up.