Solaris Fibre Channel (FC) HBA Protocol Dump/Buffer/Trace Debug Data Collection
(Doc ID 2012564.1)
Last updated on OCTOBER 05, 2022
Applies to:
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]
Solaris Operating System - Version 10 11/06 U3 and later
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.
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.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |