Hba

3/3/2014
Document 1303745.1
Muhammed
PowerView is Off
Dashboard
Knowledge
Service Requests
Patches & Updates
(0)
Contact Us
Search Knowledge Base
Troubleshooting Solaris[TM](not for Solaris[TM] 8 & 9) SAN Fibre Channel (FC) HBA connectivity issues. (Doc ID
1303745.1)
Modified: 31-Jan-2014
Help
Advanced
To Bottom
Type: TROUBLESHOOTING
In this Document
Purpose
Troubleshooting Steps
References
APPLIES TO:
Sun Storage FC HBA - Version Not Applicable to Not Applicable [Release N/A]
Qlogic FC HBA - Version All Versions to All Versions [Release All Releases]
Emulex FC HBA - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
PURPOSE
This document will outline steps to help isolate FC HBA connectivity issues as much as possible from the server side.
Looking at and troubleshooting from the FC Switches and Storage Arrays sides may also be needed to isolate the issue.
As well as, customer onsite presents to quickly do initial basic testing to help determine if issue is with a Oracle or a NON-Oracle component.
This can greatly help to resolve issue faster by focusing on correct area and getting the appropriate Oracle or NON-Oracle support involved to assist if needed.
Note: Steps apply to Oracle or NON-Oracle FC HBA card that are using Oracle FC HBA Drivers. But NON-Oracle FC HBA will not be replaced by Oracle if needed,
see doc below.
How to identify Oracle Fibre Channel (FC) HBA and CNA Cards and Their Slot Locations (Doc ID 1282491.1)
Issue
Generally, Fibre Channel (FC) HBA connectivity issues fall into one of three areas from the server perspective:
1 - Issue with a specific FC HBA port/path/card
2 - Issue with two or more FC HBA ports/paths/cards
3 - Not sure where issue is or something other than 1 and 2 above
The testing and isolation steps in this document will primarily help with items 1 and 2 above.
For item 3 above see following docs:
Fibre Channel (FC) Server-Based Connectivity Issues - Basic information and data needed by Oracle support (Doc ID 1449557.1)
Fibre Channel (FC) Switch-Based Connectivity Issues - Basic information and data needed by Oracle support (Doc ID 1450759.1)
Fibre Channel (FC) Disk Storage Array Based Connectivity Issues - Basic information and data needed by Oracle support (Doc ID 1462587.1)
Fibre Channel (FC) Tape Storage Drive/Library Based Connectivity Issues - Basic information and data needed by Oracle support (Doc ID 1462900.1)
Storage Configuration
Between FC HBA and FC Storage Device there usually (but not always) is one or more FC Switch(es) this is referred to as a Fabric Attached Storage (FAS)
configuration, also known as Storage Area Network (SAN).
In a Direct Attached Storage (DAS) configuration there is no FC Switch between the FC HBA and FC Storage Device.
Troubleshooting steps will vary depending on the type of configuration.
Known vs Suspect Issue
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=225238773481169&id=1303745.1&displayIndex=12&_afrWindowMode=0&_adf.ctrl-state=ie
1/7
3/3/2014
Known vs Suspect Issue
Document 1303745.1
Issues such as a FC HBA port being listed in a offline state or in not connected status maybe normal if there is no cable inserted into the port or the appropriate
administration has not been done on the server, fc switch and storage sides for fc hba port to see storage.
Checking previous explorer outputs and other data can help determine if there is a real issue or not.
Note: Fibre Channel HBA cards/ports have to see light before the port will emit light, so not seeing light from a fc hba ports is not a indication of a issue.
Note: Network Interface Cards (NIC) with Fibre Channel Interfaces can be mistaken for actual FC HBA cards.
NON-Oracle Solaris Commands
Any outputs from NON-Oracle Solaris commands, such as, EMC PowerPath Multipathing software commands will need to interpreted by customer to correlate to
Oracle Solaris commands outputs.
TROUBLESHOOTING STEPS
See sections below for troubleshooting steps:

