Hi
Has anyone seen this before?
We have a 3995 C66 attached to an IBM RS/6000 H70 running AIX 4.3.2 and
ADSM 3.1.2.90. We have had a major headache trying to get this optical
jukebox to work!!
The configuration with ADSM has been checked, double checked even triple
checked and no problems can be found. All previous checks as to using
/dev/rop1 no op1 and being set to WORM not OPTICAL etc. were all addressed
but everything was setup as it should be.
We have now 'resolved' the problem and it all seems to be because of the
SCSI ids on the optical drives.
When AIX boots or you manually run 'cfgmgr' it seeks the SCSI bus and adds
the discovered devices to the ODM - therefore we see our omd# devices like
so:
omd0 Available 30-70-00-0,0 SCSI Read/Write Optical Drive
omd1 Available 30-70-00-1,0 SCSI Read/Write Optical Drive
omd2 Available 30-70-00-2,0 SCSI Read/Write Optical Drive
omd3 Available 30-70-00-3,0 SCSI Read/Write Optical Drive
omd4 Available 30-70-00-4,0 SCSI Read/Write Optical Drive
omd5 Available 30-70-00-5,0 SCSI Read/Write Optical Drive
omd0 is SCSI id 0, omd1 is SCSI 1 an so on. Perfectly normal and exactly as
you expect AIX to discover the devices. However, if you configure the ADSM
op# devices to match ie.:
op0 Available 30-70-00-0,0 ADSM Read/Write Optical Drive
op1 Available 30-70-00-1,0 ADSM Read/Write Optical Drive
op2 Available 30-70-00-2,0 ADSM Read/Write Optical Drive
etc.
when attempting to label a cartridge you get the following error:
03/01/01 15:10:10 ANR8779E Unable to open drive /dev/rop1, error number=46.
03/01/01 15:10:16 ANR8815I Remove volume OP1000 from port element 10 of
library OPTICAL0.
03/01/01 15:10:16 ANR8802E LABEL LIBVOLUME process 69 for library OP1000
failed.
03/01/01 15:10:16 ANR0985I Process 69 for LABEL LIBVOLUME running in the
BACKGROUND completed with completion state FAILURE at
15:10:16.
The 'solution' was to manually add the omd# devices rather than let AIX
find them and map omd0 to SCSI id 1 -NOT- 0, omd1 to SCSI 2 etc. as below:
omd0 Available 30-70-00-1,0 SCSI Read/Write Optical Drive
omd1 Available 30-70-00-2,0 SCSI Read/Write Optical Drive
omd2 Available 30-70-00-3,0 SCSI Read/Write Optical Drive
omd3 Available 30-70-00-4,0 SCSI Read/Write Optical Drive
omd4 Available 30-70-00-5,0 SCSI Read/Write Optical Drive
omd5 Available 30-70-00-0,0 SCSI Read/Write Optical Drive
then the ADSM drives as:
op0 Available 30-70-00-1,0 ADSM Read/Write Optical Drive
op1 Available 30-70-00-2,0 ADSM Read/Write Optical Drive
op2 Available 30-70-00-3,0 ADSM Read/Write Optical Drive
op3 Available 30-70-00-4,0 ADSM Read/Write Optical Drive
op4 Available 30-70-00-5,0 ADSM Read/Write Optical Drive
op5 Available 30-70-00-0,0 ADSM Read/Write Optical Drive
This works and all the drives function fine but I have to ask the question
why?? Does the ADSM device driver for 3.1.2 expect to match the element
number with SCSI id or something? Is this a know bug at this level?
Is this how others with 3995-C6n jukeboxes and AIX have their systems
configured? Current software levels are as below:
Fileset Level State Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
D3995diag.jbdd 4.3.0.0 COMMITTED 3995 C Series Library Jukebox
Device Driver
adsm.afs.client.aix42 3.1.20.8 COMMITTED ADSM Client - AFS File Backup
Client
adsm.api.client.aix42 3.1.20.8 COMMITTED ADSM Client - Application
Programming Interface
adsm.butaafs.client.aix42
3.1.20.8 COMMITTED ADSM Client - AFS BUTA Command
adsm.butadfs.client.aix42
3.1.20.8 COMMITTED ADSM Client - DFS BUTA Command
adsm.client.aix42.base 3.1.20.8 COMMITTED ADSM Client - Backup/Archive
adsm.client.aix42.common 3.1.20.8 COMMITTED ADSM Client - Common Files
adsm.client.aix42.hsm 3.1.20.8 COMMITTED ADSM Client - Hierarchical
Storage Management
adsm.devices.NetTAPE-tlc 3.1.2.0 COMMITTED ADSM Device Support for
NetTAPE
adsm.devices.acsls 3.1.2.90 COMMITTED ADSM Device Support for ACS
adsm.devices.rte 3.1.2.90 COMMITTED ADSM Device Support runtime
adsm.dfs.client.aix42 3.1.20.8 COMMITTED ADSM Client - DFS File Backup
Client
adsm.license.rte 3.1.2.0 COMMITTED ADSM Server License
Registration
adsm.msg.en_US.emhelp 3.1.2.20 COMMITTED ADSM EM Panel Help - US
English
adsm.server.rte 3.1.2.90 COMMITTED ADSM Server Runtime
Many thanks in anticipation
Kieron
PS. Apologies for such a long post!
------------------------
Kieron Johnson
Kieron Johnson
JPMorganChase
ETech - UNIX Systems Engineering Development
Telephone: CN: 731-2818 External: +44 (0)1202 342818
Fax Number: CN: 731-7508 External: +44 (0)1202 347508
|
