Sun StorageTek NAS OS Software Release Notes, Version 4.21.M2 Table Of ContentsPrevious ChapterNoNextNoIndex

Sun StorageTek NAS OS Software Release Notes, Version 4.21.M2

These release notes contain information for the Sun StorageTektrademark NAS OS, releases 4.21 4.21 Maintenance 1 (4.21.M1) and this release, 4.21 Maintenance 2. The maintenance release resolves issues detected in the previous release.

The Sun StorageTek NAS OS and its options, the StorageTek File Replicator and StorageTek Compliance Archiving Software, manage the following:

These release notes contain the following sections:

New Features in This Release

The following change has been made in this release:

It is no longer possible to unload the ssh module. This module contains functionality that is required by other parts of the system.(6595606)

New Features in Previous Release

Version 4.21 of the Sun StorageTek NAS operating system (OS) provided the following new features:

System Requirements

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 5000 NAS family of products.

To access the Web Administrator management interface, you must have a network-attached computer running one of the following browsers. You must use a Javatrademark technology-enabled browser with Java Plug-In 1.4.0 (minimum version).


Note - To download the latest Java Plug-in software, go to http://java.sun.com/javase/downloads/index.jsp.


procedure icon  To Determine the Software Version

Perform one of the following procedures.

If the appliance is not at the latest release, download and install the release of the Sun StorageTek NAS OS from the SunSolve site, http://sunsolve.sun.com.


procedure icon  To Determine Firmware Revision Levels

Use the following command to display the current revision level of the firmware of each RAID controller unit, expansion unit, controller NVSRAM, and drive. 

raidctl get type=lsi target=profile ctlr=0..N

Software Updates and Downgrades

Upgrade your system by downloading the latest release of Sun StorageTek NAS OS software from the SunSolve site, 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.


118216

Software for the Sun StorEdge 5210 Appliance

119351

Software for the Sun StorEdge 5310 Appliance

119352

Software for the Sun StorageTek 5320 or 5220 Appliance



Note - If you are upgrading a Sun StorEdge 5210 NAS Appliance to software release 4.21.M1 from a release prior to release 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 release 4.05 (or greater) does not need the FCO applied.

When the software is upgraded, the previous release remains on the system so you can reboot to the previous release. Downgrading to an earlier release other than the one loaded on your system, as indicated on the Shutdown the Server screen of the Web Administrator, is not supported. If required, contact Sun Services.

Service Contact Information

If you need help installing or using this product, call 1-800-USA-4SUN, or go to:

http://www.sun.com/service/contacting/

Resolved Issues in This Release

The following issues have been resolved in this release. Change Request numbers are in parentheses.

NDMP

General

Resolved Issues in Previous Release

The following issues have been resolved with NAS OS release 4.21. Change Request numbers are in parentheses.

Known Issues

The issues described in these sections are not resolved. If a solution is available, it is included. Change Request numbers are in parentheses.

Workaround: Enter the correct information and when prompted to reboot, reboot the system manually.

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.

Web Administrator Issues

Workaround: Either use the Web Administrator to remove the IP addresses in LIFO order (last in, first out) or use the CLI to remove the IP addresses.

Workaround: Do not use spaces in the administrator password.

Workaround: To release the lock, log out of the Web Administrator and log in. As an alternative, use the following command:

datalock reset 0

Workaround: Refresh the panel, or wait until LUN initialization is complete.

Workaround: Manually mount all unmounted volumes.

Workaround: This is due to a rounding error. Create the volume by using the administrator console or CLI.

Workaround: Log out of the Web Administrator, restart it, and log in again.

Workaround: Verify the new settings before submitting the update.

Workaround: Perform a Scan for New Disks to populate the screens with the complete data.

Workaround: Use the F5 key to refresh the view on the Windows client.

Workaround: Do not delete LUNs in a Volume Group while that volume group is being rebuilt.

Workaround: Wait a few minutes for the move to complete.

Workaround: NFS clients using EUC-KR character sets can export only at the volume level. Volume names are restricted to ASCII.

