probe-scsi-all Device Naming (OpenBoot)
nvme2 /pci@302/pci@2/pci@0/pci@6/nvme@0/disk@1
nvme1 /pci@300/pci@2/pci@0/pci@5/nvme@0/disk@1
nvme0 /pci@300/pci@2/pci@0/pci@4/nvme@0/disk@1
net3 /pci@300/pci@1/pci@0/pci@1/network@0,3
net2 /pci@300/pci@1/pci@0/pci@1/network@0,2
net1 /pci@300/pci@1/pci@0/pci@1/network@0,1
net /pci@300/pci@1/pci@0/pci@1/network@0
net0 /pci@300/pci@1/pci@0/pci@1/network@0
virtual-console /virtual-devices/console@1
name aliases
Related Information
■
“Obtain the OpenBoot Prompt Under Various Conditions” on page 21
probe-scsi-all Device Naming (OpenBoot)
The output displayed by probe-scsi-all lists all SCSI devices in the server and provides
a basic set of information about each device. When analyzing the probe-scsi-all output,
look for the following data fields that are different names for the same device. You must use a
specific type of name in different commands.
Entity Name Definition
Target
Each SAS drive is assigned a unique target ID.
SASDeviceName
WWN value assigned to a SAS drive by the manufacturer.
Oracle Solaris recognizes this name.
SASAddress
WWN value assigned to a SCSI device that is recognized
by the OpenBoot firmware.
PhyNum
Hexidecimal ID of the controller port that is attached to the
target drive.
At a high level, the WWN mapping process consists of the following stages:
1. Identify the physical location of the hard drive that is to be the target of the operation.
2. Identify the controller port that is attached to that physical location.
3. Find the WWN-based device name of the drive attached to that controller port.
Note - Refer to the server's service manual for a description of the physical drive slot
organization.
74 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017
To Next Page
Loading...
Need help?
General