Defining Internal Storage for Oracle Solaris on Third-Party x86 Based Systems Using Bay Labels 2.0
(Doc ID 2170755.1)
Last updated on FEBRUARY 05, 2019
Applies to:Solaris x64/x86 Operating System - Version 11.2 and later
Information in this document applies to any platform.
Systems running Oracle Solaris 11.2 SRU 8.4 or later use the new bay-labels_2.0 mechanism for understanding the physical location of internal devices.
With third-party x86 based systems, the platform/HBA specific information that allows commands like diskinfo
to display the physical location of internal storage is missing.
The previous mechanism bay_label 1 uses the files /usr/platform/i86pc/lib/fm/topo/maps/*.bay_labels (see Doc ID 1411444.1),
that have been replaced by bay_label 2 since Solaris 11.2 SRU 8.4, as explained on this RFE :
BUG 19663756 - Delivery of PSARC/2014/338 bay-labels_2.0
As a result, diskinfo does not report any internal storage.
For third-party x86 platform/HBA configurations, follow the steps below to define the physical location of internal legacy SCSI storage.
Note1. Is there a list of drivers that are compatible with Bay labels 2.0?
No, this is a general mechanism.
These specific instructions are targeting internal (typically SATA) storage supported by the x86 cpu chipset itself.
Oracle often chooses to use an internal HBA that consumes an PCIE slot instead of HBA capabilities of the CPU chipset.
Note2. This document is only valid for devices that enumerate like legacy-scsi where the disk unit-address is location-oriented @<small-target-number>,0.
This document does not cover third party use of direct-attach SAS HBAs that use our SCSAv3 SAS HBA drivers (mpt_sas, lsc, lmrc),
the instructions are a bit different: focusing on setting 'sas-bay-labels' instead of 'scsi-bay-labels' , this will be covered on a new document.
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
|Example on a Third Party x86 Dell server|