Cisco NSS2000 - Gigabit Storage System Chassis How to use

Release Notes for the NSS2000 Series Firmware Version 1.16 1
Release Notes
Release Notes for the Cisco NSS2000 Series
Network Storage System, Version 1.16
November, 2009
These release notes contain important information about the Version 1.16 release
of the Cisco NSS2000 Series Network Storage System and any limitations,
restrictions, and caveats that apply to this product.
Contents
This information is in the release notes:
•Compatibility
•Downloading and Upgrading the Firmware
•Open Caveats
•Closed Caveats
Compatibility
When the NSS is joined to the Windows Server 2008 domain and multiple users
are sharing the same file, these are the compatibility issues that can occur:
•When accessing a database file (such as a Microsoft Access file), files
opened by the user automatically obtain an exclusive lock, blocking other
users from opening the files, even in read-only mode.
•In other applications, when multiple users access the same file, each user
has read-write access privileges. This can cause the file to be overwritten
and can lead to data loss. If this occurs, no user warning message appears.

2 Release Notes for the NSS2000 Series Firmware Version 1.16
Release Notes
Although this feature is working, Cisco does not fully support joining the NSS to
the Windows Active Directory Server (ADS) in a Windows Server 2008
environment. This workaround only applies to a single user. (CSCsw93385)
Downloading and Upgrading the Firmware
This procedure describes how to upgrade the firmware on the NSS by using the
NSS Configuration graphical user interface (GUI).
NOTE Back up the system configuration file to a USB flash device and/or a RAID volume
by using the Configuration GUI before you upgrade the firmware. From the
Manager Menu, click Admin Configuration to backup the file.
To download and upgrade the NSS firmware:
STEP 1 Download the latest image from the Cisco support website to your local computer.
See http://www.cisco.com/support/index.shtml for further details. After
downloading, do not unzip the file.
STEP 2 Log into the Configuration GUI.
STEP 3 From the Manager Menu, click Admin Maintenance.
STEP 4 Click the Browse button and navigate to the NSSxxxx_fwupgrade_0116.tar.gz
firmware upgrade image.
STEP 5 Click the Upgrade Firmware button.
STEP 6 Run this procedure again by repeating Steps 2 though 5.
Performing the upgrade twice allows the system to continue to operate properly
(when running the latest firmware), if a system failure occurs.
NOTE If you are moving drives between two NSS systems, make sure that both of the
systems are using the latest firmware and that the system configurations are saved
on USB memory sticks and/or a RAID volume.
•When the NSS is joined to an ADS domain and you upgrade the firmware,
the ADS is unable to access a share.
The workaround is to rejoin the NSS to the ADS domain. (CSCsw94409)
Base Model Firmware
NSS2000 NSS2000_fwupgrade_0116.tar.gz

Release Notes for the NSS2000 Series Firmware Version 1.16 3
Release Notes
For more information about upgrading the firmware, see the NSS2000
Administration Guide
available on Cisco.com.
Open Caveats
These are the open caveats for this release.
•CSCsv34635
When the NSS is running over a network that is on a different subnet, a user
cannot mount a CIFS connection by using a hostname.
The workaround is to mount the CIFS connection by using an IP address.
•CSCsv34808
When an unexpected power cycle occurs on the NSS, the time might be
corrupted on the NSS. This only applies if the time is set manually, not by
using NTP.
When this occurs, a pop-up alert window appears when you access
Configuration GUI after the unexpected shutdown.
The workaround is to manually check the time in the GUI. From the Manager
Menu, click Admin Time and correct the time if necessary.
•CSCsv34900
If a data write operation is in progress, and the system power is interrupted,
data stored in a degraded RAID1 or RAID5 array might become
inaccessible. This is common to all NSS systems using software RAID
implementations.
These are the workarounds:
-Replace the failed drives in the degraded arrays as soon as possible, as
failed RAID arrays can result in complete loss of all user data.
-Use the degraded mode management feature to limit the amount of time
that a RAID array will run in the degraded state.
-Implement a backup power strategy by using a UPS or RPSU backup
power system.

