Basic FC Utility on AIX?

Good Morning!

My p550 running AIX 5.3 TL9 SP6 is supposedly connected to its SAN. However, it's not configuring its luns or behaving like it sees any traffic at all.

"fcstat fcs0" and "fcstat fcs1" both indicate no traffic moving across the interfaces.

Does AIX have a basic command that says "display all other [ hardware addresses | world wide names ] visible to this fc interface?"

Thanks!
dafydd

Not that I know of. Make sure you have a link on the card (check LED at card maybe) and that the zoning is set up correctly on any SAN switch you use and the connected Disk Array or whatever.

Some things that come to mind:

  • firstly make sure you got the zoning right.
  • fcstat might not show traffic if there are errors related to the fc devices. Use nmon with both the "^" (FC-Adapter) and the "a" (Adapterstats) options. With fc errors you might see traffic only at the Adapterstats.
  • AIX is not good in detecting changes in the FC setup. It often helps to delete and reconfigure the devices after making changes to the SAN. rmdev -dlR the fcs devices, then run cfgmgr.

I believe you when you say AIX is slow to recognize these things. I'm actually remote to the system. The IBM SAN engineer on site had created the LUNs on the DS8300, and none of us could figure out why. Two hours later, more or less, they just showed up!

Dubya. Tee. Eff?

Anyway, all are visible. I'm waiting on validation of how I want to combine the LUNs in Oracle, and I'll start the process of verifying that I can read and write to the LUNs.

Thanks!
dafydd

Hm, I did not say "slow". I said "not good" in a sense of either you see the devices after running cfgmgr or you do not. There is no autodetection and thus it is not possible that a FC device shows up like a USB device does on a windows PC. So either cfgmgr was running for the two hours you mentioned (which is hard to imagine even if there was a giantic SAN that kept the cfgmgr going) or sbdy did change sth on the server after you ran cfgmgr. You said that you are remote from the server. Is there any chance that sbdy else (at the remote site ?) did the configuration work? Check with the "last" command if there were additional logins and look in root�s history whether there are commands you did not issue.