Sun Blade T6320 G2 and Sun Blade T6320 Server Modules Product Notes

Late-Breaking Issues

This section provides the following information on known hardware issues for the Sun Blade T6320 server module:

• Storms of Events Might Impact Logging of Telemetry Data (CR 6983799)
• 200-Gbyte SATA Hard Drive Vibration Sensitivity
• Drive OK-to-Remove LED Might Not Work When Using the cfgadm -c unconfigure Command (CR 6946124)
• cfgadm Does Not Unconfigure the Path When Multipathing Software Is Enabled (CR 6948701)
• Locate Button Is Inoperative (CR 6862442)
• Hot-Insertion of Blade Not Recognized by CMM - Intermittent (CR 6855886)
• Kernel Errors Reported (CR 6839498 and 6533591)

---

Storms of Events Might Impact Logging of Telemetry Data (CR 6983799)

Modular systems might experience issues when handling error events, where error telemetry might not be processed or logged by the service processor to the host upon processing a stream of error events. This problem can occur when the server module is running system firmware 7.2.10.a and earlier.

Workaround: Upgrade system firmware to 7.3.0 (or later). See Supported Versions of the Oracle Solaris OS, Firmware, and Patches.

---

200-Gbyte SATA Hard Drive Vibration Sensitivity

The 200-Gbyte SATA hard drive (option model XRA-ST2CF-200G5K) could experience significant throughput degradation if external vibration is applied to the system chassis in the Z-axis (vertical axis) in the range of 100-400 Hz. The drive might exhibit slow response or possibly go offline with sustained forces up to or beyond 0.17 G (Sun test standard) in this vibration frequency range.

Workaround: If the chassis is in this environment and these symptoms are exhibited, performance can be improved by relocating the server to the slots toward the center of the chassis and placing the SATA drives in the lower two slots of the server.

---

Drive OK-to-Remove LED Might Not Work When Using the cfgadm -c unconfigure Command (CR 6946124)

When a SAS2 capable REM is installed in the server module, using the cfgadm -c unconfigure command fails to illuminate the drives OK-to-Remove LED making it difficult to identify which drive to remove.

Workaround: If you are still uncertain about the location of the drive, perform the following procedure.

1. Run format utility and select the device that you need to locate.

Example:

# format 
Searching for disks...done 
AVAILABLE DISK SELECTIONS: 
       0. c0t5000C5000F8AD1FFd0 <SUN300G cyl 46873 alt 2 hd 20 sec 625> 
          /scsi_vhci/disk@g5000c5000f8ad1ff 
       1. c0t5000C5000F8BB997d0 <SUN300G cyl 46873 alt 2 hd 20 sec 625> 
          /scsi_vhci/disk@g5000c5000f8bb997 
       2. c0t5000C50003D3D85Bd0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> 
          /scsi_vhci/disk@g5000c50003d3d85b 
       3. c0t5000C50012EEE447d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> 
          /scsi_vhci/disk@g5000c50012eee447 
       4. c0t5000C5000258C457d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> 
          /scsi_vhci/disk@g5000c5000258c457 
       5. c0t5000CCA00A4A924Cd0 <SUN300G cyl 46873 alt 2 hd 20 sec 625> 
          /scsi_vhci/disk@g5000cca00a4a924c 
 
Specify disk (enter its number): 4 
selecting c0t5000C5000258C457d0    <<==

2. Make note of the cntndn number associated with the drive.

For example, in the previous output example, the string to note is
c0t5000C5000258C457d0.

3. Type q to exit the format utility.

4. Find the serial number for the device:

a. Redirect the output of the iostat command to a file.

Example:

# iostat -En > iostat_output

b. In the file, search for the string you noted in Step 2.

You can use an editor and search for the string. In the following example, we are searching for c0t5000C5000258C457d0.

