You are on page 1of 7

How to configure ovpass on AIX Page 1 of 7

Support Home | Supported Products A to Z

Knowledge Base
Document ID: 326806 Search
http://support.veritas.com/docs/326806
E-Mail this document to a colleague Advanced Search Op
Other Support Re
How to configure ovpass on AIX
 Support Forum
Ask an expert. J
product discussi
Forum communi
Details:
 Manage Cases
Determine the following: Submit and man
cases using MyS
Is the robot directly attached to the RS6000 via SCSI cable?  Contact Techni
Find the support
Is the robot directly attached to the RS6000 via Fiber cable? for your region.

Is there a bridge or switch between the RS6000 and the robot and drives?
Is the robot and drive hardware manufactured by IBM? Was this article h

j Yes n
k
l
m
n j No
k
l
m
On which adapter (fiber or SCSI) is the robotic control arm attached?
If any information wa
information you were
provided, please let u
Use the following command to determine what controller cards are on the RS6000: feedback will help us
service.
# lsdev -l | grep I/O (Enter comment her

For SCSI attached robot and drives, the SCSI ID and logical unit is assigned by the OS. (Optional Email Add

For fibre attached robot and drives, the SCSI ID and logical unit will be assigned via the
switch.
You will use an I/O controller similar to these when you run the mkdev command to create NOTE: Comments e
the ovpass pass through driver. NOT receive support
need Symantec Ente
support, please click

For Fiber attached robot:


fscsi0 Available xx-08-01 FC SCSI I/O Controller Protocol Device
fscsi1 Available xx-03-01 FC SCSI I/O Controller Protocol Device
You should see tape drive(s) connected to at least one of the xx-xx-01 interfaces.
# lsdev -Cc tape
rmt1 Available xx-08-01 Other FC Tape Driver
rmt2 Available xx-08-01 Other FC Tape Driver
rmt3 Available xx-03-01 Other FC Tape Driver
rmt4 Available xx-03-01 Other FC Tape Driver

file://H:\study\netbackup\New Folder\How to configure ovpass on AIX.htm 7/6/2010


How to configure ovpass on AIX Page 2 of 7

Then, look at the attributes of each tape drive to see the SCSI ID and LUN assigned to
each. they should be sequential and the robot should fit into the sequence on one of the
interfaces.
# lsattr -El rmt1
# lsattr -El rmt2
# lsattr -El rmt3
# lsattr -El rmt4
You should see that the scsi ID is the same for each tape drive, but the logical unit is
different. The logical unit's should be sequential, for example rmt0 should have 0x0, rmt1
should have 0x1, rmt2 should have 0x2, etc.

So, assuming that the robotic control is on the same HBA, you will need to choose the
proper 0x? lun that is associates with the robot arm. If all the rmt devices are sequential,
then choose the next available logical unit. For example if the last rmt is 0x6, choose 0x7
for the robot:
mkdev -c media_changer -s fcp -t ovpass -p fscsi0 -w 0xa1300,0x7

In the example below, the robotic control arm is connected via the same HBA that the tape
rmt1 drive is connected to. This will be fscsi0 since both are on xx-08-01.

To create ovpass.
# mkdev -c media_changer -s fcp -t ovpass -p fscsi0 -w 0xa1300,0
If robot and drives are SCSI attached:

Check for smc device driver


# lsdev -Cc | grep smc

Do lsattr -El smcX if it exists


# lsdev -Cc tape

LUN's are sequential, robotic control may be somewhere in sequence if not on its own
SCSI interface.

The lsattr command won't show the desired SCSI ID and LUN if drives are SCSI attached
(not fiber attached.)

file://H:\study\netbackup\New Folder\How to configure ovpass on AIX.htm 7/6/2010


How to configure ovpass on AIX Page 3 of 7

Prerequisites:
Make sure all OS patches and APAR's have been applied.
Determine what kind of fiber HBA is being used. IBM 6227/6228/6229 or Cambex.
IBM HBA uses fcp driver, Cambex uses scsi.
1. Determine if robotic control arm is connected to the AIX system via SCSI or fiber.
If SCSI, determine SCSI ID and LUN with these commands:
cfgmgr
lsdev -C | grep smc
smc0 Available
lsattr -El smc0
note SCSI id and lun
(redirected output to a file)
Remove smc0 - rmdev -dl smc0

Then, refer to page 32 of the NetBackup (NBU) 4.5 Media Manager (MM) device
configuration guide.
fcs0 Available 20-58 FC Adapter
fcs1 Available 20-60 FC Adapter
fscsi0 Available 20-58-01 FC SCSI I/O Controller Protocol Device
fscsi1 Available 20-60-01 FC SCSI I/O Controller Protocol Device

Did the mkdev using fscsi1 controller, hex scsi ID from the lsattr output of smc0, and lun of
1 (based on the 20-60-01) output for drives.

If there is no smcX device file, look at lsdev output for tape drives:
robot and drives are scsi attached. In example below, robotic control is most likely at 1 or
3.
rmt0 is -w 0,0
rmt1 is -w 2,0
Did mkdev with 1,0

Robtest produced an error.

file://H:\study\netbackup\New Folder\How to configure ovpass on AIX.htm 7/6/2010


How to configure ovpass on AIX Page 4 of 7

It was necessary to remove ovpass0 and recreate.


# rmdev -dl ovpass0
# mkdev -c media_changer -s scsi -t ovpass -p scsi0 -w 3,0
Used robtest and now ovpass0 is correct.

2. If fiber attached and is NOT IBM hardware:


The smc device drive will not be created and there may be an error when running cfgmgr
pertaining to a missing media changer library. In that case:
Is the robot connected to SAN via same HBA?
If unknown, assume that it is.
Do lsattr -El rmtX for each tape drive
Get scsi ID and LUN information
Robotic control should be one above or one below in the drive LUN sequence. Run mkdev
command based on type of HBA using sequential (and not already used) LUN.
When /dev/ovpassX driver is created, configure it using tpconfig. Use robtest to determine
if NBU can talk to the newly created robot. If no, remove ovpassX and recreate using the
next sequential SCSI ID / LUN.
Example:
Check to see what hardware address is assigned to each HBA, see which ones each
drive is on. Robot is probably on one of the HBA's that has drive attached to it. Need to
determine which one.
0x12b00 fscsi1
rmt1 w/ lun
rmt2 w/ lun 0x1
12a00 fscsi0
rmt3 w/ lun 0x0
rmt4 w/ lun 0x1
mkdev -c media_changer -s fcp -t ovpass -p fscsi0 -w 0x12a00,0x2
Use tpconfig to addd /dev/ovpass0 as new robot
Use robtest to see if NBU can talk to the new robot.

3. If fiber attached and IS IBM hardware:


Do lsattr -El smcX for device driver craated by OS - save output
Remove smcX

file://H:\study\netbackup\New Folder\How to configure ovpass on AIX.htm 7/6/2010


How to configure ovpass on AIX Page 5 of 7

Recreated /dev/ovpass using SCSI ID and LUN output from lsattr of smcX

4. If fiber attached and fiber cable goes from AIX box directly to robot (not via bridge or
switch):
0xcc for ovpass0
0xcb for rmt1
0xcc for rmt2
Robtest failed
There was probably a conflict between ovpass0 and rmt2 or an incorrect LUN was used.
After the removal and recreation of ovpass0 w/ scsi ID 0xca, error occurred again.
Using robtest again generates error = 5,

Remove ovpass again, then performed cfgmgr to recreate the smc0 device for the robot.
lsattr -El smc0 returned
0xcc LUN is 0x1
Removed smc0 (rmdev -dl smc0)
Did ../volmgr/driver/remove_ovpass
Recreated ovpass using the smc SCSI ID and LUN, still getting error.
Could be due to using fcp in mkdev command instead of scsi. Need to know what kind of
HBA is on the system (6228 or cambex).
Turned out that robot was on same SCSI chain as rmt2. Used same SCSI ID and different
LUN.

Symptom:
How to configure robotic control with Fiber HBA on AIX 4.3.3

Solution:
Configure ovpass for robotic control using fiber HBA
smc# device driver doesn't exist to compare LUN's
Example have 8 drives
odm_get gave all the tape drives
If robotic control is daisy chained off 2 of the drives, should be able to look at all scsi Id's

file://H:\study\netbackup\New Folder\How to configure ovpass on AIX.htm 7/6/2010


How to configure ovpass on AIX Page 6 of 7

presented in HEX. Can see the switch index by lun priority and guess which one may be
for robotic control. When trying the different SCSI Id's and LUNs, be sure to remove
ovpass driver completely before trying to add the driver using the next SCSI ID and LUN.
Remove the ovpass device using the rmdev -dl command and run the remove_ovpass
script, then do the install_ovpass and mkdev command using the next SCSI ID and LUN.

Products Applied:
NetBackup Server 6.5.3

Last Updated: October 19 2009 05:31 PM


GMT
Expires on: 365 days from publish date
Subscribe to receive critical updates
about this document
Subjects:
AIX
Publishing Status: Kcs
NetBackup Server
Publishing Status: Kcs

Languages:
English (US)

Operating Systems:
AIX
4.3.3, 5.3

Symantec World Headquarters:


20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support:
http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or
http://ftp.entsupport.symantec.com

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY
OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC
SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,

file://H:\study\netbackup\New Folder\How to configure ovpass on AIX.htm 7/6/2010


How to configure ovpass on AIX Page 7 of 7

CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT
APPLY.

file://H:\study\netbackup\New Folder\How to configure ovpass on AIX.htm 7/6/2010