Professional Documents
Culture Documents
AIX-/>
AIX-/>lsdev C
Gives all the connected devices
AIX-/>df
for example:
or
AIX-/>df -k
AIX-/>cd /var/adm/ras
AIX-/var/adm/ras>ls -lra
total 3585
-rw-rw-rw- 1 root system 929840 Aug 18 15:20 trcfile
-rw-r--r-- 1 root system 0 Sep 28 16:59 toto
-rw-r--r-- 1 root system 8192 Aug 01 14:14 nimlog
-rw-r--r-- 1 root system 5814 May 10 09:25 image.data
-r--r--r-- 1 bin bin 177408 Jun 27 09:14 errtmplt
-rw-r--r-- 1 root system 179131 Sep 28 15:02 errlog.sav
-rw-r--r-- 1 root system 179131 Sep 28 15:02 errlog
-rw-r--r-- 1 root system 41909 Sep 28 15:01 diag_log
-rw-r--r-- 1 root system 47271 Feb 25 2000 devinst.log
-rw--w--w- 1 root system 16384 Sep 28 16:09 conslog
-rw-r--r-- 1 bin bin 197206 Feb 25 2000 codepoint.cat
-rw-rw-r-- 1 root system 16384 May 10 09:25 bosinstlog
-rw-r--r-- 1 root system 8243 May 10 09:25 bosinst.data
-rw------- 1 root system 8192 Sep 28 15:00 bootlog
-rw-rw-r-- 1 root system 851 May 10 09:25 BosMenus.log
drwxr-sr-x 11 root system 512 Sep 19 11:31 ..
drwxrwxrwt 2 root system 512 Sep 28 16:59 .
AIX-/var/adm/ras>cd /
AIX-/>errpt -a
LABEL: SCSI_ERR10
IDENTIFIER: 0BA49C99
Description
SCSI BUS ERROR
Probable Causes
CABLE
CABLE TERMINATOR
DEVICE
ADAPTER
Failure Causes
CABLE LOOSE OR DEFECTIVE
DEVICE
ADAPTER
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
CHECK CABLE AND ITS CONNECTIONS
Detail Data
SENSE DATA
0001 0015 0000 0000 0000 00BE 0800 0098 2000 0000 0000 0000 0201 0205 0000 0000
0000 0000 0000 4302 0000 0000 0000 0000 0000 000A 0202 6740 870B 0000 F410 24B0
F410 23F0 000F 0200 0400 D800 0000 0008 829D 0720 0082 0200 0000 000A 02B5 6000
0008 0000 0311 9100 AF5E 0310
SNAP files
AIX-/>snap -a :
Sent with an AIX crash dump ; gives a report of all the AIX configuration and installation. The
associated files are in /tmp File system.
The size is about 20MB.
This is useful if netBIOS/X daemons are not OK when running io_maint. In this case a failure
message is given on the screen but it is sometimes difficult to understand this message. In this
case the AIX administration tool smit helps you to see the failure:
AIX-/>smitty
If you start a stopped NetBIOS/X, you can succeed and have OK on this command else you have
clearly the reason of the failure.
SPECIAL FIBRE CHANNEL
At the end of SYC normally terminated and where the device boot is defined as an IOSP Fibre
Channel GCOS8 do not recognize its disks:
1) Under IOH:
sel IOSPxx
rdtrace
You obtain something like that:
hdisk-2
If there is a problem you can have hdisk-1 or hdisk-2 in place of the disk name for hdisk-2
one or several adapters. hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-2
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
hdisk-1
If you have hdisk-2 it is probably because there is a problem in the connection between FC adapter of
the IOSP and the disk subsystem ( no cable or bad cable for example)
In cases 1 and 2, install the good file iospcds.rhd and re-run SYC.
In case 3 go to 2)
2) Open the MTM window of the IOSP concerned by boot and type :
lsdev -Cc disk
Verify that all the disk are present and declared available by AIX.
If not, you have to reconfigure AIX for FC. To do that first make a TERMINATE on SYC then on
MTM:
Then type:
It can take some minutes because at this step all the disks connected to the fchanx are deleted.
Then re-build the AIX configuration typing:
AIX-/> cfgmgr
Verify that it is OK. If yes re-run SYC.
If not, I think that there is a Problem on the AIX system or on the disk subsystem.
Then on MTM:
If the fcp is not created or is defined for one of the FC adapter, there is perhaps a driver or a FC
Firmware problem