FC HBA port in Offline state
FC HBA port in Not Connected status
FC HBA port bouncing/flapping offline/online
==========================
FC HBA port in Offline state
==========================
fcinfo is the Oracle Solaris (10 and above only) command used to check fc hba port state.
Enter following command to list the ports and their current state:
fcinfo hba-port
Run command a few times over a period of time to check if ports is changing state (ie bouncing/flapping).
Steps:
#1 Check FC HBA using FC Loopback Plug/FC Loopback Cable
- see doc
Using Solaris Fibre Channel (FC) Loopback Plug or Private Loop Cable to Test FC HBA Port That Is In a Offline State (Doc ID 1610207.1)
- if unable to use Doc ID 1610207.1 or you were able to isolate issue to something outside the server/hba then proceed to steps below.
#2 Check interconnecting components
- check/reseat cables, patch panel, splices, etc. between the fc hba port and the FC Switch port or FC Storage Device.
see doc
Checking Interconnecting Elements (IEs) in a SAN/Fibre Channel (FC) path (Doc ID 1400156.1)
- check for any change
#3 Check from FC Switch or FC Storage side
Fabric Attached Storage (FAS) configuration
- move switch end of cable to another port on the fc switch that has its own SFP module inserted in port, if available.
- otherwise, swap sfp in the fc switch port with a spare sfp if you have one onsite already.
- check for any change.
Note: In step below verify which fc switch port the hba is connected to first.
- log onto the FC Switch and reset (disable/enable) the fc switch port that the fc hba is connected to.
- check for any indications (like error logs) of defective sfp/port, is fc hba wwpn logging onto the port, etc.
2/7
3/3/2014
Document 1303745.1
Note: FC HBA port wwpn is listed in "fcinfo hba-port" command output.

Direct Attached Storage (DAS) configuration
- check storage device side for any errors logged.
- reset storage device side port.
If "fcinfo hba-port" command still list fc hba port as offline open a Oracle Service Request (SR) and provide information per doc:
==========================
FC HBA port in Not Connected status
==========================
Note: See "FC HBA port in Offline state" before checking fc hba port status.
The procedure below assumes the fc hba port is in a online state.
To correlate fc hba port path to assigned controller number run following command:
ls -l /dev/cfg
luxadm is the Oracle Solaris command used to check fc hba port status.
Enter following command to list the ports and their current status:
luxadm -e port
Note: See "CONNECTED vs NOT CONNECTED" section below for explanation of differences.
Steps below will help determine why fc hba port is listed as "NOT CONNECTED".
Step #1 Determine if hba port sees any target wwpn
Run following command:
"#" = port controller number digit of hba that has issue, ie c# for example "c1".
cfgadm -al c# | grep "::"
Example:
# cfgadm -al c1 | grep ::
c1::21000xxxxxxxxx72 disk connected configured unknown
c1::21000xxxxxxxxx6e disk connected configured unknown
#
21000xxxxxxxxx72 & 21000xxxxxxxxx6e are target wwpn's
If nothing is returned by command then no target wwpn's are being seen.
If hba port DOES NOT see any target wwpn:
Go to one of following Steps based on configuration.
Step #3 Fabric Attached Storage (FAS) configuration
Step #4 Direct Attached Storage (DAS) configuration
3/7
3/3/2014
Document 1303745.1
If hba port can see target wwpn then go to "Step #2 Verify data LUN mapped to target wwpn" below.
Step #2 Verify data LUN mapped to target wwpn

Some storage devices will only be listed as CONNECTED if a valid data LUN is seen by driver.
Verify you have mapped a data (not management) LUN to the target wwpn seen by this hba port:
If no LUN mapped yet, map a data LUN to target then "check for change".
If already mapped a data LUN to target:
- verify LUN configuration/mapping and permissions on storage side
- compare to working connection, if available
- if still have issue open a Oracle Service Request (SR) and provide information per doc:
Fabric Attached Storage (FAS) configuration

