HP Integrity rx2800 i2 Server - Manual (Page 7)

Introduction 7
• Support for updating firmware on network-based targets such as the OA, iLO 2/iLO 3 through Network
Management Port, and VC Ethernet and Fibre Channel modules on HP ProLiant servers
NOTE: HP SUM does not support third-party controllers. This includes flashing hard drives
behind these controllers.
Using this guide
HP SUM is delivered with many different deliverables. A deliverable is an HP product which contains HP
SUM and a set of firmware or software components. Some examples are the ProLiant Support for Windows
and the HP Smart Update Firmware DVD. It is important that you review the overview section after this section
for your deliverable to verify any specific limitations to HP SUM features that apply. Then, you can review the
sections describing the features of HP SUM. For more information, see the Supported deliverables overview
(on page 12 ) section.
New features of HP SUM 4.2.0
This release of HP SUM includes the following new support:
• Added the ability to retrieve the Linux RPMs from the HP FTP site ( ftp://ftp.hp.com ) for PSPs
• Added the ability to overwrite SNMP configuration parameters for Linux agents
Minimum requirements
• Minimum requirements for Windows operating systems (" Minimum requirements for Windows servers "
on page 7 )
• Minimum requirements for Linux (" Minimum requirements for Linux x86 servers " on page 8 )
NOTE: For Linux and Windows operating systems, the respective device drivers for the
embedded/add-on devices in the target servers must be installed for HP SUM to discover the
devices.
NOTE: For a current list of supported operating systems on ProLiant servers, see the PSP website
( http://www.hp.com/servers/psp ).
Minimum requirements for Windows servers
To successfully deploy HP SUM on HP ProLiant and Integrity target systems based on a Windows® operating
system, the following must be available:
• A local administrative system with 512 MB of memory
• Sufficient hard-drive space of at least twice the file size of the components to be deployed
• WMI enabled
• All remote host servers connected to the same network and use TCP/IP to enable the systems to be seen
by the administrative system
• An account with administrator privileges on each host server