Have you tried using
tpconfig? In the past, I’ve always configured my robots & drives via
tpconfig, versus using the wizard. I only started using the wizard when we
introduced Windows servers into our environments.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Taylor, David
(MARSYS)
Sent: Monday, July 14,
2008 12:46
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] robot not
enabled.
thanks dave. yes
the os does see the library as well as the drive.
SunOS truxtun 5.10
Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V210
bash-3.00#
/usr/openv/volmgr/bin/sgscan
/dev/sg/c0t0l0: Disk (/dev/rdsk/c1t0d0):
"FUJITSU MAW3073NCSUN72G"
/dev/sg/c0t1l0: Disk (/dev/rdsk/c1t1d0): "FUJITSU
MAW3073NCSUN72G"
/dev/sg/c1t0l0: Changer: "EXABYTE LTO 1x7
2U"
/dev/sg/c1t3l0: Tape (/dev/rmt/0): "HP
Ultrium 3-SCSI"
bash-3.00#
/usr/openv/volmgr/bin/scan
************************************************************
***********************
SDT_TAPE ************************
***********************
SDT_CHANGER ************************
*********************** SDT_OPTICAL
************************
************************************************************
------------------------------------------------------------
Device
Name : "/dev/sg/c1t0l0"
Passthru Name: "/dev/sg/c1t0l0"
Volume
Header: ""
Port: -1; Bus: -1; Target: -1; LUN:
-1
Inquiry : "EXABYTE LTO 1x7
2U B00B"
Vendor ID : "EXABYTE
"
Product ID : "LTO 1x7 2U "
Product Rev:
"B00B"
Serial Number:
"000087005544"
WWN :
""
WWN Id Type : 0
Device Identifier: "EXABYTE LTO 1x7
2U 000087005544"
Device Type
: SDT_CHANGER
NetBackup Robot Type:
8
Removable : Yes
Device Supports:
SCSI-4
Number of Drives : 1
Number of Slots : 7
Number of Media
Access Ports: 0
Drive 1 Serial Number :
"D217H001HU"
Flags : 0x0
Reason:
0x0
------------------------------------------------------------
Device
Name : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c1t3l0"
Volume
Header: ""
Port: -1; Bus: -1; Target: -1; LUN:
-1
Inquiry : "HP Ultrium
3-SCSI D217"
Vendor ID : "HP
"
Product ID : "Ultrium 3-SCSI "
Product Rev: "D217"
Serial
Number:
"HU171200RB"
WWN :
""
WWN Id Type : 0
Device Identifier: ""
Device
Type : SDT_TAPE
NetBackup Drive Type:
16
Removable : Yes
Device Supports:
SCSI-3
Flags : 0x0
Reason: 0x0
bash-3.00#
/usr/openv/volmgr/bin/tpconfig -l
Device Robot
Drive
Robot
Drive
Device
Second
Type
Num
Index Type
DrNum Status
Comment
Name
Path
Device Path
robot
0
-
TLD
-
-
- -
/dev/sg/c1t0l0
drive
-
0
hcart3
-
UP - HP.ULTRIUM3-SCSI.000
/dev/rmt/0cbn
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Cornely, David
Sent: Monday, July 14, 2008 12:32
PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] robot not
enabled.
Does the OS see the
robot? Check that using sgscan -- if the OS doesn’t see the changer then
that’s your problem.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Taylor, David
(MARSYS)
Sent: Monday, July 14,
2008 12:19
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] robot not
enabled.
good
morning.
i am setting up a test disaster recovery server running netbackup 6
mp5
on a v210 with solaris 10 with a exabyte magnum 1x7
autoloader.
running the storage device wizard fails thus leaving the robot
disabled
"not enabled", the lto 3 tape drive is picked up without
problems.
i have tried to configure the robot manually using tpconfig but get
the
some results.
any ideas?
thanks,
dave..