c0t5000C50003D3D85Bd0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: SEAGATE  Product: ST973402SSUN72G  Revision: 0603 Serial No: 0715215EVK 
Size: 73.41GB <73407865856 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c0t5000C5000258C457d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: SEAGATE Product:ST973451SSUN72G Revision: 0302 Serial No:0802V16VTE <<==
Size: 73.41GB <73407865856 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c1t0d0           Soft Errors: 4 Hard Errors: 2 Transport Errors: 0 
Vendor: AMI      Product: Virtual CDROM    Revision: 1.00 Serial No: 
Size: 0.00GB <0 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 2 Recoverable: 0 
Illegal Request: 4 Predictive Failure Analysis: 0 
c0t5000CCA00A4A924Cd0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: HITACHI  Product: H103030SCSUN300G Revision: A2A8 Serial No: 0950GA0B7E 
Size: 300.00GB <300000000000 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c0t5000C50012EEE447d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: SEAGATE  Product: ST914603SSUN146G Revision: 0768 Serial No: 092180GMM6 
Size: 146.81GB <146810536448 bytes> 
/c0t5000C5000258C457d0 

c. Identify the serial number associated with the string.

In the previous example, 0802V16VTE is the serial number.

5. Change to the directory where you installed the SAS2IRCU utility.

For information on downloading and installing the SAS2IRCU utility, refer to the Sun Storage 6 Gb SAS REM HBA Installation Guide.

6. Find the SAS2 controller number (shown under Index) using the sas2ircu LIST command.

Example:

# ./sas2ircu LIST
LSI Corporation SAS2 IR Configuration Utility.
Version 3.250.02.00 (2009.09.29)
Copyright (c) 2009 LSI Corporation. All rights reserved.
 
 
        Adapter      Vendor  Device                       SubSys  SubSys
Index    Type          ID      ID    Pci Address          Ven ID  Dev ID
-----  ------------  ------  ------  -----------------    ------  ------
  0     SAS2008     1000h    72h   00h:700h:00h:00h      1000h   3180h
SAS2IRCU: Utility Completed Successfully.

7. Redirect the output of the sas2ircu n display command to a file, where n is the controller number from Step 6.

Example:

# ./sas2ircu 0 display > sas2ircu_output

8. In the output file, search for the serial number obtained from Step 4.

# cat sas2ircu_output
 
Device is a Hard disk
 Enclosure #                             : 1              <<==
 Slot #                                        : 1					      <<==
 State                                          : Ready (RDY)
 Size (in MB)/(in sectors)               : 70007/143374737
 Manufacturer                            : SEAGATE
 Model Number                           : ST973451SSUN72G
 Firmware Revision                       : 0302
 Serial No                               : 0802V16VTE
 Protocol                                : SAS
 Drive Type                              : SAS_HDD

9. In the output, look for the enclosure # and slot # that correspond to this device.

• If the Enclosure # is 1:

The drive is in a server module. The Slot # refers to slot number on the server module. In the previous example, Slot # 1 corresponds to HDD1 on the front panel of the server module.

Locate the drive and do not complete the remaining steps in this procedure.

• If the Enclosure # is any number other than 1:

The drive is in a storage module. The Slot # refers to the slot number on the storage module.

Perform the remaining steps in this procedure.

10. To locate the drive in storage module, use the sas2ircu LOCATE command.

The locate ID on the drive will start blinking (amber).

Example specifying a drive in enclosure # 6, slot # 7:

# ./sas2ircu 0 LOCATE 6:7 ON

11. After replacing the drive, turn off the locate LED.

Example specifying a drive in enclosure # 6, slot # 7:

# ./sas2ircu 0 LOCATE 6:7 OFF

---

cfgadm Does Not Unconfigure the Path When Multipathing Software Is Enabled (CR 6948701)

The cfgadm -c unconfigure command fails if the path specified is an mpxio enabled device.

Workaround: This issue is fixed in the Oracle Solaris 9/10 OS and in kernel patch 14909-13 (or later). If you are unable to install Oracle Solaris 9/10 OS or patch 14909-13, perform the following procedure.

1. Start the format utility to see the drives and to obtain the drive numbers (such as c0t5000C5000F0E5AFFd0) for the drive you plan to unconfigure.

# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t5000C5000F0E5AFFd0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/scsi_vhci/disk@g5000c5000f0e5aff
1. c0t5000C5000F0FE227d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
 /scsi_vhci/disk@g5000c5000f0fe227

