Workload Management Pack - provides easier management of complex environments, improving overall server utilization and enabling Windows 2000 customers for the first time to confidently deploy multiple applications on a single multi processor ProLiant Server. Rapid Deployment Pack - an automated solution for multi-server deployment and provisioning, enabling companies to quickly and easily adapt to changing business demands.
Optional software offerings that selectively extend the functionality of an Adaptive Infrastructure to address specific business problems and needs: System Management, Performance Services and Mission Critical Support Solution Response times range from 30 mins for critical problems to two hours. Support services for fast, efficient resolution of hardware and software issuesĮxtending onsite hardware warranty coverage from next business day to same business day 13 hours, five day or 24 hours, seven days call window with options including four-hour response or six-hour Call To RepairĬomprehensive range of software technical support for Microsoft, Linux, ProLiant Essentials and VMWare based IT solutions helping to deliver high level of application availability. Installation and Start up services helps user get ProLiant servers deployed rapidlyĮducation courses provide industry leading training for IT professionals
Returns the mac address associated with the machine's primary NIC (aka eth0).Care Pack services provide a range of life cycle support options that let user choose the service levels that meet business requirements, from basic to mission-critical.A full range of HPE Care Pack hardware and software services are available including: Includes slot name, module size and module speed. Returns arrayref containing information about installed memory modules. # yields the following on a D元60/G5 with 8 GB of RAM: GENERAL METHODS new() my $ilo = Net::ILO->new(
The interface is extensive and methods have been grouped by function for easier digestion. Power and UID statuses are an exception their states can be either 'on' or 'off'.
Either form is acceptable when passing a value to your server's iLO. When ILO returns a boolean response, it is shortened to 'Y' or 'N'. However, certain names have been changed to reflect a more common usage, for example, what HP calls 'DNS_NAME' is referred to as 'hostname' by Net::ILO.īoolean types are represented in the documentation as either 'Yes' or 'No'. Wherever possible, I have mimicked HP's API to maintain consistency. Note: iLO 3 support is in BETA, and still being tested. It should work with other server models feedback (either way) is much appreciated.
This module is based on the sixth edition of the "HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide" and has been successfully tested with the following server types: D元60/G3 Not every iLO function is implemented here, however most common ones are. HP's API is XML-based and cumbersome to use this module aims to simplify accessing the iLO from Perl while retaining as much functionality as possible. The Net::ILO module is an interface to a subset of Hewlett-Packards Integrated Lights-Out out-of-band management system. # see METHODS for complete listing DESCRIPTION My $power_status = $ilo->power or die $ilo->error Net::ILO - Interface to HP Integrated Lights-Out SYNOPSIS use Net::ILO