Virtual TapeServer 6.04.03.01 for NonStop Servers Release Notes

Known Issues | 9
Known Issues
The following known issues, or “errata,” apply to the 6.04.03.01 release. The issue tracking
number is provided in parentheses. Refer to this number when making inquiries to Technical
Support.
There is a table of tracking numbers listed in ascending order, with the summary and
document section number, in
Issue Index on page 33.
Hardware and configuration
 SCSI speed for an AS/400 initiator to a VTD is less than 160MB/sec. The AS/400
initiator is not performing SCSI parallel protocol request (PPR) negotiations as required
for U160+ speeds. (TL-4139)
 HBAs use a default SCSI ID of 7. In most cases, this SCSI ID may conflict with the
SCSI ID used by host systems, which is also 7. To avoid having conflicting SCSI IDs, VTS
should use another default ID. (TL-4117)
 Initial configuration is cumbersome. After mounting the VTS server, initial
configuration of network settings is cumbersome, requiring that you log into Linux and
use system tools. If you do not complete this configuration, you cannot access the web
interface using the hostname, for example. (TL-4213)
 No automatic reboot after setting system limits on Fibre Channel ports. If you
use the Manage System Limits page to configure the Fibre Channel ports, a message is
displayed and broadcast that a reboot will occur though it does not. You must reboot after
setting system limits. (TL-4000)
 Starting a VTD on the NonStop results in two errors logged to debug.log.
Immediately after the NonStop command “SCF START TAPE $VTAPE00” is issued to
start a virtual tape device, one or more of the following messages may appear on the VTS
server in /usr/local/tape/log/debug.log:
Mon Jun 23 14:31:33 2008: [cli_tape 0x05000007] read ERROR on message
rc = 1
These messages are benign and may be ignored. (TL-1802)
 If the controller ID and the host SCSI ID are set to the same value, kernel panics
occur. Kernel panics occur on VTS if two devices are set to the same ID. (TL-2303)
WORKAROUND: When using SCSI VTDs, make sure the SCSI controller ID is set to
something different than your host machine's SCSI ID.
 Kernel panic may occur if SCSI VTD is edited while host is scanning devices. If
you change the bus and LUN of a SCSI VTD and the host is scanning devices, the system
may panic and the web interface may stop responding. (TL-4018)
 Kernel panic may occur after creating VTDs. After creating VTDs, the system may
panic. (TL-2141)
WORKAROUND: Do not configure multiple devices to have the same bus, target, or
LUN values with different initiator values.