4 Release Notes for the NSS2000 Series Firmware Version 1.16
Release Notes
•CSCsv34917
When rebuilding a RAID1 spare device, the rebuilding does not resume
after the NSS reboots. After reboot, the array might be falsely marked as
clean and the drive falsely marked as synced. This does not affect the
initial rebuild of an array following a RAID creation.
The workaround is to not reboot the NSS during the RAID rebuild.
•CSCsv34936
If power is interrupted when rebuilding a RAID array (RAID1, RAID5 or
RAID10), the rebuild does not restart automatically after the system is
powered up again.
When this occurs, the array remains in the degraded state and the rebuilt
drive is ejected from the array.
The workaround is to manually restart the rebuild by adding the ejected
drive back to the array by using the Configuration GUI.
•CSCsv46267
When the RAID global spares option is enabled in the Configuration GUI,
the RAID spares are not shared during the RAID array rebuild.
For example: If RAIDA has a hot spare and RAIDB does not, if RAIDB is
degraded while RAIDA is rebuilding, the spare will not transfer to RAIDB
until after RAIDA completes the rebuild.
There is no workaround.
•CSCsv46961
When the Default Network Policy filter is set to Drop Traffic, no automatic
Allow Filter is created for the default gateway.
When this occurs, all traffic from the default gateway is dropped and all
traffic sent from other subnets through a router is not forwarded to the
NSS.
The workaround is to manually create an AllowAll Network Access Filter
for the default gateway IP address by using the Configuration GUI.
•CSCsv47134
When writing simultaneously to the same file by using NFS and FTP or by
using NFS and CIFS, the NSS file locking mechanism does not
work properly.

Release Notes for the NSS2000 Series Firmware Version 1.16 5
Release Notes
There is no workaround.
•CSCsv47151
When you create a share by using the Initial Setup wizard and enable NFS,
users are assigned root privilege access.
The workaround is to not enable NFS in the Initial Setup wizard. If NFS is
required, you can enable it at a later time by using the Configuration GUI.
•CSCsv47178
When the NSS sends out a broadcast message to discover an NIS server,
the broadcast is only sent to the physical interfaces, not over any VLANs
that are defined in the system.
The workaround is to not use the NSS in networks where NIS servers are
only accessible over VLANs.
•CSCta50061
If a user was granted write access to a share and the write access was
revoked, the user can still write to subfolders by using FTP and NFS.
This problem only occurs under these conditions:
-The user has write privileges to the subfolder (either because the user is
the owner, or was granted access by the owner).
-The user has read privileges to the share (by having explicit share read-
only access).
The workaround is to not enable FTP and NFS (which is disabled by
default), if these protocols not being used.
•CSCta87135
When using filenames with Chinese characters, characters are lost when
transferring the files to the NSS by using the FTP protocol.
The workaround is to use the CIFS protocol.
.

6 Release Notes for the NSS2000 Series Firmware Version 1.16
Release Notes
Closed Caveats
Resolved in Firmware Version 1.16
•CSCsv34671
When the Network Access Filter is set to Policy=Drop Traffic and
Filter=AllowAll or Policy=Drop and Filter=AllowCIFS, the CIFS mount
now works.
•CSCsv34675
When the Network Access Filter is set to Filter=AllowHTTPS and
Filter=DropFTPS, you can now add Network Access from the
Configuration GUI.
•CSCsv34906
When a RAID0 array failure occurs, an alert (SNMP trap, email or system
alert) is now triggered.
•CSCsv46326
When a Seagate 1 terabyte (TB) hard drive (model ST31000340AS) is
installed in the NSS, it is not detected by the system on bootup or when
hotplugging the drive.
There is no workaround. This drive is not compatible with the NSS2000.
For a current list of compatible disk drives, see the Cisco Approved Vendor
List for Network Storage Systems at: http://www.cisco.com/en/US/
products/ps9957/prod_technical_reference_list.html
•CSCsv46327
When Seagate hard drives are installed in the NSS, they are now
immediately detected on bootup.
•CSCsv46993
The maximum transmission unit (MTU) size of the NSS is now supported.
•CSCsv47120
If a user was granted write access to a share and the write access was
revoked, the user can no longer write to subfolders by using FTP.

Release Notes for the NSS2000 Series Firmware Version 1.16 7
Release Notes
•CSCsv47174
The Network Identification page in the Configuration GUI now accepts
domain controller hostnames that begin with a digit.
•CSCta87119
When running firmware V1.13.30 on the NSS, you cannot configure a share
folder to work with the Symantec BackupExec application.
This problem was fixed in firmware version 1.16.
Cisco, Cisco Systems, the Cisco logo, and the Cisco Systems logo are registered trademarks or trademarks of Cisco Systems, Inc. and/or its
affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website are the property of their
respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)
© 2009 Cisco Systems, Inc. All rights reserved.
OL-20075-01