1. Check the new installed HBA. Run the AIX Advanced Diagnostics using the Problem Determination Mode against the Fibre Channel Adapter. While the test is running, you will be prompted to plug or unplug the fibre cable or the wrap plug to or from the connector on the fibre channel adapter.
# diag -Avd fcs<X>
2. Check the Switch.
For AIX 5.x the Switch firmware should be at least at level 06.xx.xx
Please check the following Port settings:
Port Type: Generic (Gx) or Fabric (F)
Port Speed: Negotiate, 1Gb/s for IBM 6227 or 2Gb/s for the other HBA types
Check that the port is Online and not segmented
If Port Binding is used, update the bound WWN
If your Switch is Flexport capable, check that the port is activated by a license key (one key for 8 ports)
3. AIX
There are some driver issues. Install the latest version of all filesets listed below.
(http://techsupport.services.ibm.com/server/fixes)
Commonly needed filesets:
– devices.common.IBM.fc.rte
– devices.common.IBM.fc.hba-api
– devices.fcp.disk.rte
– devices.fcp.disk.array.diag
– devices.fcp.disk.array.rte
– devices.fcp.tape.rte
– devices.scsi.disk.rte
Device Drivers:
– IBM FC 6227: devices.pci.df1000f7
– IBM FC 6228: devices.pci.df1000f9
– IBM FC 6239: devices.pci.df1080f9
– IBM FC 5716: devices.pci.df1000fa
Update the Fibre Channel Adapter, the System and Service Processor Microcode to the current level.
The IBM pSeries Support Website includes installation instructions and the current microcode.
(http://techsupport.services.ibm.com/server/mdownload.
Check the PCI Adapter Placement. Refer to the PCI Adapter Placement Reference.
(http://publib.boulder.ibm.com/infocenter/pseries/index.jsp?topic=/com.ibm.pseries.doc/hardware.htm)
You should set the default value for the HBA’s Link Initialization protocol. Al is the setting for Arbitrated Loop and Switch.
# chdev -l 'fcs<Y>' -a init_link='al' -P
4. Force a F port login:
Note: You need to know the relationship between the Fibre Channel SCSI
I/O Controller Protocol Device fscsi<X> and its parent fcs<Y>. In the example bellow fcs0 is the parent of fscsi0 and fcs1 is the parent of fscsi1. But fcs3 is the parent of fscsi2 and fcs2 is the parent of
fscsi3.
# lsdev -Ccdriver -F "parent name description" -H
parent name description
fcs0 fscsi0 FC SCSI I/O Controller Protocol Device
fcs1 fscsi1 FC SCSI I/O Controller Protocol Device
fcs3 fscsi2 FC SCSI I/O Controller Protocol Device
fcs2 fscsi3 FC SCSI I/O Controller Protocol Device
– Unconfigure the hdisks and the FC SCSI I/O Controller Protocol Device
# rmdev -Rdl fscsi<X>
– Set the HBA to defined
# rmdev -Rl fcs<Y>
– Reset the switchport
– Set the Link Initialization protocol to Arbitrated Loop and Switch
# chdev -l 'fcs0' -a init_link='al'
– Configure the HBA
# cfgmgr -vl fcs<Y>
– Now you should be able to see the fabric login
I hope, this will help to solve your problem cheer :-)