Conference decwet::networker

I have an ongoing issue at a customer. The have a RW531 and a
Alphastation 255 running UNIX. 

They were sold this config to do archiving.  The first issue was that
the 255 needs UNIX V3.2g and OSMS doesn't run on anything past V3.2c. To
solve this problem we loaned the customer a DEC 3000/600 until version
1.5 of OSMS ships. 

All the customer wants is to start a backup on platter 1a and have the
jukebox swap the platters as they fill. 

First we configured OSMS, the docs are a joke. Then was told for
automated control of the platters to install CLCxxx (scsi cam software).
The system would not rebuild the kernal after the CLCxxx was installed
due to a conflict with another installed product. Other than base UNIX,
OSMS was the only thing installed. A call to the CSC said the OSMS has
it's on SCSI CAM drivers and do not install CLCxxx. After deleting both
CLCxxx and OSMS, then reinstalling OSMS back to square one. 

The OSMS group at CSC told me for automated controll to use NSR. Great
they have a NSR license. 

Installed NSR, spent a lot of time trying to figure out all the nsr
commands to run, jbm_enabler and nsr_jukebox ect... . NSR know sees the
jukeboc as /dev/jb0 and the drives as /dev/od1 and od2. 

When I try to label the disks, I get a "no such device" error. 

With UNIX and OSMS we were able to mount and write to the drives at the
/dev/od* address. 

Does anybody have a cookbook on how to set up NSR and a jukebox? I can
blow away the system and start from scratch if it will help. 

I will cross-post this in the networker conferance. Thanks in advance.. 

Tom Cox
617-676-4305
dtn 238-4305
[email protected]
freebe::cox

if this helps, great, but this is from memory, and a few experiences.

 I recall the CLC kit, when installed, creates 2 "device" constructors
 (my words) -- one for disks (rz), and one for opticals (op? rop?).

 so when you ./MAKEDEV op4 (or whatever), you get optical device types
 and NetWorker (via CLC) properly handles them.

 I suggest since this customer already has NetWorker, they remove OSMS
 subsets, and leave CLC subsets, install BRX subsets (NetWorker) and 
 do the ./MAKEDEV, and remember to ./MAKEDEV.MC <controller> for the 
 optical.

  All this is written up in the CLC guide (install?) [which of course I do not
 have!] -- but have a lash at it.

	There is a BIG disconect here in what they are trying to do.

	If they want a backup solution get rid of OSMS completely and
	use the op devices.  OSMS is not needed for NetWorker to use
	opticals.

	If they want Optical support with all volumes in the jukebox
	apearing to be mounted at all times then get rid of NetWorker
	and use the od devices.

	OSMS can change platters, the od device is a combination
	optical interface and media changer in one.  tar, dump etc.
	will work with OSMS but if the current device fills they will
	not continue on to another.  If they are using the opticals as 
	extended hard drives then OSMS works fine.

	They can not have optical as both general purpose disk drives
	and an automated backup with platter changes.

	These two products are not integrated and have not been tested
	to work together. Please avoid this.

The last to replies have been a big help. I will be out to the customer
today or tommorow and do the following.

Remove OSMS

Remove NSR

Install CLC311

Install NSR 3.2a

Run jbm_enabler

Am I missing anything?

Tom Cox

	Unless you can't I'd start with NetWorker 4.2a not 3.2a.

If NSR V4.2a is supported under V3.2c, I'll use it.

Nope, use NetWorker V4.2B.  It is supported under DU V3.2C.

Wes

I can't find V4.2b on the UNIX V4.0b CD's or on 
the January 97 software product Cd's. 

Is V4.2b shipping yet?

Tom Cox

Sorry, I typed before I looked. Found the kit.

	You may already have it working but since I can't remeber how
	well optical is documented here's a simple setup procedure:

	1.  Install both the optical and media changer drivers from CLC311.
            Select the kernel rebuild for the second driver.  If the root
	    partion is short of space you will have to move the new kernel
	    by hand.

	2.  Create the op device with /dev/MAKEDEV.op, see the op man page.

	3.  Define the op devices in NetWorker for example:
		/dev/rop4c   /dev/rop5c  /dev/rop6c ...

	4.  Create the jukebox with jbm_enabler.  Select option 1 and 
	    accept the displayed jukebox.  jbm_enabler will create the 
	    media changer device if needed so just take the default.

	5.  Enter the optical devices when asked for the drives.  Make sure
	    they are entered with drive one of the jukebox first.  Some
	    are shipping with the SCSI IDs of the drives inverted so check
	    using the controls on the jukebox.

	6.  Have fun watching it all work.
	    

It almost worked.

I removed OSMS and NSR, then installed CLC and reinstall NSR.

Ran MAKEDEV.OP and MAKEDEV.MC . A "file" on op20c and op21c
show up as RWZ52 at the correct scsi id'd and drive numbers.
The same for mc22, RW531 at the correct address.

I then ran jbm_enabler, chose option 1. 
jbm_enabler chose [email protected], which is the correct address.
For the two drives I entered  "/dev/op20c" and /dev/op21c", after
each one I was asked drive type. I picked "optical"

I then got a error message...
jbm_enabler: RPC error, Jukebox lmf license in not install properly

I didn't think I needed any other licenses than NSR server. I tried 
a temp pak for "jukebox-tier-1", but still got the same error.

Any ideas??

