Gotcha.
Looks like I was following two different docs, and tripped myself up.
The initial doc reccommended going to /usr/openv/volmgr/bin/, making a
temp dir, and running ../sg.build from the temp dir, then running
../driver/sg.install.......seems osmewhere along the way I ran the
sg.install from the driver directory, which pushed an old sg.links file
into devlinks.tab.....I caught the fact that it pushed the wrong sg and
st.conf info, but missed the links.
I guess I ran into two different problems at different times that lead
to me getting almost there....got that cleared up now.
Looks good now. #sgscan sees all 14 tape drives..... Only issue is when
autodiscovering via the wizard, under limitations, the LTO3 drives are
showing up as "Yes, See limitations", and limitations says "unable to
determine drive type."
#tpautoconf -t reads:
bash-2.03# tpautoconf -t
TPAC45 IBM ULTRIUM-TD2 4770 1110068452 -1 -1 -1 -1 /dev/rmt/5cbn
- -
TPAC45 IBM ULTRIUM-TD2 4770 1110078586 -1 -1 -1 -1 /dev/rmt/4cbn
- -
TPAC45 HP Ultrium 3-SCSI L25S HU10528BTE -1 -1 -1 -1 /dev/rmt/3cbn
- TapeAlert enabled
TPAC45 IBM ULTRIUM-TD2 4770 9110075386 -1 -1 -1 -1 /dev/rmt/2cbn
- -
TPAC45 IBM ULTRIUM-TD2 4770 1110078601 -1 -1 -1 -1 /dev/rmt/1cbn
- -
TPAC45 HP Ultrium 3-SCSI L25S HU10526500 -1 -1 -1 -1 /dev/rmt/0cbn
- TapeAlert enabled
TPAC45 IBM ULTRIUM-TD2 4770 1110079472 -1 -1 -1 -1
/dev/rmt/13cbn - -
TPAC45 IBM ULTRIUM-TD2 4770 1110135154 -1 -1 -1 -1
/dev/rmt/12cbn - -
TPAC45 HP Ultrium 3-SCSI L25S HU10528BRV -1 -1 -1 -1
/dev/rmt/11cbn - TapeAlert enabled
TPAC45 HP Ultrium 3-SCSI L25S HU10528BTA -1 -1 -1 -1
/dev/rmt/10cbn - TapeAlert enabled
TPAC45 IBM ULTRIUM-TD2 4770 1110078600 -1 -1 -1 -1 /dev/rmt/9cbn
- -
TPAC45 IBM ULTRIUM-TD2 4770 1110134138 -1 -1 -1 -1 /dev/rmt/8cbn
- -
TPAC45 HP Ultrium 3-SCSI L25S HU1052650L -1 -1 -1 -1 /dev/rmt/7cbn
- TapeAlert enabled
TPAC45 HP Ultrium 3-SCSI L25S HU105264YL -1 -1 -1 -1 /dev/rmt/6cbn
- TapeAlert enabled
> -----Original Message-----
> From: Paul Gimpelev [mailto:paulg AT IXISCM DOT COM]
> Sent: January 23, 2006 11:56 AM
> To: Paul Keating; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] anyone using LTO3 with Solaris 8?
>
>
> Not sg devices, they need to be created "separately".
>
> paulg
>
> On Jan 23, 11:25am, Paul Keating wrote:
> > Subject: RE: [Veritas-bu] anyone using LTO3 with Solaris 8?
> > That's one I missed.
> >
> > Was just pointed out to me by my VAR.
> >
> > What do you mean by "solaris does not know how to created
> devices" ??
> >
> > The OS sees all the devices fine....
> >
> > #cfgadm -al -o show_FCP_dev - returns everything I expect.
> >
> > ok# boot -r - creates all the devices properly....just that sgscan
> > doesn't see all of them.
> >
> > Paul
> >
> > > -----Original Message-----
> > > From: Paul Gimpelev [mailto:paulg AT IXISCM DOT COM]
> > > Sent: January 23, 2006 10:56 AM
> > > To: Paul Keating; veritas-bu AT mailman.eng.auburn DOT edu
> > > Subject: Re: [Veritas-bu] anyone using LTO3 with Solaris 8?
> > >
> > >
> > > Paul,
> > >
> > > There is one more piece that you are missing - you need
> > > to modify
> > > /etc/devlink.tab. Your config is correct, but solaris does
> > > not know how to
> > > created devices. You also might want to apply latest st
> > > patch so LTO3 is
> > > supported natively (no more st.conf Ultrium= entries). Let
> > > me know if you have
> > > trouble figuring out devlink.tab.
> > >
> > > paulg
> > >
> > > On Jan 23, 9:30am, Paul Keating wrote:
> > > > Subject: [Veritas-bu] anyone using LTO3 with Solaris 8?
> > > >
> > > >
> > > > I previously had four LTO2 drives in each of two
> > > libraries....do to a
> > > > bad GBIC in a switch, and several subsequent events, one
> > > drive wasn't
> > > > visable, so my backup server was only seeing 7 drives.
> > > >
> > > > Last night, I replaced the 8 port Sun FC switches with
> a couple of
> > > > Brocade 3800s that were released from another project,
> and added an
> > > > additional 3 LTO3 drives in each library.
> > > >
> > > > I did a /usr/openv/volmgr/bin/sg.build, followed by an
> sg.install
> > > >
> > > > I've added the following to the /kernel/drv/st.conf
> > > >
> > > > "HP Ultrium 3", "HP Ultrium LTO3",
> > > "ULTRIUM3";
> > > >
> > > > ULTRIUM3 = 1,0x36,0,0xd639,4,0x44,0x44,0x44,0x44,3;
> > > >
> > > > I can see all the drives when I do a:
> > > > bash-2.03# cfgadm -al -o show_FCP_dev
> > > >
> > > > all eight LTO2, and six LTO3
> > > >
> > > > devfsadm, or a boot -r picks up all the devices properly,
> > > and creates
> > > > all the proper device files, but sgscan sees only the 7
> LTO2 drives.
> > > > I used tpconfig to remove all of the old drive configs and
> > > re-ran the
> > > > GUI device configuration wizard, but it sees 7 LTO2 drives,
> > > and 2 drives
> > > > of unknown type.
> > > >
> > > > sg.conf is up to date with all WWN maps, etc.....so
> sg.conf isn't
> > > > reporting any errors about unmapped WWNs.....
> > > >
> > > > I used tpconfig and manually configured all 14 drives and
> > > can exercise
> > > > them using robtest, but sgscan and the device config wizard
> > > still see
> > > > the same.
> > > >
> > > > any idears?
> > > >
> > > > Paul
> > > >
> > > > [ Attachment (text/x-html): ".prt10253sDcbb" 4237 bytes
> > > > Character set: us-ascii
> > > > Encoded with "quoted-printable" ]
> > > >-- End of excerpt from Paul Keating
> > >
> > >
> >
> > _______________________________________________
> > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >-- End of excerpt from Paul Keating
>
>
|
