HBA2

3/3/2014
Document 1282491.1
Muhammed
PowerView is Off
Dashboard
Knowledge
Service Requests
Patches & Updates
(0)
Contact Us
Search Knowledge Base
Advanced
How to Identify Oracle[TM] Branded Fibre Channel (FC) HBA and CNA Cards and Their Slot Locations (Doc ID
1282491.1)
Modified: 18-Sep-2013
Type: HOWTO
Language:
Help
To Bottom
English
In this Document
Goal
Solution
References
APPLIES TO:
Sun Storage FCoE CNA - Version Not Applicable and later
Sun Storage FC HBA - Version Not Applicable and later
Information in this document applies to any platform.
GOAL
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support
Community - Disk/TapeStorage Area Networks
Part I:
How to identify Oracle[TM] Branded Fibre Channel (FC) HBA and CNA Cards:
Host Bus Adapter (HBA)
Converged Network Adapter (CNA)
NOTE: The term "HBA" or "FC HBA" in this document will refer to all card types above.
Part II:
How to correlate the HBA device path to a physical slot or location on the server.
For information on Oracle FC HBA Boot Code (Fcode/BIOS), Driver and Firmware see FAQ Oracle FC HBA:
FCode/BIOS(ie. Boot Code), Firmware, and Drivers (Doc ID 1389639.1)
NOTE: Help to improve this document and knowledge base by selecting "Comments" and/or "Rate this document".
SOLUTION
Part I:
REFERENCE: Please see the attached HBA table - link at the bottom of this page
Assuming the FC HBA cards are not down and will respond to Solaris commands the following steps will help in identifying if Oracle Branded or not.
See "Exceptions" section below for BUGs, etc. that may interfere with proper identification of HBAs.
Assuming there is not a mixture of Oracle and NON-Oracle 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 Oracle Branded or not.
If there is only one FC HBA card in server and it is down then look at previous Explorer output (if available) and/or provide Explorer output(s) from server for
current support SR for analysis.
SAN: How To Collect and Send Explorer Data to Oracle SAN Support (Doc ID 1273941.1)
Oracle only support Oracle HBA Drivers and FC HBA Cards. If NON-Oracle FC HBA Card needs to be replaced contact your NON-Oracle FC HBA support vendor.
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=225307192574284&id=1282491.1&_afrWindowMode=0&_adf.ctrl-state=iewgz1mh6_210
1/8
3/3/2014
Document 1282491.1
These steps only apply to:

Fibre channel (FC-AL and Point-to-Point) HBAs Cards:
- Single or Dual port FC only ports
OR
Ethernet/IP and FC HBA Combo Cards:
- 2 Ethernet ports and 2 FC ports
OR
CEE/FCoE CNAs (Converged Network Adapters) Cards:
- 2 FCoE ports (Fibre Channel over Ethernet)
These steps DO NOT apply to:

Ethernet/IP Network Interface Cards (NIC) using optical interface:
- 1 or 2 port with Ethernet over FC
OR
SCSI or SAS or InfiniBand Adapters
Special Case:
These steps may or may not apply to:
Embedded FC HBA Application-Specific Integrated Circuit (ASIC) on Mother/System Boards or other products/components.
Use commands and table below to help determine Oracle or NON-Oracle FC HBA Cards.
Due to variety of hardware and software the steps below are not 100% guaranteed to identify Oracle versus NON-Oracle FC HBA Cards. If results are inconclusive
then ask in SAN Forum, otherwise provide a explorer output to Oracle SAN support engineer for analysis.
Topics
Using fcinfo Command:
Using prtpicl Command:
Using prtdiag Command:
HBA Table
Using fcinfo Command:

