Front and Rear Panel Components
Plan Communication With the Server Module During Installation
Optional Component Installation
Modular System Chassis Preparation
Insert the Server Module Into the Chassis
Communicating With the Server Module During Startup
Monitor the Diagnostic Messages
Powering On the Server Module for the First Time
Initial Power-On Task Overview
Power On the System for the First Time
Install Oracle Solaris Software From the Network
Oracle Solaris Configuration Settings
Assign a Static IP Address to the Service Processor
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, Sixteen-Disk Backplane)
probe-scsi-all Output Example (SPARC T3-4)
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
Front and Rear Panel Components
Interpreting Log Files and System Messages
Managing Faults (Oracle Solaris PSH)
Managing Components (ASR Commands)
Checking if Oracle VTS Software Is Installed
Find the Modular System Serial Number
Find the Server Module Serial Number
Removing the Server Module From the Modular System for Service
Clear the Fault and Verify the Functionality of the Replacement DIMM
Servicing a Service Processor Card
Remove the Service Processor Card
Install the Service Processor Card
Replacing the Server Module Enclosure Assembly
Transfer Components to Another Enclosure Assembly
Returning the Server Module to Operation
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.
The following table shows the PhyNum-to-disk slot correspondence for an eight-disk backplane configuration.
Table 3 SAS Controller Port Mapping for Eight-Disk Backplanes
|
The following example illustrates probe-scsi-all output for a SPARC T3-1 server with seven hard drives in an eight-disk capable backplane configuration. In this example, the hard drives are connected to the two SAS controllers in this manner:
Four hard drives are connected to SAS controller 0. These are targets 9, a, b, and c.
Three hard drives and a SATA DVD device are connected to SAS controller 1. These are targets 9, b, c, and a, respectively.
Because SAS controller 0 controls the hard drives installed in backplane slots 0-3, the default boot device for this sample configuration 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@400/pci@2/pci@0/pci@f/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@2/pci@0/pci@4/scsi@0 <---- SAS controller 1 FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00 Target 9 Unit 0 Disk SEAGATE ST930003SSUN300G 0B70 585937500 Blocks, 300 GB SASDeviceName 5000c5001d33fba7 SASAddress 5000c5001d33fba5 PhyNum 0 Target a Unit 0 Removable Read Only device TEAC DV-W28SS-R 1.0C SATA device PhyNum 6 Target b Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00a76e380 SASAddress 5000cca00a76e381 PhyNum 1 Target c Unit 0 Disk SEAGATE ST930003SSUN300G 0B70 585937500 Blocks, 300 GB SASDeviceName 5000cca00a76ddcc SASAddress 5000cca00a76ddcd PhyNum 3 /pci@400/pci@1/pci@0/pci@4/scsi@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 5000cca00a75dcac SASAddress 5000cca00a75dcad PhyNum 0 Target a Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00a7680d4 SASAddress 5000cca00a7680d5 PhyNum 2 Target b Unit 0 Disk SEAGATE ST930003SSUN300G 0B70 585937500 Blocks, 300 GB SASDeviceName 5000c5001d33eb5f SASAddress 5000c5001d33eb5d PhyNum 3 Target c Unit 0 Disk SEAGATE ST930003SSUN300G 0B70 585937500 Blocks, 300 GB SASDeviceName 5000c5001d40bf9b SASAddress 5000c5001d40bf99 PhyNum 1