Step #3 Troubleshoot why not seeing any target wwpn
Log onto FC switch verify/fix the following:
a. Disable/enable (bounce) port fc hba is logging onto and verify hba wwpn is seen on switch port and name server.
- if hba wwpn is not seen logging onto the switch port then run "fcinfo hba-port' command again.
- if fcinfo command still list the fc hba port as online then the transmit & receive strangs of FC cable may have been crossed resulting in it listing as online when
in fact it has not logged into anything.
b. Storage target(s) wwpn are logging onto same physical switch or another switch in same fabric as well.
c. Storage target(s) wwpn have valid data (not management) LUNs mapped to them with proper permissions to be seen by hba wwpn.
d. The hba wwpn is part of a zone which includes storage target(s) wwpn.
e. The zone is active, in effective/live zoning configuration.
f. Switch port type for HBA and Target should be F port.
g. Port speed should be same either fixed or auto-negotiate.
h. Disable/enable (bounce) storage (only if NO other hbas access that target wwpn) port.
i. Verify hba and switch ports settings are compatible by checking with any working hba port, if available.
Recheck if hba is seeing any target wwpn by running following command:
If still not seeing target wwpn in cfgadm, then open a Oracle Service Request (SR) and provide information per doc:
Direct Attached Storage (DAS) configuration

Step #4 Troubleshoot why not seeing any target wwpn
Log onto FC Storage verify/fix the following:
a. Operating properly and without any errors.
b. Disable/enable (bounce) port fc hba is logging onto and verify hba wwpn is seen logging onto the storage (if possible).
- if hba wwpn is not seen logging onto the switch port then run "fcinfo hba-port' command again.
- if fcinfo command still list the fc hba port as online then the transmit & receive strands of FC cable may have been crossed resulting in it listing as online when
in fact it has not logged into anything.
c. Storage target(s) wwpn have valid data (not management) LUNs mapped to them with proper permissions to be seen by hba wwpn.
Recheck if hba is seeing any target wwpn by running following command:
4/7
3/3/2014
Document 1303745.1

If still not seeing target wwpn in cfgadm, then open a Oracle Service Request (SR) and provide information per doc:
=========================
FC HBA port bouncing/flapping offline/online
=========================
Normally this is seen in /var/adm/message file entries.
Examples:
Qlogic HBA
Dec
Dec
Dec
Dec
7 02:30:12 Test Host qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(0): Link ONLINE
7 03:54:01 Test Host qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(0): Link OFFLINE
7 03:54:47 Test Host qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(0): Link ONLINE
7 03:55:41 Test Host qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(0): Link OFFLINE
May 31 10:48:55 Test Host qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(3): Loop OFFLINE
May 31 10:49:05 Test Host fctl: [ID 517869 kern.warning] WARNING: fp(2)::OFFLINE timeout
Emulex HBA
Mar 3 04:05:40 myhost emlxs: [ID 349649 kern.info] [ 5.05F8]emlxs0: NOTICE: 730: Link reset.
Mar 3 04:05:40 myhost emlxs: [ID 349649 kern.info] [ 5.0337]emlxs0: NOTICE: 710: Link down.
Mar 3 04:05:41 myhost emlxs: [ID 349649 kern.info] [ 5.054D]emlxs0: NOTICE: 720: Link up.
Step #1 First check for known issues, see docs below:

QLogic FC HBA link bouncing online and offline at 45-47 second intervals (Doc ID 1487742.1)
Non Oracle EMC software product "EMC Solution Enabler" causing Oracle Qlogic Link OFFLINE/ONLINE messages (Doc ID 1540637.1)
Go to one of following Steps based on configuration.