Workaround: Run the raidctl get command on the local system. Send the command’s output file using ftp, email, or some other method.

Workaround: These instances can be ignored safely. To update the display, perform a recovery process.

Workaround: To control the order of the list, you must delete all the IP addresses and add them in the order you want. As an alternative, use the CLI to configure the bond.

Workaround: Use the on-board Fibre Channel / SCSI bridge on the robot to connect to a Fibre Channel port on the NAS appliance or gateway system.

Workaround: Close the Web Administrator and browser. Open a new browser and restart the Web Administrator.

Workaround: Place the LUNS on the primary path.

Workaround: If the name server does not resolve the hostname, use the IP address to connect. To prevent this condition, verify that the host name entered for notification 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 the NIS or NIS+ database has many mappings, you must wait for the system to finish processing. Do not reboot your system.

Copy Issues (rsync)

Workaround: Avoid performing an rsync operation on a volume during a backup operation of that volume. Wait until the first operation is complete before issuing the second command.

Workaround: Establish a new ssh connection to the second head, now in the ALONE state. (6556518)

Workaround: Enter any text at the prompt and the rsync operation continues.

Backup Issues (NDMP)

Workaround: Create a checkpoint for the file system manually, using the following procedure:

1. On the replicated volume, create a checkpoint, for example, test.

2. On the mirror system, verify the checkpoint using the ls command: 

       ls /volume_name.chkpnt/test

3. From the DMA, edit the default path to specify the complete checkpoint path, that is, from the volume name to /volume_name.chkpnt/test

4. Back up the replicated volume.

Antivirus-Specific Issue

The following antivirus-specific issue is not resolved at this time:

Workaround: In the Antivirus Configuration panel, set the Max Scan Size to a value less than or equal to 2GB.

Array Firmware-Specific Issues

Workaround - Reset the controller and the NAS 5320 C appliance.

Workaround - Check the NAS system log file for messages that indicate over temperature.

Workaround

Workaround - Verify that the file system is not full.

Workaround - Remove hot spare drives and replace failed drives one at a time.

Cluster-Specific Issues

Use the following procedure when adding a LUN in a gateway cluster:

1. On the current server, use the Web Administrator to navigate to Volume Operations > Create File Volumes and then click Scan for New Disks.

2. On the current server, navigate to High Availablity > Recover and assign the LUN ownership to the desired server and click Apply.

3. On the partner server, navigate to Volume Operations > Create File Volumes and then click Scan for New Disks.

4. On the current server, navigate to High Availablity > Recover and then click Restore to move the LUN to the server that owns the LUN.

Workaround: Reboot the ALONE server a second time and then repeat the recovery.

Workaround: Log in to the system console and recover the bond on Head 2. Reassign the primary slave on Head 1 and recover the bond on Head 2.

Workaround: Use the administrator console to modify the value.

Workaround: Do not modify bonds while the server is in the ALONE state. Creating or deleting bonds in the ALONE state causes inconsistencies.

Workaround: Mount the volume manually.

Workaround: Use the Web Administrator to log into the partner server and enable failover.

Workaround: Use the following command to mount a volume: 


hostname> mount -f /volume-name

Sun StorageTek File Replicator Issues

The following replicator-specific issues are not resolved at this time. Change Request numbers are in parentheses.

Workaround: Remove the share and create a new share that points to the volume with the changed name.

Workaround: After reinstalling the license, reboot the system.

Workaround: Do not enter a zero (“0”) in the first segment. The address must be valid.

Workaround: In the left-side Navigator Tree of the Web Administrator, select another node. Then select the node displayed previously. If the mirrored volumes are still not displayed, log out of Web Administrator and close the browser. Open a new browser window, restart the Web Administrator, and log in again.

Workaround: Use the Web Administrator to create more mirrors.

Workaround: Use the CLI to unset the mirror.changerole parameter and then establish mirroring.

Workaround: Unmount the volume and then remount it.

Workaround: Avoid this problem 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: Contact Sun Technical Support for help in establishing your mirror.