For Solaris 10 Update 1 or higher.
Command:
fcinfo hba-port
For Solaris 8 & 9 or Solaris 10 before Update 1 or if fcinfo command does not work for some reason go to "prtpicl Command:"
Check "Model:" field in conjunction with "Manufacturer:" field.
LPxxxxxx-S are Oracle Emulex HBA Cards (ie has a "-S" for Sun at end).
LPxxxxxx-E are NON-Oracle HBAs usually resold by EMC.
LPxxxxxx-H are NON-Oracle HBAs usually resold by Hitachi.
LPxxxxxx-M are NON-Oracle HBAs usually resold by <unknown>
375-xxxx-xx are Oracle Qlogic HBA Cards.
QLAxxxx may or may not be Oracle Qlogic HBA Cards so you would need to use "prtpicl Command:" to determine.
Model: 2200 with Manufacturer: QLogic Corp is a old Oracle Fibre Channel Arbitrated Loop (FC-AL) HBA Cards.
Legacy discontinued JNI FC HBAs with jfca Driver are Oracle HBA cards but other JNI cards may also be listed and would require Oracle SAN engineer analysis of
explorer output to determine if it Oracle branded or not.
Example:
# fcinfo hba-port
HBA Port WWN: 23000800xxxxxxx
OS Device Name: /dev/cfg/c1
Manufacturer: QLogic Corp.
2/8
3/3/2014
Document 1282491.1

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: 22000800xxxxxxx
HBA Port WWN: 10000000cxxxxxxx
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: 20000000cxxxxxxx
HBA Port WWN: 10000000cxxxxxxx
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: 20000000cxxxxxxx
HBA Port WWN: 210100e08xxxxxxx
Model: 375-3030-xx
FCode/BIOS Version: fcode: 1.13;
Driver Name: qlc
Type: L-port
State: online
Current Speed: 1Gb
Node WWN: 200100e08xxxxxxx
HBA Port WWN: 210000e08xxxxxxx
Model: 375-3030-xx
FCode/BIOS Version: fcode: 1.13;
Driver Name: qlc
Type: unknown
State: offline
Current Speed: not established
Node WWN: 200000e08xxxxxxx
#
Using prtpicl Command:

If prtpicl command not available or does not work for some reason then go to "prtdiag Command:".
Command:
# prtpicl -v | egrep "subsystem-id|model|devfs-path|driver-name|binding-name" | awk '/subsystem-id/,/binding-name/' | sed '/subsystemid/{x;p;x;}' | nawk -F: '{ print $2 }'
Since some old FC HBA cards may not list their "subsystem-id" you need to also run following command:
3/8
3/3/2014
Document 1282491.1
Since some old FC HBA cards may not list their "subsystem-id" you need to also run following command:
# prtpicl -v | egrep -i "qla|lpfc"
# prtpicl -v | grep -i fibre-channel
Each listing is a hba port, you then use following command to see paths
# prtpicl -v | grep -i devfs-path | grep -i fibre-channel | grep -v sd | nawk -F: '{ print $2 }'
Then compare to fibre-channel devfs-paths from above to see if any difference.
See examples below.
Note: Make sure entire command string is entered

Example:
# prtpicl -v | egrep "subsystem-id|model|devfs-path|driver-name|binding-name" | awk '/subsystem-id/,/binding-name/' | sed
'/subsystem-id/{x;p;x;}' | nawk -F: '{ print $2 }'
subsystem-id
0x13a1
model
LSI,1064
devfs-path
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1
driver-name
mpt
binding-name
pci1000,50
subsystem-id
devfs-path
driver-name
binding-name
0x1648
/pci@0,600000/pci@0/pci@8/pci@0/network@2
bge
pci14e4,1648
subsystem-id
devfs-path
driver-name
binding-name
0x1648
/pci@0,600000/pci@0/pci@8/pci@0/network@2,1
bge
pci14e4,1648
subsystem-id
0xfe00
model
LPe11000-M4
devfs-path
/pci@0,600000/pci@0/pci@9/fibre-channel@0
driver-name
emlxs
binding-name
pciex10df,fe00
subsystem-id
0x125e
model
SUNW,pcie-northstar
board-model
501-7289
devfs-path
/pci@1,700000/network@0
driver-name
e1000g
binding-name
pciex8086,105e
subsystem-id
0x125e
model
SUNW,pcie-northstar
board-model
501-7289
devfs-path
/pci@1,700000/network@0,1
driver-name
e1000g
binding-name
pciex8086,105e
subsystem-id
0xfe00
model
LPe11000-M4
devfs-path
/pci@2,600000/fibre-channel@0
driver-name
emlxs
binding-name
pciex10df,fe00
subsystem-id
0x13a1
model
LSI,1064
devfs-path
/pci@10,600000/pci@0/pci@8/pci@0/scsi@1
driver-name
mpt
binding-name
pci1000,50
subsystem-id
devfs-path
driver-name
binding-name
0x1648
/pci@10,600000/pci@0/pci@8/pci@0/network@2
bge
pci14e4,1648
subsystem-id
devfs-path
driver-name
binding-name
$
0x1648
/pci@10,600000/pci@0/pci@8/pci@0/network@2,1
bge
pci14e4,1648
This list will include FC HBAs, as well as, other components.
4/8
3/3/2014
Document 1282491.1
Check table below under SSID column.

