FC Adapter "Defined", not "Available" 1

[homeincolo]

I am trying to connect multiple FC library I/O blades to an AIX server I have that has 2 FC6228 FC HBAs. "lsdev -Cc adapter" shows fcs1 as Available, but fcs0 as Defined. How do I make fcs0 available?

Thanks.

 

[p5wizard]

The adapter's configuration method was unable to find/configure the adapter at boot time.

You might want to try manually to configure it:

cfgmgr -vl fcs0

and post the output back.

Also it might be a microcode problem. Get the latest level from

http://techsupport.services.ibm.com/server/mdownload/pci.df1000f9-3.91a1.aix.noarch.rpm

and download it to the adapter with diag-service aids-download microcode and see if that helps.

Or there is a problem with the adapter itself: use diag to find out. You might end up having to call IBM support to get the adapter replaced...


HTH,

p5wizard

 

[nimrodman]

You need to first remove the devices before running the conifg manager - rmdev -Rl fcs0 or whatever the device name is, and then run cfgmgr -v - if thast does not work, completely remov ethe devices with the -dl flags and then run config mgr.

 

[p5wizard]

If fcs0 is "Defined", any child or dependent device will at most be also "Defined", so
rmdev -Rl fcs0
won't do a thing IMHO.

The command
rmdev -Rdl fcs0
will remove the device and all its children/dependents from odm.

Running
cfgmgr -v
after that might find the device again, possibly again failing to fully configuring it. But at least the output might give a clue as to why it is impossible to configure the adapter.


HTH,

p5wizard

 

[homeincolo]

I suspect that the HBA is bad. I ran

cfgmgr -vl fcs0

and got a return code = 50 - Cannot perform the requested function because the specified device was not detected.

I removed fsc0 and rescanned. It showed up as Defined again. I attempted to run diag and while Verifying Adapter's Response, the system rebooted. This happened twice.

Thanks P5 and nimrodman. This helped alot.

 

[p5wizard]

You might want to try and re-seat the adapter in its PCI slot (while powered down or if it is a PCI HotPlug slot, while setting the slot in action state: diag - service aids - hot plug tasks - PCI hot plug manager). Perhaps the adapter is not properly seated and that may be throwing a crash/reboot whenever you try to run cfgmgr on it.

Also try with the apparently failed adapter in a different slot - if you have another available.


HTH,

p5wizard