[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

521.0. "TL812 doesnt' work with 4.2B !!!!!!!" by TRN02::FRASSINO () Mon Mar 24 1997 06:50

    Hi all,
    I would like to share with you the last unbelievable behaviour of NSR
    v4.2b.
    I've configured a new TL812: it is working with every utility you can
    imagine
    
    mcutil
    robot
    xrobot
    tar
    dd
    cpio 
    
    So, really excited, I've installed NSR v4.2b FROM SCRATCH.
    Apparently all is ok ( apart previous notes' problems ), so I've done
    jb_config, specifying that I'm using a "TL810 Series" and TZ88 as
    nrmt*h. As far as I know, I'm right.
    Now: for any kind of operation I perform 
    
    nsrjb -d ...
    nsrjb -w ...
    nsrjb -I ...
    
    I ALWAYS RECEIVE AN "I/O error".
    
    Since today is a new week, and the weather is changing, and the ideas
    are confused, I decide TO DOWNGRADE TO v3.2A.
    I haven't made modification to mcxx and special files.
    I deinstall v4.2B, deleting all /nsr , and reinstall v3.2A from
    scratch.
    I run jbm_enabler, specifing TL810 and TZ87, 
    
    AND ALL IS WORKING WELL AND FAST.
    
    I can't believe it.
    
    The only suspect I have is that ON THE TL812 console I see "TL810
    v1.20" as firmware release, and on the v4.2b kit there is no the file
    camconf.0, present in v3.2A.
    
    Please, give me a logical explanation, or better, give me a contect to
    a person that HAS PERSONALLY INSTALLED TL812 at least once.
    
    This is reality, not a nightmare.
    
    			*8-( Pierpa
T.RTitleUserPersonal
Name
DateLines
521.1Device order?DECWET::RWALKERRoger Walker - Media ChangersMon Mar 24 1997 07:4810
	With a TL812 the "I/O error" usually indicates that the drives
	are not defined in the same order to NetWorker and to the
	device.  The quickest way to check this is to load a tape
	into the first drive with the front controls on the library
	and then use the 'file /dev/nrmt*h' command to check which
	tape device shows a loaded tape.  Repeat this with the
	other drives.  Extra care must always be taken with multiple
	bus libraries to match the tape files to the physical devices.

	camconf.0 is not used with NetWorker 4.2a and up.
521.2I repeat, V3.2A WORKS !!!TRN02::FRASSINOMon Mar 24 1997 08:436
    Excuse me,
    but why all the stuff works WITH V3.2A without mcxx and *rmt*h
    rebuilding ??
    
    This is really the mystery !!
    			*8-) Pierpa
521.3DECWET::RWALKERRoger Walker - Media ChangersMon Mar 24 1997 09:3910
	Pierpa, the software works.  We use it daily and configure a 
	TL810/12/?? almost every week.  Something is different between
	your installations.  I can't tell from here what the problem is and
	I don't wany to just ask questions that will take days to
	get back and forth.  I know that you can solve the problem faster	
	if you have some background and don't have to stop and wait	
	for us each step.

	The information I gave you in .1 has fixed every know problem
	installing a TL812 with NetWorker.  What more can i do?
521.4Hup.TRN02::FRASSINOMon Mar 24 1997 09:552
    Ok, I'll Ctrl-O.
    			*8-) Pierpa
521.4CLC v3.1 was the reason !!TRN02::FRASSINOTue Mar 25 1997 02:2118
    Hi guys,
    I've solved my problem.
    The incorrect configuration was:
    
    O.S. v4.0B
    CLC v3.1
    NSR v4.2B
    
    I deinstall CLC310 and install CLC v3.1A. So now
    
    O.S. v4.0B
    CLC v3.1A
    NSR v4.2B
    
    And the TL812 works PERFECTLY !!
    
    Thanks anyway for your patience !!
    					*8-) Pierpa
521.5DECWET::ONOSoftware doesn't break-it comes brokenTue Mar 25 1997 08:426
There sure are a lot of pieces.  I forgot to ask about CLC when
we spoke on the phone. 

Great work!

Wes