Understanding the Server Module
Front and Rear Panel Components
Confirming Server Module and Site Specifications
Plan Communication With the Server Module During Installation
Prepare the Modular System and Server Module
Insert the Server Module Into the Chassis
Powering On the Server Module for the First Time
Method 1a – Power On the Host Through the CMM (Web Interface)
Method 1b – Power On the Host Through the CMM (CLI)
Method 2 – Power On the Host Through the CMM SER MGT Port (CLI)
Method 3 – Power On the Host Through the Front Panel (SP CLI)
Configuring the Oracle Solaris OS
Install Oracle Solaris Software From the Network
Oracle Solaris 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 (Netra 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)
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
Front and Rear Panel Components
Interpreting Log Files and System Messages
Checking if Oracle VTS Software Is Installed
Find the Modular System Chassis Serial Number
Find the Server Module Serial Number
Preparing the Server Module for Removal
Remove the Server Module From the Modular System
Clear the Fault and Verify the Functionality of the Replacement DIMM
Replacing the Server Module Enclosure Assembly (Motherboard)
Transfer Components to Another Enclosure Assembly
Returning the Server Module to Operation
Install the Server Module Into the Modular System
Power On the Host (Oracle ILOM)
The SPARC and Netra SPARC T4-1B blades have two SCSI disk slots in the disk backplane. A Sun Blade 6000 RAID 0/1 SAS2 HBA REM, which is plugged into the motherboard, manages storage devices installed in these backplane slots.
The following table shows the PhyNum-to-disk slot mapping for the two-slot SPARC T4-1B backplane.
Table 8 SAS2 Controller Port Mapping for the SPARC T4-1B Disk Backplane
|
The following example is based on a SPARC T4-1B blade with both hard drives attached to the controller as individual storage devices.
ok probe-scsi-all /pci@400/pci@1/pci@0/pci@c/LSI,sas@0 <===== SAS Controller FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00 Target 9 Unit 0 Disk SEAGATE ST930003SSUN300G 0868 585937500 Blocks, 300 GB SASDeviceName 5000c500231694cf SASAddress 5000c500231694cd PhyNum 0 Target a Unit 0 Disk SEAGATE ST973402SSUN72G 0603 143374738 Blocks, 73 GB SASDeviceName 5000c50003d37fcb SASAddress 5000c50003d37fc9 PhyNum 1 /pci@400/pci@1/pci@0/pci@0/pci@0/usb@0,2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00 ok
In this example, the controller ports are attached to the hard drives 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 = 0
Target = 9
PhyNum = 0
SASDeviceName = 5000c500231694cf
SASAddress = 5000c500231694cd
If you want to specify the hard drive in disk slot 1 to be the boot device, it would have the following values in this example:
Controller = 0
Target = a
PhyNum = 1
SASDeviceName = 5000c50003d37fcb
SASAddress = 5000c50003d37fc9
The following example is based on a SPARC T4-1B blade with both hard drives attached to the controller as a RAID volume.
ok probe-scsi-all /pci@400/pci@1/pci@0/pci@2/LSI,sas@0 <===== SAS Controller FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00 Target 377 Volume 0 Unit 0 Disk LSI Logical Volume 3000 583983104 Blocks, 298 GB VolumeDeviceName 3ce534e42c02a3c0 VolumeWWID 0ce534e42c02a3c0 /pci@400/pci@1/pci@0/pci@0/pci@0/usb@0,2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00 ok
In this example, the controller ports are attached to a RAID volume containing the hard drives installed in disk slots 0 and 1.