Virtual TapeServer 6.04.04 for NonStop Servers Release Notes

Known Issues | 18
Known Issues
The following known issues, or “errata,” apply to the 6.04.04 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 42.
Hardware and configuration
 VTDs are not started properly and the host does not see the VTDs after upgrade.
On DL380 G6 servers with more than four cards installed, or on all DL585 G1 servers,
VTDs created on host buses higher than 9 are incorrectly converted during the upgrade.
Thus, ports cannot be enabled and the host cannot see the ports. Contact your Support
provider for a patch or interim release (IR) to address this issue. (TL-5428)
 SCSI speed is 3.3MB/s after TapeServer is restarted. If TapeServer is stopped and
started, the SCSI speed is negotiated to 3.300MB/s. (TL-4434)
WORKAROUND: To negotiate at 160.000MB/s, reboot the server.
 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
configuring ports; the Manage Connections page informs you to reboot if using this page.
(TL-4000)
 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.
 ACPI Exception messages are displayed and logged during boot. At boot time,
messages similar to the following may be displayed on the system console and in /var/log/
dmesg. These messages are benign and may be ignored. (TL-2280)
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device
is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x2
 Trace messages may be displayed on the console. These messages can be ignored.
(TL-3032)