SuSE Linux SLES 8 with 5.1 MP3 - Problems with standalone Devices

[Stefan_Ettrich]

Hello,

I had installed my first NB 5.1 (with MP3) enterprise server on a SuSE Linux SLES8 os. On the server is connected a ATL7100 with 4 x DLT7000 devices and additional one standalone DLT7000 device and one standalone DLT4000 device.
The robot and all integrated DLT´s are running absolut fine without any problems.
But I can´t use any of the standalone devices, if I start a label operation I see no activities on these two devices and at the end I get a timeout.
Device configuration is check a few times, media´s are changed, correct media type is used, all these with no effect. "Enable standalone drive extension" is also set.
With mt and tar I can use the standalone DLT´s from OS side without any problems, just NB makes trouble.
Any ideas?
Thanks in advance.
Stefan.

[Yasuhisa_Ishika]

Show us outputs of following commands when label operation is under goning.

# /usr/openv/volmgr/bin/tpconfig -d
# /usr/openv/volmgr/bin/vmoprcmd
# /usr/openv/volmgr/bin/vmquery -m

And any error reported in Activity Monitor/Reports?

[Stefan_Ettrich]

Label example:
After more then 45 minutes the only detailed label message was:
- beginn label
- started process bplable (pid 14471)
- mounting NB0001

These messages are created all in the first two second after the start, later comes nothing, no timeout, no message.
I had cancel the job after 45 minutes, message
1: (98) error requesting media (tpreq)
was created.

Here are the cmd results:

guardian:~ # tpconfig -d
Index DriveName DrivePath Type Shared Status
***** ********* ********** **** ****** ******
0 QUANTUMDLT70000 /dev/nst4 dlt No UP
1 QUANTUMDLT70001 /dev/nst0 dlt No UP
TLD(0) Definition DRIVE=1
2 QUANTUMDLT70002 /dev/nst1 dlt No UP
TLD(0) Definition DRIVE=2
3 QUANTUMDLT70003 /dev/nst2 dlt No UP
TLD(0) Definition DRIVE=3
4 QUANTUMDLT70004 /dev/nst3 dlt No UP
TLD(0) Definition DRIVE=4
5 QuantumDLT40000 /dev/nst5 dlt2 No UP

Currently defined robotics are:
TLD(0) robotic path = /dev/sg/h0c0t0l0,
volume database host = guardian

Standalone drive volume database host = guardian
guardian:~ #


guardian:~ # vmoprcmd

PENDING REQUESTS

ReqId User RecMID ExtMID Density Mode Time Barcode VolGroup
0 root NB0001 NB0001 dlt2 Write 10:59 -------- ---

DRIVE STATUS

Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId
0 dlt AVR No Yes Yes -
1 dlt TLD - No - -
2 dlt TLD - No - -
3 dlt TLD - No - -
4 dlt TLD - No - -
5 dlt2 AVR No Yes Yes -

ADDITIONAL DRIVE STATUS

Drv DriveName Shared Assigned Comment
0 QUANTUMDLT70000 No -
1 QUANTUMDLT70001 No -
2 QUANTUMDLT70002 No -
3 QUANTUMDLT70003 No -
4 QUANTUMDLT70004 No -
5 QuantumDLT40000 No -
guardian:~ #

guardian:~ # vmquery -m NB0001
================================================================================
media ID: NB0001
media type: DLT cartridge tape 2 (16)
barcode: --------
media description: ------
volume pool: DataStore (2)
robot type: NONE - Not Robotic (0)
volume group: ---
vault name: ---
vault sent date: ---
vault return date: ---
vault slot: ---
vault session id: ---
vault container id: -
created: Wed Sep 14 10:59:02 2005
assigned: ---
last mounted: ---
first mount: ---
expiration date: ---
number of mounts: 0
max mounts allowed: ---
================================================================================

guardian:~ # ps -ef | grep bplabel
root 14471 14115 0 10:59 ? 00:00:00 /usr/openv/netbackup/bin/admincmd/bplabel -o -java -m NB0001 -d dlt2 -p DataStore -host guardian.alisrz.de
root 14509 14418 0 11:00 pts/10 00:00:00 grep bplabel
guardian:~ #

[Yasuhisa_Ishika]

I tried in my solaris environment and it also results in failure with GUI.
I found the following description in Media Manager System
Administrator's Guide. By guide, we should(or must) use bplabel command
for standalone drives, because with GUI we cannot specify which drive
the target tape mounted in.

> For standalone drives, the standalone drive extension feature makes
> it unnecessary to labelmedia in a standalone drive You can, however,
> pre-label tapes by using the bplabel command.

"bplabel -m -d -u " works fine. Try it.

[Stefan_Ettrich]

Yes, thats it. A really funny solution!
Thanks for your support,
best wishes
stefan