VS Appliance Support Information
To receive notifications of firmware and documentation updates, please email support@coraid.com and request to be placed on the VS announcement mailing list.
Documentation
| VS20090518.pdf - VS Command Reference Manual | |
| The Command Reference Manual describes the user interface to the EtherDrive® VS Appliance. | |
| VSPOP20081031.pdf - VS Principles Of Operation Guide | |
| The Principles Of Operation Guide describes how the EtherDrive® VS Appliance functions. It includes information on how to configure and use it with current and new SR storage. | |
| ANVS001.pdf - Application note: Migrating Existing Data to the VS | |
| Application note ANVS001 discusses options for migrating existing AoE storage for use with the VS. | |
| VS FAQ - List of frequently-asked questions | |
| The VS FAQ contains answers to the most frequently-asked questions. | |
Related Software
| CEC client - Coraid Ethernet Console client | |
| This CEC client will compile and run on linux, solaris, and bsd flavors supporting bpf. | |
Updates
VS firmware updates are released as a single binary image and are applied as described in Appendix A of the Command Reference Manual.
VS20100707 - Update release VS20100707
[ md5sum: 3f68e4f8b7ae0d9f79df10b57bbb731e ]
bugfix: panic when cec sessions receive characters too quickly bugfix: LUN external AoE config strings corrupted after 18 bytes bugfix: mirror pvs aren't loaded on boot if secondary is missing
See the Changelog for a full list of release changes.
Release Notes
- PLD extent not marked dirty
In releases prior to 20081103 the Per Lun Data (PLD) extent that defines the metadata for the LUN was not marked dirty on the PV. If the PV on which the PLD resides is mirrored, the PLD would not be properly copied. After updating to the current release, users are recommended to take their LUNs offline, then online, to cause the PLD to be written and properly marked dirty.
- Halt via CEC
The halt command currently takes down the network as part of its shutdown procedure. As a result, users that run halt via CEC will not be able to send another keystroke to cause the VS to reboot. CEC users should not use the halt command until this is resolved.