Solaris Fibre Channel (FC) HBA card and Protocol dump/buffer/trace debug data collection

(Doc ID 2012564.1)

Last updated on JULY 29, 2016

Applies to:

Solaris Operating System - Version 8 6/00 U1 to 11.1 [Release 8.0 to 11.0]
Sun Storage FC HBA - Version All Versions to All Versions [Release All Releases]
Qlogic FC HBA - Version All Versions to All Versions [Release All Releases]
Emulex FC HBA - Version All Versions to All Versions [Release All Releases]
Sun Storage FCoE CNA - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

 How to collect Solaris Fibre Channel (FC) HBA card and Protocol dump/buffer/trace debug data.

If FC HBA extended debug logging was not already enabled when a issue occurred then Oracle Fibre channel (FC) HBA card dump/buffer data MAY contain relevant messages that can aid troubleshooting FC connectivity issues.

NOTE: For procedure to enable FC HBA extended debug logging see "Related Knowledge Base Documents" listed at end of this document.

 

The Oracle Solaris Fibre Channel (FC) HBA card and Protocol dump/buffer/trace debug data only contain FC HBA related messages unlike /var/adm/messages files.

But has less available space compared to /var/adm/messages files.

So collecting OracleSolaris Fibre Channel (FC) HBA card and Protocol dump/buffer/trace debug data should be done as soon as possible after the issue occured before relevant data is lost.

 

NOTE: Oracle Solaris Fibre Channel (FC) HBA card and Protocol dump/buffer/trace debug data may list false-positive messages so they are ONLY to be evaluated in context with other events on the server when the issue re-occurs and only by Oracle support personnel.

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms