Preparing for the Installation
Confirming Server Specifications
Optional Component Installation
Stabilize the Rack for Installation
Install Server Into the Slide Rail Assemblies
Verify Operation of Slide Rails and CMA
Rear Panel Connectors and Ports
Connect the Ethernet Network Cables
Connect the Network Module Cables
Powering On the Server for the First Time
Connect a Terminal or Emulator to the SER MGT Port
Power On the System for the First Time
Oracle Solaris OS Configuration Parameters
Assign a Static IP Address to the SP
Understanding System Administration Resources
Platform-Specific Oracle ILOM Features
Oracle VM Server for SPARC Overview
Hardware Management Pack Overview
Source for Downloading Hardware Management Pack Software
Hardware Management Pack Documentation
Display the Oracle ILOM -> Prompt
Reset the Server From the Oracle Solaris OS
Reset the Server From Oracle ILOM
Reset the SP to Default Values
Important Hardware RAID Guidelines
Disk Zones for SPARC T3-1 Servers With Sixteen-Disk Backplanes
Displaying Disk Zone Information
Enabling and Disabling Disk Zoning In the Field
Prepare to Use the FCode Utility
Hot Spare Drives in RAID Volumes (LSI)
Determining If a Drive Has Failed
RAID Drive Replacement Strategies
Changing Server Identification Information
Change Customer FRUdata Information
Change System Identifier Information
Restore Host Power State at Restart
Specify Host Power State at Restart
Disable or Re-Enable Power-On Delay
Specify Parallel Boot of the SP and Host
Configure Host Behavior With the Keyswitch State
Disable or Re-Enable Network Access to the SP
Display the DHCP Server IP Address
Using an In-band Connection to the SP
Configure the Host Boot Mode of Oracle VM Server for SPARC
Change the Host Boot Mode Behavior at Reset
Manage the Host Boot Mode Script
Display Host Boot Mode Expiration Date
Override OpenBoot PROM Settings to Reset the Server
Configuring Server Behavior at Restart
Specify Behavior When the Host Resets
Specify Behavior When the Host Stops Running
Specify Behavior at Boot Timeout
Specify Behavior if Restart Fails
Specify Maximum Restart Attempts
Enabling Automatic System Recovery
Identifying WWN-Designated SAS2 Devices
probe-scsi-all Output Example (SPARC T3-1, Eight-Disk Backplane)
probe-scsi-all Output Example (SPARC T3-1, Sixteen-Disk Backplane)
Identify a Disk Slot Using probe-scsi-all (OBP)
Identify a Disk Slot Using prtconf (Oracle Solaris, Onboard Controllers)
Identify a Disk Slot Using prtconf (Oracle Solaris, Single Initiator)
WWN Syntax in an OS Installation on a Specific Device
WWN Syntax in an OS Installation on a RAID Volume
Infrastructure Boards in the Server
Interpreting Log Files and System Messages
Using the Oracle Solaris Predictive Self-Healing Feature
Managing Components With Automatic System Recovery Commands
Checking if SunVTS Software Is Installed
Find the Chassis Serial Number
Understanding Component Replacement Categories
Removing Power From the System
Positioning the System for Servicing
Attaching Devices to the Server
Locate a Faulty Hard Disk Drive
Remove a Hard Disk Drive Filler Panel
Install a Hard Disk Drive Filler Panel
Verify Hard Disk Drive Functionality
Verify Fan Module Functionality
Verify Power Supply Functionality
Servicing Memory Risers and DIMMs
Locate a Faulty DIMM (DIMM Fault Remind Button)
Locate a Faulty DIMM (show faulty Command)
Increase Server Memory With Additional DIMMs
Remove a Memory Riser Filler Panel
Install a Memory Riser Filler Panel
DIMM Configuration Error Messages
Remove a DVD Drive or Filler Panel
Install a DVD Drive or Filler Panel
Servicing the System Lithium Battery
Servicing Expansion (PCIe) Cards
Remove a PCIe Card Filler Panel
Cable an Internal SAS HBA PCIe Card
Install a PCIe Card Filler Panel
Verify Fan Board Functionality
Verify Motherboard Functionality
Servicing the Service Processor
Service Processor Firmware and Configuration
Verify Service Processor Functionality
Servicing the Hard Disk Drive Backplane
Remove the Hard Disk Drive Backplane
Install the Hard Disk Drive Backplane
Verify Hard Disk Drive Backplane Functionality
Servicing the Power Supply Backplane
Remove the Power Supply Backplane
Install the Power Supply Backplane
Verify Power Supply Backplane Functionality
Returning the Server to Operation
Return the Server to the Normal Rack Position
When analyzing probe-scsi-all output, look for this SAS device information:
SASDeviceName -- This is the WWN that the Oracle Solaris OS recognizes.
SASAddress -- This is the WWN that the OBP recognizes.
PhyNum -- This is a hexadecimal value that identifies the port that a disk is connected to.
VolumeDeviceName -- When a RAID volume has been configured, this is the RAID volume WWN value recognized by the Oracle Solaris OS.
VolumeWWID -- When a RAID volume has been configured, this is the RAID volume WWN value referenced by OBP.
A SPARC T3-4 server has two onboard SAS controllers, each connected to a separate four-disk capable backplane. The following table shows the PhyNum-to-disk slot correspondence for these backplanes.
Table 6 SAS Controller Port Mapping for an Eight-Disk Backplane
|
Note - OBP uses a different device path for SAS controller 1 in SPARC T3-4 servers, depending on whether the server has four-processors or two processors. The path for SAS Controller 0 is the same for both processor configurations.
The following example illustrates probe-scsi-all output for a SPARC T3-4 with four processors and eight drives.
Because SAS controller 0 controls the hard drives installed in backplane slots 0-3, the default boot device for this example is PhyNum 0 in the group of hard drives under controller 0. It has a SASDeviceName value of 5000cca00a75dcac and a SASAddress value of 5000cca00a75dcad.
ok probe-scsi-all /pci@700/pci@1/pci@0/pci@0/LSI,sas@0 <---- SAS controller 1 FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00 Target 9 Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abc5cc8 SASAddress 5000cca00abc5cc9 PhyNum 0 Target a Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abaf620 SASAddress 5000cca00abaf621 PhyNum 1 Target b Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abcec4c SASAddress 5000cca00abcec4d PhyNum 2 Target c Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abc5218 SASAddress 5000cca00abc5219 PhyNum 3 /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00 /pci@400/pci@1/pci@0/pci@0/LSI,sas@0 <---- SAS controller 0 FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00 Target 9 Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abcede0 SASAddress 5000cca00abcede1 PhyNum 0 Target a Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abc51a8 SASAddress 5000cca00abc51a9 PhyNum 1 Target b Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abce89c SASAddress 5000cca00abce89d PhyNum 2 Target c Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 G SASDeviceName 5000cca00abc5354 SASAddress 5000cca00abc5355 PhyNum 3
The following example illustrates probe-scsi-all output for a SPARC T3-4 with two processors and eight drives.
Because SAS controller 0 controls the hard drives installed in backplane slots 0-3, the default boot device for this example is PhyNum 0 in the group of hard drives under controller 0. It has a SASDeviceName value of 5000cca00a75dcac and a SASAddress value of 5000cca00a75dcad.
ok probe-scsi-all /pci@500/pci@1/pci@0/pci@0/LSI,sas@0 <---- SAS controller 1 FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00 Target 9 Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abc5cc8 SASAddress 5000cca00abc5cc9 PhyNum 0 Target a Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abaf620 SASAddress 5000cca00abaf621 PhyNum 1 Target b Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abcec4c SASAddress 5000cca00abcec4d PhyNum 2 Target c Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abc5218 SASAddress 5000cca00abc5219 PhyNum 3 /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00 /pci@400/pci@1/pci@0/pci@0/LSI,sas@0 <---- SAS controller 0 FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00 Target 9 Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abcede0 SASAddress 5000cca00abcede1 PhyNum 0 Target a Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abc51a8 SASAddress 5000cca00abc51a9 PhyNum 1 Target b Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00abce89c SASAddress 5000cca00abce89d PhyNum 2 Target c Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 G SASDeviceName 5000cca00abc5354 SASAddress 5000cca00abc5355 PhyNum 3