JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Storage 6580 and 6780 Arrays

Hardware Release Notes, Release 6.9.x Update

search filter icon
search icon

Document Information

1.  Sun Storage 6580 and 6780 Array Hardware Release Notes

What's In This Firmware Release

Platform and Firmware Patch IDs

Downloading Patches and Updates

Cache Battery Expiration Notification

About the Array

System Requirements

Firmware Requirements

Updating Controller Firmware

Disk Drives and Tray Capacity

Array Expansion Module Support

Data Host Requirements

Multipathing Software

Supported Host Bus Adaptors (HBAs)

Supported FC and Multilayer Switches

Supported Premium Features

Tier 1 Support

Tier 2 Support

ALUA/TPGS with VMware

Procedure (Offline)—for ESX4.1U2, ESXi5.0 and prior

Procedure (Offline)—starting at ESX4.1U3, ESXi5.0U1 and above

Notable Fixes

Restrictions and Known Issues

Installation and Hardware Related Issues

Single Path Data Connections

Setting the Tray Link Rate

Controller Issues

Log Events Using SLES 11.1 With smartd Monitoring Enabled

After Re-Installing the Oracle Virtual Machine (OVM) Manager, International Standards Organizations (ISO) Files Are Listed by Universally Unique Identifier (UUID) Rather Than by Friendly Name

After Un-Mapping a Volume from an Oracle Virtual Machine (OVM) Server, the Volume Continues to Appear in the Storage Database on the Server

In the Oracle Virtual Machine (OVM) Manager User Interface, Only One Drive at a Time Can Be Selected for Deletion

Kernel Panics During Controller Firmware (CFW) Download

BCM Driver Fails to Load

Kernel Panics During Controller Firmware Download

Network Interface on Device eth0 Fails to Come Online When Booting a Host

When Over 128 Volumes are Mapped to a Host, Paths to Only the First 128 Volumes are Restored after the Controller is Reset

Unable to Add More Than 117 Volumes to the Oracle Virtual Machine (OVM) Manager Database

Write-Back Cache is Disabled after Controllers Reboot with Multiple Failed Volumes in a Storage Array

During Multiple Node Failover/Failback Events, Input/Output (I/O) Operations Time Out Because a Resource is Not Available to a Cluster

After an NVSRAM Download, a Controller Reboots a Second Time when the NVSRAM is Activated

When a Controller is Not Set Offline Before Being Replaced, an Exception Occurs when the Replacement Controller is Brought Online

Input/Output (I/O) Errors Occur when a Cable is Disconnected between a Host and a Controller, and the Alternate Controller is Unavailable

Backup Failure or I/O Errors with Snapshot Creation or Mounting Failure During Backup of Cluster Shared Volumes (CSV)

Data is Misread when a Physical Drive Has an Unreadable Sector

Solaris 10 Guest in Fault Tolerant Mode Is Unable to Relocate Secondary Virtual Machine (VM) Upon Host Failure

Documentation Issues

Total Cache Size Specification for Sun Storage 6780 Array

Inaccurate Cabling Diagrams in Hardware Installation Guide

Product Documentation

Documentation, Support, and Training

ALUA/TPGS with VMware

The following procedures describe how to add ALUA/TPGS with VMware support. Starting with firmware 07.84.44.10, the ALUA/TPGS enabled arrays will be managed by the VMW_SATP_ALUA plug-in. Arrays with firmware previous to 07.84.44.10 will be managed by the current VMW_SATP_LSI plug-in.

Prerequisite:

  1. Firmware version previous to 07.84.44.10 is loaded on controllers.

  2. Current storage array devices are managed by the standard VMW_SATP_LSI plug-in.

  3. Management host is available.

  4. Starting with firmware 07.84.44.10, the ALUA/TPGS enabled arrays will be managed by the VMW_SATP_ALUA plug-in.

  5. Non-TPGS array will be managed by the current standard VMW_SATP_LSI plug-in.

  6. Path policy supported is still Round-Robin (RR) or Most Recently Used (MRU).

For more information, refer to one of the following guides:VMware Compatibility Guide for 6580 arrays:

VMware Compatibility Guide for 6780 arrays:

Procedure (Offline)—for ESX4.1U2, ESXi5.0 and prior

  1. Verify that firmware 07.84.44.10 is installed on the management host.

    Currently, VMware (i.e. ESXi5.0 and 4.1u1/u2) do not have the claim rules automatically set to select the VMW_SATP_ALUA to claim our arrays that have the TPGS bit enabled. You must manually add the claim rule in ESX.

    The following example adds the claim rule for the 6580 or 6780 using VID/PID = SUN/STK6580_6780.

    1. To manually add the SATP rule in ESX 4.1Ux:

      Open a terminal to the ESX host and run the following commands:

      # esxcli nmp satp deleterule -s VMW_SATP_LSI -V SUN -M STK6580_6780

      # esxcli nmp satp addrule -V SUN -M STK6580_6780 -c tpgs_off -s VMW_SATP_LSI

      Reboot the ESX host.

    2. To manually add the SATP rule in ESXi 5.0:

      Open a terminal to the ESX host and run the following command:

      # esxcli storage nmp satp rule add -s VMW_SATP_ALUA -V SUN -M STK6580_6780 -c tpgs_on

      Reboot the ESX host.

  2. Verify the claim rule is added in ESX:
    • ESX 4.1

    1. To show a list of all the claim rules: # esxcli nmp satp listrules
    2. List only the claim rules for the VMW_SATP_LSI: # esxcli nmp satp listrules -s VMW_SATP_LSI
    3. Verify that the claim rule for the VID/PID is SUN/STK6580_6780 and the 'Claim Options' 'tpgs_off' flag is specified.
      • ESXi 5.0
    4. To show a list of all the claim rules: # esxcli storage nmp satp rule list
    5. List only the claim rules for the VMW_SATP_ALUA: # esxcli storage nmp satp rule list -s VMW_SATP_ALUA
    6. Verify that the claim rule for VMW_SATP_ALUA is VID/PID SUN/STK6580_6780 and the 'Claim Options' 'tpgs_on' flag is specified.
  3. Upgrade the storage array controllers to firmware 07.84.44.10 and NVSRAM versions.
  4. From the host management client, verify that the host OS type is set to 'VMWARE'. Starting with firmware 07.84.44.10, 'VMWARE' host type will have the ALUA and TPGS bits enabled by default.
  5. Perform a manual re-scan and verify from the ESX host that the TPGS/ALUA enabled devices are claimed by the VMW_SATP_ALUA plug-in:

    To confirm that the host is using the ALUA plugin:

    • ESX 4.1

    1. Run the command: # esxcli nmp device list
    2. The value for Storage Array Type should be "VMW_SATP_ALUA" on every device from the array with firmware 07.84.44.10. On arrays with firmware previous to 07.84.44.10, the value should be "VMW_SATP_LSI".
      • ESXi 5.0
    3. Run the command: # esxcli storage nmp device list
    4. The value for Storage Array Type should be "VMW_SATP_ALUA" on every device from the array with firmware 07.84.44.10. On arrays with firmware previous to 07.84.44.10, the value should be "VMW_SATP_LSI".

Procedure (Offline)—starting at ESX4.1U3, ESXi5.0U1 and above

  1. Verify that firmware 07.84.44.10 is installed on the management station.
  2. Starting with ESXi5.0 U1 and ESX4.1U3, VMware will automatically have the claim rules to select the VMW_SATP_ALUA plug-in to manage arrays that have the TPGS bit enabled. All arrays with the TPGS bit disabled will continue to be managed by the VMW_SATP_LSI plug-in.
  3. Upgrade the storage array controllers to firmware 07.84.44.10 and NVSRAM versions.
  4. From the Host Management client, verify that the host OS type is set to 'VMWARE'. Starting with firmware 07.84.44.10, 'VMWARE' host type will have the ALUA and TPGS bits enabled by default.
  5. Perform a manual re-scan and verify from the ESX host that the TPGS/ALUA enabled devices are claimed by the VMW_SATP_ALUA plug-in:

    To confirm that the host is using the ALUA plugin:

    • ESX 4.1

    1. Run the command: # esxcli nmp device list
    2. The value for Storage Array Type should be "VMW_SATP_ALUA" on every device from the array with firmware 07.84.44.10 installed. On arrays with firmware previous to 07.84.44.10, the value should be "VMW_SATP_LSI".
      • ESXi 5.0
    3. Run the command: # esxcli storage nmp device list
    4. The value for Storage Array Type should be "VMW_SATP_ALUA" on every device from the array with firmware 07.84.44.10 installed. On arrays with firmware previous to 07.84.44.10, the value should be "VMW_SATP_LSI".