Virtual TapeServer 6.04.03.02 for NonStop Servers Release Notes

Troubleshooting | 30
Troubleshooting
This chapter includes information about product features that need improvement or may
cause user error.
Hardware and configuration
 Fibre Channel ports do not initiate link status and lasers are off if ports are set
to target mode and VTDs are not defined. When a Fibre Channel port is enabled for
target mode, the port will not initiate link status until a VTD has been defined on that
port and the lasers will be off. The port will appear to be disconnected unless a VTD has
been defined. Likewise, when Tapeserver is stopped, the Fibre Channel ports will drop
link status, to emulate the function of a physical tape drive with the power turned off.
(TL-2641)
 Reordering Fibre Channel buses may occur when changing them from Physical
(initiator) to Virtual (target) mode. To avoid renumbering, always use the highest
numbered Physical bus as your next Virtual bus. (TL-2592)
 Must run /usr/local/tape/bin/grub-serial.bash to access GRUB from the console.
When VTS boots, you must press a key when prompted if you wish to see the GRUB
menu. The /usr/local/tape/bin/grub-serial.bash command will modify the system boot
configuration to provide serial console access to the GRUB boot menu. This command
must be run as root. In some cases, it may cause the system boot time to be greatly
increased, although the normal boot time is only expected to increase by 10 seconds after
running this command. (TL-2255)
 VTDs set as device type 519x show up as FUJITSU M2483B drives. According to
the HP web site, the 5190 drive reports itself as a Fujitsu drive. (TL-1107)
 32-bit processor platforms are not supported. 6.04 is not supported on the DL380 G3
and ML530 platforms. (TL-1287)
 VTD with no connection to a logical tape is still presented on the bus. If a VTD is
created and connected to a logical tape then the VTD is disconnected, the VTD is still
shown to the client. An SG device is created and an Inquiry command succeeds. However,
a Status command does not and the VTD cannot actually be used. (TL-2324)
 I/O fails to resume after Fibre Channel cable is disconnected and HBA times out.
If you disconnect the Fibre Channel cable to the VTS for a time period that exceeds the
VTS FC HBA driver timeout value, I/O is interrupted and will not recover. (TL-1886)
WORKAROUND: Rediscover the Fibre Channel devices on the initiator or reboot the
initiator.
General operations
 GET FW STATE messages displayed on the console after restarting TapeServer.
Stopping and restarting TapeServer causes repeated messages similar to the following on
the console. (TL-3853)
Nov 15 13:46:52 vts15 kernel: isp0: Firmware State <Config Wait->Loss
Of Sync>
Nov 15 13:46:52 vts15 kernel: isp0: Interrupting Mailbox Command
(0x69) Timeout (elapsed time 100 jiffies)