JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
SPARC T4-1B Server Module

Product Notes

search filter icon
search icon

Document Information

1.  Late-Breaking Information

Supported Chassis

Identify Your Chassis Version

Supported Hardware Components

Preinstalled Software

Minimum Supported Versions of the OS, Firmware, and Software

Required OS Patches and Package Updates

Oracle Solaris 11 OS Package Updates

Oracle Solaris 10 OS Patches

Obtain Patches

Important Firmware Upgrade Required Prior to Mixing SAS-1 and SAS-2 Components

Identifying Drive Logical Device Names and Physical Locations

Correlate WWN Device Names With Physical Locations (diskinfo Command)

Correlate WWN Device Names With Physical Locations (probe-scsi-all Command)

Oracle Solaris Jumpstart WWN Syntax

Interactive Installation Example

2.  Known Product Issues

Hardware Issues

Sun Type 6 Keyboards are Not Supported by SPARC T4 Series Servers

PSH Might Not Clear a Retired Cache Line on a Replaced Motherboard (CR 7031216)

2-Meter USB Cable Length Limit (7048419)

Uncorrectable L2 Cache Errors are Sometimes Reported as Core Faults Without Any Cache Line Retirement (CR 7071237 and CR 7071974)

During a Reboot After an Unrecoverable Hardware Error, CPUs Might Not Start (CR 7075336)

Blue LED on Drive Does Not Light When the Drive is Ready to Remove (CR 7082700)

Firmware, OS, and Other Software Issues

fault.memory.memlink-uc Fault Did Not Cause Panic as Stated by System Message (CR 6940599)

Timestamp for an Oracle ILOM Fault/Critical Event Might Be off by One Hour (CR 6943957)

e1000g Driver Generates Spurious ereports When Installing Oracle Solaris OS Over a Sun PCIe Dual Gigabit Ethernet Adapter (CR 6958011)

When diag-switch? Is Set to true, Oracle Solaris OS Fails to Update the EEPROM for Automatic Rebooting (CR 6982060)

Unable to Configure RAID Volume Sizes Other Than the Max Size When Using the sas2ircu Command (CR 6983210)

Fault Management Sometimes Sends Resolved Cases to the SP (CR 6983432)

Units Used to Define the MIB Power Management Time Limit are Reported in Seconds (CR 6993008)

Spurious Interrupt Message in System Console When Using Oracle VTS (CR 7038266)

Intermittent Link Training Timeout Displayed During Power Cycles (CR 7043201)

The cfgadm Command Might Fail on SG-SAS6-REM-Z or SGX-SAS6-REM-Z HBAs (CR 7044759)

Message From cpustat Refers to Processor Documentation Incorrectly (CR 7046898)

Using trapstat Might Cause a Panic (CR 7052070)

reboot disk Command Occasionally Fails When disk Argument Picks Up Extra Characters (CR 7050975)

PCIe Correctable Errors Might Be Reported (CR 7051331)

Watchdog Timeouts Seen With Heavy Workloads and Maximum Memory Configurations (CR 7083001)

ereport.fm.fmd.module Generated During a Reboot of an SDIO Domain (CR 7085231)

Oracle VTS dtlbtest Hangs When CPU Threading Mode is Set to max-ipc (CR 7094158)

Cold Reset Adds One Day to System Time (CR 7127740)

Identifying Drive Logical Device Names and Physical Locations

The Oracle Solaris OS now uses the worldwide number (WWN) in place of the target ID field (tn) in drive logical device names for SAS-2 storage controllers.This change affects how you correlate a drive's logical name with the drive's physical location.

These points are key to understanding the impact of this change:

To correlate drive logical device names with physical locations or the other way around:

Correlate WWN Device Names With Physical Locations (diskinfo Command)

The diskinfo command, a new disk and slot identification utility, was introduced in Oracle Solaris 10 8/11 OS and in the kernel patch 144500-19 (or later).

If you do not have access to the OS, for example, if the server module is not booted, see Correlate WWN Device Names With Physical Locations (probe-scsi-all Command).

