Whenever you need to perform an upgrade of SDD (and it is wise to keep it up-to-date), make sure you check the SDD documentation before doing this. Here's the quick steps to perform to do the updates.

• Check for any entries in the errorlog that could interfere with the upgrades:

  # errpt -a | more

• Check if previously installed packages are OK:

  # lppchk -v

• Commit any previously installed packages:

  # installp -c all

• Make sure to have a recent mksysb image of the server and before starting the updates to the rootvg, do an incremental TSM backup. Also a good idea is to prepare the alt_disk_install on the second boot disk.
• For HACMP nodes: check the cluster status and log files to make sure the cluster is stable and ready for the upgrades.
• Update fileset devices.fcp.disk.ibm to the latest level using smitty update_all.
• For ESS environments: Update host attachment script ibm2105 and ibmpfe.essutil to the latest available levels using smitty update_all.
• Enter the lspv command to find out all the SDD volume groups.
• Enter the lsvgfs command for each SDD volume group to find out which file systems are mounted, e.g.:

  # lsvgfs vg_name

• Enter the umount command to unmount all file systems belonging to the SDD volume groups.
• Enter the varyoffvg command to vary off the volume groups.
• If you are upgrading to an SDD version earlier than 1.6.0.0; or if you are upgrading to SDD 1.6.0.0 or later and your host is in a HACMP environment with nonconcurrent volume groups that are varied-on on other host, that is, reserved by other host, run the vp2hd volume_group_name script to convert the volume group from the SDD vpath devices to supported storage hdisk devices. Otherwise, you skip this step.
• Stop the SDD server:

  # stopsrc -s sddsrv

• Remove all the SDD vpath devices:

  # rmdev -dl dpo -R

• Use the smitty command to uninstall the SDD. Enter smitty deinstall and press Enter. The uninstallation process begins. Complete the uninstallation process.
• If you need to upgrade the AIX operating system, you could perform the upgrade now. If required, reboot the system after the operating system upgrade.
• Use the smitty command to install the newer version of the SDD. Note: it is also possible to do smitty update_all to simply update the SDD fileset, without first uninstalling it; but IBM recommends doing an uninstall first, then patch the OS, and then do an install of the SDD fileset.
• Use the smitty device command to configure all the SDD vpath devices to the Available state.
• Enter the lsvpcfg command to verify the SDD configuration.
• If you are upgrading to an SDD version earlier than 1.6.0.0, run the hd2vp volume_group_name script for each SDD volume group to convert the physical volumes from supported storage hdisk devices back to the SDD vpath devices.
• Enter the varyonvg command for each volume group that was previously varied offline.
• Enter the lspv command to verify that all physical volumes of the SDD volume groups are SDD vpath devices.
• Check for any errors:

  # errpt | more
  # lppchk -v
  # errclear 0

• Enter the mount command to mount all file systems that were unmounted.

# dpovgfix vg_name

You can run into an issue with EMC storage on AIX systems using MPIO (No Powerpath) for your boot disks:

After installing the ODM_DEFINITONS of EMC Symmetrix on your client system, the system won't boot any more and will hang with LED 554 (unable to find boot disk).

The boot hang (LED 554) is not caused by the EMC ODM package itself, but by the boot process not detecting a path to the boot disk if the first MPIO path does not corresponding to the fscsiX driver instance where all hdisks are configured. Let me explain that more in detail:

Let's say we have an AIX system with four HBAs configured in the following order:

# lscfg -v | grep fcs
fcs2 (wwn 71ca) -> no devices configured behind this fscsi2 driver instance (path only configured in CuPath ODM table)
fcs3 (wwn 71cb) -> no devices configured behind this fscsi3 driver instance (path only configured in CuPath ODM table)
fcs0 (wwn 71e4) -> no devices configured behind this fscsi0 driver instance (path only configured in CuPath ODM table)
fcs1 (wwn 71e5) -> ALL devices configured behind this fscsi1 driver instance

# lspath -l hdisk2 -H -F"name parent path_id connection status"
name   parent path_id connection                      status
hdisk2 fscsi0 0       5006048452a83987,33000000000000 Enabled
hdisk2 fscsi1 1       5006048c52a83998,33000000000000 Enabled
hdisk2 fscsi2 2       5006048452a83986,33000000000000 Enabled
hdisk2 fscsi3 3       5006048c52a83999,33000000000000 Enabled

# rmpath -l hdisk2 -p fscsi0 -d
# rmpath -l hdisk2 -p fscsi2 -d
# rmpath -l hdisk2 -p fscsi3 -d
# lspath -l hdisk2 -H -F"name parent path_id connection status"

# lspv
hdisk10 0003027f7f7ca7e2 rootvg active
# lsdev -Cc disk
hdisk2 Defined   00-09-01 MPIO Other FC SCSI Disk Drive
hdisk10 Available 00-08-01 EMC Symmetrix FCP MPIO Raid6

From powerlink.emc.com:

