JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
SPARC T4-1B Server Module HTML Document Collection
search filter icon
search icon

Document Information

Using This Documentation

Related Documentation

Feedback

Support and Accessibility

Installation

Understanding the Server Module

Installation Task Overview

Server Module Overview

Front and Rear Panel Components

Confirming Server Module and Site Specifications

Physical Specifications

Environmental Specifications

Electrical Specifications

Preparing for Installation

Inventory

Handling Precautions

ESD Precautions

Tools Needed for Installation

Plan Communication With the Server Module During Installation

Dongle Cables

Installing the Server Module

Prepare the Modular System and Server Module

Install Optional Components

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

Configure the OS

Install Oracle Solaris Software From the Network

Oracle Solaris Configuration Parameters

Assign a Static IP Address to the SP

Administration

Understanding System Administration Resources

Oracle ILOM Overview

Platform-Specific Oracle ILOM Features

Oracle Solaris OS Overview

OpenBoot Overview

Oracle VM Server for SPARC Overview

Multipathing Software

Hardware Management Pack Overview

Source for Downloading Hardware Management Pack Software

Hardware Management Pack Documentation

Accessing the Server

Log In to Oracle ILOM

Log In to the System Console

Display the ok Prompt

Display the Oracle ILOM -> Prompt

Use a Local Graphics Monitor

Oracle ILOM Remote Console

Controlling the Server

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

Configuring Hardware RAID

Hardware RAID Support

Important Hardware RAID Guidelines

Prepare to Use the FCode Utility

FCode Utility Commands

Create a Hardware RAID Volume

Hot Spare Drives in RAID Volumes (LSI)

Determining If a Drive Has Failed

RAID Drive Replacement Strategies

Locate Device Paths

Changing Server Identification Information

Change Customer Data on FRU PROMs

Change System Identifier Information

Configuring Policy Settings

Specify Cooldown Mode

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)

Configuring Network Addresses

SP Network Address Options

Disable or Re-Enable Network Access to the SP

Display the DHCP Server IP Address

Display the IP Address of the SP

Display the Host MAC Address

Using an In-band Connection to the SP

Configuring Boot Mode

Boot Mode Overview

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

Set the Boot Timeout Interval

Specify Behavior at Boot Timeout

Specify Behavior if Restart Fails

Specify Maximum Restart Attempts

Configuring Devices

Unconfigure a Device Manually

Reconfigure a Device Manually

Monitoring the Server

Monitoring Faults

Enabling Automatic System Recovery

Display Server Components

Locate the Server

Updating the Firmware

Display the Firmware Version

Update the Firmware

Display OpenBoot Version

Display POST Version

Identifying WWN-Designated SAS2 Devices

World Wide Name Syntax

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)

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

Service

Identifying Components

Illustrated Parts Breakdown

Front and Rear Panel Components

Detecting and Managing Faults

Diagnostics Overview

Diagnostics Process

Diagnostics LEDs

Managing Faults (Oracle ILOM)

Interpreting Log Files and System Messages

Checking if Oracle VTS Software Is Installed

Managing Faults (POST)

Managing Faults (PSH)

Managing Components (ASR)

Preparing for Service

Safety Information

Handling Precautions

Tools Needed for Service

Find the Modular System Chassis Serial Number

Find the Server Module Serial Number

Locate the Server Module

Preparing the Server Module for Removal

Remove the Server Module From the Modular System

Remove the Cover

Servicing Drives

Drive Configuration

Drive LEDs

Drive Hot-Plugging Guidelines

Locate a Faulty Drive

Remove a Drive

Remove a Drive Filler

Install a Drive

Install a Drive Filler

Verify Drive Functionality

Servicing Memory

Memory Faults

DIMM Locations

DIMM Configuration Guidelines

DIMM Handling Precautions

Locate a Faulty DIMM

Remove a DIMM

Install a DIMM

Clear the Fault and Verify the Functionality of the Replacement DIMM

Verify DIMM Functionality

Servicing the REM

Remove a REM

Install a REM

Servicing the FEM

Remove a FEM

Install a FEM

Servicing the SP Card

Remove the SP Card

Install the SP Card

Servicing the ID PROM

Remove the ID PROM

Install the ID PROM

Verify the ID PROM

Servicing a USB Flash Drive

Remove a USB Flash Drive

Install a USB Flash Drive

Servicing the Battery

Replace the Battery

Replacing the Server Module Enclosure Assembly (Motherboard)

Transfer Components to Another Enclosure Assembly

Returning the Server Module to Operation

Replace the Cover

Install the Server Module Into the Modular System

Power On the Host (Oracle ILOM)

Power On the Host (Power Button)

Glossary

Index

probe-scsi-all WWN Mapping Example (SPARC T4-4 With Two CPUs)

The SPARC T4-4 server has two REM cards plugged into the motherboard. These modules are referred to as controllers 0 and 1. Each SAS controller is connected to a separate four-slot disk backplane. The following table shows the PhyNum-to-disk slot mapping for the two four-slot SPARC T4-4 backplanes.

Table 7 SAS2 Controller Port Mapping for the SPARC T4-4 Disk Backplane

Disk Backplane 0
Disk Backplane 1
SAS2 Controller
Controller Port ID

(PhyNum)

Disk Slot ID
SAS2 Controller
Controller Port ID

(PhyNum)

Disk Slot ID
0
0
01
1
0
4
1
1
1
5
2
2
2
6
3
3
3
7

1Default boot drive

This table shows that ports 0-3 of controller 0 are connected to backplane slots 0-3 and ports 0-3 of controller 1 are connected to slots 4-7.

The following example is based on a SPARC T4-4 server with two CPUs and eight hard drives. These hard drives are deployed as six individual storage devices and a virtual drive that consists of two hard drives configured as a RAID volume. Controllers 0 and 1 are attached to these storage devices in the following manner:


Note - OBP uses a different device path for SAS controller 1 in SPARC T4-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.


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 457 Volume 0
  Unit 0   Disk   LSI     Logical Volume   3000   583983104 Blocks,   298 GB
  VolumeDeviceName 3ce534e42c02a3c0   VolumeWWID 0ce534e42c02a3c0
 
ok

In this example, the controller ports are attached to the hard drives in the following manner:

Disk Backplane 0
Disk Backplane 1
Controller Port (PhyNum)
Disk Slot ID
Target
Controller Port (PhyNum)
Disk Slot ID
Target
0
01
9
0
4
9
1
1
a
1
5
a
2
2
RAID Target 457
2
6
b
3
3
RAID Target 457
3
7
c

1Default boot drive


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:

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 1, it has the following values:

Related Information