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

Product Notes

search filter icon
search icon

Document Information

Using This Documentation

Related Documentation

Feedback

Support and Accessibility

Late-Breaking Information

Supported Chassis

Identify Your Chassis Version

Supported Hardware Components

Preinstalled Software

Supported Versions of the OS, Firmware, and Software

Required OS Package and Patch Updates

Determining Oracle Solaris 11 OS Package Update Version

Oracle Solaris 10 OS Patches

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

High-Altitude Mode Oracle ILOM Feature

Known Product Issues

Hardware Issues

Sun Type 6 Keyboards Are Not Supported by SPARC and Netra SPARC T4 Series Servers

Chassis CMM Does Not Allocate Enough Power to the Netra T4-1B Server Module (CR 7141886)

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)

sas2ircu Message That RAID Volume Sizes Other Than MAX Are Not Supported (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)

The 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)

Documentation Issues

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

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

    • tn = t5000c50033438dbb

      where n is the SASDeviceName value.

    • dn = d0

      where n is 0 for all embedded SCSI devices.

    The resulting logical device name is c0t5000c50033438dbbd0.