1. Before making any changes, collect host logs to document the current configuration. At a minimum, save the following: inq, lsdev -Cc disk, lsdev -Cc adapter, lspv, and lsvg
2. Shutdown the application(s), unmount the file system(s), and varyoff all volume groups except for rootvg. Do not export the volume groups.

   # varyoffvg <vg_name>

   Check with lsvg -o (confirm that only rootvg is varied on)
   If no PowerPath, skip all steps with power names.
3. For CLARiiON configuration, if Navisphere Agent is running, stop it:

   # /etc/rc.agent stop

4. Remove paths from Powerpath configuration:

   # powermt remove hba=all

5. Delete all hdiskpower devices:

   # lsdev -Cc disk -Fname | grep power | xargs -n1 rmdev -dl

6. Remove the PowerPath driver instance:

   # rmdev -dl powerpath0

7. Delete all hdisk devices:
   For Symmetrix devices, use this command:

   # lsdev -CtSYMM* -Fname | xargs -n1 rmdev -dl

   For CLARiiON devices, use this command:

   # lsdev -CtCLAR* -Fname | xargs -n1 rmdev -dl

8. Confirm with lsdev -Cc disk that there are no EMC hdisks or hdiskpowers.
9. Remove all Fiber driver instances:

   # rmdev -Rdl fscsiX

   (X being driver instance number, i.e. 0,1,2, etc.)
10. Verify through lsdev -Cc driver that there are no more fiber driver instances (fscsi).
11. Change the adapter instances in Defined state

    # rmdev -l fcsX

    (X being adapter instance number, i.e. 0,1,2, etc.)
12. Create the hdisk entries for all EMC devices:

    # emc_cfgmgr

    or

    # cfgmgr -vl fcsx

    (x being each adapter instance which was rebuilt). Skip this part if no PowerPath.
13. Configure all EMC devices into PowerPath:

    # powermt config

14. Check the system to see if it now displays correctly:

    # powermt display
    # powermt display dev=all
    # lsdev -Cc disk
    # /etc/rc.agent start

With POWER6, the default addresses of the service processors have changed. This only applies to environments where the managed system was powered on before the HMC was configured to act as an DHCP server. The Service Processors may get their IP-Addresses by three different mechanisms:

1. Addresses received from a DHCP Server.
2. Fixed addresses given to the interfaces using the ASMI.
3. Default addresses if neither of the possibilities above is used.

Port HMC1: 192.168.2.147/24
Port HMC2: 192.168.3.147/24

First Service Processor:
Port HMC1: 169.254.2.147/24
Port HMC2: 169.254.3.147/24

Second Service Processor:
Port HMC1: 169.254.2.146/24
Port HMC2: 169.254.3.146/24

If you decide to update to HMC release 7.3.5, Fix Central only supplies you the ISO images.

This procedure describes how you can update your HMC using the network without having to sit physically in front of the console.

First, check if this new HMC level is supported by the firmware levels of your supported systems using this link. If you're certain you can upgrade to V7.3.5, then make sure to download all the required mandatory fixes from IBM Fix Central. Don't download the actual base level of HMC v7.3.5 of 3 Gigabytes. We'll download that directly to the HMC later on.

Then, perform the "Save upgrade data" task using either the Web interface or the command line. Then get the required files from the IBM server using ftp protocol using the following command:

# getupgfiles -h ftp.software.ibm.com -u anonymous --passwd ftp
-d /software/server/hmc/network/v7350

# chhmc -c altdiskboot -s enable --mode upgrade

# hmcshutdown -r -t now

Run to install:

# yum install pure-ftpd

# chkconfig pure-ftpd on

# /etc/init.d/pure-ftpd start

# /etc/init.d/pure-ftpd restart

Install the software:

# yum -y install mysql mysql-server php-mysql httpd php phpmyadmin

# cd /var/www/html
# ln -s /usr/share/phpMyAdmin

# chkconfig httpd on
# chkconfig --add mysqld
# chkconfig mysqld on
# service httpd start
# service mysqld start

# mysqladmin -u root password root

# mysql -u root -p
mysql> DROP DATABASE test; [removes the test database]
mysql> DELETE FROM mysql.user WHERE user = ''; [Removes anonymous access]

<?php
   phpinfo();
?>

mysql> create database testdb

<Directory "/usr/share/phpMyAdmin">
   Order allow,deny
   Allow from all
</Directory>

# service httpd restart

Use yum to update your system (for Fedora or Red Hat):

# yum update

proxy=http://address-of-proxyserver.org:80

Even though Ubuntu is very complete initially, you might want extra's, like a media player. You can use a script to do this for you:

# wget http://download.ubuntuforums.org/ubuntusetup/ubuntusetup.sh
# sudo sh ubuntusetup.sh

APT is short for Advanced Packaging Tool and is found in Debian distributions of Linux, like Ubuntu. To be able to use APT, you first need to download a list of available software:

# sudo apt-get update

# sudo apt-get install mozilla-firefox

# sudo apt-cache search [search-term]

# sudo apt-get upgrade