SLES 8 and fibre channel

[Ezra V. Isacco Di Biase_1]

Hi all,

Could anyone tell me how to detect the WWNN of a fibre channel adapter?
I found the adapter installed on a bl20p.

I have to set ACL on a MSA1000 so I need the WWNN, isn't it?
I am new to Linux but have experience on unix.

Thanks to all.
Ezra

[Uwe Zessin]

Ezra,
I have never worked with blades, but:

- see if the blade provides an adapter BIOS - the PCI cards have one that can display the WWN

- download the Windows driver and check if the FLASUTIL.EXE is enclosed / works with the chip - it can display the WWN on PCI cards (you need a DOS floppy, though)

- look on the fibre channel switch - the command is 'switchShow' if you have a Brocade switch

- if this is the only adapter that has been connected recently to the MSA, then the connection's name should be 'unknown'


Do not forget to assign the 'Linux' profile to the new connection(s).

[V.Tamilvanan]

Hi,
You can find the WWNN on /var/adm/messages file.

[Craig Gilmore]

The iLO and SIM utilities can display the WWNN for the card. I'm guessing that you are using the Mezzanine card on a BL20p.

Also see:

http://issgweb.cca.cpqcorp.net/products/servers/proliant-bl/p-class/bl-p-interconnect-switch2.html

[Colin Topliss]

Hmm.

Do you know what FCA you have?

You can find all the information you need by:

cd /proc/scsi
ls (look for your card type - eg qla2300)
cd qla2300
ls
You'll see a file with a number for a name. That number equals the SCSI channel assigned to that device (eg 3). Do
cat 3

This will give you alot of information about the card - including what I think you're after.

If you can't see anything, then it may be that the driver for the card has not been loaded. You'll need to post the card type, and the output from lsmod so we can see what has been loaded.

Col.

[Ezra V. Isacco Di Biase_1]

Thanks to all.

When we installed the drivers for the adapter, we haven't noticed that in the file /etc/sysconfig/kernel would be erased any occurence with the adapter module.

We added "qla2300" in the file and executed mkinitrd, when the system rebooted the problem was solved.

Thanks again for your replies.
Ezra