DSN-2100-10/DSN-3200-10 Firmware Release Notes


Firmware: 2.5.1.81
Hardware: A1
Date: April, 10, 2009 


Please note that V1.6.x firmware release must be installed as the first step in upgrading to the V2.5.1 release.  If you have not done so previously, please upgrade to at least V1.6.x first followed by upgrading to V2.5.1.

Note: The upgrade from firmware V1.6.1 to V2.5.1 requires the installation of a new and improved system kernel.  It is recommended that you copy your system configuration (LAGs, LUNs, targets, etc.) down on paper manually and have it available when the upgrade is complete.  Please review your final configuration to make sure they match your previous settings.  Make changes if necessary.


Enhancements:

1. User friendly GUI for better management experience
2. Pop–up message notice when doing software upgrade with Windows Firewall enabled.
In previous releases, a software upgrade would fail without any explanation if the Windows Firewall was enabled on a Windows host system.  The system now checks the status of the Windows Firewall when you are upgrading the software, and displays a clear error message in a pop-up window if the Windows Firewall is enabled.  This change has no effect on non-Windows host systems.
3. Down Drive function with message notice improvement
In previous releases, the “Down Drive” selection had no warning or confirmation messages.  In this release, the Storage View on the Management Console shows the drive health as "Down Drive in progress" while the Down Drive action is operating.  The drive status also changes to "Needs Attention".When the Down Drive operation completes, the drive health changes to “Normal” and the Pool Type changes to “Unavailable”.  At that time, the drive may be safely removed from the enclosure.. 
4. Duplicate volume names are no longer permitted
To reduce the possibility of confusion when selecting Target Nodes, the system will no longer allow you to create a new volume (or rename an existing volume) using a volume name that is already used for another existing volume. However, any existing volumes that already have duplicate names are still supported, so no changes are required.


Problems Resolved:

1. Icons in System Administration view had unclean edges.
2. Incorrect vendor name appeared in some “Enclosure” event log entries
3. No warning message appeared when attempting to specify an invalid VLAN group number of “1”.