Installation guide

96107 Fourth Edition 27
StorageTek Proprietary
Overview
Start trace using:
/usr/lpp/cbxfc/runtrace
Stop trace using:
trcstop
Save trace in memory to file using:
trcrpt > /tmp/trc.log
Device Detection
The storage system should be connected to the HBA(s) and configured
correctly. This includes upgrading the storage system firmware/nvsram to the
latest versions.
What you should see using the failover driver
If all is working correctly, the lsdev –Cc disk command (for BladeStore) should
show the devices:
# lsdev –Cc disk
hdisk0 Available 10-60-00-10,0 16 Bit LVD SCSI Disk Drive
hdisk1 Available 10-68-05 STK Universal XPort
hdisk2 Available 20-58-05 STK Universal XPort
hdisk3 Available 10-68-01-01 Storagetek BladeStore with Path Failover
hdisk4 Available 10-68-02-01 Storagetek BladeStore with Path Failover
hdisk5 Available 10-68-03-01 Storagetek BladeStore with Path Failover
hdisk6 Available 10-68-04-01 Storagetek BladeStore with Path Failover
Common mistakes (using a BladeStore example)
Symptom: Failover does not work and I see some BladeStore volumes on
each path.
Possible problem:
a) May not have Cambex failover driver installed.
b) May not have Cambex DPF license installed.
c) May have selected AIX for host type instead of AIX_FO.
Symptom: I see the UTM LUNs in lsdev but the Client cannot find the
BladeStore.
Possible Problem: The agent software is started at boot time or install time
and scans for UTM LUNs. If they are not found (because of problems like