Virtual TapeServer 6.04.02 for NonStop Servers Release Notes

Resolved Issues and Enhancements | 5
Resolved Issues and Enhancements
The following changes have been incorporated into the software since the 6.04.01 release.
Hardware and configuration
 VTS is installed on the first available drive instead of the smallest. Previously, the
VTS system was installed on the smallest available drive. Now, it is installed on the first
available drive. (TL-2659)
 VTDs were not working on Fibre Channel ports. One or more Fibre Channel ports
were not functioning due to initialization failures. Usually, this was the result of more
than four VTDs defined on the port. This has been fixed. (TL-2640)
 Updated RPM for libxml2 is installed on the VTS server. The latest libxml2 release
for CentOS, which includes security fixes, is installed on the VTS server. (TL-2538, EAR
4751)
 No response to an Inquiry command yielded ABORT and Inquiry commands to
non-existent LUNs. The FC port in target mode sometimes received an Inquiry
command from a Linux initiator for a non-existing LUN. This resulted in not all VTDs
appearing to host in some situations. This has been resolved. (TL-2477)
 4Gb FC connections now supported. All 6.04.02 models now support 4Gb PCI-e ports.
(TL-1438)
 USB drivers now supported. With version greater than 6.04, the VTS software
supports the use of USB flash drives. This capability is included as part of the CentOS5+
base. (TL-2)
 SCSI VTDs could not be used if /tmp/targctl.lock existed. If /tmp/targctl.lock existed
at boot up, SCSI VTDs could not be used and an error similar to a 224 error was
generated. This has been resolved. (TL-2268)
 VTD emulations did not startup if the Fibre Channel switch link did not come
up in a timely fashion. Some Fibre Channel switches take a long time for the login
process. This delay caused VTDs to fail to startup. This has been fixed. (TL-2284)
 Asynchronous Fibre Channel events may have been lost when a VTD was
deleted. When a Fibre Channel VTD was deleted, Fibre Channel asynchronous events
(such as when one of the FC cables is unplugged) may not have been recognized. This has
been fixed. (TL-2304)
 Host server could not recognize the virtual tape device type. Sometimes the host
server could not recognize the tape drive type of the virtual tape device and operations on
the device failed. This has been fixed. (TL-2336)