Storage : Identify Sun Fibre Channel (FC) HBA
Assuming there is not a mixture of SUN and NON-SUN FC HBAs in server, (ie. all HBAs from same vendor) if one of the HBAs is down looking at other HBAs in server will tell us if HBAs in server are SUN Branded or not.
These steps only apply to:
- Fibre channel (FC-AL and Point-to-Point) HBAs Cards: – Single or Dual port FC only ports
- Ethernet/IP and FC HBA Combo Cards: - 2 Ethernet ports and 2 FC ports
- CEE/FCoE CNAs (Converged Network Adapters) Cards: - 2 FCoE ports (Fibre Channel over Ethernet)
Using fcinfo Command:
For Solaris 10 U1 or above -
Command: fcinfo hba-port
For Solaris 8 & 9 or Solaris 10 before U1 or if fcinfo command does not work for some reason go to ”prtpicl” Command and check “Model:” field in conjunction with “Manufacturer:” field.
LPxxxxxx-S are SUN Emulex HBA Cards (ie has a “-S” for Sun at end).
LPxxxxxx-E are usually NON-SUN HBAs resold by EMC.
LPxxxxxx-H are usually NON-SUN HBAs resold by Hitachi.
375-xxxx-xx are SUN Qlogic HBA Cards.
- QLAxxxx may or may not be SUN Qlogic HBA Cards so you would need to use “prtpicl Command:” to determine.
- Model: 2200 with Manufacturer: QLogic Corp is a old SUN Fibre Channel Arbitrated Loop (FC-AL) HBA Cards.
- Legacy discontinued JNI FC HBAs with jfca Driver are SUN HBA cards but other JNI cards may also be listed and would require SUN SAN engineer analysis of explorer output to determine if it SUN branded or not.
Example:
# fcinfo hba-port
HBA Port WWN: 2300080020fb288d
OS Device Name: /dev/cfg/c1
Manufacturer: QLogic Corp.
Model: 2200
Firmware Version: 2.01.145
FCode/BIOS Version: ISP2200 FC-AL Host Adapter Driver: 1.14 01/11/20
Serial Number: not available
Driver Name: qlc
Driver Version: 20090415-2.30
Type: L-port
State: online
Supported Speeds: 1Gb
Current Speed: 1Gb
Node WWN: 2200080020fb288dHBA Port WWN: 10000000c94a30f8
OS Device Name: /dev/cfg/c5
Manufacturer: Emulex
Model: LP10000DC-S
Firmware Version: 1.92a1 (T2D1.92A1)
FCode/BIOS Version: Boot:5.01a4 Fcode:1.50a4
Serial Number: BG52130223
Driver Name: emlxs
Driver Version: 2.31t (2009.04.05.14.10)
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb
Current Speed: 2Gb
Node WWN: 20000000c94a30f8HBA Port WWN: 10000000c94a30f9
OS Device Name: /dev/cfg/c6
Manufacturer: Emulex
Model: LP10000DC-S
Firmware Version: 1.92a1 (T2D1.92A1)
FCode/BIOS Version: Boot:5.01a4 Fcode:1.50a4
Serial Number: BG52130223
Driver Name: emlxs
Driver Version: 2.31t (2009.04.05.14.10)
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb
Current Speed: 2Gb
Node WWN: 20000000c94a30f9HBA Port WWN: 210100e08b263e96
OS Device Name: /dev/cfg/c3
Manufacturer: QLogic Corp.
Model: 375-3030-xx
Firmware Version: 2.01.145
FCode/BIOS Version: fcode: 1.13;
Serial Number: not available
Driver Name: qlc
Driver Version: 20090415-2.30
Type: L-port
State: online
Supported Speeds: 1Gb
Current Speed: 1Gb
Node WWN: 200100e08b263e96HBA Port WWN: 210000e08b063e96
OS Device Name: /dev/cfg/c4
Manufacturer: QLogic Corp.
Model: 375-3030-xx
Firmware Version: 2.01.145
FCode/BIOS Version: fcode: 1.13;
Serial Number: not available
Driver Name: qlc
Driver Version: 20090415-2.30
Type: unknown
State: offline
Supported Speeds: 1Gb
Current Speed: not established
Node WWN: 200000e08b063e96
#
Using prtpicl Command:
If prtpicl command not available or does not work for some reason then go to “prtdiag Command:”.
Sample Command: prtpicl -v | egrep “devfs-path|driver-name|subsystem-id” | nawk ‘/:subsystem-id/ { print $0; getline; print $0; getline; print $0; }’ | nawk -F: ‘{ print $2 }’
Note: Make sure entire command string is entered correctly
Example:
# prtpicl -v | egrep “devfs-path|driver-name|subsystem-id” | nawk ‘/:subsystem-id/ { print $0; getline; print $0; getline; print $0; }’ | nawk -F: ‘{ print $2 }’
subsystem-id 0×8
devfs-path /pci@1f,4000/TSI,gfxp@4
driver-name gfxp
subsystem-id 0x10a
devfs-path /pci@4,4000/SUNW,qlc@3
driver-name qlc
subsystem-id 0x10a
devfs-path /pci@4,4000/SUNW,qlc@3,1
driver-name qlc
subsystem-id 0xffff
devfs-path /pci@6,4000/pci@3/scsi@4
driver-name qus
subsystem-id 0xffff
devfs-path /pci@6,4000/pci@3/scsi@5
driver-name qus
subsystem-id 0×4083
devfs-path /pci@6,2000/pci@1/SUNW,qlc@4
driver-name qlc
subsystem-id 0×4083
devfs-path /pci@6,2000/pci@1/SUNW,qlc@5
driver-name qlc
#
This list will include FC HBAs, as well as, other components. Check table below under SSID column.
NOTE: If WinDriver (unsupported NON-SUN driver development tool) is installed it can alter HBA card info by a prepending a digit “8″ to SSID and changing fcode driver strings which alter the device path to QLGC,qlc. This WinDrivers has also can cause servers to panic and reboot.
Search /var/adm/messages for following strings to determine if WinDriver is installed:
windrvr6
Jungo
WinDriver
WDsolarisAttach
Example:
SUN Qlogic HBAsubsystem-id 0×143
devfs-path /pci@0/pci@0/pci@8/pci@0/pci@8/SUNW,qlc@0
driver-name qlc
binding-name pciex1077,143
changed to
subsystem-id 0×8143
devfs-path /pci@0/pci@0/pci@8/pci@0/pci@8/QLGC,qlc@0
binding-name QLGC,qlc
Not supported by SUN or Qlogic. Do not know effect on Emulex HBAs.
NOTE: Keep in mind that the table may not have been updated yet with any recently release (ie. new) FC HBAs and CNAs Cards. SUN SAN support may need to be engaged to determine if new FC HBAs are SUN branded or not.
- First look at devices that use SUN Qlogic HBA Driver “qlc” and/or SUN Emulex HBA Driver “emlxs” to see if their subsystem-id matches any in table.
- If no matches are found then there are no SUN FC HBAs (see NOTE above) in server therefore any FC HBAs in server are NON-SUN HBA Cards.
- Then check for reference to “fibre-channel” in the device path. It typically means that it is a NON-SUN HBA Cards with no Fcode installed. One exception to this is the SUN-Emulex jumper problem.
- If you see any of the following references they are NON-SUN HBA Cards:
NON-SUN Qlogic:
- qlaxxxx
- QLGC,qla
- QLGC,qlc
- SUNW,qla
NON-SUN Emulex:
- emlx (emlxs is SUN)
- lpfc
- These may or may not be SUN HBA Cards:
- fibre-channel
- JNI
Using prtdiag Command:
For SPARC (not x86) server/Solaris only. If x86 server or none of these commands provide conclusive data on hba then provide Explorer output per instruction at beginning of this document to support engineer for analysis.
Command: prtdiag -v
Then go to “IO Cards” or “IO Devices” section of output. You may be able to see model and/or subsystem-id of hbas then check table for any matches.
Examples:
========================= IO Cards =========================
Bus Max IO Port Bus Freq Bus Dev,Brd Type ID Side Slot MHz Freq Func State Name Model
—- —- —- —- —- —- —- —- —– ——————————– ———————-
I/O PCI 8 B 4 33 33 1,0 ok pci-pci1011,26.5/SUNW,qlc (scsi-+ PCI-BRIDGE
I/O PCI 8 B 4 33 33 4,0 ok SUNW,qlc-pci1077,2200.1077.4083.+ device on pci-bridge
I/O PCI 8 A 1 66 66 1,0 ok SUNW,emlxs-pci10df,fc00/fp (fp) LP10000DC-S
I/O PCI 8 A 1 66 66 1,1 ok SUNW,emlxs-pci10df,fc00/fp (fp) LP10000DC-S
Note: the qlogic HBA shows the subsystem-id (4083, using the above example).
LPxxxxxx-E are usually NON-SUN HBAs resold by EMC.
LPxxxxxx-H are usually NON-SUN HBAs resold by Hitachi.
Below is the HBA Reference table from official Sun support site:
| PART# | Chipset | FRU | Model | SSID | BUS | xGb |
| Emulex HBAs | ||||||
| SG-XPCI1FC-EM2 | Thor | 375-3304 | LP10000-S | fc00 | PCI-X | 1Gb |
| SG-XPCI2FC-EM2 | Thor | 375-3305 | LP10000DC-S | fc00 | PCI-X | 2Gb |
| SG-XPCI1FC-EM4-Z | Helios | 375-3398 | LP11000-S | fc11 | PCI-X | 4GB |
| SG-XPCI2FC-EM4-Z | Helios | 375-3399 | LP11002-S | fc12 | PCI-X | 4GB |
| SG-XPCIE1FC-EM4 | Zephyr | 375-3396 | LPe11000-S | fc21 | PCI-E | 4GB |
| SG-XPCIE2FC-EM4 | Zephyr | 375-3397 | LPe11002-S | fc22 | PCI-E | 4GB |
| SG-XPCIE2FC-EB4-Z | Zephyr | 375-3386 | LPem11002-S | fc2e | PCI-E | 4GB |
| SG-XPCIE20FC-NEM-Z | Zephyr | 375-3385 | LPe11020-S | fc2a | PCI-E | 4GB |
| SG-XPCIE2FC-ATCA-Z | not listed | 371-3264 | LPeA11002-S | fc2d | PCI-E | 4GB |
| SG-XPCIE2FCGBE-E-Z | not listed | 371-4018 | LPem11002E-S | fc23 | PCI-E | 4GB |
| SG-XPCIE1FC-EM8-Z | Saturn | 371-4295 | LPe12000-S | fc41 | PCI-E | 8Gb |
| SG-XPCIE2FC-EM8-Z | Saturn | 371-4306 | LPe12002-S | fc42 | PCI-E | 8Gb |
| SG-XPCIEFCGBE-E8-Z | not listed | 371-4666 | LPem12002E-S | e402 | PCI-E | 8Gb |
| Qlogic HBAs | ||||||
| x6799 | ISP-2200A | 375-3019 | ISP2200 | 4082 | PCI | 1Gb |
| x6727 | ISP-2200A | 375-3030 | ISP2200 | 4083 | PCI | 1GB |
| x6748 | ISP-2200A | 375-0118 | ISP2200 | 4084 | cPCI | 1GB |
| x6757 | ISP-2200A | 375-3048 | ISP2200 | 4085 | Sbus | 1GB |
| SG-XPCI1FC-QF2 | ISP2310 | 375-3102 | ISP2300 | 106 | PCI-X | 2Gb |
| SG-XPCI1FC-QL2 | ISP2312 | 375-3383 | ISP2312 | 149 | PCI-X | 2Gb |
| SG-XPCI2FC-QF2 | ISP2312 | 375-3108 | ISP2312 | 10a | PCI-X | 2Gb |
| SG-XPCI2FC-QF2-Z | ISP2312 | 375-3363 | ISP2312 | 10a | PCI-X | 2GB |
| SG-XPCI1FC-QLC | not listed | 375-3253 | SP212 | 132 | PCI-X | 2GB |
| SG-XPCI1FC-QLC-Z | not listed | 375-3364 | SP212 | 132 | PCI-X | 2GB |
| SG-XPCI1FC-QF4 | ISP2422 | 375-3354 | QLA2460 | 140 | PCI-X | 4GB |
| SG-XPCI2FC-QF4 | ISP2422 | 375-3294 | QLA2462 | 141 | PCI-X | 4GB |
| SG-XPCIE1FC-QF4 | ISP2432 | 375-3355 | QLE2460 | 142 | PCI-E | 4Gb |
| SG-XPCIE2FC-QF4 | ISP2432 | 375-3356 | QLE2462 | 143 | PCI-E | 4Gb |
| SG-XPCIE2FC-QB4-Z | ISP2432 | 375-3384 | QEM2462 | 13d | PCI-E | 4Gb |
| SG-XPCIE2FCGBE-Q-Z | not listed | 371-4017 | QEM3472 | 14b | PCI-E | 4Gb |
| SG-XPCIE1FC-QF8-Z | ISP2532 | 371-4324 | QLE2560 | 170 | PCI-E | 8GB |
| SG-XPCIE2FC-QF8-Z | ISP2532 | 371-4325 | QLE2562 | 171 | PCI-E | 8GB |
| SG-XPCIEFCGBE-Q8-Z | not listed | 371-4522 | QEM3572 | 172 | PCI-E | 8GB |
| JNI HBAs | ||||||
| SG-XPCI1FC-JF2 | not listed | 375-3156 | FCX-6562-L | 656c | PCI-X | 2Gb |
| SG-XPCI2FC-JF2 | not listed | 375-3157 | FCX2-6562-L | 656b | PCI-X | 2Gb |
| FCoE CNAs | ||||||
| SG-XPCIEFCOE2-Q-SR | ISP8112 | 375-3681 | ISP8112 | 183-qlc 184-qlge | PCIe | 10Gb |
| SG-XPCIEFCOE2-Q-TA | ISP8112 | 375-3682 | ISP8112 | 18b-qlc 18c-qlge | PCIe | 10Gb |
| SG-XEMFCOE2-Q-SR | not listed | 375-3684 | QEM8152 | 20d-qlc 20e-qlge | PCIe | 10Gb |
| SG-XEMFCOE2-Q-TA | not listed | 375-3685 | QEM8152 | 20d-qlc 20e-qlge | PCIe | 10Gb |
Note:
- Boot from SAN will not work on SPARC. This is because FCode will not be recognized on SPARC systems. The device path will say “fibre-channel” instead of “SUNW,emlxs.”
- The Solaris Leadville driver will not check the HBA firmware and update it if there is a mis-match between what is on the board and what is in the driver. However, firmware can be updated manually.







7 Comments on “Storage : Identify Sun Fibre Channel (FC) HBA”
HI,
I am new to SAN …I m trying to install navisphere simulation P1 on windows 7 by running it in windows xp service pack 2 compatibility mode…all my currecnt java versions are uninstalled but I am facing issue while installing as there is no processing at installation step i,e the installer screen keeps showing installing but nothin is happening even after leaving it like this for 2 hours..can u help in this regard?
Thanks in Advance
Rajat
Rajat, It is a very old simulator and is fully supported on XP, but it also work on windows 7. You have to run it as adminstrator, is it throwing any errors as if its missing some files? if so you have load them manually and try installing simulator
HI Ravi,
It is not showing any errors, the problem is when we run the installation there is nothing happening at the installation step ,the screen freezes there and nothin happens .I left my system like that and nothin happend . I have download e new simulator will try installing that. Apart from that what all is required if I need to prepare for an interview I have just bought a book with the name Information & Storage Management by EMC. I have a prior experience in Unix Application support and administration.
Just a quick comment – first, that with Solaris that Qlogic works a lot better than Emulex. In fact when I first started in SAN about 2007 our main Oracle was on Solaris SPARC with sun storage and we were getting “blips” that was shutting down our system. After a call to SUN confirmed Emulex was not preferred and they were constantly having problems followed up with a recommendation to use QLogic, replacing with QLogic did the trick
That being said .. .QLogic seems to spend a lot of time on driver and management – the command line SCLI is awesome and amazing and they have it for linux and solaris.
I definitely like the methods you mention above since it will work for all HBAs, but if you have QLogic, I highly recommend downloading and installing their SCLI (command line utility)
Here’s a screenshot of the linux version of the SCLI
http://geekswing.com/wp-content/uploads/2013/03/qlogic-sansurfer-scli-screenshot.jpg
Thanks for the awesome post!
Hi Ben, Thanks for the nice point.
Scli / Qlogic branded driver can not recognize a new target (say you are adding a new fiber connection ) and needs reboot and it does not support cfgadm utility; that is why we switched all scli QLA**** drivers to sun native leadville driver (SUNWqlc).
Hi Kevin, Thanks for the information.