What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

ESX Hardware status (SOAP) sensor after Update to HP esxi 5.5 Update 3 warnings

Votes:

0

Your Vote:

Up

Down

Hi Paessler Support

Ich habe am Wochenende unsere Server von "HP esxi 5.5 Update 1" auf "ESXI 5.5 Update 3" upgedatet.

Bei einem Server motzt der esx hardware status (SOAP) sensor (esxserverhosthealthsensor) auf den esxi servern selbst sowie über das vcenter.

Er warnt alle devices (auch solche die gar nicht installiert sind). PRTG Update auf Version 15.4.20.4378 habe ich eben erledigt.

Irgend eine Idee?

Warning. 129 elements return a warning state: Proc 2; Proc 1; Memory; Power Supply 3 Power Supplies - unknown; System Board 11 Memory: Correctable ECC logging limit reached - unknown; System Board 11 Memory: Uncorrectable ECC - unknown; Disk or Disk Bay 1 C1 P1I Bay 1: Rebuild Aborted - unknown; Disk or Disk Bay 1 C1 P1I Bay 1: Rebuild In Progress - unknown; Disk or Disk Bay 1 C1 P1I Bay 1: In Failed Array - unknown; Disk or Disk Bay 1 C1 P1I Bay 1: In Critical Array - unknown; Disk or Disk Bay 1 C1 P1I Bay 1: Parity Check In Progress - unknown; Disk or Disk Bay 1 C1 P1I Bay 1: Predictive Failure - unknown; Disk or Disk Bay 1 C1 P1I Bay 1: Drive Fault - unknown; Disk or Disk Bay 2 C1 P1I Bay 2: Rebuild Aborted - unknown; Disk or Disk Bay 2 C1 P1I Bay 2: Rebuild In Progress - unknown; Disk or Disk Bay 2 C1 P1I Bay 2: In Failed Array - unknown; Disk or Disk Bay 2 C1 P1I Bay 2: In Critical Array - unknown; Disk or Disk Bay 2 C1 P1I Bay 2: Parity Check In Progress - unknown; Disk or Disk Bay 2 C1 P1I Bay 2: Predictive Failure - unknown; Disk or Disk Bay 2 C1 P1I Bay 2: Drive Fault - unknown; tg3 device firmware 5719-v1.33 NCSI v1.0.60.0; tg3 device firmware 5719-v1.33 NCSI v1.0.60.0; tg3 device firmware 5719-v1.33 NCSI v1.0.60.0; tg3 device firmware 5719-v1.33 NCSI v1.0.60.0; HP Smart Array Controller HPSA1 Firmware 4.68; tg3 driver 3.137h.v55.1; tg3 driver 3.137h.v55.1; tg3 driver 3.137h.v55.1; tg3 driver 3.137h.v55.1; VMware xhci-xhci 1.0-2vmw.550.3.68.3029944 2015-08-31 08:13:27.000; Hewlett-Packard char-hpilo 550.9.0.2.3-1OEM.550.0.0.1198610 2014-03-31 19:44:41.000; VMware sata-sata-sil 2.3-4vmw.550.0.0.1331820 2013-09-19 06:06:39.000; VMware esx-dvfilter-generic-fastpath 5.5.0-0.0.1331820 2013-09-19 06:06:59.000; Hewlett-Packard scsi-hpdsa 5.5.0.36-1OEM.550.0.0.1331820 2015-04-09 18:07:36.000; Broadcom net-bnx2x 2.710.70.v55.7-1OEM.550.0.0.1331820 2014-11-10 16:55:40.000; VMware esx-base 5.5.0-3.68.3029944 2015-08-31 08:13:49.000; Hewlett-Packard hpbootcfg 5.5.0.02

esxi hardware-monitoring wrong-status

Created on Oct 19, 2015 4:01:44 PM by  Thomas Umbricht (2,820) 3 3



3 Replies

Accepted Answer

Votes:

1

Your Vote:

Up

Down

Sehr geehrter Herr Umbricht

Als erster Schritt empfiehlt sich, den CIM- und/oder VPXA-Service auf dem VSphere neuzsutarten. Sie finden weitere Informationen dazu hier http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037330 und hier http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2020665

Zeigt der Sensor nur wieder einen vernünftigen Status an?

Created on Oct 21, 2015 4:25:25 PM by  Arne Seifert [Paessler Support]



Votes:

4

Your Vote:

Up

Down

Hallo Arne Seifert

Der Neustart der beiden Dienste hat nicht geholfen. Diese beiden Befehle (musste zuerst PowerCLI installieren) haben jedoch den Fehler behoben.

(Get-View (Get-VMHost -Name esxhostname | Get-View).ConfigManager.HealthStatusSystem).ResetSystemHealthInfo()
(Get-View (Get-VMHost -Name esxhostname | Get-View).ConfigManager.HealthStatusSystem).RefreshHealthStatusSystem()

"esxhostname" muss derselbe Name sein welcher im vcenter als Host angezeigt wird (bei mir sind halt IP Adressen)

Vielen Dank Thomas Umbricht

Created on Oct 22, 2015 7:54:10 AM by  Thomas Umbricht (2,820) 3 3

Last change on Oct 22, 2015 1:56:33 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Sehr geehrter Herr Umbricht

Vielen Dank für die Veröffentlichung Ihrer Problemlösung.

Created on Oct 22, 2015 1:56:23 PM by  Arne Seifert [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.