Workaround: Unmount the volume and then remount it.

Workaround: Use the administrator console.

iSCSI-Specific Issues

The following iSCSI-specific issues are not resolved at this time. The numbers in the parentheses indicate the Change Request.

Workaround: Do not create iSCSI LUNs on system volumes.

Workaround: An iSCSI session supports four simultaneous connections to the NAS appliance or gateway system. Wait approximately a minute for old sessions to time out and log in again.

Workaround: Make another change to the access list and save to force the list to update Head 2.

Workaround: Do not use Data Digest with Solaris clients. If Data Digest is needed, use an iSCSI HBA implementation.

Documentation Issues

The following issues have been identified in the documentation:

Correction: This sentence should refer to a controller enclosure, not a controller unit.

Correction: The sentence that has the linked URL is correct.

Correction:

# Smcli IP_address_controller_B -f CtrlBModRegion12

# Smcli IP_address_controller_A -c...

similar to the command example in Step 7.

Addenda to the Documentation

This section includes information that is additional to or overrides information in the documentation. It contains the following topics:

About the McAfee Secure Internet Gateway

You can use a McAfee Secure Internet Gateway 3000, 3100, 3200, and 3300 appliance or the McAfee Secure Web Gateway 3400 appliance that runs a minimum of SCM Version 4.21 Patch 5, to scan files stored on the Sun StorageTek NAS device. The McAfee appliance works in the same way as the other supported scan engine software products, as described in the online Help and in Chapter 4 of the Sun StorageTek NAS OS Administration Guide (819-4284-nn).

To perform the antivirus scans, configure the McAfee appliance with the following attributes:

About the rsync Protocol

The rsync protocol transfers new files and changes to existing files between a Sun StorageTek 5000 NAS system and a remote system. Use rsync for purposes that require more efficiency than the ftp protocol and more control than the rcp protocol, but do not require a real-time replication solution such as the Sun StorageTek File Replicator option. It is most efficient when the file exists on both systems and only changes are transferred.

Restrictions on rsync

The implementation of the rsync protocol in this release has the following limitations (6544680):

Configuring rsync

The rsync feature is disabled by default. To use the feature at any time, issue the following command before using the rsync command: 

load rsync

To enable the rsync feature, edit the inetload.ncf file to load rsync each time the NAS system reboots, using the following procedure:

1. Edit the inetload.ncf file, located in the /dvol/etc directory.

2. At the end of the file, add a comment and the command: 

# The rsync module provides remote copy of incremental file changes.
# YYYY:MM:DD
rsync

3. Save and close the file.

4. Issue the following commands to use the new version of the inetload.ncf file: 

> unload inetload
> load inetload

The rsync protocol is now enabled in the current session and will be enabled after any system reboot.

Using rsync

This release supports the rsync protocol in server mode. This means that from the system where you are logged in, you can copy file system objects from your system to the NAS head or you can copy file system objects from the NAS head to your system.

The general procedure for using the rsync protocol is to log into a network system, issue the rsync command, specifying the files to be copied. The rsync command uses the system’s ssh client to transfer the files.

1. Log in to a network system. This example uses a Windows system.

2. Click Start > Run from your Windows desktop.

3. In the Run window, type cmd and click OK.

4. Enter the rsync command, using the following syntax: 

>rsync [OPTIONS] source_location destination_location

where both source_location and destination_location are the current directory or one specified in the format: [USER@]hostname:directory_name. The hostname is the IP address or DNS name, the single colon specifies that the transfer uses the ssh client, and the directory_name is the path.

For example, to copy changes to files in the current directory on the system you are logged into (local) to the NAS appliance in your network (remote_nas) in its Monday directory, use the following command: 

rsync [OPTIONS] * remote_nas:Monday

To retrieve files that might have changed from the NAS appliance and put them in the local Wednesday directory, use the following command: 

