Sun StorageTek 5000 NAS OS Software Release Notes
These release notes contain information for the Sun StorageTek 5000 NAS OS version 4.12. The software is backward-compatible with previous versions of the Sun StorEdge 5210 NAS Appliance, Sun StorEdge 5310 NAS family of products, and the Sun StorageTek 5320 NAS family of products.
These release notes contain the following sections:
Note - There is no means to upgrade a Sun StorEdge 5310 NAS Appliance to a Sun StorageTek 5320 NAS Appliance. At a later date an upgrade package and support services will be available to allow the upgrade of a Sun StorEdge 5310 NAS Appliance to a Sun StorageTek 5320 NAS Appliance.
The Sun StorageTek NAS operating system (OS) 4.12 provides support for the following items:
With the release of Sun StorageTek NAS OS 4.12, Sun Microsystems, Inc. has chosen to re-brand the 5000 NAS Family software with the Sun StorageTek brand to reflect our continued and increased commitment to the storage market. Sun StorageTek NAS OS 4.12 along with the StorageTek File Replicator and StorageTek Compliance Archiving Software options provide support for the following platforms:
The Sun StorageTek NAS OS is pre-installed on all supported platforms. You do not need to install any software to manage the Sun StorageTek 5320 NAS Appliance or Sun StorageTek 5320 NAS Gateway System.
To access the Web Administrator management interface, you must have a network-attached computer running one of the following browsers. You must use a Java technology-enabled browser with Java Plug-In 1.4.0 (minimum version).
Perform one of the following procedures.
Use the raidctl get type=lsi target=profile ctlr=0..N command to determine and record the current firmware revision level of each RAID controller unit, expansion unit, controller NVSRAM, and drive.
For more information, see:
Please upgrade your system by downloading the latest version of Sun StorageTek NAS OS software from http://sunsolve.sun.com. This requires a valid service contract. Select the Patchfinder link, and then enter the patch number that is appropriate for your system.
Note - If you are upgrading a Sun StorEdge 5210 NAS Appliance to software version 4.12 from a release prior to version 4.05, Field Change Order (FCO) 257 is required. Contact SunSM Service to get FCO 257 applied prior to upgrading your software. Any Sun StorEdge 5210 NAS Appliance with software version 4.05 (or greater) does not need the FCO applied.
Downgrading to an earlier version of the Sun StorageTek NAS OS other than what is loaded on your system, as indicated on the Shutdown the Server screen of the Web Administrator GUI, is not supported. If required, contact Sun service. When the software is upgraded the previous release remains on the system. So you can reboot to the previous release.
The following issues have been resolved with this release. The numbers in the parentheses indicate the Change Request.
The numbers in the parenthesis indicate the Change Request.
Important - The Web Administrator supports only a single login at a time. A best practice would thus be to have only one person administering the system at a time to avoid command conflicts. In a cluster configuration, you must log in to each server separately to manage that server.
The following issues are not resolved at this time. The numbers in the parenthesis indicate the Change Request.
Workaround: Run the raidctl get command on the local system. The command will save it's output to a file. Then send the file over a network using ftp, email, or some other method
Workaround: This might be due to a controller error that causes the controller to reboot. After it has finished rebooting the system log should report that the temperature sensor is fine within five minutes.
Workaround: Do not create HA bonds of more than seven ports.
Workaround: Before enabling Anti-Virus protection, make sure there are no client connections to CIFS-mapped shares, or reboot the system after enabling anti-virus protection to force all client connections to reconnect.
Workaround: Configure the anti-virus scan engine to allow access to all malformed containers, and allow access to files when a processing limit is met (or exceeded). Note that files actually infected with viruses will still be overwritten.
Workaround: Set LUN paths manually. Alternatively, initialize a new LUN by creating a file volume.
Workaround: Following are the three different ways that fans are identified. Email notification uses the same method as the syslog.
Workaround: Evaluate the power supply LEDs. Then check the enclosure section of the diagnostic info from the CLI. If a fan failure has occurred contact Technical Support.
Workaround: Refer to the "Days until replacement:" information in the raidctl profile for a more accurate report of battery replacement needs.
Workaround: The system will work correctly and this may be ignored. To fix the system must go through the recovery process.
Workaround: You must login to the console of the Sun StorageTek 5320 NAS Appliance head and manually delete and reassign the incorrectly assigned ip addresses.
Workaround: You must delete all the IPs and recreate the list from the top field. Another option is to use the CLI.
Workaround: Finish editing. You will then be able to cancel the edit session.
Workaround: Use the on-board Fibre Channel / SCSI bridge on the robot to connect to a Fibre Channel port on the network attached storage (NAS). (6347059)
Workaround: This may be caused by duplicate SSIDs on the EUs. To bring the LUNs online, do the following.
1. Turn off all the storage arrays.
2. Turn on the controller array.
3. Wait for the array to complete power up.
4. Power on each drive module, waiting for each to complete power up before powering the next.
Workaround: Close the Web Administrator and browser. After restarting the Web Administrator the information provided should be correct.
Workaround: Contact SUN service.
Workaround: After physical changes to the back-end configuration, a user- initiated rescan is required. Using the Web Administrator, go to Volume Operations Create File Volumes and click Scan for New Disks.
Workaround: Place the *LUNS* back on the *primary* path by using the Web Administrator.
Workaround: Close all instances of the Web Administrator and web browsers. After the system reboots, reopen a web browser and relaunch the Java browser interface.
Workaround: If the Domain Naming System (DNS) does not resolve the hostname, use the IP address to connect to the Sun StorEdge 5210 or 5310 NAS Appliance. Ensure that the host name defined in the Sun StorEdge 5210 or 5310 NAS Appliance is registered in a name server (for example, DNS or Network Information System (NIS)).
Workaround: Select a different IP address for the bond.
Workaround: If there are no other critical hardware errors and you see significant performance degradation, this degradation could be related to Fibre Channel link errors. Contact Sun Service for assistance. (See Service Contact Information.)
Wait for the system to finish processing and repaint the screen. Do not reboot your system.
Workaround: When reconfiguring SATA drives using the Web Administration tools, be sure to not go over the 2.0 Terabyte LUN maximum size limit of the RAID controller.
Workaround: This can occur when an offline LUN caused by a double fault is followed by a deletion of a file system from that LUN. A reboot is required.
The following cluster-specific issues are not resolved at this time. The numbers in the parenthesis indicate the Change Request.
Workaround: Enable failover on the partner head by logging into the partner head using the Web Administrator GUI.
Workaround: Repeat the head recovery process and check for the LUN to be returned to the appropriate head. The head recovery process can be initiated from the WEB or Telnet menu. This process can be repeated as many times as needed while the heads are in any failover state.
Workaround: Copy the Array Firmware, non-volatile static random access memory (NVSRAM), and Just a Bunch of Disks (JBOD) code to the Sun StorageTek 5320 NAS Appliance head. Manually load the NVSRAM and JBOD code (not the Array Firmware code) using the "No-reboot" instructions. Then reboot the Sun StorageTek 5320 NAS Appliance head. Please refer to the system log to verify that the firmware upgrade succeeded.
Workaround: Deleting the bond from the Web Administrator GUI may not properly clean up the duplicate IP addresses. Delete the bond from the CLI. Then make sure all NICs have been assigned IPs before recreating the bond.
Workaround: Remove existing PA bonds before installing new NICs. After the NIC installation is completed, and the system has rebooted, create new PA bonds.
If the bond was already created before installing the NICs go to the CLIs Host Name & Network menu and edit the IP addresses of the NICs. Then on the CLI on either of heads: (considering the bond is called bond1) perform the following.
Workaround: Use the Web Administrator GUI or the CLI/Telnet Menu to reboot a single head only.
Workaround: Perform another recover from the Alone head to ensure that your clusters are in Normal mode before doing any upgrades.
Workaround: Run a manual disk scan from either the Web Administrator or the Telnet Menu/CLI and the head will refresh the LUN capacity.
Workaround: Using the Telnet Menu / CLI, type the following command:
If physical access to the system is not available, you should Telnet to the cluster system. You will be logged into the Alone head. From there you can either check the log to ensure that the Quiet head has finished booting, or ping the Quiet head's heartbeat. By default the heartbeat IP is 10.10.10.1 for head 1 and 10.10.10.2 for head 2.
Workaround: Close all the browser instances, then restart the Web Administrator. This appears to occur with Mozilla variants of web browsers and not Internet Explorer.
The following replicator-specific issues are not resolved at this time. The numbers in the parenthesis indicate the Change Request.
Workaround: This problem can be avoided by unmounting and remounting the volume after renaming or attaching segments. The volume can be replicated after it has been remounted. Alternatively, the head can be rebooted instead of unmounting/remounting the volume. The target system (mirror) is not affected and does not need to be rebooted.
Workaround: Do not attempt mirroring without a valid File Replication license.
Workaround: You can break the mirror. Then recreate the mirror after enough space and partitions are available on the target system.
Workaround: Contact Sun Technical Support for help in re-establishing your mirror.
Workaround: Do a manual remount of the file volume from the CLI. For example, if the volume name is volx, type the following:
Workaround: This option is available via the Telnet menu. (6198789)
The following gateway-specific issues are not resolved at this time. The numbers in the parenthesis indicate the Change Request.
Workaround: Perform a recovery operation.
Workaround: Run the CLI disk disk-name command. If the owner of the LUN is listed as "noDPMGR," then the disk has residual data.
Run the following CLI command to clear the data and make the LUN usable.
This section includes information that is additional to or overrides information in the documentation. It contains the following topics.
In a NAS Cluster Gateway System, each head must have two Fibre Channel connections to a SAN storage unit. One Fibre Channel connection is insufficient for proper High Availability (HA) funtionality.
In a cluster system using In-Band RAID Management (IBRM), it is important that the HBA ports on head 2 link to the same RAID Controller as the ports on head 1 using the same sequence. The setup needs to be configured identically.
For example, if HBA port 2 on Head 1 is connected to Controller A, then HBA port 2 on Head 2 must be connected to Controller A on the same array controller. See FIGURE 1 for an example.
When you assign a LUN to each server in a gateway cluster configuration, you must manually scan the disk on both servers to pick up the new LUNs. You can scan for new disks using Web Admin in one of two ways:
This procedure describes how to add a new Sun StorEdge 5300 EU Expansion Enclosure to an existing Sun StorEdge 5310 NAS Appliance or Sun StorageTek 5320 NAS Appliance without shutting down the system.
The Sun StorEdge 5310 NAS Appliance must be at version 4.11 or the Sun StorageTek 5320 NAS Appliance must be at version 4.12 before you start the upgrade. If not, download and install the latest version of the Sun StorageTek 5000 NAS OS from http://sunsolve.sun.com.
If you are not familiar with how to access the Console Administrator, refer to Appendix A of the Sun StorEdge 5310 NAS Appliance and Gateway System Administration Guide or the Sun StorageTek 5320 NAS Appliance and Gateway System Administration Guide.
a. Use Telnet to connect to the Sun StorEdge 5310 NAS Appliance or Sun StorageTek 5320 NAS App[liance.
b. At the CLI, type:
1. Install the new expansion enclosure in an available slot in the cabinet.
Refer to the Sun StorEdge 5310 NAS Appliance and Gateway System Getting Started Guide or the Sun StorageTek 5320 NAS Appliance and Gateway System Getting Started Guide for rackmount installation procedures.
2. Set the new expansion enclosure to a unique ID.
Refer to the Sun StorEdge 5310 NAS Appliance and Gateway System Getting Started Guide or the Sun StorageTek 5320 NAS Appliance and Gateway System Getting Started Guide for information about setting the tray ID.
3. Connect the power cable to the new expansion enclosure.
4. Power on the new expansion enclosure.
Connect the new expansion enclosure to the existing RAID controller enclosure one data cable path at a time.
1. Connect data cable from port 2, Channel A of the last enclosure to port 1, Channel A of new expansion enclosure.
2. Remove data cable from port 2, Channel B of the last enclosure and connect to port 2 Channel B of the new expansion enclosure.
3. Connect data cable from port 2 Channel B of the last enclosure and connect to port 1 Channel B of the new expansion enclosure.
1. At the main menu, select D. Disks and Volumes.
2. Type 9 to scan for the new disk drives (and LUNs).
3. Verify that the new expansion enclosure, drives, and LUNs are detected.
4. Enable Sysmon, by entering the following commands.
iSCSI LUNs will provide optimal performance if the volumes they reside on are used exclusively for iSCSI LUNs. If these volumes also contain Common Internet File System (CIFS) shares or Network File System (NFS) mounts, the performance of the iSCSI LUNs might not be optimal (depending on the I/O traffic of each protocol).
The cluster power-on procedure in the Sun StorEdge 5310 NAS Appliance and Gateway System Getting Started Guide instructs you to power on server H1 first. To determine the H1 server, look for the software serial number (ending in -H1) on the label that is affixed to the back panel of the Sun StorageTek 5310 NAS Appliance server. If the label is not located at the back of the server, check the sheet metal on left side of the Sun StorageTek 5310 NAS Appliance server.
After multiple continuous reboots, one or more file systems may become unmounted. To mount the file systems, issue the following command: (6306480)
The Sun StorEdge 5310 NAS Appliance Version 4.5 documentation set does not reflect the Web Administrator GUI change from Fault Tolerance to High Availability. Therefore, when a step instructs you to select Fault Tolerance, select High Availability instead. For example, to initiate a recovery from failover, select High Availability Recover. (6301656)
During file system creation, the NAS will automatically assign a drive letter to file systems accessible by way of SMB/CIFS. It is possible to run out of drive letter. (6315946)
This message is for informational purposes only. The file system will be created but, to assign it a drive letter, you must reassign a drive letter that is currently used by another file system.
The following information applies to the Sun StorageTek Compliance Arthiving software.
To turn the Windows trigger on, use the following CLI command:
When upgrading to a release that is 4.10 or higher, from a release earlier than 4.10, you will be asked to re-enter timezone information, even though it was previously entered. This is due to a changed implementation that offers additional timezone locations.
This section provides instructions for connecting and configuring the Sun StorEdge 5310 NAS Gateway system to the Sun StorEdge 6130 array. The procedure assumes that you have already done the following:
You can connect the Gateway system directly to the Sun StorEdge 6130 array or through a single or dual Fibre Channel switches. A minimum of one port must be available on the Sun StorageTek 5310 NAS Appliance server and the 6130 array.
The Sun StorEdge 5310 NAS Gateway system requires software version 4.10 (minimum) for gateway support.
Sun StorEdge 6130 array requires the following software and firmware listed in TABLE 2.
1. If your Gateway system does not have software version 4.10 (minimum), download the latest version from http://sunsolve.sun.com.
2. Install the update as described in the install.txt file provided with the patch.
If the Sun StorEdge 6130 Array Management Software is currently at version 1.2, upgrade the management software to version 1.3 before installing the patches.
If the Sun StorEdge 6130 Array Management Software is currently at version 1.3, install the patches as described in To Upgrade the Sun StorEdge 6130 Array Firmware.
To upgrade the management software:
1. From the Sun StorEdge 6130 array management interface, log in to the Sun Storage Automated Diagnostic Environment and clear all existing alarms.
2. Log in to the management host as root.
3. Go to http://sunsolve.sun.com and download the latest Sun StorEdge 6130 host software package for Solaris from to any working directory on the management host.
4. Unzip the distribution file and untar the file.
5. Enter the following command:
The -n option specifies a non-interactive upgrade. After asking whether you want to upgrade software or firmware, the script will complete the upgrade without pausing for questions.
When the installation is complete, a confirmation is displayed followed by the date and time that the upgrade finished.
You can now install the patches as described in the next section.
The Sun StorEdge 6130 array management software requires version 1.3 firmware before you can install the required patches.
To upgrade the firmware for the Sun StorEdge 6130 array:
1. Download the required patches (see TABLE 2) from http://sunsolve.sun.com/.
2. Stop all I/O to the disk drives.
3. Log in to the management host as root.
4. Change to the directory to which you downloaded the software.
5. Install each patch by following the instructions in the patch README file.
6. Verify that the latest patches are installed:
a. Open a supported browser.
b. Enter the IP address of the management host using this format:
c. Log in to the management software.
d. Click Sun StorEdge 6130 Configuration Service.
The Array Summary page is displayed.
e. Verify that the Firmware Version column displays 06.12.09.10 (or greater).
To verify that the array is seen by the Sun StorEdge 6130 host software, use automatic discovery or manual registration.
If the array is on the same subnet as the management host, you can automatically verify the array.
1. Open a supported browser.
2. Enter the IP address of the management host using this format:
3. Log in to the management software.
4. Click Sun StorEdge 6130 Configuration Service.
The Array Summary page is displayed.
5. Click Auto Discover to display arrays that are on the same subnet as the management host.
6. Verify that the array is listed on the Array Summary page.
If the array is not on the same subnet as the management host, you must manually register the array.
1. Open a supported browser.
2. Enter the IP address of the management host using this format:
3. Log in to management software.
4. Click Sun StorEdge 6130 Configuration Service.
The Array Summary page is displayed.
5. Click Register Array.
The Array Registration page is displayed.
6. Enter the IP address of the controller and click OK.
7. Verify that the array is listed on the Array Summary page.
To make the Sun StorEdge 6130 SAN storage available to the NAS Gateway system, do the following:
1. Create an initiator on the Sun StorEdge 6130 array.
2. Define a new volume on the Sun StorEdge 6130 array.
3. Define a NAS volume on the NAS server.
1. Log in to the Sun StorEdge 6130 Configuration Service software, and click Physical Storage Initiators.
The Initiator Summary page is displayed.
2. Click New.
The New Initiator Summary page is displayed.
3. Enter a name for the new initiator, using a maximum of 30 characters.
4. Select an existing World Wide Name (WWN), or enter a new one.
5. Select the host for the new initiator.
6. Select the host type for the initiator.
7. Click OK.
The Initiator Summary page displays the initiator name, host name, host type, and WWN of the new initiator.
1. In the Sun StorEdge 6130 Configuration Service interface, click Logical Storage > Volumes.
The Volume Summary page is displayed.
2. Click New.
The New Volume wizard is displayed.
3. Enter a name and capacity for the volume.
4. Select the virtual disk you want to use for this volume.
5. Map the volume to the Sun StorEdge 5310 NAS Gateway host.
The new volume is displayed on the Volume Summary page.
1. From a client of the NAS server, log in to the Web Administrator.
2. Create a NAS volume on the Sun StorEdge 6130 volume and format it:
a. Open the File Volume Operations menu.
b. Select Create File Volumes.
c. Click Scan New Disks.
The newly created 6130 LUN is displayed on the left side of the center pane.
d. Name the volume, enter the required parameters, and click Apply.
See the Sun StorEdge 5310 NAS Appliance and Gateway System Administration Guide for information about the required parameters.
A reboot is required when a LUN is deleted and then reintroduced to the NAS using a method other than In-Band RAID Management (6281673).
A server reboot is not required for the gateway system. You can unmap and remap the LUN as described in the Sun StorEdge 5310 NAS Appliance and Gateway System Administration Guide.
LUNs or volumes that are offline cannot be deleted. A LUN must be brought online before it or its volumes can be deleted (6282821).
The /cvol file system should not be manually shared or mounted. Do not make modifications to /cvol using any method other than the Web Administrator or Telnet/CLI. (6280955)
Do not perform mirror operations such as Change Role when a cluster is in a degraded state. Please refer to the Sun StorEdge 5310 NAS Appliance and Gateway System Administration Guide, 819-3238-10, for information on best practices (6291398,6218561,6233839,6234948).
You can export a file volume only to a set of hosts with root permission (like Sun Solaris or UNIX) by adding the hosts to the "trusted group" using the Set Up Hosts window. Another way of doing this is to add the set of hosts to a host group and then export the required file volume against this group using the "with Map Root User set to Root User" option (6222556).
The Management Information Base (MIB) files are installed with the image in the boot-directory/www/data/mib directory; for example, /cvol/nf1/www/data/mib. The MIB files are available via Web Admin in the mib sub-directory, for example; http://hostname/mib, where hostname is the appropriate system hostname or IP address.
The MIB files can also be found in the release software download from http://sunsolve.sun.com.
If your system log contains error messages stating "Unowned SFS2" volumes, call Technical Support for assistance. (6186842)
The following documentation is posted on the documentation Web site at:
If you need help installing or using this product, call 1-800-USA-4SUN, or go to: