Am also getting the same issue, from abt 3hrs it is showing the same screen "Please wait,anasyzing system". any clue how u have resolved.
↧
Re: DL380p Gen8 Unexpected Shutdown
↧
Re: Cannot POST, rebooting at 10% during CPU initialization, Code 0168 and/or 4048
flip switch 6 on, power up the system, after a few moments, you should see a message that CMOS/NVRAM has been reset or cleared, power system off, flip switch 6 back to the off posisiton, boot as normal
↧
↧
Re: Cannot POST, rebooting at 10% during CPU initialization, Code 0168 and/or 4048
Hmmm... flipping switch 6 doesn't make a difference. the system still reboots during the post before the CMOS reset happens.
=(
Any other ideas?
Thanks,
↧
Re: ProLiant DL380 Gen5 Display Resolution
Hi,
This forum is for HP Service Manager product. Let me try to get the correct channel for you.
Regards,
↧
Re: Cannot POST, rebooting at 10% during CPU initialization, Code 0168 and/or 4048
mr_yellow wrote:Hmmm... flipping switch 6 doesn't make a difference. the system still reboots during the post before the CMOS reset happens.
=(
Any other ideas?
Thanks,
If you haven't, please open a support ticket
↧
↧
Re: What does this mean? - RESTful error during POST on a ProLiant DL380 Gen9
Try updating the system ROM and the iLO firmware
↧
ML310 G5p PCIe version/generation?
The spec sheet claims the ML310 G5p (and G5?) are "PCI-Express 3.0 Compliant" on page 4, section "Industry Standard Compliance".
But the Intel 3210 Chipset only claims to support PCIe 1.1 .
What generation of PCIe does it support?
↧
Re: What does this mean? - RESTful error during POST on a ProLiant DL380 Gen9
Hi Jimmy,
I've updated both firmware but no change.
Product Name: ProLiant DL380 Gen9
Product ID: 752689-B21
System ROM: P89 v1.52 (11/10/2015)
System ROM Date: 11/10/2015
Backup System ROM: 07/20/2015
License Type: iLO 4 Advanced
iLO Firmware Version: 2.30 Aug 19 2015
↧
2012 R2 on a Proliant ML310 G5
Hello,
I can't find a link where I can check the compatibility with Windows Server 2012 R2 for an HP ML310 G5 server.
Is there someone that have installed WS 2012 R2 on this server?
Any link where I can found more informations?
Thank you.
↧
↧
Re: What does this mean? - RESTful error during POST on a ProLiant DL380 Gen9
One last suggestion would be to reset the system using mainainance switch 6. If this doesn't correct the error you need to open a support call with HPE.
power off, switch 6 on, power system on, system will POST and display a message system has been reset. power off, switch 6 off position.
↧
Re: 2012 R2 on a Proliant ML310 G5
you can find the server certification and support matrix here: http://h17007.www1.hpe.com/us/en/enterprise/servers/supportmatrix/windows.aspx
2012 was not tested on G5 so it is not a supported OS
↧
Re: What does this mean? - RESTful error during POST on a ProLiant DL380 Gen9
Hi Jimmy. I performed the steps you mentioned but still get the same error, so I'll log a ticket.
Many thanks for your help.
Andy.
↧
hprest.exe type HPBios not available
I am using hprest.exe to set different Bios settings like ServerAssetTag which are located at the type HpBios.1.2.0
Now i have a problem with one ProLiant ML350 Gen9 out of 10, where hprest says that the type HPBios. is not available: Unable to locate instance for 'HPBios.'
If I use the command types than the problem ML350 Gen9 returns this:
hprest > types Type options: AccountService.1.0.0 BaseNetworkAdapter.1.1.0 Chassis.1.0.0 Collection.1.0.0 ComputerSystem.1.0.0 EthernetNetworkInterface.0.92.0 EventService.1.0.0 ExtendedError.1.0.0 FwSwVersionInventory.1.0.0 HpESKM.1.0.0 HpHttpsCert.1.0.0 HpSecureBoot.1.0.0 HpSecurityService.1.0.0 HpServerPCISlot.1.0.0 HpServerPciDevice.1.0.0 HpSmartStorage.1.0.0 HpSmartStorageArrayController.1.0.0 HpSmartStorageDiskDrive.1.0.0 HpSmartStorageLogicalDrive.1.0.0 HpSmartStorageStorageEnclosure.1.0.0 HpiLOActiveHealthSystem.1.0.0 HpiLODateTime.1.0.0 HpiLOEmbeddedMedia.1.0.0 HpiLOFederatedGroupCapping.1.0.0 HpiLOFederationGroup.1.0.0 HpiLOFederationPeers.1.0.0 HpiLOFirmwareUpdate.1.0.0 HpiLOLicense.1.0.0 HpiLOSSO.1.0.0 LogService.1.0.0 Manager.1.0.0 ManagerAccount.1.0.0 ManagerNetworkService.0.11.0 PowerMetrics.0.11.0 ServiceRoot.1.0.0 SessionService.1.0.0 SnmpService.1.0.0 ThermalMetrics.0.10.0 VirtualMedia.1.0.0
And we see HPBios.1.2.0 is missing, on an other ML350 Gen9 with the same Bios Version, ILO Version and UEFI enabled i get following output via hprest types:
hprest > types Type options: AccountService.1.0.0 BaseNetworkAdapter.1.1.0 Chassis.1.0.0 Collection.1.0.0 ComputerSystem.1.0.0 EthernetNetworkInterface.0.92.0 EventService.1.0.0 FwSwVersionInventory.1.0.0 HPPowerMeter.1.0.0 HpBaseConfigs.0.10.0 HpBios.1.2.0 HpBiosMapping.1.2.0 HpESKM.1.0.0 HpHttpsCert.1.0.0 HpSecureBoot.1.0.0 HpSecurityService.1.0.0 HpServerBootSettings.1.2.0 HpServerPCISlot.1.0.0 HpServerPciDevice.1.0.0 HpSmartStorage.1.0.0 HpSmartStorageArrayController.1.0.0 HpSmartStorageDiskDrive.1.0.0 HpSmartStorageLogicalDrive.1.0.0 HpSmartStorageStorageEnclosure.1.0.0 HpiLOActiveHealthSystem.1.0.0 HpiLODateTime.1.0.0 HpiLOEmbeddedMedia.1.0.0 HpiLOFederatedGroupCapping.1.0.0 HpiLOFederationGroup.1.0.0 HpiLOFederationPeers.1.0.0 HpiLOFirmwareUpdate.1.0.0 HpiLOLicense.1.0.0 HpiLOSSO.1.0.0 HpiSCSISoftwareInitiator.1.0.0 LogService.1.0.0 Manager.1.0.0 ManagerAccount.1.0.0 ManagerNetworkService.0.11.0 PowerMetrics.0.11.0 ServiceRoot.1.0.0 SessionService.1.0.0 SnmpService.1.0.0 ThermalMetrics.0.10.0 VirtualMedia.1.0.0
So this types are missing on the problem Sever:
HpBaseConfigs.0.10.0 HpBios.1.2.0 HpBiosMapping.1.2.0 HpServerPciDevice.1.0.0 HpiSCSISoftwareInitiator.1.0.0
Would be nice if someone can point me in the right direction why this type is available on 9 of my 10 ML350 Gen9?
(I already tryed reflash 2.30 ilo4 firmware and reset ilo to factory defaults - nothing helped)
Thanks a lot!
↧
↧
SNMP returning degraded disk controller degraded
We use PRTG to monitor the health of a number of ProLiant Servers via SNMP.
One is an ML350 G6 running Server 2008 R2. Before Christmas, PRTG started to warn that the disk controller on this server was degraded, which normally means a disk in the RAID has dropped.
The server has two SmartArray controllers, a P410i (4 x HDs) and a P212 (Ultrium drive only).
HP SSA reports no errors on the P410i but does show an orange warning for the P212. The warning is that no configurable physical drives are attached. Correct!
However, SNMP monitoring reports disk controller degraded - why?
Walking SNMP OIDs on the server returns:
.1.3.6.1.4.1.232.6.1.3.0 (System health) - 2
1.3.6.1.4.1.232.3.1.3.0 (Drive array health) - 3 (degraded)
The server has been in use August 2011 wtih this SA configuration but the degraded array only pop-up in December. Have upgraded almost everything (drivers, firmware etc) I can find bar the system ROM.
↧
Disabling the Dynamic Smart Array on a Gen8 from the RBSU CLI
I'm trying to find out how to disable the Dynamic Smart Array on my Gen8 Microserver so that the boot firmware just treats it as a normal SATA interface.
I can disable it from the GUI version of the RBSU and I can disable it OK using conrep in the scripting toolkit or from a customised kickstart, but I can't see the option in the RBSU CLI. Since I prefer to run ProLiant's headless using the VSP as the console it would make my life easier to be able to disable this feature from the RBSU CLI.
I'm running Linux (CentOS various versions, not that it matters) The OS just sees the disks unless I add the hpvsa driver and I'd prefer not to in this case.
I've got the 06/06/2014 revision of the J06 firmware.
↧
Re: Failed to clear Integrated Management Log
Changed the SNMP community string. It worked. Thanks :)
↧
Re: Gen9 version control agent
I am having the same issue. Used the latest SPP, running HP Insight Management Agents for Windows Server x64 Editions ver 10.30.0.0 and there is no software status nor is there a VCA to install?
↧
↧
DL380p Gen8 Memory Configured
Hi All,
Just want to see if anyone ever experience the issue we are facing.
HP DL380p Gen8, Dual CPU, 256GB RAM
Boot Post screen show 224GB Installed.
Rom Utility and HP Diagnostic Utlity shows 256GB configured.
There are no post errors or beep codes.
See image: http://imgur.com/a/kzJBP
↧
Re: ProLiant DL385 G7
Yes, I am experiencing the same issue as
So what was the fix for this case ? The Blade server has been running for more than 2 years with no reboot at all.
Uncorrectable Machine Check Exception (Board 0, Processor 1, APIC ID 0x00000010, Bank 0x00000004, Status 0xF2000000'00070F0F, Address 0x00000000'00000000, Misc 0x00000000'00000000)
Uncorrectable Chipset Error (Error status 1 0x0018C154, Error status 2 0x00244000)
Uncorrectable Chipset Error (Error status 1 0x0018C160, Error status 2 0x00002040)
Uncorrectable Chipset Error (Error status 1 0x0018C16C, Error status 2 0x20000080)
Uncorrectable Chipset Error (Error status 1 0x0018C170, Error status 2 0x040406FF)
Uncorrectable Chipset Error (Error status 1 0x0018C174, Error status 2 0x00000003)
Uncorrectable Chipset Error (Error status 1 0x0018C178, Error status 2 0x9452EA00)
My BIOS is A19 12/08/2012 but according to http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c03250482 The System ROM dated 12.31.2011 corrects this issue which is older ?
↧
Re: DL380G7 Uncorrectable Machine Check Exception
Here's the IML logs:
Uncorrectable Machine Check Exception (Board 0, Processor 1, APIC ID 0x00000010, Bank 0x00000004, Status 0xF2000000'00070F0F, Address 0x00000000'00000000, Misc 0x00000000'00000000)
Uncorrectable Chipset Error (Error status 1 0x0018C154, Error status 2 0x00244000)
Uncorrectable Chipset Error (Error status 1 0x0018C160, Error status 2 0x00002040)
Uncorrectable Chipset Error (Error status 1 0x0018C16C, Error status 2 0x20000080)
Uncorrectable Chipset Error (Error status 1 0x0018C170, Error status 2 0x040406FF)
Uncorrectable Chipset Error (Error status 1 0x0018C174, Error status 2 0x00000003)
Uncorrectable Chipset Error (Error status 1 0x0018C178, Error status 2 0x9452EA00)
My Server ROM is on A19 12/08/2012 but according to http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c03250482 The system ROM dated 12.31.2011 corrects this issue which is older ?
↧