a. Move FC Switch end of cable coming from fc hba port to another FC Switch port (assuming soft/wwn zoning being used) that has it own SFP. This will eliminate
the original FC Switch sfp/port.
b If offline/online messages stop then issue was with original FC Switch port/sfp. Contact FC Switch (Oracle or NON-Oracle) support vendor to check/replace FC
Switch port/sfp.
If offline/online messages continue then check/swap/replace cable(s), patch panels, splices between the FC HBA port and the FC Switch port.
If offline/online messages continue, then open a Oracle Service Request (SR) and provide information per doc:
5/7
3/3/2014
Document 1303745.1
Check/swap/replace cable(s), patch panels, splices between the FC HBA port and the FC Storage Device port.
If offline/online messages continue, then open a Oracle Service Request (SR) and provide information per doc:
=========================
CONNECTED vs NOT CONNECTED
=========================
A CONNECTED status in luxadm means the HBA has established communication with at least one other node. This is typically a target device (disk, tape, etc.), but
could even be another initiator, ie. FC HBA (if switch zoning best practices have NOT been followed). When connecting to targets through a FC Switch, it is NOT
necessary to have any LUNs visible on the target to get a CONNECTED status (there could be no LUNs mapped, or all mapped LUNs could be masked (ie.
permissions) away). All that is required is visibility to the target.
A CONNECTED status does prove that you are seeing something out on the fabric.
A NOT CONNECTED status only proves that the Oracle FC HBA driver cannot see any devices. It does not prove that you are not physically attached to anything.
When cabled to FC Switch (ie establishing fabric login to a FC Switch ) it will not change to CONNECTED since the switch is not a node (N_Port) on the fabric. So
keep in mind that it is possible to be physically connected to a FC Switch, but see a NOT CONNECTED status from luxadm -e port. Being physically connected
to a FC Switch can help us troubleshoot issue faster so it is important to know what the HBA is cabled to.
The presence of a visible LUN on the target is not necessary to be in a CONNECTED status when cabled through a SAN (FC Switch) , but may be needed with
Direct-Attached (no FC Switch) Storage (DAS). When in direct attach configuration, you may have to have at least one visible LUN on the target to get a
CONNECTED status depending on the storage type. Hitachi Storage Arrays (HDS) with lun security enabled is one example that can display a NOT CONNECTED
status in direct attach.
luxadm -e port
= port status
fcinfo hba-port = port state
"CONNECTED" or "NOT CONNECTED"

"Online" or "Offline"
=========================
FC HBA card port layout
=========================
If dual port FC HBA card then ports on the card would be label as followed:
Oracle Qlogic FC HBA - First port = 1 and Second port = 2
Oracle Emulex FC HBA - First port = 0 and Second port = 1
Oracle JNI FC HBA - First port = A and Second port = B
Fibre Channel SAN Online Community

Questions can be posted to Oracle customer SAN community as well.
Note: Do not post any command output showing system specific information.
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/Tape Storage Area Networks (SAN)
Related
Products
Sun Microsystems > Boards > Fibre Channel (FC) > Sun Storage FC HBA > Connectivity
Sun Microsystems > Boards > Fibre Channel (FC) > Qlogic FC HBA > Connectivity
Sun Microsystems > Boards > Fibre Channel (FC) > Emulex FC HBA > Connectivity
6/7
3/3/2014
Document 1303745.1
Sun Microsystems > Boards > Fibre Channel (FC) > Emulex FC HBA > Connectivity
Keywords
CARDS; CHANNEL; CONNECTIVITY; FCINFO; FIBRE CHANNEL; OFFLINE; PORT ISSUE; STORAGE; TROUBLESHOOT
Back to Top
Copy right (c) 2014, Oracle. A ll rights reserv ed.
Legal Notices and Terms of Use
Priv acy Statement
7/7

Hba

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Hba

Загружено:

Авторское право:

Доступные форматы

3/3/2014

Patches & Updates

Search Knowledge Base

Known vs Suspect Issue

See sections below for troubleshooting steps:

Note: FC HBA port wwpn is listed in "fcinfo hba-port" command output.

Step #2 Verify data LUN mapped to target wwpn

Fabric Attached Storage (FAS) configuration

Direct Attached Storage (DAS) configuration

cfgadm -al c# | grep "::"

Step #1 First check for known issues, see docs below:

Step #2 Fabric Attached Storage (FAS) configuration

Step #3 Direct Attached Storage (DAS) configuration

fcinfo hba-port = port state

"CONNECTED" or "NOT CONNECTED"

Fibre Channel SAN Online Community

Legal Notices and Terms of Use

Priv acy Statement

Вам также может понравиться