Is there anything special that needs to be done to communicate with the ribcl interface of HP iLO v2 on the RX series servers? We've got a set of perl scripts that use a SSL socket to communication via XML to iLO for the purposes of monitoring. These scripts work perfectly fine on the DL series but don't get a responce from the RX series.
I attempted to use curl to see what sort of return I was getting but I only see a error message about a cookie:
curl --insecure --data '<LOCFG version="2.21"/><RIBCL VERSION="2.0"><LOGIN USER_LOGIN="Admin" PASSWORD = "Admin"></RIBCL></LOCFG>' https://x.x.x.x/ribcl
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!--
**************************************************************************
* (c) Copyright Hewlett-Packard Company 1999-2007. All Rights Reserved. *
**************************************************************************
-->
<title>HP iLO Error Page: Cookie Invalid</title> Here's a sniplet of the code being used:
$client = IO::Socket::SSL->new(
PeerAddr => 'x.x.x.x',
SSL_verify_mode => SSL_VERIFY_NONE,
SSL_version => "SSLv3",
Timeout => $timeout,
);
print $client "POST /ribcl HTTP/1.1 \r\n HOST: localhost \r\n Content-length: 30 \r\n Connection: Close \r\n <RIBCL VERSION='2.0'></RIBCL> \r\n"; This hangs forever waiting for a responce, would love any feedback we could get
