General Information

C H A P T E R 1

General Information

These product notes provide important late-breaking information about Oracle’s Netra SPARC T3-1B server module.

This document is for system administrators, technicians, service providers, and users who have experience administering computer systems.

This chapter provides the following information:

Identifying the Netra Chassis Models

‘Supported Modular Components

Supported Versions of Oracle Solaris OS, Firmware, and Software

Patch Information

Oracle Solaris OS Has Changed How It Specifies Logical Device Names

Identifying the Netra Chassis Models

This section replaces similar information in the service manual. There are four Netra 6000 chassis models. Two models are AC and two are DC. Some server modules and some components will only work together in a certain chassis, and that information is also provided in these product notes.

Netra 6000 Modular System Chassis Marketing Number	CMM ILOM Firmware	T3-1B Server Module Support
N6000-AC 594-6438	3.X	Not supported
N6000-DC 594-6726	3.X	Not supported
N6000-AC 7100418 594-6893	4.X	Yes
N6000-DC 7100417 594-6892	4.X	Yes

The most visible difference between the two chassis models is the CMM on the rear of the chassis.

The illustration shows the two different CMM LED arrangements.

Left: CMM (501-7379) on the N6000-AC 594-6438 chassis, and the N6000-DC 594-6726 chassis.

Right: CMM (511-1531) on the N6000 DC 7100417 chassis and the N6000 AC 7100418 chassis.

Right: CMM Product Part Number 7019286 or higher on the 7100417 chassis and the 7100418 chassis. (This CMM is required to support the Sun Blade 6000 Virtualized 40GbE Network Express Module)

‘Supported Modular Components

The following table lists the modular components that are supported with the Sun Netra SPARC T3-1B server module.

Note - For the latest information on hardware component requirements, refer to the product notes for your component.

Product Model Number and Name	Notes
NEMs
NEM 2073A - Sun Blade 6000 Ethernet Switched Network Express Module 24p 10GbE NEM	Requires: For 10GbE network connectivity - FEM 4871A-Z, or FEM 4871A-Z-N. Refer to the NEM documentation at: `http://www.oracle.com/pls/topic/lookup?ctx=E19285-01`
NEM 4250A - Sun Blade 6000 Network Express Module 10-port 1 GbE Pass-Through NEM	Provides GbE connectivity - no FEM required.
RAID Express Modules (REMs)
SG-SAS6-REM-Z Sun Blade 6000 RAID 0/1 SAS2 HBA REM	For internal storage connectivity.
Fabric Expansion Modules (FEMs)
X5735A 10GbE XAUI Pass-Through FEM	For 10GbE network connectivity. Must be installed in the FEM X and FEM 0 motherboard connectors.
X4871A-Z Dual 10GbE PCIe 2.0 FEM (Intel)	For 10GbE network connectivity. Must be installed in the FEM 0 motherboard connector.
7100283 (ATO) / 7100633 (PTO) PCI-E Pass-Through FEM	Must be installed in the FEM 0 and FEM 1 motherboard connectors.
PCIe Expansion Modules (PCIe EMs)
7100486, 7100487, Quad Gigabit Ethernet Express Module MMF PCI EM, (Fiber)
7100483, 7100484, Quad Gigabit Ethernet UTEP Express Module (copper)	Requires shielded twisted pair ethernet cable to meet NEBS Level 3 ESD requirements.
SGX-SAS6-EM-Z SAS2 Dual Port Express Module
SG-XPCIEFCGBE-Q8-Z 2x8Gb FC and 2xGbE Combo Express Module	Must have part number 375-4522-02 or a higher dash level.
SG-XPCIEFCGBE-E8-Z-N 2x8Gb FC and 2x GbE Combo Express Module
X7284A-Z-N 1GbE Quad Port ExpressModule, Copper
X1110A-Z 10GbE Dual Port SFP+ Express Module

Supported Versions of Oracle Solaris OS, Firmware, and Software

The OS and firmware are preinstalled at the factory. The following table lists the supported versions of Oracle Solaris OS, firmware, and software.

Software	Supported Versions
Oracle Solaris OS on the server module host	10 9/10 (Minimum) 10 10/09 OS with Oracle Solaris 10 9/10 Patch Bundle
Electronic prognostics on the server module host	1.1.1 Note - This software provides early warning of the potential for specific FRU faults.
System firmware on server module (patch ID that provides this version)	Minimum version: 8.0.5.a (includes Oracle ILOM 3.0) (patch ID 145670-02 or later)
Oracle VM Server for SPARC (LDoms)	2.0
Chassis management module (CMM) Software	4.0.1 or later

