JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Storage 2500-M2 Arrays

Hardware Release Notes, Release 6.10

search filter icon
search icon

Document Information

1.  Sun Storage 2500-M2 Arrays Hardware Release Notes

What's New in This Release

Product Overview

About the Management Software

System Requirements

Firmware Requirements

Supported Disk Drives and Tray Capacity

Array Expansion Module Support

Data Host Requirements

Multipathing Software

Supported Host Bus Adaptors (HBAs)

Supported FC and Multilayer Switches

Expansion Tray Specifications

ALUA/TPGS Multipathing with VMware

Procedure for ESX4.1U2 and ESXi5.0

Procedure for ESX4.1U3 and ESXi5.0U1

Restrictions and Known Issues

Restrictions

Single Path Data Connections

SAS Host Ports on the Sun Storage 2540-M2

Controller Issues

Log Events 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

Tasks Aborts Are Logged During a Controller Firmware Upgrade

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 Disconnection of Devices from a SAS Switch Is Not Detected

A Path Failure and Premature Failover Occur when a Cable is Disconnected between a Host and a Controller

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

With 3 Gb/s SAS Host Bus Adapters (HBAs) and Heavy Input/Output (I/O), I/O Timeouts Occur During a Controller Firmware Upgrade

Host Operating System Logs "Hung Task" During a Path Failure

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

With Multiple SAS Hosts Using Single‐PHY, a Host Cable Pull During Input/Output (I/O) Operations Causes a Controller Reboot

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 Bugs

Hardware Installation Guide

Related Documentation

Documentation, Support, and Training

ALUA/TPGS Multipathing with VMware

The following procedures describe how to enable ALUA/TPGS multipathing with VMware support to an array. Starting with firmware 07.84.44.10, multipathing to ALUA/TPGS-enabled arrays is provided by the VMW_SATP_ALUA plug-in. Arrays with firmware previous to 07.84.44.10 use the VMW_SATP_LSI plug-in.

Prerequisites:


Note - The path policy supported is Round-Robin (RR) or Most Recently Used (MRU).


Procedure for ESX4.1U2 and ESXi5.0

VMware versions ESX4.1u1/u2 and ESXi5.0 (and earlier) do not automatically enable ALUA/TPGS multipathing for arrays that offer this feature. You must manually enable multipathing as described below.

VID/PID values:

  1. Install CAM software with firmware version 07.84.44.10 (minimum) on the management host.

  2. To enable ALUA/TPGS multipathing support for ESX 4.1Ux or ESX 5.0:

    • For ESX 4,1, open a terminal to the ESX host and run the commands:

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

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

      Reboot the ESX host.

    • For 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 LCSM100_F -c tpgs_on

      Reboot the ESX host.

  3. Verify the claim rule is added in ESX.

    For ESX 4.1:

    1. 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 the VID/PID is SUN/LCSM100_F for 2540-M2 (or SUN/LCSM100_S for 2530-M2) and the Claim Options flag tpgs_off is set.

    For ESXi 5.0:

    1. Show a list of all the claim rules:

      # esxcli storage nmp satp rule list

    2. List only the claim rules for the VMW_SATP_ALUA:

      # esxcli storage nmp satp rule list -s VMW_SATP_ALUA

    3. Verify the VID/PID for VMW_SATP_ALUA is SUN/LCSM100_F for 2540-M2 (or SUN/LCSM100_S for 2530-M2) and the Claim Options flag tpgs_on is set.

  4. Upgrade the controller firmware to 07.84.44.10 (minimum) and its corresponding NVSRAM version via the management host. The controller firmware and NVSRAM are part of the CAM baseline.

  5. Using CAM, verify the VM host initiator host type is set to VMWARE. Starting with firmware 07.84.44.10, the VMWARE host type defaults to ALUA/TPGS multipathing.

  6. On the ESX host, perform a manual re-scan.

  7. Verify the 7.84 ALUA-enabled arrays have the VMW_SATP_ALUA plug-in, as follows.

    • For ESX 4,1, run the command:

      # esxcli nmp device list

    • For ESXi 5.0, run the command:

      # esxcli storage nmp device list

    For LUNs from arrays with firmware version 07.84.44.10 (and later), the value is VMW_SATP_ALUA. For LUNs from arrays with firmware version previous to 07.84.44.10, the value is VMW_SATP_LSI.

Procedure for ESX4.1U3 and ESXi5.0U1

Starting with ESX4.1U3 and ESXi5.0 U1, VMware automatically enables the VMW_SATP_ALUA plug-in for arrays that offer ALUA/TPGS multipathing.

  1. Install CAM software with firmware version 07.84.44.10 (minimum) on the management host.

  2. Upgrade the controller firmware to 07.84.44.10 (minimum) and its corresponding NVSRAM version via the management host. The controller firmware and NVSRAM are part of the CAM baseline.

  3. Using CAM, verify the VM host initiator host type is set to VMWARE. Starting with firmware 07.84.44.10, the VMWARE host type defaults to ALUA/TPGS multipathing.

  4. On the ESX host, perform a manual re-scan.

  5. Verify the VMW_SATP_ALUA plug-in is enabled.

    • For ESX 4.1, run the command:

      # esxcli nmp device list

    • For ESXi 5.0, run the command:

      # esxcli storage nmp device list

    For LUNs from arrays with firmware version 07.84.44.10 (and later), the value is VMW_SATP_ALUA. For LUNs from arrays with firmware version previous to 07.84.44.10, the value is VMW_SATP_LSI.