Confirming Server and Site Specifications
Overcurrent Protection Requirements
DC Power Source, Power Connection, and Grounding Requirements
PCIe2 Expansion Slot Guidelines
Mounting the Server Into a 4-Post Rack
Mounting the Server Into a 2-Post Rack
Connecting Data and Management Cables
Powering On the Server for the First Time
Connect a Terminal or Emulator to the SER MGT Port
Power On the Server 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
Power On the Server (Oracle ILOM)
Power Off the Server (Oracle ILOM)
Reset the Server (Oracle Solaris OS)
Reset the Server (Oracle ILOM)
Reset the SP to Default Values
Important Hardware RAID Guidelines
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 Data on FRU PROMs
Change System Identifier Information
Restore the Host Power State at Restart
Specify the Host Power State at Restart
Disable or Re-Enable the Host Power-On Delay
Specify Parallel Boot of the SP and Host
Configure Host Behavior (Keyswitch State)
Disable or Re-Enable Network Access to the SP
Display the DHCP Server IP Address
Display the IP Address of the SP
Using an In-band Connection to the SP
Configure the Host Boot Mode (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 OBP 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
Mapping WWN Values to Hard Drives (OBP probe-scsi-all Command)
probe-scsi-all WWN Mapping Overview
probe-scsi-all WWN Mapping Example (SPARC T4-1)
probe-scsi-all WWN Mapping Example (SPARC T4-2)
probe-scsi-all WWN Mapping Example (Netra SPARC T4-2)
probe-scsi-all WWN Mapping Example (SPARC T4-4 With Four CPUs)
probe-scsi-all WWN Mapping Example (SPARC T4-4 With Two CPUs)
probe-scsi-all WWN Mapping Example (SPARC T4-1B and Netra SPARC T4-1B)
Identify a Disk Slot Using prtconf (Oracle Solaris OS)
WWN Syntax in an OS Installation on an Individual Drive
WWN Syntax in an OS Installation on a RAID Volume
Power Supply, Hard Drive, and Rear Fan Module Locations
Motherboard, PCIe2 Cards, and SP Locations
Front Fans, Subchassis, Memory Riser, and DIMM Locations
Understanding Fault Management Commands
Interpreting Log Files and System Messages
Checking if Oracle VTS Is Installed
Component Service Task Reference
Removing Power From the Server
Locate a Faulty Front Fan Module
Determine if the DVD Drive Is Faulty
Determine if the Rear Fan Module Is Faulty
Locate a Faulty DIMM (Oracle ILOM)
Determine if the Battery Is Faulty
Install SAS Cable for Sun Storage 6 Gb SAS PCIe RAID HBA, Internal
Determine if the ID PROM Is Faulty
Determine if the LED Board Is Faulty
Determine if the Motherboard Is Faulty
Servicing the Power Distribution Board
Determine if the Power Distribution Board Is Faulty
Remove the Power Distribution Board
Install the Power Distribution Board
Verify the Power Distribution Board
Servicing the Hard Drive Backplane
Determine if the Hard Drive Backplane Is Faulty
Remove the Hard Drive Backplane
Install the Hard Drive Backplane
Verify the Hard Drive Backplane
Returning the Server to Operation
Power On the Server (Oracle ILOM)
The Netra SPARC T4-1 server uses only one of the two SAS2 RAID controllers on the motherboard. The controller connects to four slots on the disk backplane. The following table shows the PhyNum-to-disk slot mapping.
Table 4 SAS2 Controller Port Mapping for the Netra SPARC T4-1 Disk Backplane
|
The following example is based on a Netra SPARC T4-1 server with four hard drives. These hard drives are deployed as four individual storage devices. Controller 1 is attached to these storage devices in the following manner:
Controller 1 is attached to Targets 9, b, c, and d (four individual storage devices).
Target a (is a DVD drive).
Note - For Netra SPARC T4-1 servers, the second field of the device path specifies the controllers: /pci@400/pci@2 = controller 1 and /pci@400/pci@1 = controller 0.
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.56, MPT Version 2.00, Firmware Version 9.00.00.00 Target 9 Unit 0 Disk HITACHI H106030SDSUN300G A2B0 585937500 Blocks, 300 GB SASDeviceName 5000cca012b76b40 SASAddress 5000cca012b76b41 PhyNum 0<-HD slot 0 Target a Unit 0 Removable Read Only device TEAC DV-W28SS-V 1.0B SATA device PhyNum 6 <- DVD Target b Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00a4d2ff0 SASAddress 5000cca00a4d2ff1 PhyNum 2<-HD slot 2 Target c Unit 0 Disk SEAGATE ST930003SSUN300G 0868 585937500 Blocks, 300 GB SASDeviceName 5000c50017871633 SASAddress 5000c50017871631 PhyNum 1 <- HD slot 1 Target d Unit 0 Disk SEAGATE ST930003SSUN300G 0868 585937500 Blocks, 300 GB SASDeviceName 5000c5001cb42adf SASAddress 5000c5001cb42add PhyNum 3 <- HD slot 3 /pci@400/pci@1/pci@0/pci@4/scsi@0 <---- SAS controller 0 (Not Used) FCode Version 1.00.56, MPT Version 2.00, Firmware Version 9.00.00.00 ok
In this example, the controller ports are attached to the hard drives and the DVD in the following manner:
|
Note - Target values are not static. The same storage device can appear in two consecutive probe-scsi-all listings with different Target values.
The default boot device has the following values:
Controller = 1
Target = 9
PhyNum = 0
SASDeviceName = 5000cca012b76b40
SASAddress = 5000cca012b76b41
If you want to specify another drive to be the boot device, find its PhyNum value in the output and use the SASDeviceName assigned to that device. For example, if you want to use the hard drive in disk slot 2, it has the following values:
Controller = 1
Target = b
PhyNum = 2
SASDeviceName = 5000cca00a4d2ff0
SASAddress = 5000cca00a4d2ff1