Thank for all the response to this note.

Tom Cox

  RTFM, I found the license answer in the SPD,
  I need a "tier-2" license for 17-64 slots.

Tom Cox

    
    
    Message-Id: <[email protected]>
    To: [email protected]
    Cc: loh
    Subject: Quick question on optical jukebox 
    Date: Fri, 14 Feb 97 13:47:07 -0500
    From: "Lannie Loh" <loh>
    X-Mts: smtp
    
    
    Wes,
    
    Sorry to bother you with this email.  I just spoke to Tom Cox, the FE
    that
    had a problem with CLCOP and OSMS conflict.  He is on customer site,
    and can't wait too long, so I am trying to get a quick answer for him.
    If you don't have the answer, could you please forward this mail to the 
    right person?  Thanks!
    
    He has configured the jukebox without any error.  When trying to label
    volumes, he got this error:
    
    Verify label operation in progress
    Can't read disk label: no such device or address
    (repeat above two lines)
    Label without mount operation inporgress
    Labelled optical disk <volume_name>
    Eject operation in progress
    (then volume ejected)
    .
    .
    . (repeat above for all 32 platters)
    .
    .
    
    He can see all the volumes in the Volumes window.  He then went
    ahead to mount the first volume, he got this:
    
    Mount operation in progress
    Can't read disk label: no such device or address
    Verify label operation in progress
    Can't read disk label: no such device or address
    
    Any idea what he is missing?  
    
    Thanks,
    Lannie 
    

is this a two sided optical?? are they being labelled as such?

Can they post the /nsr/res/nsrjb.res??

    
    Tom is on customer site, and the system is not on the network.
    Can't send me email.  Any specific thing you want me to check in
    this file?
    
    Thanks,
    Lannie

Lannie, Tom --

Back in reply .11, Roger mentioned the fact that new optical jukeboxes are
delivered with their SCSI ids in descending order, e.g. the first drive
might have id 4 and the second 3.  Roger, et al., correct me on this, but...
this may affect the order in which the drives have to be listed in the
NetWorker jukebox configuration.  They may need to be listed with the
"first" drive first.  This would have the device numbers in descending
order, e.g. /dev/rop12c /dev/rop11c.

The SCSI ids can be displayed from the front panel of the jukebox -- the
jukebox will show the ids for the two drives with the id for the "first"
drive first.

To test the configuration, load a platter into only one drive using
whatever commands NetWorker provides -- can anyone help with this?
(It has to be something that uses NetWorker's jukebox configuration.)
Run "file" on the raw device files for the two drives and see which
one is online.  Is it the right one?

>> Can they post the /nsr/res/nsrjb.res??

> Tom is on customer site, and the system is not on the network.
> Can't send me email.

Is Tom near a DEC facility?  If so, maybe he could get the nsrjb.res on
tape, and send it from the DEC facility.

Bruce --

> is this a two sided optical?? are they being labelled as such?

Is this a particular medium type that they should select when configuring
the drives? the jukebox?

-- Pat

    
    Pat,
    
    Thanks for your information.  Tom has left the customer site.  
    I don't even know if the problem has solved yet.  It's really hard to 
    support for situation like this.  Firstly, we don't have an optical 
    jukebox here in the CSC.  Secondly, there is not much in documentation 
    regarding optical jukebox configuration and troubleshooting.  I would 
    be extremely frustrated if I were in his situation.
    
    Thanks,
    Lannie  

    I have left a voice mail for the customer to FTP or print the
    /nsr/res/nsrjb.res file for me. Today, Monday, is a holiday in MA and
    the customer is out. 
    
    The drives were configured in NSR as /dev/op20c and /dev/op21c not as
    the raw device /dev/rop*. The drives are listed as /dev/op20c first
    followed by /dev/op21c, does this mean scsi id 4 is before scsi id 5?
    
    Tom Cox

	Stick with the basics first.

	While you need to use the raw devices the error is not caused
	by that.  "No such device or address" would make me think that
	the driver isn't even seeing the drives.  

	Use the file command to verify that the driver is seeing the 
	optical drives.  'file /dev/rop*c'.  If it just says character
	special or something like that you have a driver setup or
	configuration problem.

	Use the jukebox's controls to put a platter in each drive one
	at a time and use the file command to verify that it works.

	If the SCSI IDs for the RW531 are set to the defaults you will
	need to use /dev/rop21c for the first drive and /dev/rop20c for
	the second drive.  This is if the drive 1 is at SCSI ID 5 and
	drive 2 is at SCSI ID 4.  Use the controls on the jukebox to check.

    Last things first. The scsi id's are 4 and 5 for the drives. When I ran
    jbm_enabler, I put id 4 , /dev/op20c, as the first drive and id 5,
    /dev/op21c as the second. I will change that so id 5, /dev/op21c, is
    the first drive.
    
    Second, when I run jbm_enabler, should I use the raw rop* device?
    
    The file command on /dev/rop* returns "SCSI #4 RWZ52 device 160" or
    something like that, I typing for memory. File on "/dev/mc22" returns
    "SCSI #6 RW531 device 176"
    
    Tom Cox

	Yes you must use the raw devices for the software to operate
	properly.�The file commands show that the driver seems to be working
	so getting the order right should help.

	Please make sure that you have the previous replys about the setup
	in hand, I think we have covered most of the actions needed
	to work it out step by step.