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
Auto Login
Auto login provides direct access to iLO 2 from the OA for users who already logged in to the
OA. A user who has authenticated their connection to the OA can follow a link to a server blade
in the enclosure without an additional login step. Auto login features and usage are as follows:
• A user who has authenticated a connection to the OA is able to establish a connection with
iLO 2 without providing the user login and password to iLO 2.
• The OA provides the following auto login connection methods to iLO 2 links to users to launch
these connections to iLO 2:
iLO CLI SSH Connection If you logged in to the OA CLI through SSH, enter
connect server <bay number> to establish an
SSH/Telnet connection with iLO 2.
iLO Web GUI Connection If you logged in to the OA web GUI, click on the link to
launch the iLO web GUI.
• Auto login is implemented using IPMI commands over I2C between the OA and iLO 2 to
create and delete user commands.
• Supports a maximum of four simultaneous OA user accounts. The OA keeps track of these
users locally. The information maintained for each user is the user name, password, and
privilege levels.
• User accounts for the auto login feature are created in the MP database when an auto login
session is established. These accounts are deleted when the auto login session is terminated.
• If a maximum number of user accounts has already been reached, and the OA creates another
account on iLO 2. The OA sends a request to iLO 2 to delete one of the previously created
accounts, before attempting to create a new one.
• If iLO 2 is rebooted or power-cycled, it checks if there are any previously created OA user
accounts in the iLO 2 user database when it boots up. If there are any previously-created OA
user accounts, it deletes those accounts.
• View and manage user accounts created in iLO 2 by the OA like any other local user account
on iLO 2. To view and manage user accounts, use the TUI WHO, UC commands; or use the
User Administration Page in the web GUI.
• View and disconnect user connections established through the auto login feature just like other
connections to iLO 2. To view and disconnect user connections, use the TUI WHO, DI
commands, or use the User Administration Page in the web GUI.
• The OA supports three types of users: administrators, operators, and users. These user types
map to the following iLO 2 capabilities:
Administrators Can perform any function including iLO 2 MP configuration. This level
equates to an iLO 2 user with all privilege levels such as, Administer
User Accounts, Remote Console Access, Virtual Power and Reset,
Virtual Media, and Configure iLO MP settings. It allows access to all
aspects of the OA including configuration, firmware updates, user
management, and resetting default settings.
Operators Provided access to the host system IRC, serial console, and vMedia.
This level equates to an iLO 2 user with Remote Console Access, Virtual
Power and Reset, Virtual Media, and Configure iLO settings. It allows
access to all but configuration changes and user management. This
account is used for individuals who might be required to periodically
change configuration settings.
Users Provided read-only login access to iLO 2. This account is used for
individuals who need to see the configuration of the OA but do not
Server Blade Connection 43