I have a DL360 Gen8 running Windows 2012 R2. The NIC is the 4-port 331FLR. The device showes up in the BIOS and in the iLO when the OS is not running. As soon as the OS boots the NIC shows up as Unknown in the status window of the iLO and is totally missing from the OS. Any thought?

Is there a tool/utility to set the hardware clock on a proliant ml350p gen8 through Windows (ie without rebooting the server)?

Thanks!

This issues has been discussed in the past; and i can usually find most all of the firmware i'm looking for.... but this one has proved to be nearly impossible.  HELP!!!!

Out of (4) servers, I have (1) DL580 G7 that appears to have had the system IO board replaced in the past.  Under no circumstances can i install an E7 processor in Processor #3 slot.  The server will not post.  (needed to run the optional PCIe board).  After a TON of reading, and flashing all the firmware back to the first supported SPP and updating to current, nothing updates the CPLD code.  This server (iLO3 diagnostics) has a CPLD - PAL1 version of 0x0E.  The other (3) are all PAL1 ver 0x11 and have E7 processors installed in slot #3.  this server does post with (3) E7 processors installed in slots 1,2, and 4.... ?????????   

As an example here is the CPLD update for a DL980 G7:  https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX-1d6a350eea2249b0a4f5c3b802 

All of my investigating points to a non published update/fix that is provided only when needed by tier3 support.  Others have been provided this update due to an NMI issue accidently being generated by the CPLD.  It's described as CPLD code flasher for windows.   It is NOT located on ANY SPP (i have tried them all from 2011 thru 2018).  It is not on any FTP or HP SUM source that i can locate.   Can anyone help me find this?  Obviously i cannot open a support case for this server any longer.  (although it was kept under support while in production)

Elsewhere someone indicated that some ROM flashes may update / modify the CPLD code. (i cannot confirm this) i have disected several USB offline ROM installers, and sequencially installed offline ROM's from 2011 through current; thinking that not every bios update might have to update embeded controllers / CPLD etc...  Unfortunately rompaq.exe does not give any advanced options to force update embeded controller code even though it might exist....

This is a crazy stupid rabbit hole i'm stuck in... especially when there is a simple resolution.  So far the ONLY working resolution suggested is to buy (another) replacement system IO board (ebay) and hope that it's got the proper revision.  I should not have to go this route.  Especially since we kept this server under support for at least 5 years. 

If anyone has access to this unpublished / tier3 fix, OR can point me in the right direction i'd be very thankful. 

Hello! This is my first time posting here. I'll try to keep things to-the-point.

I recently purchased a ProLiant DL580 G7, and was hoping to use an SSD with it. The drive in question is a WD Blue 3D NAND 500GB SATA SSD. It's currently plugged into one of the front-facing bays on my server, and the indicator LED for it glows steady red. I understand that this means the drive is offline and cannot be used. Something tells me that this SSD is incompatible with this server, but correct me if I am wrong. If this SSD cannot be made to work with the server, what other affordable SSDs could I get in its place? Looking for something between 512GB and 1TB (1024GB) in capacity. Thank you for your time and consideration.

I would check to make sure the drive is good, and installed / seated properly. I can confirm that the backplane supports ANY consumer SSD i've put in my DL580 G7.  It works with both the onboard P410i as well as LSI HBA controllers.  If you are using the onboard P410i, go into the menu during boot and see if you are given any warnings.  Also if you have the ACU installed you can just launch that.  I've got a mix of SAS and sata drives installed in the front drive bays. 

IF you want to go really crazy... you can move some cables around and get one SSD installed DIRECTLY on the system board.  It's not a bolt in fit, but i can confirm it works.  It'll be connected to the onboard SATA controller and NOT be seen by the P410i.  Turns out this works great for a local esxi Datastore when you want to use the onboard controller for ALL shared storage.  the port is located in front of the power supply backplane down on the system board.  you'll have to disconnect several cables, install the drive, then arrange the cables in such a way that it's not causing the drive to stand straight up.  there is both a sata & sata power connector right on the board.  It turns out to fit perfectly.  Of course in this configuration you will NOT get a red light indicating a drive failure for that particular drive. 

dl980g7-offline-cpld-fpga-fmp-flash-1.0-8.zip  - does not work natively.  After getting into a huge rabbit hole with this issue, i extracted all the files and found (6) different raw firmware files.    ex:  4w_noSub_noSFF_042611.vme   the *.vme is what is needed to flash the CPLD.  You can also flash the CPLD through ilo firmware update if you have the correct file.  I was unable to manually flash these through DOS with the HPE tools.  It also did not work with ILO.  I'm currently looking for other servers that might also have an appropriate flash that could be modified.

