BladeSystem Management Software

Onboard Administrator (OA) scripting for Power-on Delay.

 
chuckk281
Trusted Contributor

Onboard Administrator (OA) scripting for Power-on Delay.

Dave had a blade Power-on question:

 

*****************

 

                I’m trying to automate an OA script for p4800 enclosures. We need to set the ‘PowerOnDelay’ settings.

I’ve been able to get the rest of the script to work, but the cfg file on a thumb drive will change the configs.

I have tried it with script ode on and off. I know my script works if I putty into the OA and paste it through ssh.

 

I have tried the long method:

#Set PowerDelay Information

SET INTERCONNECT POWERDELAY 1 210

SET INTERCONNECT POWERDELAY 2 210

SET INTERCONNECT POWERDELAY 3 210

SET INTERCONNECT POWERDELAY 4 210

SET INTERCONNECT POWERDELAY 5 180

SET INTERCONNECT POWERDELAY 6 180

SET INTERCONNECT POWERDELAY 7 210

SET INTERCONNECT POWERDELAY 8 210

SET SERVER POWERDELAY 1 360

SET SERVER POWERDELAY 2 360

SET SERVER POWERDELAY 3 360

SET SERVER POWERDELAY 4 360

SET SERVER POWERDELAY 5 360

SET SERVER POWERDELAY 6 360

SET SERVER POWERDELAY 7 270

SET SERVER POWERDELAY 8 270

SET SERVER POWERDELAY 9 360

SET SERVER POWERDELAY 10 360

SET SERVER POWERDELAY 11 360

SET SERVER POWERDELAY 12 360

SET SERVER POWERDELAY 13 360

SET SERVER POWERDELAY 14 360

SET SERVER POWERDELAY 15 270

SET SERVER POWERDELAY 16 270

 

And the shorten version:

#Set PowerDelay Information

SET INTERCONNECT POWERDELAY 1-4,7,8 210

SET INTERCONNECT POWERDELAY 5,6 180

SET SERVER POWERDELAY 1-6,9-14 360

SET SERVER POWERDELAY 7,8,15,16 270

 

Both work in putty, but not in a cfg file on a USB drive in the OA USB port executed by the Insight Display.

The OA is at 3.55

 

Has anyone seen this issue before?

 

************

 

Monty replied:

 

******************

 

One thing to remember for c-Class enclosure configurations with the  HP SAS switch interconnects, the OA has embedded power sequence logic that understands that the server SAS Mezz cards are dependent upon the SAS switches, so the OA automatically will delay the server power requests until the SAS switches signal to the OA that they are ready for connections after a cold power on of the entire enclosure.

 

In your scenario with external P4800 - if it does not power up automatically, you will need something programmed to bring it online after datacenter power loss.

 

There should be no reason to configure powerdelay for the SAS switches, but I agree that the servers should be configured to disable iLO auto poweron, and you can disable OA powerdelay for those servers.  That will result in the SAS switches powering on first and then whatever server is scripting the power up for the P4800 could then power on all the attached servers using the OA CLI.

 

This would utilize the internal OA to SAS switch power on logic and result in delaying the server power on until the SAS switches were ready, then they would boot and the SAS drives would be available.

 

****************

 

Any other comments or suggestions?