11.07.2015 Views

HP Integrated Lights-Out 2 User Guide

HP Integrated Lights-Out 2 User Guide

HP Integrated Lights-Out 2 User Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

A separate network increases the security of the management network because you canphysically control which workstations are connected to the network.2. How will iLO 2 acquire an IP address?To access iLO 2 after connecting it to the network, the management processor must acquire an IPaddress and subnet mask. This is typically accomplished using either a dynamic or static process.• Dynamic IP address—iLO 2 is set by default to obtain its IP address and subnet mask fromDNS/DHCP servers on the network. This is the simplest method of performing this process.• Static IP address—If DNS/DHCP servers are not available on the network, a static IP addresscan be configured in iLO 2 using the ROM-Based Setup Utility (RBSU).If using Static IP, you must have an IP address before starting iLO 2 setup.3. What access security is required and what user accounts and privileges are needed?iLO 2 provides several choices to control user access. One or more of the following methods must beselected to prevent unauthorized access to corporate IT assets.• Local accounts—Up to 12 user names and passwords can be stored on iLO 2. This is ideal forsmall environments such as labs and small and medium businesses.• Directory services—Use the corporate directory (Microsoft® Active Directory or NovelleDirectory) to manage iLO 2 user access. This is ideal for environments with a large number offrequently changing users. If you plan to use Directory services, <strong>HP</strong> still recommends leaving atleast one local account enabled for alternate access.For more information regarding iLO 2 access security see the "iLO 2 security" section.4. What method do you want to use to configure iLO 2?<strong>HP</strong> recognizes customer usage models vary. iLO 2 supports various interfaces for configuration andoperation. This guide details the following interfaces:• iLO 2 RBSU ("Setup using iLO 2 RBSU" on page 15) can be used when the system environmentdoes not use DHCP and DNS or WINS.• Browser-based setup ("Set up using the browser-based option" on page 16) can be usedwhen you can connect to iLO 2 on the network using a browser. This method can also used toreconfigure a previously configured iLO 2.• SMASH CLP can be used when a command line is accessible through telnet, SSH, or physicalserial port. (Refer to the "<strong>HP</strong> <strong>Integrated</strong> <strong>Lights</strong>-<strong>Out</strong> Management Processor Scripting andCommand Line Resource <strong>Guide</strong>".)NOTE: iLO supports a preliminary draft version of the new SMASH CLP under development by the DMTF.For more advanced setup of multiple iLO 2 management processors using scripting commands, thefollowing methods are available. Scripts are text files written in a style of XML called RIBCL. You can useRIBCL scripts to configure iLO 2 on the network, during initial deployment, or from an already deployedhost. Each of these methods is described in the "<strong>HP</strong> <strong>Integrated</strong> <strong>Lights</strong>-<strong>Out</strong> Management Processor Scriptingand Command Line Resource <strong>Guide</strong>".• CPQLOCFG is a Microsoft® Windows® utility that sends RIBCL scripts to iLO 2 over the network.• <strong>HP</strong>ONCFG is a local on-line scripted setup utility that runs on the host and passes RIBCL scripts tothe local iLO 2. There are Windows® and Linux versions of this utility, which require the <strong>HP</strong> iLO 2Management Interface Driver.• Perl is a scripting language that can be used from Linux clients to send RIBCL scripts to iLO 2 overthe network.Connect to the networkTypically iLO 2 is connected to the network in one of two ways. iLO 2 can be connected through a:iLO 2 setup 13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!