If your OS does not provide the diskinfo command, refer to the SPARC and Netra SPARC T4 Series Servers Administration Guide for alternative methods.

  1. Log into the OS.
  2. Type:
    # diskinfo -a
     
    Enclosure path:         1114BD0ACC-physical-hba-0
    Chassis Serial Number:  1114BD0ACC-physical-hba-0
    Chassis Model:          ORCL,SPARC-T4-1B
     
    Label      Disk name               Vendor   Product          Vers
    ---------- ----------------------  -------- ---------------- ----
    /SYS/HDD0  c0t5000C50033438DBBd0   SEAGATE  ST930003SSUN300G 0B70
    /SYS/HDD1  c0t5000C50005C15803d0   SEAGATE  ST930003SSUN300G 0468
  3. Use the output under the Label and Disk Name columns to correlate a drive's physical location with its corresponding logical device name.

    For this server module:

    • /SYS/HDD0 represents a drive in slot 0.

    • /SYS/HDD1 represents a drive in slot 1.

    In this example, the drive installed in slot 0 has a logical device name of c0t5000C50033438DBBd0.


    Note - The diskinfo command provides a variety of disk information depending on the command options you specify. For more information, type diskinfo -h and refer to the diskinfo(1M) man page.


Correlate WWN Device Names With Physical Locations (probe-scsi-all Command)

If you have access to the OS, you might be able to use the diskinfo command instead. See Correlate WWN Device Names With Physical Locations (diskinfo Command).

  1. At the ok prompt, type:
    {0} 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 0B70    585937500 Blocks, 300 GB
     SASDeviceName 5000c50033438dbb  SASAddress 5000c50033438db9  PhyNum 0 <=HD,slot 0
    Target b
     Unit 0   Disk   SEAGATE  ST930003SSUN300G 0468    585937500 Blocks, 300 GB
     SASDeviceName 5000c50005c15803  SASAddress 5000c50005c15801  PhyNum 1 <=HD,slot 1
    Target c
     Unit 0   Encl Serv device   SUN      NEM Hydra II SOL 0308
     SASAddress 5080020000bb193d  PhyNum 24
     
    /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
  2. In output, look for the following disk identifiers:
    • LSI,sas@0 – Controller (REM) on the server module.

    • SASDeviceName – WWN that the Oracle Solaris OS recognizes.

    • SASAddress – WWN that the OBP references.

    • PhyNum – Physical slot that the drive occupies.

  3. Use the values in the output to construct the resulting Oracle Solaris logical device name as expressed by cntndn.

    This example is based on the previous output:

    • cn = c0

      n is the SAS controller number, 0 in this example.

    • tn = t5000c50033438dbb

      n is the SASDeviceName value.

    • dn = d0

      n is 0 for all embedded SCSI devices.

    The resulting logical device name is c0t5000c50033438dbbd0.

Oracle Solaris Jumpstart WWN Syntax

The Oracle Solaris syntax requires all WWN alpha characters to be capitalized.


Note - Only the WWN portion of the logical device name requires capitalized alpha characters. The c0 and d0 portion are not capitalized.


This Jumpstart profile example shows how to use the WWN syntax when installing the OS on a specific drive.

#
install_type flash_install    
boot_device c0t5000C50033438DBBd0 preserve
 
archive_location nfs
129.148.94.249:/export/install/media/solaris/builds/s10u9/flar/latest.flar
 
# Disk layouts
#
partitioning explicit
filesys rootdisk.s0                                     free /
filesys rootdisk.s1                                     8192 swap

Interactive Installation Example

In an interactive installation, you are asked to specify one or more drives as the targets for the OS installation. This step ensures that sufficient storage capacity is provided for the installation. Specify the drive with the WWN value that corresponds to the drive on which you want to install the software.

These WWN values are illustrated in the following interactive example. The drive selected as the installation target is located in drive slot 0, the default boot location.


Note - If you prefer to use some other disk, specify it instead of the one in HDD slot 0.


_ Select Disks_________________________________________________________________
 
On this screen you must select the disks for installing Solaris software. Start
by looking at the Suggested Minimum field; this value is the approximate space
needed to install the software you've selected. Keep selecting disks until the
Total Selected value exceeds the Suggested Minimum value.
NOTE: ** denotes current boot disk
 
Disk Device                                                         Available Space
=============================================================================
[ ] c0t5000C50005C15803d0                                                         286090 MB
[X] c0t5000C50033438DBBd0                                                         286090 MB (F4 to edit)
 
                        Total Selected: 286090 MB
                        Suggested Minimum: 5032 MB
 
______________________________________________________________________________
Esc-2_Continue             F3_Go Back                         F4_Edit             F5_Exit             F6_Help
 

Note - You might need to label new and replacement drives using the format utility before you can install the OS on the drives.