Cisco NSS2000 - Gigabit Storage System Chassis Release Notes page 4

Release Notes
4
• 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. 1 6