Quantcast
Channel: Data Protector Practitioners Forum topics
Viewing all articles
Browse latest Browse all 3189

(DP) Support Tip: [12:1405] Device detection not possible for selected client

$
0
0

[Error Message]
IBM LTO devie that is connected to HP-UX can not be detected by the following error .

GUI :
 [12:1405] Device detection not possible for selected client.

CLUI :
# devbra -dev
Passthrough creation
Please use atdd_mksf or insf
mksf: Installing special files for atdd instance 169 address 64000/0xfa00/0x9c
One of atdd or acdd must be specified with -d
mksf: Don't know how to handle driver "atdd"

Tape    IBM:ULTRIUM-TD3  Path: "/dev/rtape/tape169_BESTn"  SN: ".........."
        Description: IBM LTO drive
        Revision: 8711  Device type: lto [13]  Flags: 0x0005


Operating System (HP-UX) recognizes the device with atdd driver .

# ioscan -fnkNC tape
Class     I  H/W Path  Driver S/W State   H/W Type     Description
==================================================================
tape    169  64000/0xfa00/0x9c  atdd     CLAIMED     DEVICE       IBM     ULTRIUM-TD3
                      /dev/rtape/tape169_BEST    /dev/rtape/tape169_BESTnb
                      /dev/rtape/tape169_BESTb   /dev/rtape/tape169_BESTr
                      /dev/rtape/tape169_BESTn


[Cause]
To use atdd device , mksf command is executed to create Passthrough device file but it failed .


[Workaround]
IBM suggests using native operating system device driver (stape on HP-UX) for IBM tape drive .
So, mksf command doesn't expect atdd .

.omnirc variable OB2SAFEINQUIRY=0 can be set on the HP-UX server where the tape device is connected .
It makes DataProtector skip the step of mksf and directly access the related device file. (ex. /dev/rtape/tape169_BESTn)


Viewing all articles
Browse latest Browse all 3189

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>