HP StorageWorks 9100 Extreme Data Storage System administration guide V1.0.2 (AN540-96018, February 2010)

2. Copy the RPM file to a convenient location. For example, if the firmware is called mxso-firm-

ware-1.1-1234.rpm, copy it as shown in the following example:

glory1# scp sys1:/stage/mxso-firmware-1.1-1234.rpm /tmp

3. Run the exdsmgr install update command:

glory1# exdsmgr install update /tmp/mxso-firmware-1.1-1234.rpm

4. Run the exdsmgr syscheck command to validate that there are no RPM issues as follows:

# glory1# exdsmgr syscheck enable=software

The exdsmgr syscheck command warns you about dependency and related issues with RPMs. To

determine which RPMs have been added or removed since a server was initially installed, use the

exds_rpmcheck command as follows:

# /opt/hp/mxso/diags/bin/exds_rpmcheck local

The exds_rpmcheck command only runs on the server where the command is run. To check all

servers, use the pdsh(1) and dshbak(1) commands as follows:

# pdsh -w glory[1-8] /opt/hp/mxso/diags/bin/exds_rpmcheck all | dshbak

-c

NOTE:

This takes several minutes.

Reinstalling a server blade

NOTE:

Use this process to reinstall a server blade. The process destroys any information on the server's system

disk and replaces it with a new image. To install a new server blade, see Adding new server blades.

The server blade is installed using the server that is the current admin server. To reinstall a server:

1. Use the exdsmgr show matrix command to determine which server is the current admin

server:

# exdsmgr show matrix | grep exdsadmin

exdsadmin 192.168.9.90 glory2

where glory2 is the admin server

2. Complete any customization tasks that you are performing on the admin server (glory2 in this

example). This is because the following files are copied to the newly installed server:

• /root/.matrixrc

• /etc/hosts

• /etc/ntp.conf

• /etc/localtime

• /etc/sysconfig/clock

• /etc/sysconfig/nfs

Changing system parameters92