
Hi,
does this only work on certain physical servers?
I have one where it works but on most physical servers I dont have the option to collect these statistics.
Out of curiosity, what server(s) is the hardware monitoring working for, and which are not? Make/model information would be very helpful. E.G. "Dell PowerEdge 1950" for instance.
Hi, the problem was actually that the server was not allowed to access SNMP on most servers.
We mostly have HP Proliant servers but I am sure they will work once we install APM5 GA on production server :)
The one server the Hardware Health Monitoring is working for also has the "Virtual Machine Details" box on its details page though... it looks like its showing the virtual machine details of a different server there.
The one server the Hardware Health Monitoring is working for also has the "Virtual Machine Details" box on its details page though... it looks like its showing the virtual machine details of a different server there.
Are you polling this ESX host through vCenter or directly? What makes you believe that the hardware details are for a different node? Can you provide a screenshot of what you're seeing?
Hi Jeremy,
this is not an ESX host but for some reason I still see the Virtual Machine details, the information in this part (judging from the path it shows to the "virtual machine") relates to a test machine that is not even managed by Orion.
I will send you a screenshot tomorrow by email (if I dont forget).
Ok, now that hardware health is also polled via WMI, we should see all of our hardware servers.
Unfortunately we don't, there are a lot of servers without hardware health but I have sent you MIB Walks of all our physical servers, so hopefully in the final release they will be in there too :)
Is something like this planned for NPM for network devices as well? Much more comfortable and easier to look at than UnDPs!
Haven't checked yet but I hope we can also build report and alerts from that data :-)
Questionario, are you seeing all your hardware details for SNMP nodes? For your WMI nodes, do you have the hardware vendors supplied agent software installed on these hosts? Are you seeing no hardware information for any WMI node or just a reduced subset of hardware information compared to your SNMP nodes? Are you running the latest SAM 5.0 Beta 4?
Hi Jeremy,
we only have one hardware node for testing where we have SNMP for the APM beta server (restricted SNMP access to production orion only).
We are running SAM5.0 beta4 :)
We do have the agents running on our hardware servers.
Actually I never checked if we saw "all" hardware information as I remember you saying it's still in a proof of concept phase.
So I am actually talking about it not being able to detect any hardware health at all.
PS: one feature request for the real time process explorer.... on W2k8R2, could you include the RAM-usage of Metafile?
-> http://wasthatsohard.wordpress.com/2011/03/01/high-memory-usage-windows-server-2008-r2-file-server/
It helps when checking whats using up all the RAM.
So I am actually talking about it not being able to detect any hardware health at all.
What is the make and model of the server that you're testing the WMI hardware monitoring against? What version of the agent software is installed? When you run a "list resources" against this WMI node what resources are listed for this node? A screenshot here would be very helpful.
PS: one feature request for the real time process explorer.... on W2k8R2, could you include the RAM-usage of Metafile?
Thank you for the suggestion. Unfortunately Metafile memory usuage information is not accessible/available remotely which is one reason why Sysinternals Process Explorer doesn't provide the ability to connect to hosts remotely.
for example HP Proliant DL360 G6, dont know which version of the tools is installed on there.
Using WBEMTEST built into Windows or using a 3rd party free tool such as WMI Explorer can you verify the HP Proliant server has the Root\HPQ WMI namespace? Below is an example of an HP server we have working in our lab being polled for hardware via WMI.