Figure 7-7 Viewing change in RSA II login profiles after script file completes

7.6 Resetting the RSA II back to factory defaults

This section describes how to return the RSA or RSA II back to the factory
default settings.

Notes: Changes made include the following:

򐂰 Reset the user ID and password back to the default setting USERID and
PASSW0RD (with a zero and not the letter o).
򐂰 For the RSA II, change the IP address back to the default setting of DHCP,
then static, with a static IP address 192.168.70.125 and subnet mask
255.255.255.0.
򐂰 For the RSA, change the IP address back to the default setting of DHCP
with no static backup.
򐂰 Reset the host name back to ASMA +, the MAC address of the service
processor (for example, ASMA00096b0a8469).

An easy way to reconfigure these service processors after resetting them is

connecting via an ASM interconnect network connection.

There are four ways to perform this task.

򐂰 ASU: See below.
򐂰 IBM Director: See “Using IBM Director” on page 250.
򐂰 MPCLI: See “Using MPCLI” on page 252.
򐂰 Web interface (select Restore Defaults from the navigation menu).

248 IBM Eserver xSeries and BladeCenter Server Management

 The ASU and IBM Director methods do not require that you know a valid user ID
and password on the service processor. The MPCLI, however, does require that
you know this information.

7.6.1 Using ASU

You would need to use ASU to reset the RSA or RSA II back to factory defaults if
the administrator has forgotten the IP address, user ID, and/or password, or the
service processor (or left the company), and your company has not implemented
IBM Director.

To reset the adapter to factory defaults using ASU, do the following:

1. Install ASU locally on the server (see 6.2, “Advanced Settings Utility” on
page 160).
2. Add the RSAI/RSAII definition file to ASU (see 6.2.4, “Using the ASU
definition files” on page 163).
3. Enter the following command to reset the service processor:
– For Windows: asu resetrsa
– For Linux: ./asu resetrsa
4. The service processor will be reset to the factory defaults and then be
restarted.
5. You may also wish to configure some of the basic settings using ASU:
– Disable DHCP.
– Set a static IP address, subnet mask, and gateway.
– Replace the default user ID with a new one (for example, u=lesley,
p=ba1n).
Use the SET commands as shown in Example 7-4 (for Linux use ./asu
instead of asu). See Example 6-1 on page 166 for a complete list of SET
commands.

Example 7-4 ASU commands to configure basic RSA settings

asu set RSA_DHCP1 Disabled
asu set RSA_Network1 Enabled
asu set RSA_HostIPAddress1 xxx.xxx.xxx.xxx
asu set RSA_HostIPSunet1 xxx.xxx.xxx.xxx
asu set RSA_GatewayIPAddress1 xxx.xxx.xxx.xxx
asu set RSAString_loginId1 “lesley”
asu set RSAString_Password1 “ba1n”

Chapter 7. Scenarios and best practices 249

 Tip: See 6.2.8, “ASU batch commands” on page 174, for information on how
to issue these commands in batch.

7.6.2 Using IBM Director

IBM Director also has the capability to reset the RSA and RSA II settings back to
the factory defaults. You will need:
򐂰 IBM Director Agent installed on the server where you have the service
processor you are wishing to reset (we will call this the target server)
򐂰 The appropriate service processor drivers installed for your server
򐂰 IBM Director Server installed on a server in your network

To reset the adapter to factory defaults using IBM Director, do the following:
1. Using the IBM Director management console, ensure that the target server
has been discovered by IBM Director.
2. Expand the Management Processor Assistant task in the Tasks pane.
3. Select Configuration subtask and drag and drop it on to the target server.
Figure 7-8 on page 251 opens. If you are not able to connect to the service
processor you will see a pop-up message. Verify that the service processor
driver is installed correctly.

250 IBM Eserver xSeries and BladeCenter Server Management

Figure 7-8 IBM Director MPA configuration view

4. To restore the service processor factory defaults, click General settings.

Figure 7-9 appears.

Figure 7-9 General settings window within the MPA configuration window

5. Check the check box under the heading Reset default configuration (scroll to
the right if necessary; see Figure 7-9).
6. Click Apply in the menu above to save your changes to the service
processor.
7. All the factory defaults should now be set again, ready to be reconfigured
either via this interface or another of your choice.

Chapter 7. Scenarios and best practices 251

 Note: There are no security risks with either of the above tasks to reset the
RSA or RSAII adapter. ASU is secure because this is a local tool and will only
be installed by the company system administrator. IBM Director is fully secure,
as there is a requirement to have a user ID and password to log on to the IBM
Director management console.

7.6.3 Using MPCLI

If you know the IP address, user ID, and password of the service processor, you
can reset the configuration back to the factory defaults using the MPCLI utility.
The MPCLI is useful when the server does not have an operating system
installed that you can log into.

To reset the adapter to factory defaults using MPCLI, do the following:

