|C H A P T E R 1|
The ILOM 3.0 Documentation Collection is available at: http://docs.sun.com/app/docs/prod/int.lights.mgr30#hic
Oracle’s Integrated Lights Out Manager (ILOM) provides advanced service processor hardware and software that you can use to manage and monitor your Oracle Sun servers. ILOM’s dedicated hardware and software is preinstalled on a variety of Oracle Sun server platforms, including x86-based Sun Fire servers, Sun Blade modular chassis systems, Sun Blade server modules, as well as on SPARC-based servers. ILOM is a vital management tool in the data center and can be used to integrate with other data center management tools already installed on your systems.
ILOM is supported on many Oracle systems enabling users to experience a single, consistent, and standards-based service processor (SP) across all Oracle Sun server product lines. This means you will have:
ILOM enables you to actively manage and monitor the server independently of the operating system state, providing you with a reliable Lights Out Management (LOM) system. With ILOM, you can proactively:
The ILOM service processor (SP) runs its own embedded operating system and has a dedicated Ethernet port, which together provide out-of-band management capability. In addition, you can access ILOM from the server’s host operating system (Solaris, Linux, and Windows). Using ILOM, you can remotely manage your server as if you were using a locally attached keyboard, monitor, and mouse.
ILOM automatically initializes as soon as power is applied to your server. It provides a full-featured, browser-based web interface and has an equivalent command-line interface (CLI). There is also an industry-standard SNMP interface and IPMI interface.
You can easily integrate these management interfaces with other management tools and processes that you might have working already with your servers, such as Oracle Enterprise Ops Center. This easy-to-use system management platform for Solaris and Linux provides the tools that you need to efficiently manage systems on your network. Oracle Enterprise Ops Center can discover new and existing systems on your network, update firmware and BIOS configurations, provision the operating environment with off-the-shelf distributions or Solaris images, manage updates and configuration changes, and remotely control key aspects of the service processor such as boot control, power status, and indicator lights. For more information about Oracle Enterprise Ops Center, go to:
In addition, you can integrate ILOM with these third-party management tools:
A description of these third-party system management tools and their support for Oracle’s Sun systems is available at:
ILOM offers a full set of features, functions, and protocols that will help you monitor and manage your server systems.
ILOM 3.0 is enhanced with many new features and functions that were not available in ILOM 2.x, including improved security, improved usability, and easier integration into your data center environment. TABLE 1-2 lists new features for ILOM 3.0.
For ILOM 3.0, user roles are implemented to control user privileges. However, for backward compatibility, ILOM 2.x style user accounts (which have either Administrator or Operator privileges) are still supported.
For more information about ILOM 3.0 user roles, see ILOM 3.0 User Account Roles.
For backward compatibility, ILOM 3.0 supports ILOM 2.x user accounts such that users with ILOM 2.x Administrator or Operator privileges are granted ILOM 3.0 roles that match those privileges. TABLE 1-3 lists the roles assigned to users with Administrator and Operator privileges.
Note - To make the level of authorization granted to users with Operator privileges consistent with 2.x capabilities, the Console (c) role granted in this case is modified to prohibit the user from accessing the ILOM Remote Console (JavaRConsole).
To access all of ILOM’s features and functions, you can choose to use a browser-based web interface, a command-line interface, or industry-standard protocols. For more information on ILOM interfaces, see the Overview chapters in the ILOM 3.0 Procedures Guides.
ILOM supports multiple interfaces for accessing its features and functions. You can choose to use a browser-based web interface, a command-line interface, or industry-standard protocols.
For more information about using IPMI to monitor or manage your Oracle Sun system, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Management Protocols Reference Guide.
For more information about WS-Management/CIM, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Management Protocols Reference Guide.
For a complete list of SNMP MIBs supported and used by ILOM, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Management Protocols Reference Guide.
ILOM supports two ways of managing a system: using the SP directly or using the chassis monitoring module (CMM), if you are using a modular chassis system.
You can access ILOM 3.0 from a browser interface or Secure Shell (SSH) client using either an IPv4 address, IPv6 address, or a DNS hostname. For detailed information on logging in to ILOM for the first time using the root user account, see the following guides:
ILOM 3.0 provides two preconfigured accounts: the root user account and the default user account. You will use the root account for initial login to ILOM. This root user account will be familiar to users who are migrating from ILOM 2.x to ILOM 3.0 and who know how to log in using the root user account. The default user account is a new feature in ILOM 3.0 that is used for password recovery.
The root user account is persistent and is available on all interfaces (web interface, CLI, SSH, serial console, and IPMI) unless you choose to delete the root account. The root account provides built-in administrative privileges (read and write) for all ILOM features, functions, and commands.
To log in to ILOM, use the following root account user name and password:
User name: root
To prevent unauthorized access to your system, you should change the root password (changeme) on each service processor (SP) or chassis monitoring module (CMM) installed in your system. Alternatively, you can delete the root account to secure access to your system. However, before you delete the root account, you must set up a new user account or configure a directory service so that you will be able to log in to ILOM.
The default user account is used for password recovery. The default user account is available through the serial console only and you must prove physical presence at the server to use the default user account. The default user account cannot be changed or deleted.
If you delete the root account before you have configured another user account to log in to ILOM, you can use the default account as an alternative way to log in and re-create the root account. To re-create the root user account, use the normal ILOM user commands to create a new account. For information about how to create a user account, see the section about Add User Account and Assign Privileges in either the web interface or CLI section of the Oracle Integrated Lights Out Manager (ILOM) 3.0 Getting Started Guide.
For password recovery, use the following user name and password to log in using the default account:
User name: default
As of ILOM 3.0.6, when the root password in ILOM is set to the factory default, a warning will appear on the ILOM CLI and web interface.
As of ILOM 3.0.8, system administrators can create banner messages and display them on the Login page or immediately after logging in to ILOM.
Creating and displaying banner messages in ILOM is optional. However, system administrators can use this capability whenever there is a need to share information about system updates, system policies, or other important announcements. Examples of where (Login page or after login) the banner message appear in ILOM after they have been created are shown in FIGURE 1-1, FIGURE 1-2, and FIGURE 1-3.
For instructions on how to create the banner messages in ILOM, see the following guides:
FIGURE 1-1 Login Page - Connect Banner Example - Web Interface
FIGURE 1-2 After Logging In - Banner Message Example - Web Interface
FIGURE 1-3 Banner Message Example - CLI