2. To exit the format utility, select one of the drives and type q.

Specify disk (enter its number): 1
selecting c0t5000C5000F0FE227d0

3. Use the mount command to identify whether the device is mounted or if it is a boot drive.

• The following example shows the output when the drive is mounted:


# mount | grep c0t5000C5000F0E5AFFd0 /mnt on /dev/dsk/c0t5000C5000F0E5AFFd0s6 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=600016 on Fri Jun 4 10:37:08 2010


• The following example shows the output when the drive is a boot drive:


# mount | grep c0t5000C5000F0FE227d0 / on /dev/dsk/c0t5000C5000F0FE227d0s0 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=800010 on Wed Jun 9 09:58:24 2010 /export/home on /dev/dsk/c0t5000C5000F0FE227d0s7 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=800017 on Wed Jun 9 09:59:13 2010

4. Based on your results, do one of the following:

• If the disk is a not boot drive, go to Step 5.
• If the disk is a boot drive, go to Step 6.

5. Identify the processes running on the drive:

a. Run the fuser command to identify the processes accessing the disk.

• The following example shows there are no processes using the disk:


# fuser -d /dev/dsk/c0t5000C5000F0E5AFFd0s2 /dev/dsk/c0t5000C5000F0FE227d0s2:


• The following example shows a process accessing the disk, followed by the process ID (PID):


# fuser -d /dev/dsk/c0t5000C5000F0FE227d0s2 /dev/dsk/c0t5000C5000F0FE227d0s2: 1036o

b. If you identify a process, use the ps command to further identify the process.

Example:

# ps -ef | grep 1036
root 1036 982 0 11:56:34 pts/2 0:02 dd if=/dev/dsk/c0t5000C5000F0E5AFFd0s2 of=/dev/dsk/c0t5000C5000F0FE227d0s7

c. Kill processes identified in Step b using kill -9 PID.

d. Use the umount command to unmount any mount points and then run sync command to synchronize the disk.

Example:

# umount /mnt
 
# mount | grep c0t5000C5000F0E5AFFd0
 
# sync

e. Remove the disk, and do not continue with subsequent steps in this procedure.

6. If the drive is a boot drive, run the following commands to synchronize the drive and shutdown the system:

# sync
 
# init 0

7. Remove the disk.

---

Locate Button Is Inoperative
(CR 6862442)

Pressing the Locate button on the front panel does not toggle the Locator LED on or off. This problem is not present on server modules running System Firmware version 7.1.x.

Workaround: Control the Locator LED using the one of the following commands:

• From the ILOM CLI:


-> set /SYS/LOCATE value=on <or> -> set /SYS/LOCATE value=off


• From the ALOM CMT CLI:


sc> setlocator on <or> sc> setlocator off

Fix: Update the server module SP System Firmware to version 7.2.4.e or later.

---

Hot-Insertion of Blade Not Recognized by CMM - Intermittent (CR 6855886)

There is an intermittent problem with hot-insertions. This problem only applies to modular systems that are running CMM firmware 3.0.3.32.

When you perform a hot-insertion of the Sun Blade T6320 server module, sometimes the CMM does not detect the insertion. When you check for the presence of the blade using the CMM CLI or Web UI, no indication of the blade is displayed.

If this failure is not corrected, undetected blades might not receive adequate temperature management and might hit upper temperature limits.

Workaround: If you inserted a blade and it is not recognized, reset the CMM with the following command:

-> reset /CMM
 

---

Kernel Errors Reported (CR 6839498 and 6533591)

Some server modules with less than 64 G-bytes of memory might display kernel warning messages during high activity.

Examples:

panic . . . cannot satisfy mandatory allocation
 

. . . DL_BADADDR observed on nxge . . .

Workaround: This issue is fixed in the Oracle Solaris 9/10 OS and in kernel patch 142909-13 (or later). If you are unable to install this OS or patch, you might be able to improve this condition by increasing the memory on your server module.

Sun Blade T6320 G2 and Sun Blade T6320 Server Modules Product Notes

E37211-01

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.