Confirming Server and Site Specifications
Overcurrent Protection Requirements
DC Power Source, Power Connection, and Grounding Requirements
Stabilize the Rack for Installation
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 (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)
probe-scsi-all WWN Mapping Example (SPARC T4-1B and Netra SPARC T4-1B)
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 Fan Module Locations
Top Cover, Filter Tray, and DVD Tray Locations
Motherboard, DIMMs, and PCI Board 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
Determine if the Hard Drive Fan Is Faulty
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
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
Determine if the DVD Drive Is Faulty
Determine if the LED Board Is Faulty
Determine if the Fan Board Is Faulty
Servicing the PCIe2 Mezzanine Board
Determine if the PCIe2 Mezzanine Board Is Faulty
Remove the PCIe2 Mezzanine Board
Install the PCIe2 Mezzanine Board
Verify the PCIe2 Mezzanine Board
Locate a Faulty PCIe2 Riser Card
Remove a PCIe2 Card From the PCIe2 Mezzanine Board
Remove a PCIe2 Card From the PCIe2 Riser Card
Install a PCIe2 Card Into the PCIe2 Mezzanine Board
Install a PCIe2 Card Into the PCIe2 Riser Card
Install SAS Cable for Sun Storage 6 Gb SAS PCIe RAID HBA, Internal
Servicing the Signal Interface Board
Determine if the Signal Interface Board Is Faulty
Remove the Signal Interface Board
Install the Signal Interface Board
Verify the Signal Interface Board
Determine if the Battery Is Faulty
Determine if the ID PROM Is Faulty
Determine if the Motherboard Is Faulty
Returning the Server to Operation
Power On the Server (Oracle ILOM)
The procedure described below applies to SPARC T4-1 and SPARC T4-4 servers, which have eight-disk backplane configurations. The same methodology can be used for the SPARC T4-2 server and SPARC T4-1B blade systems.
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t5000CCA00ABBAEB8d0 <SUN300G cyl 46873 alt 2 hd 20 sec 625> /scsi_vhci/disk@g5000cca00abbaeb8 1. c0t5000C5001D40D7F7d0 <SUN300G cyl 46873 alt 2 hd 20 sec 625> /scsi_vhci/disk@g5000c5001d40d7f7 [...]
The remaining steps in this example will identify the physical slot that corresponds to the device name c0t5000CCA00ABBAEB8d0.
Device Minor Nodes: dev=(32,0) dev_path=/scsi_vhci/disk@g5000cca00abbaeb8:a spectype=blk type=minor dev_link=/dev/dsk/c0t5000CCA00ABBAEB8d0s0 <<=== Device link dev_link=/dev/sd3a dev_path=/scsi_vhci/disk@g5000cca00abbaeb8:a,raw spectype=chr type=minor dev_link=/dev/rdsk/c0t5000CCA00ABBAEB8d0s0 <<=== Device link dev_link=/dev/rsd3a
Note the obp-path value listed under WWN 5000cca00abbaeb8.
Refer to the following table to find the controller.
|
For SPARC T4-1 servers, the controller is identified in the second field: pci@1 = controller 0 and pci@2 = controller 1.
For SPARC T4-4 servers, the controller is identified in the first field. For systems with a four-processor configuration, pci@400 = controller 0 and pci@700 = controller 1. For systems with a two-processor configuration, pci@400 = controller 0 and pci@500 = controller 1.
Note - Because SPARC T4-2 and SPARC T4-1B systems contain only one SAS controller, only controller 0 will be listed.
The following output example shows the obp-path for a SPARC T4-1 server.
Paths from multipath bus adapters: mpt_sas#5 (online) name='wwn' type=string items=1 value='5000cca00abbaeb8' <<=== Hard drive WWN ID name='lun' type=int items=1 value=00000000 name='target-port' type=string items=1 value='5000cca00abbaeb9' <<=== Hard drive SAS address name='obp-path' type=string items=1 value='/pci@400/pci@1/pci@0/pci@4/scsi@0/disk@w5000cca00abbaeb9,0' name='phy-num' type=int items=1 value=00000000 name='path-class' type=string items=1 value='primary'
In this SPARC T4-1 example, the obp-path is:
/pci@400/pci@1/pci@0/pci@4/scsi@0/disk@w5000cca00abbaeb9,0
Based on the previous table, this disk is on controller 0.
The following output example shows the obp-path for a SPARC T4-4 server.
Paths from multipath bus adapters: mpt_sas#5 (online) name='wwn' type=string items=1 value='5000cca00abbaeb8' <<=== Hard drive WWN ID name='lun' type=int items=1 value=00000000 name='target-port' type=string items=1 value='5000cca00abbaeb9' <<=== Hard drive SAS address name='obp-path' type=string items=1 value='/pci@400/pci@1/pci@0/LSI,sas@0/disk@w5000cca00abbaeb9,0' name='phy-num' type=int items=1 value=00000000 name='path-class' type=string items=1 value='primary'
In this SPARC T4-4 example, the obp-path is:
/pci@400/pci@1/pci@0/pci@0/LSI,sas@0/disk@w5000cca00abbaeb9,0
Based on the previous table, this disk is on controller 0.
|