Installation guide

AIX - Installation Support-
28 Fourth Edition 96107
StorageTek Proprietary
not mapping UTM LUNs), agent needs to be cycled to rediscover the UTM
LUNs once they show up in lsdev. This is done by:
Type: SMagent stop
SMagent stopped
Type: SMagent start
After a few seconds, messages like the following will appear:
Checking device /dev/rhdisk2 : Skipping
Checking device /dev/rhdisk5 : Skipping
Checking device /dev/rhdisk6 : Skipping
Checking device /dev/rhdisk7 : Skipping
Checking device /dev/rhdisk8 : Skipping
Checking device /dev/rhdisk9 : Skipping
Checking device /dev/rhdisk10 : Skipping
Checking device /dev/rhdisk11 : Skipping
Checking device /dev/rhdisk12 : Skipping
Checking device /dev/rhdisk13 : Skipping
Checking device /dev/rhdisk14 : Skipping
Checking device /dev/rhdisk15 : Skipping
Checking device /dev/rhdisk16 : Activating
Checking device /dev/rhdisk3 : Skipping
Checking device /dev/rhdisk4 : Skipping
Checking device /dev/rhdisk17 : Activating
Running...
There should be 2 activated UTM LUNs. If they do not show up in this scan list but DO
show up in lsdev, it is possible that the UTM LUNs were removed using rmdev without
first stopping agent. This can leave the UTM LUNs reserved. Cycle the controllers
power to release these.
Other troubleshooting methods
If the adapters are active with the lsdev –Cc adapter command but the disks
don’t show up, run cfgmgr with the –v (verbose) parameter and send it to a
file. (cfgmgr –v > /tmp/cfg1.log).
Edit this file and search for the fcs(n) (for IBM HBAs) or fscsi(n) (for Cambex
HBAs) devices that are the HBAs. There will usually be some indication of
whether any targets (controllers) were discovered.
The following procedures cover special tasks required.
Removing existing configuration on the host
If upgrading an existing storage system installed and configured on AIX,
perform the following actions to remove existing devices.
• Unmount any mounted file systems using the umount command or smit
• Vary offline any volume groups using varyoffvg or smitty