Patch Information

Any patches that were known to be needed at the time your server module was prepared for shipment were installed at the factory. However, if you reinstall the OS, see the following lists to understand which patches you must install.

Required patches for Oracle Solaris 10 9/10 OS:

143647-08 or later

144488-03 or later

144567-01 or later

145868-01 or later

145961-01 or later

Required patches for Oracle Solaris 10 10/09 OS:

Oracle Solaris 10 9/10 Patch Bundle

All required patches for Oracle Solaris 10 9/10 OS

Access OS, Patch, and Firmware Updates

1. Access the latest OS, patches, and firmware information from the system administration portal.

Go to:

http://www.oracle.com/technetwork/systems/software-stacks/stacks/index.html

2. Under the Netra Carrier-Grade Systems heading, select the Netra SPARC T3-1B Server Module link.

Power Calculator

The Sun Netra 6000 Modular System power calculator is available at:

http://www.oracle.com/us/products/servers-storage/sun-power-calculators/calc/netra-6000-power-calculator-519736.html

Oracle Solaris OS Has Changed How It Specifies Logical Device Names

The Oracle Solaris OS now uses world wide ID (WWID) in place of the tn (target ID) field in logical device names for all SAS 2.0 storage controllers including the Sun Blade 6000 RAID 0/1 SAS2 HBA REM (SG-SAS6-REM-Z) when installed in this server module.

This change affects how you identify the target disk when downloading the OS over a network. The following points are key to understanding the impact of this change:

When downloading the OS over a network, specify the disk in HDD slot 0 as the download destination. OBP uses this disk as the default boot device.

Before the change to using WWIDs, this disk was known to the OS by the logical name c0t0d0.

With the change, the device identifier for the default boot device is now referred to as c0tWWIDd0, where WWID is a hexadecimal value. This WWID value does not map in a predictable way to the physical ID of the disk in HDD slot 0.

To reliably specify HDD slot 0 for the OS download operation, you must determine the correspondence between the WWID value for that disk and its physical location. You can do this by running probe-scsi-all and reading the output.

In the probe-scsi-all output, look for the following disk identifiers:

SASDeviceName - The WWID that the Oracle Solaris OS recognizes.

SASAddress - The WWID that the OpenBoot PROM references.

PhyNum - The physical HDD slot that the disk occupies. This number is also expressed as a hexadecimal value.

Your server module has one on-board SAS controller, which controls all four connected drives. This example shows probe-scsi-all output for a Netra SPARC T3-1B server module with two drives.

Note - In the example, the disk installed in HDD slot 0 has a PhyNum value of 0, the SASDeviceName is 5000c500231694cf, and the Target number is 9.

{0} ok probe-scsi-all
/pci@400/pci@1/pci@0/pci@7/pci@0/usb@0,2/hub@5/storage@3
  Unit 0   Removable Disk     smiUnigen  PSA4000         1100
 
/pci@400/pci@1/pci@0/pci@7/pci@0/usb@0,2/hub@3/storage@2
  Unit 0   Removable Read Only device    AMI     Virtual CDROM   1.00
 
/pci@400/pci@1/pci@0/pci@2/LSI,sas@0     <===== SAS Controller
 
MPT Version 2.00, Firmware Version 4.05.52.00
 
Target 9
  Unit 0   Disk     SEAGATE ST930003SSUN300G0868    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

Oracle Solaris Jumpstart Example

This Oracle Solaris Jumpstart profile example shows how to use the WWID syntax when installing the OS on a specific disk drive. The SASDeviceName is taken from the previous configuration listing.

Note - The Oracle Solaris syntax rules require all alpha characters to be capitalized.

#
install_type flash_install    
boot_device c0t5000C500231694CFd0 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 disks as the targets for the OS installation. The purpose of this step is to ensure that enough disk capacity is provided for the installation. For this step, specify the disk with the WWID value corresponding to the drive on which you want to install the software.

These WWID values are illustrated in the following interactive example,. The drive selected as the install target is located in HDD slot 0, the default OBP location.

Note - If you prefer other disk, you can specify it instead of the disk 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
=============================================================================
[ ] c0t5000C50003D37FCBd0-----------286090 MB
[X] c0t5000C500231694CFd0-----------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