NOTE: On rare occusion the following manufacturing defect can be encountered causing certain Oracle Branded Emulex FC HBA to appear to be NON-Oracle
Emulex FC HBAs. See defect doc id and further details below:
Procedure for identifying and removing unwanted header jumpers on Sun StorageTek Pyramid and Summit Host Bus Adapters.(Doc ID 1019152.1)
Conflicting information is presented by the system.
When using prtpicl command we see Oracle Emulex FC HBA Driver emlxs used but device has "fibre-channel" in path and model is sometimes not seen.
Example:
subsystem-id
devfs-path
driver-name
binding-name
0xfe00
/pci@0/pci@0/pci@8/fibre-channel
emlxs
pciex10df,fe00
subsystem-id
0xfe00
model
LPem11002-S
devfs-path
/pci@0/pci@0/pci@8/fibre-channel@0,1
driver-name
emlxs
binding-name
pciex10df,fe00
Also
Message may list "Emulex-S" and "LPem11002-S" name for same device.
$ grep -h "Driver attach" /var/adm/mess* | grep "\-S"
Dec 13 05:39:05 Test-Server emlxs: [ID 349649 kern.info] [ B.175F]emlxs3: NOTICE: 100: Driver attach. (Emulex-S s10-64 sparc v2.50o
(2010.01.08.09.45 ))
Dec 13 05:39:05 Test-Server emlxs: [ID 349649 kern.info] [ B.1762]emlxs3: NOTICE: 100: Driver attach. (LPem11002-S Dev_id:fc20
Sub_id:fc2e Id:31)
(2010.01.08.09.45 ))
Sub_id:fc2e Id:31)
(2010.01.08.09.45 ))
Sub_id:fc2e Id:31)
(2010.01.08.09.45 ))
Sub_id:fc2e Id:31)
$
$
Also
Message may list Fcode found on hbas as "none"
$
$ grep Fcode: /var/adm/mess*
messages:Dec 13 05:39:05 Test-Server emlxs: [ID 349649 kern.info] [ B.176F]emlxs3: NOTICE: 100: Driver attach. (Firmware:2.82a4
(Z3F2.82A4) Boot:5.02a1 Fcode:none)
messages.0:Dec 4 17:59:18 Test-Server emlxs: [ID 349649 kern.info] [ B.176F]emlxs3: NOTICE: 100: Driver attach. (Firmware:2.82a4
$
Example:
$ prtpicl -v | grep -i fibre-channel | grep -v
fibre-channel (obp-device, 4b300000160e)
fibre-channel (obp-device, 4b30000016be)
fibre-channel (obp-device, 4b3000001ca2)
fibre-channel (obp-device, 4b3000001d52)
$
5/8
3/3/2014
Document 1282491.1
Each listing is a hba port, you then use following command to see paths
$ prtpicl -v | grep -i devfs-path | grep -i fibre-channel
Example:
$ prtpicl -v | grep -i devfs-path | grep -i fibre-channel | grep -v sd | nawk -F: '{ print $2 }
devfs-path
devfs-path
devfs-path
devfs-path
$
Windriver
NOTE: If WinDriver 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.
Not supported by Oracle or Qlogic.
Do not know effect on Emulex HBAs.
http://www.jungo.com/st/windriver_usb_pci_driver_development_software.html
http://www.jungo.com/st/wd-solaris.html
WinDriver for Solaris automates and simplifies the development of user-mode Solaris device drivers for PCI / CardBus / ISA / ISAPnP / EISA / PMC / PCI-X / PCI104 and CompactPCI. No OS internals knowledge or kernel level programming required.
One source of this Windriver is Veritas (symantec) Netbackup software product. See technote below referencing referencing the prepending of a digit "8" to SSID
and user guide below:
http://www.symantec.com/business/support/index?page=content&id=TECH70313
And here is the guide that describes what the driver is for and how to install it. Not sure if this is the latest version, but the relevent details appear to starts around
page 30.
http://www.symantec.com/business/support/index?page=content&id=TECH127068
To determine if Windriver is installed:
$ grep -i windrv /var/sadm/install/contents
/opt/openv/netbackup/bin/driver/windrvr6.5.9 f NBclass 0544 root bin 289904 57605 1185226200 SYMCnetbp
/opt/openv/netbackup/bin/driver/windrvr6.conf f NBclass 0444 root bin 190 16083 1185226200 SYMCnetbp
$
To determine if Windriver is currently running:

$ modinfo | egrep -i "windrvr6|Jungo|WinDriver|WDsolarisAttach"
and/or
$ cd /var/adm
$ egrep -h -i "windrvr6|Jungo|WinDriver|WDsolarisAttach" mess* > windrv
$ more windrv
Even if Windriver is not currently running, if it was run before it may have already prepended a digit "8" to a HBA SSID which remain even if Windriver is removed.
Example:
Oracle Qlogic HBA where Windriver prepended a digit "8" to SSID and changing fcode driver strings which alter the device path to QLGC,qlc
subsystem-id
devfs-path
driver-name
binding-name
0x143
/pci@0/pci@0/pci@8/pci@0/pci@8/SUNW,qlc@0
qlc
pciex1077,143
changed to
subsystem-id
devfs-path
binding-name
0x8143
/pci@0/pci@0/pci@8/pci@0/pci@8/QLGC,qlc@0
QLGC,qlc
Use following command string to gather SSID of components(hbas and others) on your Solaris server:
6/8
3/3/2014
Document 1282491.1
$ prtpicl -v | egrep "devfs-path|driver-name|subsystem-id" | nawk '/:subsystem-id/ { print $0; getline; print $0; getline; print $0; }' | nawk F: '{ print $2 }'
To uninstall the Windriver from Netbackup use following command which will require a reboot of server as well:
# nbftsrv_config -d
Verify Windriver not being used before removing it
NOTE: Keep in mind that the table may not have been updated yet with any recently release (ie. new) FC HBAs and CNAs Cards. Oracle SAN support may need
to be engaged to determine if new FC HBAs are Oracle branded or not.
- First look at devices that use Oracle Qlogic HBA Driver "qlc" and/or Oracle Emulex HBA Driver "emlxs" to see if their subsystem-id matches any in table.
- If no matches are found then there are no Oracle FC HBAs (see NOTE above) in server therefore any FC HBAs in server are NON-Oracle HBA Cards.
- Then check for reference to "fibre-channel" in the device path. It typically means that it is a NON-Oracle HBA Cards with no Fcode installed. One exception to this
is the Oracle-Emulex jumper problem. See following document for details:
Procedure for identifying and removing unwanted header jumpers on Sun StorageTek Pyramid and Summit Host Bus Adapters.(Doc ID 1019152.1)
If you see any of the following references they are NON-Oracle HBA Cards:
NON-Oracle Qlogic:
qlaxxxx
QLGC,qla
QLGC,qlc
SUNW,qla
NON-Oracle Emulex:
emlx (emlxs is Oracle)
lpfc
These may or may not be Oracle 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 | more (multi-page output)
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-S are Oracle Emulex HBA Cards (ie has a "-S" for Sun at end).
LPxxxxxx-E are NON-Oracle HBAs usually resold by EMC.
LPxxxxxx-H are NON-Oracle HBAs usually resold by Hitachi.
LPxxxxxx-M are NON-Oracle HBAs usually resold by <unknown>
You can also check following Qlogic web site document for SSIDs of NON-Oracle and some Oracle FC HBAs:
7/8
3/3/2014
Document 1282491.1
Identifing Whether QLogic or SUN HBA is Installed in a Solaris Server

Exception:
NOTE: See Windriver section above as well.
Procedure for identifying and removing unwanted header jumpers on Sun StorageTek Pyramid and Summit Host Bus Adapters.
Impact
The HBA's PCI Device and Subsystem Device IDs will be that of the standard Emulex HBA rather than the Sun unique IDs. Drivers will attach and I/O can be run.
However, the following Sun product features will not work;
. 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.
Part II:
Determining hba card slot location in a server:
Here are some resourses:
Solaris[TM] Operating System: Matrix of Recognized Device Paths (Doc ID 1005907.1)

x64 and x86 Platforms: Matrix of Recognized Device Paths (Doc ID 1277396.1)
Sun SPARC[TM] Enterprise M4000 and M5000 Server Device Paths (Doc ID 1002807.1)
Physical device mapping for PCI-X I/O Boards (Sun Fire[TM] 4800, E4900, 6800, E6900) and PCI-X IB_SSC (Sun Fire[TM] v1280, E2900 and Sun Netra[TM]
1280, 1290). (Doc ID 1003932.1)
Verifying the HBA controller path on V210/V240/V215/V245/V440/V445, T1000/T2000, T5120/T5140/T5220/T5240/T5440, V480/V490/V880/V890 servers
[Video] (Doc ID 1005523.1)
Sun SPARC Enterprise M4000/M5000/M8000/M9000 Servers : Logical System Board (LSB) (Doc ID 1011446.1)
Sun SPARC(R) Enterprise M8000 and M9000 Device Paths (Doc ID 1004116.1)
Sun Enterprise[TM] 10000: Decoding Component Numbering (Doc ID 1005429.1)
Use following command on explorer outputs

# cd <explo>/sysc*
# pwd
# egrep "subsystem-id|port-wwn|model|devfs-path|driver-name|binding-name" prtpicl-v.out | awk '/subsystem-id/,/binding-name/'|sed '/subsystem-id/{x;p;x;}' |
nawk -F: '{ print $2 }'
# egrep -i "qla|lpfc" prtpicl-v.out
# grep -i fibre-channel prtpicl-v.out
# grep -i devfs-path prtpicl-v.out | grep -i fibre-channel | grep -v sd | nawk -F: '{ print $2 }'
Attachments
HBA_Table_16_Aug_2013 (56.93 KB)
Related
Products
Sun Microsystems > Boards > Fibre Channel (FC) > Sun Storage FCoE CNA > Hardware
Sun Microsystems > Boards > Fibre Channel (FC) > Sun Storage FC HBA > Hardware
Keywords
ADAPTER; JNI; SOLARIS; STORAGE
Translations
English Source
Japanese
Back to Top
Copy right (c) 2014, Oracle. A ll rights reserv ed.
Legal Notices and Terms of Use
Priv acy Statement
8/8

HBA2

Uploaded by

Copyright:

Available Formats

You might also like

HBA2

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HBA2

Uploaded by

Copyright:

Available Formats

3/3/2014

Patches & Updates

Search Knowledge Base

These steps only apply to:

These steps DO NOT apply to:

Using fcinfo Command:

Manufacturer: QLogic Corp.

Using prtpicl Command:

Note: Make sure entire command string is entered

This list will include FC HBAs, as well as, other components.

Check table below under SSID column.

To determine if Windriver is currently running:

========================= IO Cards =========================

Identifing Whether QLogic or SUN HBA is Installed in a Solaris Server

Solaris[TM] Operating System: Matrix of Recognized Device Paths (Doc ID 1005907.1)

Use following command on explorer outputs

Legal Notices and Terms of Use

Priv acy Statement

You might also like