HP Integrity iLO 2 Operations Guide
Table Of Contents
- HP Integrity iLO 2 Operations Guide
- Contents
- About This Document
- 1 Introduction to iLO 2
- Features
- Standard Features
- Always-On Capability
- Virtual Front Panel
- Multiple Access Methods
- Security
- User Access Control
- Multiple Users
- IPMI over LAN
- System Management Homepage
- Firmware Upgrades
- Internal Subsystem Information
- DHCP and DNS Support
- Group Actions
- Group Actions Using HP SIM
- SNMP
- SMASH
- SM CLP
- Mirrored Console
- Remote Power Control
- Power Regulation
- Event Logging
- Advanced Features
- Standard Features
- Obtaining and Activating iLO 2 Advanced Pack Licensing
- Supported Systems and Required Components and Cables
- Integrity iLO 2 Supported Browsers and Client Operating Systems
- Security
- Features
- 2 Ports and LEDs
- 3 Getting Connected to iLO 2
- 4 Logging In to iLO 2
- 5 Adding Advanced Features
- Lights-Out Advanced KVM Card for sx2000 Servers
- Lights-Out Advanced KVM card Requirements
- Configuring the Lights-Out Advanced KVM Card
- Lights-Out Advanced KVM Card IRC Feature
- Lights-Out Advanced KVM Card vMedia Feature
- Installing the Lights-Out Advanced KVM Card in a Server
- Lights-Out Advanced KVM Card Quick Setup Steps
- Using Lights-Out Advanced KVM Features
- Mid Range PCI Backplane Power Behavior
- Troubleshooting the Lights-Out Advanced KVM Card
- Core I/O Card Configurations
- Supported PCI-X Slots
- Upgrading the Lights-Out Advanced KVM Card Firmware
- Lights-Out Advanced KVM Card for sx2000 Servers
- 6 Accessing the Host (Operating System) Console
- 7 Configuring DHCP, DNS, LDAP, and Schema-Free LDAP
- 8 Using iLO 2
- Text User Interface
- MP Command Interfaces
- MP Main Menu
- MP Main Menu Commands
- CO (Console): Leave the MP Main Menu and enter console mode
- VFP (Virtual Front Panel): Simulate the display panel
- CM (Command Mode): Enter command mode
- SMCLP (Server Management Command Line Protocol): Switch to the SMASH SMCLP
- CL (Console Log): View the history of the console output
- SL (Show Logs): View events in the log history
- HE (Help): Display help for the menu or command in the MP Main Menu
- X (Exit): Exit iLO 2
- MP Main Menu Commands
- Command Menu
- Command Line Interface Scripting
- Command Menu Commands and Standard Command Line Scripting Syntax
- BP: Reset BMC passwords
- BLADE: Display BLADE parameters
- CA: Configure asynchronous local serial port
- DATE: Display date
- DC (Default Configuration): Reset all parameters to default configurations
- DF: Display FRU information
- DI: Disconnect LAN, WEB, SSH, or Console
- DNS: DNS settings
- FW: Upgrade the MP firmware
- HE: Display help for menu or command in command menu interface
- ID: System information settings
- IT: Inactivity timeout settings
- LC: LAN configuration usage
- LDAP: LDAP directory settings
- LM: License management
- LOC: Locator UID LED configuration
- LS: LAN status
- PC: Power control access
- PM: Power regulator mode
- PR: Power restore policy configuration
- PS: Power status
- RB: Reset BMC
- RS: Reset system through the RST signal
- SA: Set access LAN/WEB/SSH/IPMI over LAN ports
- SNMP: Configure SNMP parameters
- SO: Security option help
- SS: System Status
- SYSREV: Firmware revisions
- TC: System reset through INIT or TOC signal
- TE: Send a message to other mirroring terminals
- UC: User Configuration (users, passwords, and so on)
- WHO: Display a list of iLO 2 connected users
- XD: iLO 2 Diagnostics or reset
- Web GUI
- System Status
- Remote Serial Console
- Integrated Remote Console
- Virtual Media
- Power Management
- Administration
- BL c-Class
- Help
- SMASH Server Management Command Line Protocol
- SM CLP Features and Functionality Overview
- Accessing the SM CLP Interface
- Using the SM CLP Interface
- SM CLP Syntax
- System1 Target
- System Reset Power Status and Power Control
- Map1 (iLO 2) Target
- Text Console Services
- Firmware Revision Display and Upgrade
- Remote Access Configuration
- Network Configuration
- User Accounts Configuration
- LDAP Configuration
- Text User Interface
- 9 Installing and Configuring Directory Services
- Directory Services
- Directory Services for Active Directory
- Directory Services for eDirectory
- Installing and Initializing Snap-In for eDirectory
- Example: Creating and Configuring Directory Objects for Use with iLO 2 Devices in eDirectory
- Directory Services Objects for eDirectory
- Setting Role Restrictions
- Setting Time Restrictions
- Setting Lights-Out Management Device Rights
- Installing Snap-Ins and Extending Schema for eDirectory on a Linux Platform
- Using the LDAP Command to Configure Directory Settings in iLO 2
- User Login Using Directory Services
- Certificate Services
- Directory-Enabled Remote Management
- Directory Services Schema (LDAP)
- Glossary
- Index
Server Blade Connection
For a server blade, you can connect directly through the SUV cable to the serial console or you
can connect using the MP LAN internal connection in the blade enclosure.
NOTE: You do not cable up a separate MP LAN cable to each server blade.
In most circumstances, it is not necessary to physically connect to the iLO 2 on a Server Blade. The
iLO 2 on server blades typically use the MP LAN connection in the blade enclosure, and typically
get their LAN IP addresses assigned using the OA. In the rare cases where a physical connection
directly to a server blade iLO 2 is necessary, use one of the following methods:
• Connect to iLO 2 with DHCP enabled. Use the OA/iLO network port on the rear of the
enclosure. If the OA/iLO network port on the enclosure is connected to the local network that
has a DHCP server, your iLO 2 MP IP address is automatically generated by the DHCP server.
The server blade is factory set with DHCP enabled.
• Connect to iLO 2 with no network connection. Use the console serial port on the SUV cable.
If the enclosure is not connected to any network, you must configure your server through the
console serial port (RS-232) on the SUV cable.
NOTE: The local video port can be used to access the console at EFI or potentially the OS, but
is not a connection to iLO 2. The USB provides keyboard and mouse to the operating system on
HP Integrity server blades. Also, server blades do not support directly connecting a modem to the
MP (called the remote RS-232 port on servers), so there is no remote RS-232 connection on the
server blade. In addition, there is no LAN connection on the front of the server blade.
Connecting to a Server Blade iLO 2 Using the Console Serial Port
If the enclosure is not connected to any network, you must configure your server through the console
serial port (RS-232) on the SUV cable. Use this procedure to configure the console serial port to
enable iLO 2 access. To perform this procedure, you need a terminal emulator (for example, a
laptop using hyperterm) to connect to the server blade.
NOTE: On the HP Integrity server blades, you have access to two serial ports through the RS-232
connector. The default setting is for the iLO 2 interface, the other is for an AUX UART directly
connected to the host operating system and can be used for any serial device (terminal, debug
port, and so on). HP recommends using the AUX UART for server blade setup and debug purposes
only.
You can use a command to toggle between the two ports. However, if access to the iLO 2 MP TUI
CLI is not possible through Telnet and if the port mode of operation is set to the AUX UART, perform
a hard reset of iLO 2 to set it to the default shipping settings. To perform a hard reset, push the
recessed MP Reset button.
TIP: It is not necessary to physically connect to iLO 2 through the console serial port to perform
management tasks. Use the OA/iLO 2 LAN port to communicate with any iLO 2 in the enclosure
and the OA. You can use the LCD panel and the OA to configure and determine the iLO 2 MP
LAN address.
Server Blade Connection 39