Issues with scripting boot via ILO

Fredriks3 — Mon, 01 Jul 2013 07:18:32 GMT

Trying to create a script to boot multiple servers via ilo (multible versions of ilo) using the scriots bellow. But when I run it I get the following error:

IP Address is: server1-oob
SIO_connect failure.
9344:error:0200274C:system library:connect:reason(1868):.\crypto\sio\s_sock.c:606:host=server1-oob:443
9344:error:10065068::lib(16) :SIO_CONNECT:connect error:.\crypto\sio\s_sock.c:608:
CPQLOCFG.EXE: ERROR: SIO_connect:reason(10060).

What can cause this?

There is no valid ssl certificats on the ilo so there is allways a warning about this ehen conencting via a browser.

boot.bat

@echo off

set iLO_uN=root
set iLO_PW=rootpass
set iLO_XML=Set_Host_Power.xml
IF NOT EXIST .\LOGS MKDIR .\LOGS

for %%i in (
server1-oob
) do (

CPQLOCFG.EXE -s %%i -f %iLO_XML% -u %iLO_uN% -p %iLO_PW%
	
)

Set_Host_Power.xml

<!--         RIBCL Sample Script for HP Lights-Out Products          -->
<!--Copyright (c) 2012 Hewlett-Packard Development Company, L.P.     -->

<!-- Description:  This is a sample XML script to toggle the power   -->
<!--               on the host server in which one of the following  -->
<!--               devices is executing:                             -->
<!--                 Integrated Lights-Out 4 (iLO 4)                 -->
<!--                 Integrated Lights-Out 3 (iLO 3)                 -->
<!--                 Integrated Lights-Out 2 (iLO 2)                 -->

<!-- NOTE:  You will need to replace the USER_LOGIN and PASSWORD     -->
<!--        values with values that are appropriate for your         -->
<!--        environment.                                             -->

<!--        This script will use the ACPI Power Button function to   -->
<!--        attempt to gracefully shutdown the host operating system -->
<!--        (if your OS supports and is configured for graceful      -->
<!--        shutdown) before it powers off the server.               -->

<!--        Use CPQLOCFG.EXE ver 4.00 or greater with this script.   -->

<!--        This script was written for iLO 4 firmware version 1.01  -->
<!--        release.                                                 -->

<!--        See "HP Integrated Lights-Out Management Processor       -->
<!--        Scripting and Command Line Resource Guide" for more      -->
<!--        information on scripting and the syntax of the RIBCL     -->
<!--        XML.                                                     -->

<!--        Firmware support information for this script:            -->
<!--            iLO 4 - All versions.                                -->
<!--            iLO 3 - All versions.                                -->
<!--            iLO 2 - All versions.                                -->

<RIBCL VERSION="2.0">
   <LOGIN USER_LOGIN="root" PASSWORD="rootpassword">
      <SERVER_INFO MODE="write">
         <!-- Modify the HOST_POWER attribute to toggle power on the host server -->
         <!-- HOST_POWER="No"  (Turns host server power off)              -->
         <!-- A graceful shutdown will be attempted for ACPI-aware        -->
         <!-- operating systems configured to support graceful shutdown.  -->
         <!-- HOST_POWER="Yes" (Turns host server power on) -->
         <SET_HOST_POWER HOST_POWER="Yes"/>
      </SERVER_INFO>
   </LOGIN>
</RIBCL>

Re: Issues with scripting boot via ILO

Fredriks3 — Mon, 01 Jul 2013 07:31:42 GMT

well SSL is the issue but how to owercome it? i dobt that manny people have valid ssl certificats for there ILO.

Re: Issues with scripting boot via ILO

Jimmy Vance — Mon, 01 Jul 2013 12:44:37 GMT

Using your batch file, I was able to turn an iLO4 system off and on.

I used cpqlocfg.exe version 4.00, and version 4 of the iLO XML scripting samples.

Re: Issues with scripting boot via ILO

Oscar A. Perez — Mon, 01 Jul 2013 21:29:37 GMT

Apparently, CPQLOCFG.exe is failing to establish a TCP connection to iLO port 443. See error Windows Socket error 10060 below:

WSAETIMEDOUT 10060

Connection timed out.

A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

Are your iLOs configured to listen to a port other than 443 for HTTPS?

Re: Issues with scripting boot via ILO

Fredriks3 — Tue, 02 Jul 2013 08:41:45 GMT

well the solution was fairly easy, I had put the script on a server that did not have acces to the ILO network

topic Re: Issues with scripting boot via ILO in ProLiant Servers (ML,DL,SL)

Issues with scripting boot via ILO

Re: Issues with scripting boot via ILO

Re: Issues with scripting boot via ILO

Re: Issues with scripting boot via ILO

Re: Issues with scripting boot via ILO