. HP Integrity Servers with Microsoft®Windows Server™ 2003 and WindowsServer™ 2008HP Insight Management WBEM ProviderEvents Reference GuideHP Part Number: 5992-4510Published: September 2008. © Copyright 2008 Hewlett-Packard Development Company, L.P.Legal NoticesConfidential computer software.
Get HP HP Systems Insight Manager 6.x Windows Software HP Systems Insight. On a HP Insight Management WBEM Providers for. Internet Engineering. HP Insight Management WBEM Providers are based on the Distributed Management Task Force’s (DMTF) Web-based Enterprise Management standard for.
Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor's standard commercial license.The information contained herein is subject to change without notice.
Table of ContentsAbout This Document.5Intended Audience.5New and Changed Information in This Edition.5Document Organization. About This DocumentThis document describes the Windows System Log Event ID number, severity, and descriptionof events generated by the Web-Based Enterprise Management (WBEM) providers on HP Integrityservers running Microsoft® Windows® Server 2003 and Windows® Server 2008.The document printing date and part number indicate the document’s current edition. Theprinting date changes when a new edition is printed. Minor changes may be made at reprintwithout changing the printing date. Related InformationYou can find more information about HP Integrity servers, server management, and softwarein the following locations:.For an overview of the HP Integrity server family:other documents supporting Windows Server 2003 and Windows Server 2008 on HPIntegrity Servers:. 1 WBEM Provider Event TablesIntroductionThis reference guide describes the Windows System Log Event ID number, severity, anddescription of events generated by HP Integrity WBEM provider software. The WBEM providersare a group of services that run continuously in the background on HP Integrity servers andreport the status of system components.
Each WBEM provider has its own unique table in thisdocument. Event ID135188Event Severity Event DescriptionErrorTemperature sensor crossed upper non-recoverable threshold. Probable Cause: Thetemperature inside the server has gone far outside the factory specified range fornormal operation. To avoid permanent damage to your server hardware, go andturn off the server immediately. Event ID0720722Event Severity Event DescriptionErrorMachine Check Initiated. Probable Cause: A Machine Check Abort event means thehardware detected a critical error.
This event is generated whenever a system errordue to processor, firmware, hardware and operating system is encountered. MCAevents may be either recoverable or non-recoverable.
If it is recoverable, the systemwill attempt to recover from the error for the purpose of maintaining high availability. Event ID73773810Event Severity Event DescriptionErrorPower failure in power supply.
Probable Cause: Indicates a failure with the AC powersource that is connected to one of the redundant power supply units. RecommendedAction: Check the power cord or source voltage. WBEM EventID: 726. WBEMProviderName: FPLIndicationProvider02ErrorVoltage reached critical level. Event IDEvent Severity Event DescriptionErrorMissing FRU device. Probable Cause: A required device was not detected.
See theSystem Event Log (SEL). Recommended Action: Install missing, required device.WBEM EventID: 739. WBEM ProviderName: FPLIndicationProvider02ErrorMissing Entity.
Probable Cause: A required device was not detected. RecommendedAction: Install missing, required device. WBEM EventID: 740.
Event ID12Event Severity Event DescriptionErrorA temperature inside the server went far outside the factory specified range. ProbableCause: The temperature inside the server has gone far outside the factory specifiedrange for normal operation. To avoid permanent damage to your server hardware,go and turn off the server immediately.
Event ID37Event Severity Event DescriptionErrorBoot cell launch EFI failure. Probable Cause: The system has failed to launch EFIbecause of an internal error. Recommended Action: Reboot or update System FW.
Ifproblem persists contact your HP representative for support. WBEM EventID: 203.WBEM ProviderName: FPLIndicationProviderErrorMonarch selection failure. Event ID505914Event Severity Event DescriptionErrorCould not allocate memory for EFI image. Probable Cause: SFW could not allocateenough memory for EFI image.
Recommended Action: Reboot. If problem persistscontact your HP representative for support. WBEM EventID: 217. WBEMProviderName: FPLIndicationProviderErrorEFI image corrupted. Probable Cause: EFI image is corrupted.
Event IDEvent Severity Event Description5060ErrorTrap taken. Probable Cause: This will follow other events indicating some type ofIVT error. Recommended Action: This event is for debugging the address, otherevents will determine the user action.
WBEM EventID: 233. WBEM ProviderName:FPLIndicationProvider5063WarningLDB State bad on entry. Probable Cause: No action is required WBEM EventID: 234.WBEM ProviderName: FPLIndicationProviderErrorInterrupt with ic bit clear. Event ID0616Event Severity Event DescriptionErrorError extracting salb from rom. Probable Cause: ROM Corrupt or unreadable.Recommended Action: Reboot, if problem persists contact your HP representativefor support. WBEM EventID: 250. WBEM ProviderName: FPLIndicationProviderErrorScratch RAM bad.
Probable Cause: Bad or corrupt Scratch RAM. Event ID33Event Severity Event DescriptionErrorUnexpected trap. Probable Cause: An unexpected trap has occurred. During SystemFirmware boot time this indicates the system has requested a trap that firmware hasnot registered.
During OS run time it indicates the system has requested a trap thatis not recognized in the OS's trap table. Recommended Action: If at FW boot time,reboot or upgrade System FW.
Event ID515218Event Severity Event DescriptionWarningI/O host bridge inaccessible because rope reset failed to complete. Probable Cause:I/O CEC failure. Recommended Action: Contact your HP representative to check theI/O CEC. WBEM EventID: 276. WBEM ProviderName: FPLIndicationProviderWarningInsufficient power to turn on PCI slot.
Probable Cause: The power budget for the IOsubsystem has been exceeded. Event ID765179Event Severity Event DescriptionErrorError in temporary mdt area. Probable Cause: The memory area where the MDT issupposed to be built has an error in it, so the MDT cannot be built there.Recommended Action: Reboot, if problem persists contact your HP representativefor support.
WBEM EventID: 293. WBEM ProviderName: FPLIndicationProviderErrorFailed to find lmmio entry in mdt. Event IDEvent Severity Event DescriptionWarningMemory ECC multiple-bit data error detection failed. Probable Cause: The CEC failedMBE detection. Recommended Action: Contact HP support personnel to troubleshootthe problem WBEM EventID: 307. WBEM ProviderName: FPLIndicationProviderWarningMemory ECC multiple-bit ECC error signalling failed. Probable Cause: The CECfailed MBE detection.
Recommended Action: Contact HP support personnel totroubleshoot the problem WBEM EventID: 308. Event ID50Event Severity Event DescriptionErrorNo memory found. Probable Cause: FW found memory, but it could not find acorrectly loaded rank. Recommended Action: Before this event is sent, FW will outputwhich ranks it is deallocating and why.
Review the preceding events and refer to theusers manual to correct the memory loading. WBEM EventID: 321. Event ID79528022Event Severity Event DescriptionWarningThe DIMM Loading Order check was bypassed. Probable Cause: Control bit to skipDIMM loading order check is set. Recommended Action: Clear NVM RecommendedAction: Update PDC Recommended Action: Contact HP support to troubleshoot theproblem WBEM EventID: 334.
WBEM ProviderName: FPLIndicationProviderWarningLooping on destructive memory tests. Event IDEvent Severity Event DescriptionWarningFirmware is adding a DEGRADED cpu node to the device tree. Probable Cause: ACPU that is not fully functional is installed in the cell board. Recommended Action:Replace cpu indicated in data field of event. WBEM EventID: 349. WBEMProviderName: FPLIndicationProviderErrorPD rendezvous will fail do to a Firmware Tree error. Probable Cause: Decode theASCII string in the data field to determine what resource is missing.
Event IDEvent Severity Event Description5411ErrorA CPU has taken over for the monarch CPU. Probable Cause: The previous monarchmay be suspect. WBEM EventID: 365.
WBEM ProviderName: FPLIndicationProviderErrorSram cannot be used on the cell. Probable Cause: SRAM cannot be located or usedon the cell board. Replace the cell board. WBEM EventID: 366.
WBEM ProviderName:FPLIndicationProviderErrorThe dillon hardware cannot be located. Probable Cause: ROM is corrupt. Event IDEvent Severity Event DescriptionWarningLBA correctable Timeout Error was encountered. Probable Cause: An LBA correctabletimeout error occurred.
Recommended Action: No action necessary, the error wascorrected. Information only. WBEM EventID: 381.
WBEM ProviderName:FPLIndicationProviderErrorLBA uncorrectable Function Error was encountered. Probable Cause: An LBAuncorrectable function error was encountered. Recommended Action: Replace/repairfaulty hardware. WBEM EventID: 382. Event IDEvent Severity Event Description5485ErrorFailure to install a Partition level PDT. Probable Cause: Reset WBEM EventID: 400.WBEM ProviderName: FPLIndicationProviderErrorA critical resource could not be found or is unusable. Probable Cause: Determine thefailing component or hardware from the data field as described and replace.
WBEMEventID: 401. WBEM ProviderName: FPLIndicationProvider5491ErrorInternal firmware programming error. Event IDEvent Severity Event DescriptionErrorError Processing encountered an unrecoverable error. Probable Cause: Decode theASCII message and correct the problem. WBEM EventID: 416. WBEM ProviderName:FPLIndicationProviderErrorSystem is unable to complete the Reset For Reconfiguration request. Probable Cause:Delay the request for reconfiguration until after the PD has been released from SincBIB.
WBEM EventID: 417. Event ID558028Event Severity Event DescriptionErrorThis indicates that the cell missed the rendezvous at the partition level. ProbableCause: The cell will independently step through some of the error logging steps andthen finally reset itself. WBEM EventID: 559.
WBEM ProviderName:FPLIndicationProviderErrorThis means that the PD monarch timedout. Event IDEvent Severity Event Description5581ErrorThe PD number specified in the complex profile is out of range. Probable Cause:Reconfigure the partition number, push out a new profile and reset. WBEM EventID:2458. WBEM ProviderName: FPLIndicationProvider5583WarningCould not obtain the crossbar port semaphore.
![Hp wbem agent Hp wbem agent](http://i1-win.softpedia-static.com/screenshots/PacketTrap-PT360-Tool-Suite_16.png)
Probable Cause: No action requiredWBEM EventID: 573. WBEM ProviderName: FPLIndicationProvider5584WarningCould not release the crossbar port semaphore. Event ID5630Event Severity Event DescriptionWarningPAL B execution rom warning. Probable Cause: PALBROM has generated awarning. Recommended Action: Reboot, update SFW if necessary, if problem persistscontact your HP representative for support.
WBEM EventID: 588. WBEMProviderName: FPLIndicationProviderErrorAn error was encountered when firmware tried to update the Group B Profile. Event ID98Event Severity Event DescriptionWarningMC: Get PAL features failed. Probable Cause: SFW failed to get the feature set fromPAL Recommended Action: Update firmware to get newer PAL that support thePALGETFEATUREs call. WBEM EventID: 443. WBEM ProviderName:FPLIndicationProviderWarningMC: Previous PAL rendezvous failed; rebooting. Probable Cause: PAL Failed torendezvous the processors during a MCA.
Event ID20572132Event Severity Event DescriptionErrorThe computed checksum for ESI Table incorrect. Probable Cause: Table corrupted.Recommended Action: Reboot. If problem persists contact your HP representativefor support.
WBEM EventID: 456. WBEM ProviderName: FPLIndicationProviderWarningESI Table contains an unsupported entry type. Probable Cause: Corrupted table.Recommended Action: Reboot system. Event ID355737Event Severity Event DescriptionWarningEFI unable to read current speedy boot settings. Probable Cause: BMC not functioningproperly. Recommended Action: Reset the BMC.
Contact your HP representative tocheck the BMC. WBEM EventID: 470.
WBEM ProviderName: FPLIndicationProviderErrorUnpermitted SAL callback attempted. Probable Cause: Internal EFI error.Recommended Action: Reboot. Event ID5234Event Severity Event DescriptionWarningmonarch not lowest stepping. Probable Cause: The monarch processor has a steppingthat is greater than a slave processor installed in the system. Recommended Action:No action is needed. If problem persists, update System FW or contact your HPrepresentative for support. WBEM EventID: 485.
WBEM ProviderName:FPLIndicationProviderWarningprocessors are over clocked. Event ID695770Event Severity Event DescriptionWarningThe system ID(s) currently in the system is invalid. Probable Cause: The system ID(s)is invalid and the user did not elect to fix the problem. Recommended Action: Rebootthe system and follow the prompts to fix the issue. WBEM EventID: 498. WBEMProviderName: FPLIndicationProviderErrorEFI unable to find the SAL services for installing interrupt handlers.
Event IDEvent Severity Event DescriptionWarningUnable to enter normal system mode because EFI/SAL interface not initialized.Probable Cause: Internal EFI error. Recommended Action: Upgrade system firmware.If problem persists, contact HP support to troubleshoot the problem. WBEM EventID:512. WBEM ProviderName: FPLIndicationProvider5772ErrorUnable to initialize part of the SAL/EFI interface.
Probable Cause: Incompatibleversions of EFI and SAL, Internal EFI error. Recommended Action: Reboot. Event IDEvent Severity Event DescriptionErrorAn unexpected or invalid value was read from a crossbar remote route table.
ProbableCause: An XBC is indicating a port failure Recommended Action: Validate all of thecells connectivity to the PDCheck the XBC chips seating reset the system replaceeither cells/system backplane WBEM EventID: 527. WBEM ProviderName:FPLIndicationProviderErrorError reading the PORTnNEIGHBORINFO XBC CSR. Probable Cause: Possiblebad link, crossbar, or cell connection. Event IDEvent Severity Event DescriptionErrorThe XBC neighbor chip number does not match the expected value for this topology.Probable Cause: Bad connection between XBC and cell.
Recommended Action: Resetcell. WBEM EventID: 542. WBEM ProviderName: FPLIndicationProviderErrorThe XBC neighbor port number does not match the expected value for this topology.Probable Cause: Bad connection between XBC and cell. Recommended Action: Resetcell. WBEM EventID: 543.
Event ID60Event Severity Event DescriptionErrorCoherency controller (CC) registers indicate a Deadlock Recovery Reset. ProbableCause: Coherency controller (CC) resources are deadlocked and the CC is resettingthe cell. Recommended Action: Analyze the Deadlock Recovery logs (like MCA logs)to determine the cause of the failure. WBEM EventID: 1019. Event ID768540Event Severity Event DescriptionWarningAn unexpected XBC forward progress state was continually found until timing out.Probable Cause: An XBC is indicating a port failure Recommended Action: Validateall of the cells connectivity to the PDCheck the XBC chips seating reset the systemreplace either cells/system backplane WBEM EventID: 601. Event IDEvent Severity Event DescriptionWarningManagement Processor detected an I2C Communication Error with BMC. ProbableCause: An I2C Communication failure with the Baseboard Management Controllerwas detected.
Without I2C communication, the system cannot be powered on/off orreset. Check the I2C communication via the 'SR' command or the 'PS' command. Ifit is indeed down, look for hardware reasons. Event ID42Event Severity Event DescriptionErrorPartition being reset due to watchdog timeout expiring.
Probable Cause: The watchdogmechanism triggers the MP to reset a partition if its OS becomes unresponsive. Anunresponsive OS is detected when the OS fails to refresh the watchdog timer beforeit expires. Event ID78287829Event Severity Event DescriptionWarning1 Side Converter Over Temp. Probable Cause: If this code is not accompanied byother codes pointing to the same Bulk Power Supply, then it is an internal componentfailure. Recommended Action: Contact HP Support personnel to troubleshootproblem. WBEM EventID: 2436. WBEM ProviderName: FPLIndicationProviderWarningBulk Power Supplies are not Redundant.
Event ID786544Event Severity Event DescriptionWarningIO Fan Failed. Probable Cause: IO Cooling Fan Failed Recommended Action: ReplaceIO Fan Module as soon as possible following the IO Fan Module Remove and ReplaceProcedures.
WBEM EventID: 678. WBEM ProviderName: FPLIndicationProviderWarningCabinet Power System is in overload.
Probable Cause: A Bulk Power Supply hasfailed, or, entities were added. Event ID787879Event Severity Event DescriptionErrorIO Power Board Over temperature. Probable Cause: The ambient air is too warm.Recommended Action: Check the Error Log for other Overtemp Warnings to confirmthe environmental problem. WBEM EventID: 690.
WBEM ProviderName:FPLIndicationProviderErrorIO Power Board Fault. Probable Cause: The named power brick on the named IOChassis has failed. Event ID4846Event Severity Event DescriptionErrorSystem Backplane voltage margin failed.
Probable Cause: The CLU was unable towrite to the voltage margin register on the System backplane. Recommended Action:Try re-margining the system backplane and check connections. If many I2C accessevents are occurring inspect the UGUY utilities board. WBEM EventID: 700. Event IDEvent Severity Event DescriptionErrorCPUs loaded in wrong order. Probable Cause: CPUs not loaded in correct order.Recommended Action: Load CPUs in order 0, 1, 2, 3.
WBEM EventID: 615. WBEMProviderName: FPLIndicationProvider7963ErrorThe XBC SBE and LPE errors were not cleared properly. Probable Cause: the linkgenerated a new error Recommended Action: check CC, check link Check logs forother errors. If error is persistent, replace cell board WBEM EventID: 1031. Event ID814348Event Severity Event DescriptionWarningAn unknown error has been detected by the PDHC firmware.
Probable Cause:Hardware in unknown state, or programming bug found. Recommended Action:Recommended Action: Upgrade PDHC firmware to latest revision.
If already atcurrent revision, contact HP support personnel to troubleshoot the problem. WBEMEventID: 627. Event ID908194Event Severity Event DescriptionErrorBoot is disabled because the cell type does not match the System FW ROM type.Probable Cause: The cell's installed CPU modules do not all have the same type,frequency and partition compatibility, so the Cell type cannot be accuratelydetermined. Recommended Action: Contact HP support personnel to troubleshootthe mismatched CPU module WBEM EventID: 712. Event IDEvent Severity Event DescriptionErrorFailed reading an XBC forward progress register. Probable Cause: Fabric access errorRecommended Action: Contact HP Support personnel to analyze the fabric.
WBEMEventID: 726. WBEM ProviderName: FPLIndicationProviderErrorCould not find an adjacent XBC due to broken fabric links. Probable Cause: Possiblecrossbar failure Recommended Action: Contact HP Support personnel to analyzethe crossbar. WBEM EventID: 727. Event ID86438645Event Severity Event DescriptionErrorInternal firmware programming error in the PMI handler.
Probable Cause: Reportthe IP to the firmware team. Reset the system.
This cannot be worked around in thefield. WBEM EventID: 743. WBEM ProviderName: FPLIndicationProviderErrorDuring a Cell On Line Add inconsistent number of cells discovered. Probable Cause:This can be caused by inconsistent profile information. Event IDEvent Severity Event DescriptionErrorAttempt to update the PD PDT with OLA Cell failed. Probable Cause: Unable to addOLA cell's PDT to the partition PDT.
Error accessing PDH space. Check fabricconnection between OLA cell and core cell. Recommended Action: Gather IPMI eventlogs and contact HP Support. WBEM EventID: 6959.
WBEM ProviderName:FPLIndicationProviderWarningAttempt to update the cell map to include the OLA Cell failed. Probable Cause:Unable to write registers on the CC. Event ID238745Event Severity Event DescriptionErrorAn error was encountered while resetting the SBA. Probable Cause: The SBAcomponent could not reset one or more LBA ropes, probably due to faulty hardware.Recommended Action: Replace the failed IO backplane. WBEM EventID: 781. WBEMProviderName: FPLIndicationProviderWarningThere was an error initializing the IO link.
Event IDEvent Severity Event DescriptionErrorFirmware was unable to find a suitable block of main memory to relocate ROM.Probable Cause: Probably caused by lots of PDT entries, or no main memory present.WBEM EventID: 1036. WBEM ProviderName: FPLIndicationProviderWarningCell started OLA but is not configured in the complex profile of the partition. ProbableCause: Cell was issued an OLA command without first updating the complex profileto reflect its slot as configured in the partition.
Event IDEvent Severity Event DescriptionWarningFirmware could not set Pal Proc features. Probable Cause: FW MCA code uses thisPALSETPROCFEATURES to escalate future MCA to BINIT. This event id whenemitted during an MCA processing means that any subsequent global MCA wouldnot cause all the processors in the PD to MCA again. WBEM EventID: 2443. WBEMProviderName: FPLIndicationProviderWarningMeans that the error log space in the Nvram has not been allocated.
Event IDEvent Severity Event DescriptionWarningThe System Flash Write Enable bit is incorrectly set and now clearing by PDC.Probable Cause: The System Flash Write Enable bit is incorrectly set by hardwareand now cleared by PDC. Recommended Action: If this chassis code occurs in everyboot then contact HP Support personnel to troubleshoot the problem. WBEM EventID:1764. WBEM ProviderName: FPLIndicationProviderErrorFirmware encountered a problem trying to initialize. Event IDEvent Severity Event DescriptionWarningFailed to write the CC link disable register. Probable Cause: Fabric Access Failure.Recommended Action: Contact HP Support personnel to analyze the fabric. WBEMEventID: 853.
WBEM ProviderName: FPLIndicationProviderWarningAn unknown backplane type was found. Event ID74897558Event Severity Event DescriptionErrorError while copying the XBC routing to the local port. Probable Cause: Error accessingXBC CSRs. Recommended Action: Contact HP Support personnel to analyze thefabric. WBEM EventID: 870. WBEM ProviderName: FPLIndicationProviderErrorA read after write of a XBC CSR failed.
Probable Cause: Fabric Access Error, XBCKey Disabled. Event IDEvent Severity Event Description8976WarningUnexpected fabric firmware error. Probable Cause: An unanticipated error occurred.Contact HP Support personnel to analyze the IPMI FPL log. WBEM EventID: 884.WBEM ProviderName: FPLIndicationProvider8979WarningThe CPU is performance or functionally restricted.
Probable Cause: A CPU is broken.Replace it. WBEM EventID: 885. WBEM ProviderName: FPLIndicationProviderWarningThe RTC was found to be invalid and has been cleared. Event IDEvent Severity Event DescriptionWarningCell/Partition to be reset because PDC couldn't read PDH memory. Probable Cause:Cell hardware problem like PDH memory itself, the CC chip, the executing CPU orinteraction between any of these cell components. Recommended Action: Troubleshootthe cell and either fix it or replace it.
WBEM EventID: 897. WBEM ProviderName:FPLIndicationProviderWarningCell/Partition to be reset because PDC couldn't read PDH memory. Event ID85Event Severity Event DescriptionWarningCell about to be halted because PDC couldn't determine relocated address of code.Probable Cause: Cell was unable to access its own PDH memory. RecommendedAction: Troubleshoot the cell board and replace it if necessary. WBEM EventID: 910.WBEM ProviderName: FPLIndicationProviderWarningHalting cell because a CPU didn't complete the task for which it was awakened.
Event ID62Event Severity Event DescriptionErrorCell failed compatibility checks. Probable Cause: A Cell or CPU module's FRU datais programmed incorrectly. Recommended Action: If this is in manufacturing,re-program the FRU specific field of the FRU data for the cell or CPU module.Otherwise, contact HP Support personnel to troubleshoot the problem. WBEMEventID: 923. Event IDEvent Severity Event DescriptionWarningError clearing the init packet received bit in the XIN error mask. Probable Cause: CCaccess failure.
Recommended Action: PDC Reviewed alert level for SR - 9/6/03 CC.WBEM EventID: 938. WBEM ProviderName: FPLIndicationProviderWarningFailed to read the XBC's Port Status register. Event ID84948564Event Severity Event DescriptionWarningFailed to write the XBC CSR that contains the number of failed links. Probable Cause:Fabric Access Failure Recommended Action: Contact HP Support personnel to checkXBC, Backplane, CC, look for additional chassis codes to describe the problem. WBEMEventID: 949.
Event ID989652Event Severity Event DescriptionErrorThe system firmware had an error with the structured error handling mechanism.Probable Cause: Either there is an error in the system firmware or the system firmwarehas exhausted all resources. Recommended Action: Invalidate NVM or check fornewer version of system firmware. WBEM EventID: 963.
Event ID968166Event Severity Event DescriptionWarningWindows: Server Agents Management data not accessible, locked property. ProbableCause: The installed management software has detected an unstable state of theunderlying IPMI (Intelligent Platform Management Interface) subsystem and hasdisabled all management information from being shown by any manageabilityapplications. Event ID97089709Event Severity Event DescriptionWarningFirmware unable to relocate VGA BIOS. Probable Cause: Most likely there is apermanent memory error in the VGA BIOS region (physical address 0xc0000 - 0xdffff).Recommended Action: Replace the DIMM causing the permanent memory error inthe VGA BIOS region. The PDT reports which DIMM is causing errors in the physicaladdress range 0xc0000 - 0xdffff.
WBEM EventID: 986. Event ID975068Event Severity Event DescriptionWarningThe core cell selected is not in the rendezvoused partition. Probable Cause:Configuration error, main backplane failure; the intended core cell failed duringboot. Recommended Action: check partition configuration, check for failed cells,check for additional chassis codes indicating more failure detail. WBEM EventID:997. Event ID97789780Event Severity Event DescriptionErrorWindows: Predictive Failure in Memory (Critical). Probable Cause: You will receivethis message if the system is correcting a lot of ECC single bit errors.
It may meanthat the module is about to fail, or environmental conditions in the server are causingmore errors than usual. Event ID49986770Event Severity Event DescriptionWarningFailed to copy the XBC CSR Error Symbol01 Block. Probable Cause: Fabric AccessFailure; Possibly an invalid destination address. Check hardware, Contact HP SupportWBEM EventID: 1833. WBEM ProviderName: FPLIndicationProviderWarningFailed to copy the XBC CSR Error Symbol23 Block.
Probable Cause: Fabric AccessFailure; Possibly an invalid destination address. Event IDEvent Severity Event DescriptionWarningCPU deconfigured due to error obtaining parameters from PAL. Probable Cause:internal error.
Recommended Action: the CPU will be deconfigured. If the errorpersists after a powercycle, contact HP Support.
WBEM EventID: 1846. WBEMProviderName: FPLIndicationProviderWarningCPU deconfigured due to failure retrieving icache parameters from PAL. ProbableCause: internal error. Recommended Action: during system boot the CPU will bedeconfigured. Event IDEvent Severity Event DescriptionWarningRight ejector latch is open. Probable Cause: The right ejector latch is open.Recommended Action: Close the right ejector latch on the specified cell. WBEMEventID: 2412.
WBEM ProviderName: FPLIndicationProviderWarningThe optical emitters on the cell latch sensors are not functioning. Probable Cause:There is a hardware failure. Recommended Action: The cell board must be repairedor replaced. WBEM EventID: 2411.
Event ID10377Event Severity Event DescriptionWarningfabric API is about to open the a link going out of the local cell. Probable Cause: Anerror prevented the use of a fabric link. Recommended Action: Collect IPMI eventlogs for more information regarding the failure. Contact your HP SupportRepresentative to investigate the fabric subsystem. WBEM EventID: 2914. Event ID74Event Severity Event DescriptionWarningXBC port with an unexpected neighbor chip type.
Data field: (expected chip type) (actual chip type 16) (xbcNum 32) (portNum 48). Probable Cause: System firmwarenoticed a discrepancy from the expected topology of the system. RecommendedAction: Capture IPMI event logs, look for additional errors. Contact your HP SupportRepresentative to analyze the fabric WBEM EventID: 2921. Event ID10401Event Severity Event DescriptionWarningError reading Skyline ALRECALBID CSR. Data field: (Skyline port) (Cell number56).
Probable Cause: System firmware was unable to read a fabric hardware register.Recommended Action: Capture IPMI event logs, look for additional errors. Contactyour HP Support Representative to analyze the fabric WBEM EventID: 2931. Event ID76Event Severity Event DescriptionWarningArches Fabric Traversability code unexpectedly found the local cell link not connected.Data field: linkState (0 = connected, 1 = link pending, 2 = not connected, -1 = error).Probable Cause: A previously healthy link was found to have fatal errors.Recommended Action: Capture IPMI event logs, look for additional errors. Event IDEvent Severity Event DescriptionWarningIn SetupNCTable, a write to the GLOBALLINKSELNONCOH CSR failed.
Datafield: (data written to CSR) (actual CSR data read 32). Probable Cause: Systemfirmware was unable to write a fabric hardware register. Recommended Action:Capture IPMI event logs, look for additional errors.
Contact your HP SupportRepresentative to analyze the fabric WBEM EventID: 2952. Event IDEvent Severity Event DescriptionWarningSystem Firmware was unable to access the configured set stored in the complexprofile. Probable Cause: SFW was unable to access the configured set stored in thecomplex profile.
Recommended Action: Collect IPMI events and contact your HPSupport Representative. WBEM EventID: 6874. WBEM ProviderName:FPLIndicationProviderWarningSystem Firmware detected an error during Fabric Init. Probable Cause: Error detectedby SFW during Fabric Init.
Event IDEvent Severity Event DescriptionWarningFailure to get the XBC Global Semaphore address. Probable Cause: Failed to get afabric address Recommended Action: Look for additional IPMI event logs. Contactyour HP Support Representative to analyze the fabric. WBEM EventID: 4852. WBEMProviderName: FPLIndicationProviderWarningFailed to write the XBC Global Semaphore. Event ID1062180Event Severity Event DescriptionWarningError while routing the remote side of a route.
Probable Cause: System Firmwarewas unable to route the crossbar fabric. Recommended Action: Collect IPMI Eventlogs. Contact your HP Support Representative to troubleshoot the fabric and/orbackplane subsystem. WBEM EventID: 4898. Event ID10705Event Severity Event DescriptionWarningUnexpected return from an Arches Fabric vertex module function while copying acell's graph. Data field: return value from vertex module function.
Probable Cause:Internal firmware error or data corruption. Recommended Action: Capture IPMIevent logs, look for additional errors.
Contact your HP Support Representative toanalyze the fabric WBEM EventID: 4528. Event ID1081482Event Severity Event DescriptionErrorAn internal firmware inconsistency exists or the server exhausted its internal resourcesand is unable to create an fPars EFI ownership variable for a CPU device in thepartition. Either of these conditions is fatal. Probable Cause: NVRAM corruption offPars specific database. Recommended Action: Restore NVRAM to factory defaults.Reset server and reconfigure soft partitions. Event IDEvent Severity Event DescriptionWarningOver-temperature condition detected on a processor. Probable Cause: The processortemperature is above the operating range.
The processor's performance is throttledby the firmware to reduce the temperature Recommended Action: The firmware hasalready taken necessary action. Once the temperature comes down, the firmwarewill restore the processor's performance to normal WBEM EventID: 4543. Event ID84Event Severity Event DescriptionWarningFirmware error setting the NVRAM value of preferred-bsp for the vPars monitor.The partition will boot using the PD monarch, but the value of preferred-bsp maynot match this CPU. Probable Cause: Firmware could not store to the NVRAM holdingthe EFI preferred-bsp variable Recommended Action: Reset the server, restore factorydefault NVRAM and reconfigure soft partitions. Event IDEvent Severity Event DescriptionWarningToo many edges were encountered during a procedure call.
Data Field: link count.Probable Cause: There was a problem while collecting a list of fabric link info.Recommended Action: Look for additional IPMI event logs. Contact your HP SupportRepresentative to analyze the fabric. WBEM EventID: 4864. Event IDEvent Severity Event DescriptionWarningAn error was encountered while routing the fabric. This error prevents an appropriateroute from being selected. Data Field: Destination Cell 56 XBC Port 44 XBC # 32 return status.
Probable Cause: An error occurred while routing the fabricRecommended Action: Contact your HP support representative to inspect the fabricand system firmware. WBEM EventID: 4873. Event IDEvent Severity Event DescriptionErrorClock fault for clocks supplied from the Hot Swap Oscillator (HSO) board to thesystem backplane.
HSO has reported a fault or has been removed. The data fieldcontains the physical location of the HSO.
Probable Cause: HSO assembly has reporteda fault or has been removed. Recommended Action: Check HSO assembly. WBEMEventID: 4915. Event ID88Event Severity Event DescriptionWarningThe system software violated one of the 'well-behavedness' rules of soft partitionsand tried to call a firmware procedure within the firmware instance of a sibling. Thisis an access violation and firmware rejects the call. Probable Cause: System SoftwareDefect - using the wrong entry address for the owner of the CPU. Event IDEvent Severity Event DescriptionErrorIO Backplane +12V power fault.
Probable Cause: One of the +12v VRM's is reportinga fault. One failure and power state is N, after two power state will be N.Recommended Action: Check IO backplane power board. Faulted VRM is given byPS command. WBEM EventID: 6828. WBEM ProviderName: FPLIndicationProviderErrorIO Backplane 1.5V temperature fault.
Event ID1170390Event Severity Event DescriptionWarningArfRouteEnable returned an unexpected error while enabling routes to the localcell. Data field: (local cell number 56) (bitmap of routes to enable).
Probable Cause:An error occurred while routing the fabric. Recommended Action: Collect IPMI eventlogs, and contact your HP support representative to inspect the fabric and systemfirmware. WBEM EventID: 4951. Event ID11723Event Severity Event DescriptionErrorAn ISA UART was created without a data structure. A PCI UART structure exists.Probable Cause: The ISA UART code was called when a PCI UART structure and noISA UART structure were created.
Recommended Action: Verify that the configurationcontains the correct UART type. WBEM EventID: 5138. Event ID1185092Event Severity Event DescriptionErrorReboot failed. The virtual machine will exit. Probable Cause: The virtual machinewas unable to restart. The next event contains the Unix error.
Recommended Action:Restart if possible WBEM EventID: 5151. WBEM ProviderName:FPLIndicationProviderWarningSetupInitialCohTables returned an error. Data field: (cell set 32) (return valuefrom SetupInitialCohTables). Event ID11966Event Severity Event DescriptionWarningFirmware had an unexpected error while setting up links.
Data field: vType1 63:56 vPort1 55:48 vId1 47:32 vType2 31:24 vPort2 23:16 vId2 15:0. ProbableCause: An error occurred while routing the fabric, possible data corruption orfirmware error. Event IDEvent Severity Event DescriptionErrorCell on-line add/delete in FPARs mode failed to get the FPARs semaphore. ProbableCause: Cell on line add/delete in FPARs mode failed to get the FPARs semaphore.Recommended Action: Do not use cell on line add/delete in FPARs mode. WBEMEventID: 6900. WBEM ProviderName: FPLIndicationProviderErrorMore than one processor from an FPAR called into cell on-line add/delete.
Event IDEvent Severity Event DescriptionWarningAn error encountered while retrieving the expected neighbor fabric chip fordistributing traffic over crossbar links. Probable Cause: Unexpected error retrievinginformation from the fabric graph. Recommended Action: Collect IPMI event logsand contact your HP Support Representative to investigate the fabric system firmwaresubsystem WBEM EventID: 5189.
Event ID96Event Severity Event DescriptionWarningAn error occurred while retrieving the crossbar chip number. Probable Cause: Systemfirmware had difficulty determining the crossbar number from the graph datastructure Recommended Action: Capture IPMI event logs, look for additional errors.Contact your HP Support Representative to analyze the fabric WBEM EventID: 5251.
Event IDEvent Severity Event Description12135WarningDuplicate DIMM serial numbers have been detected. Data field gives physical locationof DIMM. Check for other events specifying other DIMMs with same serial number.Probable Cause: Multiple DIMMs have the same serial number. RecommendedAction: Replace DIMMs with duplicate serial numbers. Ensure new DIMMs haveunique serial numbers. WBEM EventID: 6564.
Event ID98Event Severity Event DescriptionWarningThe operating system has recovered from a PCI error. Probable Cause: If the dataword is not 0x000000, then the problem is most likely with the PCI card.If the value of the data word is 0x000000, then check event log withkeyword PCIERRORSTATUS. If PCIERRORSTATUS 1, then the problem is inthe connection between System Bus Adapter and Lower Bus Adapter.
Event ID12227Event Severity Event DescriptionErrorThis is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried toacquired the same semaphore twice which resulted in a deadlock. This is an internalSFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL,console logs and forward them to the SFW team.
Also note all activities around thetime of this event. Event ID100Event Severity Event DescriptionWarningOver-Temperature or power condition detected for processor. Probable Cause: Theprocessor temperature or power has exceeded normal limits. The Enhanced ThermalManagement (ETM) feature of the processor has been employed to reduce the chippower to allow operation within normal limits. If this condition persists, this willhave an adverse impact on the performance of this processor. Event IDEvent Severity Event DescriptionWarningThe cell being added has incompatible hardware or firmware revision with thepartition.
Probable Cause: The cell being added has incompatible hardware orfirmware revision with the partition. Recommended Action: Previous events willgive a description of the error that led to this event. These need to be corrected beforethe cell can be added. WBEM EventID: 6892. Event IDEvent Severity Event DescriptionWarningAn electronic keying problem has been detected. Probable Cause: The 'e-keying error'only occurs during the power-up if the SVB must be left off due to an electronickeying problem. Recommended Action: Try installing SVB in a different location.WarningA Blade was installed in an improper location in the enclosure in violation of enclosureconfiguration rules.
Review the installation documentation for additional information. Event ID12627Event Severity Event DescriptionErrorBulk power supply (BPS) redundancy has been lost on one or more row(s) of powersupplies in the complex. The further loss of a single BPS or an AC grid will mostlikely result in the shutdown of partitions.
Probable Cause: An AC source has beenlost. Recommended Action: Verify that the chassis is connected to working powergrid(s). WBEM EventID: 7253.
Event IDEvent Severity Event Description118Error%1 File access failure:%2.%3%1 - 'component name'%2 - 'Error opening file'%3- 'See log file for details.118Error%1 File access failure:%2.%3%1 - 'component name'%2 - 'Error writing to softlogfile'%3 - 'See log file for details.118Error%1 File access failure:%2.%3%1 - 'component name'%2 - 'Error resetting filepointer'%3 - 'See log file for details.118Error%1 File access failure:%2. HP System Management Homepage EventsSource in Windows Event Log: HP System Management HomepageEvent IDEvent Severity Event Description9Informational The HP System Management Homepage Win32 service has been started successfully.10Informational The HP System Management Homepage Win32 service has been stopped successfully.11ErrorThe HP System Management Homepage Win32 service could not be startedsuccessfully. HP BMC IPMI Driver EventsSource in Windows Event Log: hpipmiEvent IDEvent Severity Event DescriptionErrorDuring communication with the IPMI BMC device, the system detected that the BMCentered an error state.
The driver attempted to set the BMC state to a working statebut failed to do so. After 20 successive attempts, the driver has set the IPMI deviceto a non working state.
It is recommended that you seek assistance fromHewlett-Packard. Server Provider (SysEvt) EventsSource in Windows Event Log: HP SystemEvent IDEvent Severity Event Description2001Informational HP Insight Management WBEM Providers have started.
Hi, i'm having a problem that i try many ways to solve but i could not. The problem is updating or installing WBEM providers on Windows Server Enterprise 2008 R2. I'm doing several testing with HP SIM.
1) Installed the Server with all features with HP Smart Start (WMI and SNMP), then configure the credentials and necesary configuration to HP SIM view the server 2) Both protocols worked, and WBEM as default protocol. On HP SIM i see all information of the server via WBEM.
So far so good. 3) Then uninstall WBEM Providers from Control Panel/Uninstall Programs and reboot the server. This i made because on others servers the WBEM Providers is not installed, and i'm testing to install in this scenario, when not install with HP Smart Start, and install with HP Smart Update Manager. 4) I download the ProLiant Support Pack 8.70 from HP and run HP SUM (Smart Update Manager) 5) Then install de HP Insight Management WBEM Providers, when it finish show a fail message: HP Smart Update Manager Installation Log Source: cp013839.exe Version: 2.8.0.0 Log Date: 16:11:43 Log Session Start. Executing setup utility - cpqsetup.exe. Setup Session Beginning - 16:11:44 - Command Line Parameters Given: /silent Name: HP Insight Management WBEM Providers for Windows Server 2003/2008 x64 Editions New Version: 2.8.0.0 Determining component installation state. Is operating system supported.
Yes - Is necessary disk space available. Yes - Is hardware present. Yes - Is component already installed. No - Is component marked for removal. No - Installed component version status.
Older - Checking dependency list. The software is not installed on this system, but is supported for installation. the component will be installed Initiating installation. Checking for previous version. Does not exist. Executing MSI. The installation procedure did not complete successfully.
An error occurred during the setup process. The operation was not successful. End Session - Setup utility completed.
Log Session End. 16:12:16 Return Code (0) 6) The HP Insight Management WBEM Providers install any way, i can see in Start/AllPrograms the folder HP Insight Management WBEM Providers, but on HP System Management Homepage/ Settings/ i can't see the option to select between WEB or SMTP Protocol, only show SMTP Web Agent.
7) One thing that i see is that the HP WMI Storage Providers Service disappeared on Windows Services, is not on the list. (i don't know if this is the problem or something related) If someone can help me i would appreciate! Hi, BTW what is the hardware model on which you are installing WBEM? Take a look at this CA c02288378: Also refer to HP Insight Management WBEM Providers 2.8.0.0 Hardware Support Matrix You can try Uninstalling SNMP-Based HP Insight Management Agents and then install WBEM. To uninstall HP Insight Management Agents on a single local server: For Windows Server 2008, open the Windows Programs and Features interface. Select HP Insight Management Agents. For Windows Server 2008, right-click, and select Uninstall.
At the prompt, to confirm the removal of HP Insight Management Agents from the system, click Yes. If the HP System Management Homepage is active in a browser window, close and reopen it to verify that it reflects the change. Hope this helps.