rsync [OPTIONS] remote_nas:Monday/* Wednesday/*

To see all the options and a description of the command as it is implemented in your network, use one of the following command on a network system: 

>man rsync
>rsync --help

The rysnc process copies the following:

About Online System Registration and Auto Service Request (ASR)

The online Help and Sun StorageTek NAS OS Administration Guide describe the Online System Registration feature but do not emphasize that, in addition to registering the system, this feature monitors the system and can generate automatic service requests (ASR). This feature notifies the Sun Technical Support Center when events that generate a critical alarm occur.

ASR is available to all customers with current StorageTek Warranty or StorageTek Spectrum Contracts. The service is available from activation until the end of warranty or contract period. The service levels are based on the contract level and response times of the connected devices. The ASR service uses SSL security and your Sun online account credentials to authenticate transactions but does not monitor stored data. The feature collects only the following information:

Details and security documentation are available at http://www.sun.com/service/remoteconnectstorage.

Requirements for Online System Registration and ASRs

Each NAS system must be enabled individually and meet the following requirements:

Enabling Online Registration and ASRs

You configure the registration using the Web Administrator’s Online Registration Panel. To register the system, log into the Web Administrator and do the following:

1. From the navigation panel, choose System Operations > Online System Registration.

2. Read Sun’s privacy policy and disclaimer. To continue, click the Agree button.

3. If you do not have a Sun Account, click on the here link at the bottom of the dialog. This opens the Sun Online Account Registration portal. Click Register to begin to create the account.

4. If you have a Sun Account, type its ID in the Sun Account ID and enter its password.

5. Click Next to go to the Proxy Server tab.

6. If your site will use a proxy server, enter the name of the proxy server you want Sun Services to use and its port number. If the proxy server uses authentication, enter its user name and its password.

The information for registration is complete. To enable the Auto Service Request feature:

7. Click Next to go to the Options tab.

8. Select both options: Send Heartbeat Data and Send Fault Events. The heartbeat data is a daily check without regard to the type of event. The fault events are sent when a failure is occurring.

9. Read the Purpose statement and click OK to submit the request.

Your site’s contact email account receives a confirmation message that the system has been activated. The Online System Registration dialog identifies the system as Registered.

If you prefer to stop sending heartbeat or fault events to Sun Services, use the same procedure to display the Options tab and clear the checkboxes. The system remains registered but the information is not sent.

Creating a Core Dump File

A serviceability enhancement in version 4.21 was a diagnostic email message that support engineers can use to diagnose and solve problems. For some specific problems, the support engineer might need to perform a core dump analysis, which requires a core file. A core file contains a snapshot of the contents of physical memory when a system crash occurs.

The following procedure configures the NAS server to capture a core dump and save it as a file in a directory on the backend storage. When you complete the procedure, the next system failure or panic saves the core dump data to a raw disk partition and, after the system reboots, then saves the data to a file, leaving the raw disk partition available for any future core dump procedures. For more detail on core dump files and advanced configuration, see document 89129 in the SunSolve Knowledgebase, located on the SunSolve site, http://sunsolve.sun.com.


Note - Do not perform this procedure unless a support engineer requests a core file.

1. To make a raw disk partition of sufficient size to capture the size of physical memory, log into the administrator console and make the following selections:

a. From the Configuration menu, choose Disks & Volumes.

b. Identify a drive with at least 6 GB of available space and that does not already have a raw partition.

c. Type the letter of the drive to select it.

d. Choose 1, Edit.

e. Use the arrow keys to scroll to the desired free space.

f. Select 1, Create.

g. Select 3, Raw.

h. For size, enter 6000.

i. Select 7, Proceed with create.

2. Press the Esc key to display the command line.

3. Identify a directory location to store the core files or create a new one. Do not use /cvol or /dvol flash storage.

4. Enter the following commands: 

set kern.dumpdir /volume/path
savevars

where /volume/path is the path to an existing directory to store the core files.

5. If you have a cluster configuration, repeat this procedure for each NAS head in the cluster.

6. If it is possible to create the conditions under which the system panics or an NMI is generated, perform those actions. The system then reboots.

After the system reboots, the core file is saved in the directory you specified, with the filename, vmcore.x.gz, incrementing x for each new core file.

Configuring Quotas With Limits

The following information was not included in the description of the Configure User and Group Quotas Panel: (5058072)

Hard and Soft Limits

A hard limit is the absolute maximum amount of space available to the user or group. When a user’s or group’s storage reaches a soft limit, which is equal to or lower than the hard limit, a grace period of seven days starts in which files can be removed. After the grace period, the user or group cannot write to the volume until the amount of space used is below the soft limit.

The hard limit must be equal to or higher than the soft limit. For disk space, it can be no more than approximately 2 terabytes. For the number of files, the hard limit can be no more than 4 billion files.

The root user and root group do not have hard or soft limits for space or files and cannot have quotas defined.

Collecting Information for Configuration

You configure the Sun StorageTek NAS OS software using the Web Administrator’s Configuration wizard. The following worksheet lists information you can gather before you start the wizard, depending on the type of environment you select: Windows Only, Unix Only or Both. (6250174)


TABLE 1 Sun StorageTek NAS 5000 Family Configuration Worksheet

For All environments

 

For Server Name, a string to identify this NAS appliance. Begin with a uppercase or lower case character or number 0-9, can include hyphen, underscore, or period character. Limit is 30 characters.

 

For Contact, the name of your company, department, or unit.
This string will be included in diagnostic messages.

 

Network adapters

If your network does not use a Dynamic Host Configuration Protocol (DHCP) server, you must specify a static IP address for each network port:

>Internet Protocol (IP) address

>netmask

>network interface card (NIC) port role

>alias IP address (optional)

 

Default gateway IP address

 

For Windows or Both environment

 

For Domains and Workgroups Active Directory Service (ADS):

Name of this NAS appliance’s domain:

 

Username and password of a domain user or, if ADS, the Windows 2000 user who is domain administrator.

 

For ADS Container, the ADS path location of the Windows 2000 administrative user in LDAP distinguished name (DN) notation (common name and organizational unit). Do not include the domain name in the path.

 

For Site, the site name. Specify if the ADS domain controller is in a different subnet than this NAS appliance.

 

For Workgroup Name, the name of an existing group

 

For configuring the NAS appliance as a Windows Internet Naming Service (WINS) client:

 

IP address of the server for NetBIOS name resolution.

 

IP address of a server to be contacted if the first WINS server does not respond.

 

Name of this NAS appliance’s domain

 

For DNS Server, either the IP address of a new one or
the name of an existing one

 

Name of the domain that contains this NAS appliance

 

For UNIX or Both environment

 

For DNS Server, either the IP address of a new one or
the name of an existing one

 

Name of the domain that contains this NAS appliance

 

For Network Information Service (NIS)

Name of the domain the NAS appliance uses for NIS services

 

Either the IP address of a new NIS server or the name of an existing one.

If you do not know the IP address, you can let the server be acquired.

 

For NIS+ (name service with added security), configure NIS+ after you complete the wizard.

 

For LDAP Server:

Name of the domain that contains the LDAP server

 

Password for the domain server.

 

IP address of the LDAP server.

 

If you use a proxy domain, the name of the proxy.

 

Identify the lookup order of the name services to use for each type:

>user

>group

>netgroups

>hosts.

 

For All environment

 

For Email Notification, either the IP address of your SMTP server
or the DNS name of your SMTP server

 

Up to 4 email addresses to receive notification messages

 

For a remote log: Either the DNS host name or
the IP address of the system where system log will reside.

 

For a local log: Full path and filename of the log file.

 

Specify the number and size of archive files

 

Specify time, date, and working language

 

For registering the system for online Sun Service, your Sun Account ID and password.

 

The ID for an outbound-only HTTP connection through port 443 using HTTPS or
if your network uses a proxy server, the name of the proxy server and its port number. This server might require a username and password also.

 


Using a Sun StorageTek Flexline 380

To use the Sun StorageTek NAS 5320 Gateway Appliance with a StorageTek Flexlinetrademark FLX380 enterprise storage system that has FLA/FLC expansion trays, you must run a script to create a host entry in the NVSRAM for the NAS LUNs. Patch 124128-01 contains the scripts and instructions, available from http://sunsolve.sun.com

Exempting a Host Group from Virus Scans

Using the /dvol/etc/approve file to exempt a host group as documented does not exempt the share from scanning. The correct syntax for exempting a host group in the approve file includes an @ symbol, as in the following: 

vscan sharename @hostgroup access=noscan

An alternative is to use the Configure Share function. (6540932)

Restrictions on Sun StorageTek File Replicator

Upgrading to NDMP V4

With this release, the default version of NDMP is V4. The NDMP client is a data management application (DMA) and it must be changed to continue to work with systems running this release:

ndmp devices

For example, the format of the drive path for robot and jukeboxes has changed from isp1m001 to the following:

/dev/scsi/changer/0

where 0 is the target ID

The format for the drive path for a tape drive has changed from isp1t001 to the following:

/dev/rmt/0

where 0 is the target ID

Using a Sun StorageTek 5320 NAS Expansion Unit With a Sun StorEdge 5300 RAID EU Controller Enclosure

This release of the NAS OS software enables you to configure a new expansion unit as back-end storage for a Sun StorEdge 5310 system that has the Sun StorEdge 5300 RAID EU Controller Enclosure. After a firmware upgrade, the controller enclosure can recognize and manage the new expansion unit. TABLE 2 shows which configurations are supported and where the procedures are documented.


TABLE 2 Supported Combinations of Controllers and Expansion Units for Sun StorageTek 53xx NAS Systems

Controller

 

 

Expansion

Sun StorEdge 5300 RAID EU Controller Enclosure

Sun StorageTek 5320 RAID Controller Unit

 

Sun StorEdge 5300 EU Expansion Enclosure

Supported for Sun StorEdge 5310 and Sun StorageTek 5320 NAS systems and documented in:

  • Sun StorEdge 5310 NAS Appliance and Gateway System Getting Started Guide
  • Sun StorageTek 5320 NAS Appliance and Gateway System Getting Started Guide (819-4283-nn)

 

 

 

Not supported.

 

Sun StorageTek 5320 Expansion Unit

Supported in Sun StorEdge 5310 and Sun StorageTek 5320 NAS systems with 4.20.M3 software (minimum) and documented in the release notes for that release and also Sun StorageTek 5320 NAS Appliance and Gateway System Getting Started Guide (819-4283-11)

Supported for Sun StorageTek 5320 and documented in Sun StorageTek 5320 NAS Appliance and Gateway System Getting Started Guide (819-4283-11)


Using a Sun StorageTek 5320 RAID Controller Unit With a Sun StorEdge 5300 RAID CU Controller Enclosure

This release of the NAS OS software enables you to configure an existing Sun StorageTek 5320 NAS appliance with two types of controllers: a 5320 RAID controller unit and an 5300 RAID controller enclosure. After a firmware upgrade on the appliance, it can recognize both types of controllers and manage them. However, each controller stores data in separate back-end storage independently of the other controller. The advantage of this configuration is to improve I/O throughput but the disadvantage is the storage arrays are independent and do not provide failover protection for each other. This configuration and procedure does not apply to Sun StorageTek 5320 NAS Gateway systems or Sun StorEdge 5310 NAS systems.


procedure icon  To Upgrade Array and Drive Firmware on 5300 and 5320 RAID Controllers

Use this procedure to upgrade the array and drive firmware to run a Sun StorageTek 5320 NAS appliance with both a StorEdge 5300 RAID controller and StorageTek 5320 RAID controller. The NAS server updates each controller with different files, one at a time, when it is powered on. In general, the plan for upgrading the controllers is the following:

This procedure upgrades the 5300 RAID controller first and then the 5320 RAID controller.


Note - Follow the power cycle instructions exactly because the server upgrades the controller during that process.

1. Download the latest patch from www.sunsolve.sun.com and unzip the file.

2. Review the patch readme file to determine which firmware revision levels are associated with the patch.

3. From a Sun StorageTek 5320 NAS Appliance, enable ftp. Refer to the Sun StorageTek NAS OS Administration Guide for information about how to enable ftp using the Web Administrator or CLI.

4. Change to the directory where you downloaded the patch.


procedure icon  To Upgrade the Sun StorEdge 5300 RAID Controller

5. Use ftp to connect to the Sun StorageTek 5320 NAS Appliance or, in a cluster configuration, server 1. Log in as the admin user.

6. Enter bin for binary mode.

7. At the ftp prompt, create the following directories on /cvol by entering these commands: 

mkdir /cvol/firmware
mkdir /cvol/firmware/2882
mkdir /cvol/firmware/2882/ctlr
mkdir /cvol/firmware/2882/nvsram
mkdir /cvol/firmware/2882/jbod
mkdir /cvol/firmware/2882/drive

8. Use the put command to copy each file to the appropriate directory: 

ftp> put filename /cvol/newdir/filename.ext

Firmware files are truncated after they are copied to their directories. TABLE 3 shows example directory and firmware file names.


TABLE 3 Directory and Firmware File Examples for 5300 RAID Controllers

Component

Directory

Example File Name

RAID controller

/cvol/firmware/2882/ctlr

SNAP_288X_06120910.dlp

RAID controller NVSRAM

/cvol/firmware/2882/nvsram

N2882-612843-503.dlp

Fibre Channel EU

/cvol/firmware/2882/jbod

esm9631.s3r

SATA EU

/cvol/firmware/2882/jbod

esm9722.dl

Drive Firmware

/cvol/firmware/2882/drive

D_HDS7250SASUN500g_0604


9. Log out of the ftp session.

10. Power down the NAS server. In a cluster configuration, power down both server 1 and server 2.

11. Power down the StorageTek 5320 RAID controller and all attached trays. Do not power down the StorEdge 5300 RAID controller or its trays. The controller must be powered on to be upgraded.


Note - Do not power down the RAID controller while the upgrade is in progress. Upgrade times can vary.

12. Power up the NAS server or server 1.

When the NAS server is powered on, it downloads the new firmware to the StorEdge 5300 RAID controller and then removes the files.


Note - In cluster configurations, do not power on server 2 at this time. If server 1 comes up in QUIET mode, select the TAKE ALL LUNs command from the LCD.

13. Use the administrator console to connect to the NAS server or server 1, and log in to a user account with admin privileges.

14. Verify that the new firmware has been loaded by entering this command: 

raidctl get type=lsi target=profile ctlr=0

Check the system log for failures and to make sure that downloading is complete.


procedure icon  To Upgrade the StorageTek 5320 RAID Controller

15. Change to the directory where you downloaded the patch.

16. Use ftp to connect to the NAS server or server 1, and log in as the admin user.

17. Enter bin for binary mode.

18. At the ftp prompt, create the following directories on /cvol by entering these commands: 

mkdir /cvol/firmware
mkdir /cvol/firmware/399x
mkdir /cvol/firmware/399x/ctlr
mkdir /cvol/firmware/399x/nvsram
mkdir /cvol/firmware/399x/jbod
mkdir /cvol/firmware/399x/drive

19. Change to the same directory that you created for the previous firmware. Those files have been removed.

20. Use the put command to copy each file to the appropriate directory: 

ftp> put filename /cvol/newdir/filename.ext

Firmware files are truncated after they are copied to their directories. TABLE 4 shows firmware file names and directories.


TABLE 4 Directory and Firmware File Examples for 5320 RAID Controllers

RAID controller

/cvol/firmware/399x/ctlr

SNAP_399x_06192510.dlp

RAID controller NVSRAM

/cvol/firmware/399x/nvsram

N399x-619843-502.dlp

EU

/cvol/firmware/399x/jbod

esm9884.esm

Drive Firmware

/cvol/firmware/399x/drive

D_HDS7250SASUN500G_0604


21. Log out of the ftp session.

22. Power down the NAS server or server 1.

23. Power down the StorEdge 5300 RAID controller and all attached trays.


Note - Do not power down if the upgrade is in progress. Upgrade times can vary.

24. Power up the 5320 RAID controller and all attached trays.

You powered the RAID controller down in Step 11 but it must be powered on so that the NAS server can upgrade its firmware.

25. Wait until the LEDs on the StorageTek 5320 RAID controller and its trays display as solid.

26. Power on the NAS server or server 1.

When the NAS server is powered on, it downloads the new firmware to the StorageTek 5320 RAID controller and then removes the files.


Note - In cluster configurations, do not power on server 2 at this time. If server 1 comes up in QUIET mode, select the TAKE ALL LUNs command from the LCD.

27. Use the administrator console to connect to the NAS server or server 1, and log in to a user account with admin privileges.

28. Verify that the new firmware has been loaded by entering this command: 

raidctl get type=lsi target=profile ctlr=0

Check the system log for failures and to make sure that downloading is complete.

29. Power down the NAS server. In a cluster configuration, power down both server 1 and server 2.

30. Power up the StorEdge 5300 RAID controller and its trays.

At this point, both the StorEdge 5300 and StorageTek 5320 RAID controllers and their trays are powered on.

31. Wait until the LEDs on the StorEdge 5300 RAID controller and its trays display as solid.

32. Power on the NAS server. In a cluster, power on both server 1 and server 2.


Note - If you are running a cluster system and server 2 powers up in QUIET mode, run a recovery from server 1. If you ran the TAKE ALL LUNs command in Step 12 or Step 26, you might need to distribute LUNs also.

Release Documentation

The following documentation is posted on the documentation Web site at: 

http://www.sun.com/hwdocs/Network_Storage_Solutions/nas

Title

Part Number

Sun StorageTek NAS OS Administration Guide

819-4284-nn

Sun StorageTek 5320 NAS Appliance Setup [poster]

819-4385-nn

Sun StorageTek 5320 NAS Gateway System Setup [poster]

819-4286-nn

Sun StorageTek 5320 NAS Appliance and Gateway System Getting Started Guide (Sun StorageTek 5320 back-end storage)

819-4283-nn

Sun StorageTek 5320 NAS Appliance and Gateway System Getting Started Guide (Sun StorEdge 5300 back-end storage)

819-6387-nn

Sun StorageTek 5320 NAS Appliance and Gateway System Storage Regulatory and Safety Compliance Manual

819-7315-nn

Sun StorageTek 5320 NAS Array Regulatory and Safety Compliance Manual

819-6048-nn

Sun StorageTek 5220 NAS Appliance Setup [poster]

819-7166-nn

Sun StorageTek 5220 NAS Appliance Getting Started Guide

819-7167-nn

Sun StorageTek 5220 NAS Appliance Regulatory and Safety Compliance Manual

819-7366-nn

Sun StorageTek 5220 NAS Array Regulatory and Safety Compliance Manual

819-7367-nn

Setting Up the Sun StorEdge 5310 NAS Appliance [poster]

819-1168-nn

Sun StorEdge 5310 NAS Gateway System Poster

819-3240-nn

Sun StorEdge 5310 NAS Appliance and Gateway System Getting Started Guide

819-3237-nn

Sun StorEdge 5310 NAS Appliance and Gateway System Administration Guide

819-3238-nn

Sun StorEdge 5310 NAS Appliance Safety and Compliance Guide

819-0881-nn

Sun StorEdge 5210 NAS Appliance Administration Guide

819-5376-nn

Sun StorEdge 5210 NAS Hardware Installation, Configuration, and User Guide

817-6660-nn

Sun StorEdge 5210 Expansion Unit Safety, Regulatory, and Compliance Manual

817-7515-nn

Sun StorEdge 5300 RAID Expansion Unit and Sun StorEdge 5300 Expansion Unit Safety and Compliance Guide

819-0882-nn 


 


Sun StorageTek NAS OS Software Release Notes, Version 4.21.M2 819-6652-20 Table Of ContentsPrevious ChapterNoNextNoIndex

Copyright © 2009 Sun Microsystems, Inc. All rights reserved.