Skip to main content

Emulex info in the Open Source domain....

The Emulex proprietary drivers and included utilities are extremely helpful. (the only oddity is where they are installed /usr/sbin/lpfc - but, whatever...). I happen to be at a shop that uses the OS multipath and Emulex fiber channel drivers. There is a bunch of good information to be found...

# lspci | grep -i emulex
0b:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03)
11:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03)

# cat /sys/class/scsi_host/host[2-3]/fwrev
2.00A3 (U3D2.00A3), sli-3
2.00A3 (U3D2.00A3), sli-3

# cat /sys/class/scsi_host/host[2-3]/lpfc_drvr_version
Emulex LightPulse Fibre Channel SCSI driver 8.2.0.87.1p
Emulex LightPulse Fibre Channel SCSI driver 8.2.0.87.1p

# hbacmd listhbas | grep "Port WWN" | awk '{print $4}' | xargs -n 1 hbacmd HbaAttributes
HBA Attributes for 10:00:00:00:c9:a6:91:35

Host Name : dbslp0066
Manufacturer : Emulex Corporation
Serial Number : VM03980823
Model : LPe12000-E
Model Desc : EMC LPe12000-E 8Gb PCIe Fibre Channel Adapter
Node WWN : 20 00 00 00 c9 a6 91 35
Node Symname : Emulex LPe12000-E FV2.00A3 DV8.2.0.87.1p
HW Version : 31004549
Opt ROM Version: 5.03a10
FW Version : 2.00A3 (U3D2.00A3), sli-3
Vendor Spec ID : 10DF
Number of Ports: 1
Driver Name : lpfc
Device ID : F100
HBA Type : LPe12000-E
Operational FW : SLI-3 Overlay
SLI2 FW : 2.00a3
SLI3 FW : 2.00a3
IEEE Address : 00 00 c9 a6 91 35
Boot Code : Enabled
Boot Version : 5.03a10
Driver Version : 8.2.0.87.1p; HBAAPI(I) v2.3.b, 07-12-10
Kernel Version : 1.10a8
HBA Temperature: Normal
Function Type : FC
Sub Device ID : F100
Sub Vendor ID : 10DF


HBA Attributes for 10:00:00:00:c9:a6:8c:63

Host Name : dbslp0066
Manufacturer : Emulex Corporation
Serial Number : VM03980805
Model : LPe12000-E
Model Desc : EMC LPe12000-E 8Gb PCIe Fibre Channel Adapter
Node WWN : 20 00 00 00 c9 a6 8c 63
Node Symname : Emulex LPe12000-E FV2.00A3 DV8.2.0.87.1p
HW Version : 31004549
Opt ROM Version: 5.03a10
FW Version : 2.00A3 (U3D2.00A3), sli-3
Vendor Spec ID : 10DF
Number of Ports: 1
Driver Name : lpfc
Device ID : F100
HBA Type : LPe12000-E
Operational FW : SLI-3 Overlay
SLI2 FW : 2.00a3
SLI3 FW : 2.00a3
IEEE Address : 00 00 c9 a6 8c 63
Boot Code : Enabled
Boot Version : 5.03a10
Driver Version : 8.2.0.87.1p; HBAAPI(I) v2.3.b, 07-12-10
Kernel Version : 1.10a8
HBA Temperature: Normal
Function Type : FC
Sub Device ID : F100
Sub Vendor ID : 10DF

# ls -1 -d /sys/bus/pci/drivers/lpfc/*/host*
/sys/bus/pci/drivers/lpfc/0000:0b:00.0/host2
/sys/bus/pci/drivers/lpfc/0000:11:00.0/host3

2012-03-07 -- I found the following @
http://kairo.wordpress.com/2010/05/13/identify-qlogic-wwn-on-red-hat-enterprise-linux-5-and-4-rhel/


# lspci | grep -i fibre
04:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
04:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
05:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
05:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
On  Red Hat Enterprise Linux 5 (5.x) is on /sys/class/fc_host/hostX/port_name
(X is your device 1,2,3,…N)
For get use:
cat /sys/class/fc_host/hostX/port_name
Sample with multiple HBA (Fibre) QLogic
# ls /sys/class/fc_host/
host3  host4  host5  host6
# cat /sys/class/fc_host/host[3-6]/port_name
0x2100001b32936e24
0x2101001b32b36e24
0x2100001b32932821
0x2101001b32b32821
On Red Hat Enterprise Linux 4 (AS/ES) is on /proc/scsi/qla2xxx/1 (1,2,3,..N)
Sample:
# egrep [node|port] /proc/scsi/qlx2xxx/0
scsi-qla0-adapter-node=200000e08b1c19f2;
scsi-qla0-adapter-port=210000e08b1c19f2;

Comments

  1. hari@myserverstatistics]# hbacmd listhbas | grep "Port WWN" | awk '{print $4}' | xargs -n 1 hbacmd
    bash: hbacmd: command not found

    ReplyDelete

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.