Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide

---

Backing Up the ILOM Configuration

Before You Begin

• Log in to the ILOM CLI as a user assigned the Admin, User Management, Console, Reset and Host Control, and Read Only (a,u,c,r,o) roles. These roles are required in order to perform a complete backup of the ILOM SP configuration.
• If you use a user account that does not have the roles listed above, the configuration backup file that is created might not include all of the ILOM SP configuration data.

1. Log in to the ILOM SP CLI or the CMM CLI.

2. Change to the /SP/config directory. Type:

-> cd /SP/config

3. If you want sensitive data, such as user passwords, SSH keys, certificates, and so forth, to be backed up, you must provide a passphrase. Type:

-> set passphrase=passphrase

4. To initiate the Backup operation, type the following command from within the /SP/config directory:

-> set dump_uri=transfer_method://username:password@ipaddress_or_hostname/directorypath/filename

Where:

• transfer_method can be tftp, ftp, sftp, scp, http, or https.
• username is the name of the user account on the remote system. (username is required for scp, sftp, and ftp. username is not used for tftp, and it is optional for http and https.)
• password is the password for the user account on the remote system. (password is required for scp, sftp, and ftp. password is not used for tftp, and it is optional for http and https.)
• ipaddress_or_hostname is the IP address or the host name of the remote system.
• directorypath is the storage location on the remote system.
• filename is the name assigned to the backup file.

For example:

-> set dump_uri=scp://adminuser:userpswd@1.2.3.4/Backup/Lab9/SP123.config

The Backup operation executes and you will be prompted when the operation completes. A Backup operation typically takes two to three minutes to complete.

---

Restoring the ILOM Configuration

Before You Begin

• Log in to the ILOM CLI as a user assigned the Admin, User Management, Console, Reset and Host Control, and Read Only (a,u,c,r,o) roles. These roles are required to perform a complete restore of the ILOM SP configuration.
• When executing a Restore operation, use a user account that has the same or more privileges than the user account that was used to create the backup file; otherwise, some of the backed up configuration data might not be restored. All configuration properties that are not restored appear in the event log. Therefore, one way to verify whether all the configuration properties were restored is to check the event log.

1. Log in to the ILOM SP CLI or the CMM CLI.

2. Change to the /SP/config directory. Type:

-> cd /SP/config

3. If a passphrase was specified when the backup file was created, you must specify the same passphrase to perform the Restore operation. Type:

-> set passphrase=passphrase

The passphrase must be the same passphrase that was used when the backup file was created.

4. To initiate the Restore operation, type the following:

-> set load_uri=transfer_method://username:password@ipaddress_or_hostname/directorypath/filename

Where:

• transfer_method can be tftp, ftp, sftp, scp, http, or https.
• username is the name of the user account on the remote system. (username is required for scp, sftp, and ftp. username is not used for tftp, and it is optional for http and https.)
• password is the password for the user account on the remote system. (password is required for scp, sftp, and ftp. password is not used for tftp, and it is optional for http and https.)
• ipaddress_or_hostname is the IP address or the host name of the remote system.
• directorypath is the storage location on the remote system.
• filename is the name assigned to the backup file.

For example:

-> set load_uri=scp://adminuser:userpswd@1.2.3.4/Backup/Lab9/SP123.config

The Restore operation executes. The XML file is parsed. A Restore operation typically takes two to three minutes to complete.

---

Edit the Backup XML file

Before You Begin

• Before you use a backed up XML file on another system, you should edit the file to remove any information that is unique to a particular system, for example, the IP address.

The following is an example of a backed up XML file. The contents of the file are abbreviated for the example used in this procedure.

<SP_config version="3.0">
<entry>
<property>/SP/check_physical_presence</property>
<value>false</value>
</entry>
<entry>
<property>/SP/hostname</property>
<value>labysystem12</value>
</entry>
<entry>
<property>/SP/system_identifier</property>
<value>SUN BLADE X8400 SERVER MODULE, ILOM v3.0.0.0, r32722
</value>
</entry>
.
.
.
<entry>
<property>/SP/clock/datetime</property>
<value>Mon May 12 15:31:09 2008</value>
</entry>
.
.
.
<entry>
<property>/SP/config/passphrase</property>
<value encrypted="true">89541176be7c</value>
</entry>
.
.
.
<entry>
<property>/SP/network/pendingipaddress</property>
<value>1.2.3.4</value>
</entry>
.
.
.
<entry>
<property>/SP/network/commitpending</property>
<value>true</value>
</entry>
.
.
.
<entry>
<property>/SP/services/snmp/sets</property>
<value>enabled</value>
</entry>
.
.
.
<entry>
<property>/SP/users/john/role</property>
<value>aucro</value>
</entry>
<entry>
<entry>
<property>/SP/users/john/password</property>
<value encrypted="true">c21f5a3df51db69fdf</value>
</entry>
</SP_config>

1. Consider the following in the example XML file:

• The configuration settings, with exception of the password and the passphrase, are in clear text.
• The check_physical_presence property, which is the first configuration entry in the file, is set to false. The default setting is true so this setting represents a change to the default ILOM configuration.
• The configuration settings for pendingipaddress and commitpending are examples of settings that should be deleted before you use the backup XML file for a Restore operation because these settings are unique to each server.
• The user account john is configured with the a,u,c,r,o roles. The default ILOM configuration does not have any configured user accounts so this account represents a change to the default ILOM configuration.
• The SNMP sets property is set to enabled. The default setting is disabled.

2. To modify the configuration settings that are in clear text, change the values or add new configuration settings.

For example:

• To change the roles assigned to the user john, change the text as follows:


<entry> <property>/SP/users/john/role</property> <value>auo</value> </entry> <entry>


• To add a new user account and assign that account the a,u,c,r,o roles, add the following text directly below the entry for user john:


<entry> <property>/SP/users/bill/role</property> <value>aucro</value> </entry> <entry>


• To change a password, delete the encrypted=”true” setting and the encrypted password string and enter the password in plain text. For example, to change the password for the user john, change the text as follows:


<entry> <property>/SP/users/john/password</property> <value>newpassword</value> </entry>

3. After you have made the changes to the backup XML file, save the file so that you can use it for a Restore operation on the same system or a different system.

---

Resetting the ILOM Configuration

Before You Begin

• To reset the ILOM configuration to the default settings, you need the Admin (a) role enabled.

1. Log in to the ILOM SP CLI or the CMM CLI.

2. Change to the /SP directory, type:

-> cd /SP

3. Type one of the following commands, depending on the option you select to reset the default settings.

• If you want to reset the ILOM configuration using the all option, type:

-> set reset_to_defaults=all

On the next reboot of the ILOM SP, the ILOM configuration default settings are restored.

• If you want to reset the ILOM configuration using the factory option, type:

-> set reset_to_defaults=factory

On the next reboot of the ILOM SP, the ILOM configuration default settings are restored and the log files are erased.

• If you want to cancel a reset operation just previously specified, type:

-> set reset_to_defaults=none

The previously issued reset_to_defaults command is canceled provided the reset_to_defaults=none command is issued before the ILOM SP reboots.

Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide

820-6412-12

Copyright © 2010, Oracle and/or its affiliates. All rights reserved.