1. Install the MPCLI on another workstation. See 6.3.5, “Installing the MPCLI” on
page 181, for details.
2. Start the MPCLI:
– Windows: Start → Programs → IBM → MPCLI → MPCLI
– Linux: /opt/IBMmpcli/bin/MPCLI.bsh
3. At the MPCLI command prompt type in the following command (substituting
your own values for service processor IP address, user ID, and password):
logonip -hostname xxx.xxx.xxx.xxx -userid userid -password password
4. Enter the following command to reset the service processor:
resetmp

Note: Default network configurations are as follows:

򐂰 RSA II: Use DHCP if it can reach a DHCP server, or failing that, to set
the static address 192.168.70.125, subnet 255.255.255.0.
򐂰 RSA: Use DHCP. If no DHCP server can be found, no IP address is
assigned.

5. You may also wish to configure some of the basic settings using the MPCLI:
– Disable DHCP.
– Set a static IP address, subnet mask, and gateway.
– Replace the default user ID with a new one (for example, u=lesley,
p=ba1n).
You can use scripting for this task. Refer to “Scripting with the MPCLI
commands” on page 186. The commands used for this task are as shown in

252 IBM Eserver xSeries and BladeCenter Server Management

 Example 7-5 (substitute the DHCP-assigned address for the service
processor in the logonip command, if applicable).

Example 7-5 MPCLI commands to set basic defaults

logonip -hostname 192.168.70.125 -userid USERID -password PASSW0RD
setnethw -interface 1 -enabled true
setdhcp -enabled false
setip -interface 1 -method static
setip -interface 1 -ipaddress xxx.xxx.xxx.xxx
setip -interface 1 -gateway xxx.xxx.xxx.xxx
setip -interface 1 -subnet xxx.xxx.xxx.xxx
setdialinentry -index 1 -id userid -password password -dialback false -readonly false

Note: There are three method types applicable for the RSA II (the RSA
only supports the first two):
򐂰 static - Uses the static IP address
򐂰 dhcp - Gets an assigned IP address from a DHCP server
򐂰 dhcpstatic - Uses static IP address if DHCP server is not available

7.7 How to use ASU remotely

As described in 6.2, “Advanced Settings Utility” on page 160, ASU is a utility
designed to be installed and run locally on the server. However, with the use of
IBM Director’s File Transfer and Remote Console tasks, you can install and use
the ASU tool remotely.

This scenario could help when, in a lights out remote environment, you need to
make changes to the server’s CMOS or RSA/RSA II adapter settings without
restarting the server.

We make the following assumptions for this scenario:

򐂰 You already have an IBM Director management server installed in your
environment.
򐂰 You have already installed IBM Director Agent on the server you want to use
the ASU utility with.
򐂰 You have IBM Director console installed at your remote location, for example,
on your laptop, and you are able to connect to the IBM Director server.
򐂰 You are able to discover the IBM Director Agent from the IBM Director
management server.

Chapter 7. Scenarios and best practices 253

 򐂰 You have downloaded the required ASU code to your laptop or remote
location. For details on what code is required, refer to 6.2.3, “Downloading
ASU and definition files” on page 162.

Refer to the IBM Director Installation Guide for details on installation of the agent
and server portions of IBM Director.

Using ASU remotely can be done as follows:

1. Open and connect to the IBM Director server from your remote console.
2. Once connected, select the task File Transfer in the right-hand pane, and
drag and drop this onto the server you want to use ASU with. The file transfer
window will now open. See Figure 7-10.

Figure 7-10 File transfer window

3. From the local (left) pane navigate to and expand the directory you
downloaded the ASU tool to. See Figure 7-11 on page 255.

254 IBM Eserver xSeries and BladeCenter Server Management

Figure 7-11 ASU download directory location on local

4. Expand the directory on the remote server where you want to copy the ASU
files to.
5. Select the ASU files from local system and drag and drop them on the remote
directory location.
6. You are now ready to install ASU on this remote server. Refer to the
instructions in 6.2.3, “Downloading ASU and definition files” on page 162, to
unpack the ASU files; and 6.2.4, “Using the ASU definition files” on page 163,
to add the required definition files to ASU.
7. Once you have completed the configuration of ASU, you can now begin to
operate remotely.
8. From the director console select the Remote Session task and drag and
drop it onto the system you want to use ASU with. The remote session will
open. You can now begin to work remotely and issue ASU commands to the
server. See Figure 7-12 on page 256 for an example of using the IBM Director
remote session task to issue ASU commands remotely.

Chapter 7. Scenarios and best practices 255

 Figure 7-12 IBM Director remote session running ASU remotely

7.8 Remote BIOS and firmware updates

Every environment should have a change management procedure in place. This
will ensure that your servers are always updated to the latest release of BIOS,
firmware, and device drivers.

There are a number of ways to upgrade the service processor firmware and
system BIOS of your servers:
򐂰 MPCLI (described in 7.8.1, “Using MPCLI to upgrade firmware” on page 257)
򐂰 IBM Director software distribution (described in 7.8.2, “Using IBM Director to
upgrade firmware” on page 259)
򐂰 UpdateXpress RemoteUX (described in 7.8.3, “Using UpdateXpress
RemoteUX to update firmware” on page 266)
򐂰 RSA II Web interface

256 IBM Eserver xSeries and BladeCenter Server Management