I'll go on and pull the SSD for a quick test now, to see if it's faulty or not

Hello,

Please let me know the current status of the server.

If you feel this was helpful please click the KUDOS! thumb below!   

Regards,

Two of the memory sticks I ordered ended up being bad. I got the new sticks today and everything is working as expected. Posts with 64 GB of memory.

I ended up having to initialise the drive on another computer, because the DL580 G7 didn't appear to have an easy way for initialising drives on its own. The smart array controller didn't even see it until after I threw a partition onto it. But it now ready for regular use  

Hi Neil

I am fighting the simillar problem with trying to boot OMV from SD card on DL360 G7

Have you had a chance to overcome the issue?

Hello,

I would suggest you update bios, ILO firmware, and Agentless Management Service (AMSD.

HPE ProLiant Agentless Management Service for Windows X64

https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_34cd3b27222e4144a71f218efe#tab-history

If you feel this was helpful please click the KUDOS! thumb below!   

Regards,

Hello,

We have to connect the hard disk with the SA controller or onboard S100i controller.

Please find the below link for your reference.

https://support.hpe.com/hpesc/public/docDisplay?docId=a00026901en_us&docLocale=en_US

Please let me know if you have any other queries.

If you feel this was helpful please click the KUDOS! thumb below!   

Regards,

Hello,

HPE releases the driver and firmware after testing.

Could you share the server model? ( like gen8or gen9)

If you feel this was helpful please click the KUDOS! thumb below!   

Regards,

I have done all of those updates, BIOS, iLO and AMS. I noticed the all of the devices are sharing three IRQs in the BIOS. It is acting like the RAID controller and the NIC are conflicting for resources on startup.

Hi all, 

I've installed the latest version of the HP Agentless Management Service on a freshly installed HPe DL20 Gen 10 server. ESXi confirms de packeges are installed:

amscli Agentless Management Service ESXCLI Extension for ESXi 11.5.0.22-1OEM.700.0.0.15525992 HPE 

amsd Agentless Management Service Daemon for VMware ESX 700.11.5.0.28-1OEM.700.1.0.15525992 HPE 

But they don't start when ESXi is booted and also a manual start through SSH doens't help:

[root@localhost:/etc/init.d] ./amsd start

[root@localhost:/etc/init.d] ./amsd status
daemon_smarev is not running
daemon_ahslogger is not running
daemon_amshelper is not running
daemon_ahsd is not running
daemon_amsd is not running
daemon_smad is not running

Below the syslog, hopefully someone has some suggestions.

2020-08-30T08:54:51Z jumpstart[1049796]: executing start plugin: amsd
2020-08-30T08:54:51Z jumpstart[1049796]: executing start plugin: loadESX
2020-08-30T08:54:51Z jumpstart[1049796]: vmtoolsd started.
2020-08-30T08:54:51Z jumpstart[1049796]: xorg started.
2020-08-30T08:54:51Z jumpstart[1049796]: Jumpstart failed to start: esxapiadapter reason: Execution of command: /etc/init.d/esxapiadapter start failed with status: 3
2020-08-30T08:54:51Z jumpstart[1049796]: Method invocation failed: esxapiadapter->start() failed: Execution of command: /etc/init.d/esxapiadapter start failed with status: 3
2020-08-30T08:54:51Z jumpstart[1049796]: loadESX started.
2020-08-30T08:54:51Z daemon-amsd-smad: daemonizing setsid /usr/lib/vmware/daemonMgmt/bin/watchdog.sh -t 100 -n -s amsd-smad /opt/amsd/bin/smad
2020-08-30T08:54:51Z daemon-amsd-smad: [1050942] Begin '/opt/amsd/bin/smad', min-uptime = 60, max-quick-failures = 5, max-total-failures = 100,
2020-08-30T08:54:51Z daemon-amsd-smad: Executing '/opt/amsd/bin/smad'
2020-08-30T08:54:51Z daemon-amsd-smad: saved 1050942 1050949 in /var/run/vmware/daemon-amsd-smad.pid
2020-08-30T08:54:51Z daemon-amsd-smad: returned from wait for PID 1050949 with exit status 0
2020-08-30T08:54:52Z vaainasd[1049930]: DISKLIB-PLUGIN : DiskLibNasPluginFindAndStartSession : NasPluginAddMapping failed
2020-08-30T08:54:52Z vaainasd[1049930]: DISKLIB-PLUGIN : DiskLibNasPluginFindAndStartSession : NasPluginAddMapping failed
2020-08-30T08:54:52Z vaainasd[1049930]: DISKLIB-PLUGIN : DiskLibNasPluginFindAndStartSession : NasPluginAddMapping failed
2020-08-30T08:54:52Z vaainasd[1049930]: DISKLIB-PLUGIN : DiskLibNasPluginFindAndStartSession : NasPluginAddMapping failed
2020-08-30T08:54:53Z lsud: [info] fd6:GETDEVICEINFO dev name = mxxxxxxxxxxxx
2020-08-30T08:54:53Z lsud: [info] fd7:GETDEVICELOCATION dev name = mxxxxxxxxxxxx, num = 4
2020-08-30T08:54:53Z lsud: [info] fd6:GETDEVICEINFO dev name = mxxxxxxxxxxxx
2020-08-30T08:54:57Z slpd[1050566]: SLPDRegMulticast: no v6 service sock found, no service groups joined for service:wbem:https
2020-08-30T08:54:58Z sfcb-vmw_ipmi[1051048]: IpmiIfcSdrReadRecordId:record id: 29, error 210. Try again...
2020-08-30T08:54:58Z sfcb-vmw_ipmi[1051048]: IpmiIfcSdrReadRecordId:record id: 29, error 210. Try again...
2020-08-30T08:55:00Z crond[1049715]: USER root pid 1051062 cmd /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
2020-08-30T08:55:00Z hostd-probe.sh: Starting hostd-probe
2020-08-30T08:55:01Z jumpstart[1049796]: amsd started.
2020-08-30T08:55:01Z jumpstart[1049796]: executing start plugin: amsesxcli.sh
2020-08-30T08:55:01Z root: amsesxcli.sh: runtime check ok.
2020-08-30T08:55:01Z root: amsesxcli.sh: /opt/amsd/bin/amsdesxcliwd.sh start
2020-08-30T08:55:01Z root: amsdesxcliwd start
2020-08-30T08:55:01Z jumpstart[1049796]: amsesxcli.sh started.
2020-08-30T08:55:01Z init: starting pid 1051088, tty '': '/usr/lib/vmware/misc/bin/ucode_workarounds.py'
2020-08-30T08:55:01Z init: starting pid 1051089, tty '': '/bin/apply-host-profiles'
2020-08-30T08:55:01Z init: starting pid 1051090, tty '': '/usr/lib/vmware/configmanager/bin/applyconfig'
2020-08-30T08:55:01Z daemon-amsd-smad: Unable to verify amsd-smad started after 10 seconds
2020-08-30T08:55:01Z daemon-amsd-amsd: daemonizing setsid /usr/lib/vmware/daemonMgmt/bin/watchdog.sh -t 100 -n -s amsd-amsd /opt/amsd/bin/amsd
2020-08-30T08:55:01Z daemon-amsd-amsd: [1051101] Begin '/opt/amsd/bin/amsd', min-uptime = 60, max-quick-failures = 5, max-total-failures = 100,
2020-08-30T08:55:01Z daemon-amsd-amsd: Executing '/opt/amsd/bin/amsd'
2020-08-30T08:55:01Z daemon-amsd-amsd: saved 1051101 1051108 in /var/run/vmware/daemon-amsd-amsd.pid
2020-08-30T08:55:01Z daemon-amsd-amsd: returned from wait for PID 1051108 with exit status 0

2020-08-30T08:55:02Z init: starting pid 1051120, tty '': '/usr/lib/vmware/secureboot/bin/secureBoot.py ++group=host/vim/vmvisor/boot -a'
2020-08-30T08:55:02Z sfcb-vmw_ipmi[1051048]: IpmiIfcFruGetInv: fruDeviceId = 0x3, failed send cc = 0xcb
2020-08-30T08:55:02Z sfcb-vmw_ipmi[1051048]: IpmiIfcFruGetInv: fruDeviceId = 0x2, failed send cc = 0xcb
2020-08-30T08:55:03Z init: starting pid 1051137, tty '': '/usr/lib/vmware/vmksummary/log-bootstop.sh boot'
2020-08-30T08:55:03Z addVob[1051140]: Log for VMware ESXi version=7.0.0 build=build-16324942 option=Release
2020-08-30T08:55:03Z addVob[1051140]: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2020-08-30T08:55:03Z addVob[1051140]: DictionaryLoad: Cannot open file "//.vmware/config": No such file or directory.
2020-08-30T08:55:03Z addVob[1051140]: DictionaryLoad: Cannot open file "//.vmware/preferences": No such file or directory.
2020-08-30T08:55:03Z init: starting pid 1051141, tty '': '/usr/lib/vmware/coredump/collect-coredump-at-boot.sh'
2020-08-30T08:55:03Z init: starting pid 1051149, tty '': '/bin/vmdumper -g 'Boot Successful''
2020-08-30T08:55:03Z init: starting pid 1051150, tty '': '/usr/lib/vmware/misc/bin/killTimeoutConsole.sh'
2020-08-30T08:55:03Z init: starting pid 1051157, tty '': '/bin/sh ++min=0,group=host/vim/vimuser/terminal/shell /etc/rc.local'
2020-08-30T08:55:03Z root: init Running cleanupStatefulHost.py
2020-08-30T08:55:04Z root: init Completed cleanupStatefulHost.py (exit 0)
2020-08-30T08:55:04Z root: init Running kickstart.py
2020-08-30T08:55:04Z root: init Completed kickstart.py (exit 0)
2020-08-30T08:55:04Z root: init Running lifecycle.sh
2020-08-30T08:55:05Z root: init Completed lifecycle.sh (exit 0)
2020-08-30T08:55:05Z root: init Running local.sh
2020-08-30T08:55:05Z root: init Completed local.sh (exit 0)
2020-08-30T08:55:05Z root: init Completed /etc/rc.local.d
2020-08-30T08:55:05Z init: starting pid 1051230, tty '': '/bin/esxcfg-init --set-boot-progress done'
2020-08-30T08:55:05Z init: starting pid 1051231, tty '': '/bin/vmware-autostart.sh start'
2020-08-30T08:55:05Z init: starting pid 1051234, tty '': '/usr/lib/vmware/perf/bin/bootStatsRead.sh'
2020-08-30T08:55:05Z VMware[startup]: Starting VMs
2020-08-30T08:55:05Z init: starting pid 1051235, tty '/dev/tty1': '/bin/initterm.sh tty1 /bin/techsupport.sh'
2020-08-30T08:55:05Z init: starting pid 1051236, tty '/dev/tty2': '-/bin/initterm.sh tty2 /bin/dcuiweasel'
2020-08-30T08:55:05Z DCUI[1051236]: Log for VMware ESXi version=7.0.0 build=build-16324942 option=Release
2020-08-30T08:55:05Z DCUI[1051236]: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2020-08-30T08:55:05Z DCUI[1051236]: DictionaryLoad: Cannot open file "//.vmware/config": No such file or directory.
2020-08-30T08:55:05Z DCUI[1051236]: DictionaryLoad: Cannot open file "//.vmware/preferences": No such file or directory.

2020-08-30T08:55:11Z daemon-amsd-amsd: Unable to verify amsd-amsd started after 10 seconds
2020-08-30T08:55:11Z daemon-amsd-ahsd: daemonizing setsid /usr/lib/vmware/daemonMgmt/bin/watchdog.sh -t 100 -c -s amsd-ahsd /opt/amsd/bin/ahsd
2020-08-30T08:55:11Z daemon-amsd-ahsd: [1051295] Begin '/opt/amsd/bin/ahsd', min-uptime = 60, max-quick-failures = 5, max-total-failures = 100,
2020-08-30T08:55:11Z daemon-amsd-ahsd: Executing '/opt/amsd/bin/ahsd'
2020-08-30T08:55:11Z daemon-amsd-ahsd: saved 1051295 1051302 in /var/run/vmware/daemon-amsd-ahsd.pid
2020-08-30T08:55:11Z daemon-amsd-ahsd: returned from wait for PID 1051302 with exit status 0
2020-08-30T08:55:11Z daemon-amsd-ahsd: not restarting due to exit status 0
2020-08-30T08:55:22Z daemon-amsd-ahsd: Unable to verify amsd-ahsd started after 10 seconds
2020-08-30T08:55:22Z daemon-amsd-amshelper: daemonizing setsid /usr/lib/vmware/daemonMgmt/bin/watchdog.sh -t 100 -c -s amsd-amshelper /opt/amsd/bin/amshelper
2020-08-30T08:55:22Z daemon-amsd-amshelper: [1051342] Begin '/opt/amsd/bin/amshelper', min-uptime = 60, max-quick-failures = 5, max-total-failures = 100,
2020-08-30T08:55:22Z daemon-amsd-amshelper: Executing '/opt/amsd/bin/amshelper'
2020-08-30T08:55:22Z daemon-amsd-amshelper: saved 1051342 1051349 in /var/run/vmware/daemon-amsd-amshelper.pid
2020-08-30T08:55:22Z daemon-amsd-amshelper: returned from wait for PID 1051349 with exit status 0
2020-08-30T08:55:22Z daemon-amsd-amshelper: not restarting due to exit status 0
2020-08-30T08:55:32Z daemon-amsd-amshelper: Unable to verify amsd-amshelper started after 10 seconds
2020-08-30T08:55:32Z daemon-amsd-ahslogger: daemonizing setsid /usr/lib/vmware/daemonMgmt/bin/watchdog.sh -t 100 -c -s amsd-ahslogger /opt/amsd/bin/ahslogger
2020-08-30T08:55:32Z daemon-amsd-ahslogger: [1051384] Begin '/opt/amsd/bin/ahslogger', min-uptime = 60, max-quick-failures = 5, max-total-failures = 100,
2020-08-30T08:55:32Z daemon-amsd-ahslogger: Executing '/opt/amsd/bin/ahslogger'
2020-08-30T08:55:32Z daemon-amsd-ahslogger: saved 1051384 1051391 in /var/run/vmware/daemon-amsd-ahslogger.pid
2020-08-30T08:55:32Z daemon-amsd-ahslogger: returned from wait for PID 1051391 with exit status 0
2020-08-30T08:55:32Z daemon-amsd-ahslogger: not restarting due to exit status 0
2020-08-30T08:55:42Z daemon-amsd-ahslogger: Unable to verify amsd-ahslogger started after 10 seconds
2020-08-30T08:55:42Z daemon-amsd-smarev: daemonizing setsid /usr/lib/vmware/daemonMgmt/bin/watchdog.sh -t 100 -n -s amsd-smarev /opt/amsd/bin/smarev
2020-08-30T08:55:42Z daemon-amsd-smarev: [1051425] Begin '/opt/amsd/bin/smarev', min-uptime = 60, max-quick-failures = 5, max-total-failures = 100,
2020-08-30T08:55:42Z daemon-amsd-smarev: Executing '/opt/amsd/bin/smarev'
2020-08-30T08:55:42Z daemon-amsd-smarev: saved 1051425 1051432 in /var/run/vmware/daemon-amsd-smarev.pid
2020-08-30T08:55:42Z daemon-amsd-smarev: returned from wait for PID 1051432 with exit status 0
2020-08-30T08:55:52Z daemon-amsd-smarev: Unable to verify amsd-smarev started after 10 seconds

Dear friends,

We own a HPE ProLiant DL380 Gen9 Server. It has one single Xeon E5-2620 v4 processor with 4 times 16GB RDIMM (64GB in total).

There is one single riser with PCIe 3.0 x8 slots. The power supply supports 500W; the heatsink is standard I guess, since the processor’s usage is below 120W (from the specs).

I have two questions concerning a GPU and additional RAM. I would be grateful if you could give me some advice.

1. We would like to equip the server with a GPU. Unfortunately, I can not see what additional parts we need in order to enable the server to support a graphics card.

- Graphics Enablement kit (what is included here?)

- double wide PICe riser x16 (is it included in the Graphics Enablement kit?)

- power supply of at least 800W (according to specs); but the Graphics card uses 250W, the processor 85W, so we are far below the 500W supply, already built in?

-additional power cable kit gen9 (not included in the Graphics Enablement kit?)

-additional heatsink (for processors with standard heatsink and double wide PCIe cards?)

2. We would like to add some additional RAM

- is it possible to add at most 8 more 16GB RDIMMs (4 already built in)?

If you require further information, please let me know.

Thnx in advance

what i really need is for anyone (knowledgeable) from HPE support to find this in the archive somewhere.  please?

Hi there,

Sadly no, but I did manage to work around it OK.

The workaround was to install VMWare ESXi on the server first, and run OMV as a virtual server.

It works just fine, with the proviso that mapping drives with existing backups gets quite complex, or if you want to create a RAID volume or similar. Basically ESXi wants to own all of your drives if it can. 

It is possible to map existing filesystems but harder than it needs to be.

So apologies, no easy answer I can give you but I found the VMWare route acceptable. I did a lot of research and it seems much better people than me gave up on it too. ESXi had no issues at all installing on SD card and booting from it on HP server, and seems to add no noticable overhead. Free as well...