[Veritas-bu] Examples of SSO vm.conf files
2006-01-27 19:32:00
Subject: |
[Veritas-bu] Examples of SSO vm.conf files |
From: |
SJACOBSO AT novell DOT com (Scott Jacobson) |
Date: |
Fri, 27 Jan 2006 17:32:00 -0700 |
This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=__PartDAF84E90.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Kathryn,
In a SSO environment your Drive Names must be unique.
In my environment for example, from the Master, run "vmoprcmd". These
are the names I use
to keep things straight.
-sj
>>> Kathryn Hemness <kfhemness AT ucdavis DOT edu> 1/27/2006 4:41 pm >>>
Hi Mark --
Here are my tpconfigs on both the Master and Media servers:
Master server: /usr/openv/volmgr/bin/tpconfig -d
Index DriveName DrivePath Type Shared
Status
***** ********* ********** **** ******
******
0 Hagrid-1 /dev/rmt/3cbn hcart2 Yes
UP
TLD(0) Definition DRIVE=1
1 Hagrid-2 /dev/rmt/2cbn hcart2 Yes
UP
TLD(0) Definition DRIVE=2
2 Hagrid-3 /dev/rmt/1cbn hcart2 Yes
UP
TLD(0) Definition DRIVE=3
3 Hagrid-4 /dev/rmt/0cbn hcart2 Yes
UP
TLD(0) Definition DRIVE=4
Currently defined robotics are:
TLD(0) robotic path = /dev/sg/c0tw2001005013e00369l1,
volume database host = albus.ucdavis.edu
*******************************************************************************
Media Server:# /usr/openv/volmgr/bin/tpconfig -d
Index DriveName DrivePath Type Shared
Status
***** ********* ********** **** ******
******
0 Hagrid-1 /dev/st/nh1c0t0l2 hcart2 Yes
UP
TLD(0) Definition DRIVE=1
1 Hagrid-2 /dev/st/nh1c0t0l3 hcart2 Yes
UP
TLD(0) Definition DRIVE=2
2 Hagrid-3 /dev/st/nh1c0t0l4 hcart2 Yes
UP
TLD(0) Definition DRIVE=3
3 Hagrid-4 /dev/st/nh1c0t0l5 hcart2 Yes
UP
TLD(0) Definition DRIVE=4
Currently defined robotics are:
TLD(0) robot control host = albus.ucdavis.edu
volume database host = albus.ucdavis.edu
All I/O is still going through the device paths of the Master Server.
On Fri, 27 Jan 2006 Mark.Donaldson AT cexp DOT com wrote:
> Date: Fri, 27 Jan 2006 15:51:24 -0700
> From: Mark.Donaldson AT cexp DOT com
> To: kfhemness AT ucdavis DOT edu, veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] Examples of SSO vm.conf files
>
> It's not vm.conf, it's tpconfig.
>
> Be sure which drives are the shared ones, ie /dev/rmt/x on server1
is
> /dev/rmtY on server2. Then carefully setup the drives as shared
drives via
> tpconfig.
>
> vm.conf is plain.
>
> Really, the manual is your friend on an SSO setup.
>
> -M
>
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Kathryn
> Hemness
> Sent: Friday, January 27, 2006 2:26 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Examples of SSO vm.conf files
>
>
> Greetings -
>
> I'm trying to setup SSO for an LTO2 library shared between a Solaris
9
> Master and a RHEL3 Linux Media server. Can someone give me examples
of
> the vm.conf files on each server?
>
> Right now, I'm using an evaluation license and I can see drives
> on both Master and Media servers and the robotic is controlled
> by the Master. However, all of the traffic is still going through
> the Master server. The Master server has a vm.conf but my Linux
> media server doesn't.
>
>
> --kathy
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
--kathy
===============================================================================
Kathryn Hemness kfhemness AT ucdavis DOT edu
System Administrator phone: 530.752.6547
Campus Data Center & Client Services fax: 530.752.9154
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=__PartDAF84E90.1__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Kathryn,</DIV>
<DIV> </DIV>
<DIV>In a SSO environment your Drive Names must be unique.</DIV>
<DIV> </DIV>
<DIV>In my environment for example, from the Master, run "vmoprcmd". =
These are the names I use</DIV>
<DIV>to keep things straight.</DIV>
<DIV> </DIV>
<DIV>-sj<BR><BR>>>> Kathryn Hemness <kfhemness AT ucdavis DOT
edu> =
1/27/2006 4:41 pm >>><BR>Hi Mark --<BR><BR>Here are my tpconfigs =
on both the Master and Media servers:<BR><BR>Master server: /usr/openv/volm=
gr/bin/tpconfig -d<BR><BR>Index DriveName &nbs=
p; DrivePath &nb=
sp; =
Type Shared Status<BR>***** ********* &n=
bsp; =
**********  =
; **** ****** ******<BR>&nb=
sp; 0 Hagrid-1 &=
nbsp; /dev/rmt/3cbn &n=
bsp; hcart2 Yes =
UP<BR> TLD(0) =
Definition DRIVE=3D1<BR> =
1 Hagrid-2  =
; /dev/rmt/2cbn =
hcart2 Yes &nbs=
p; UP<BR> TLD(0) =
Definition DRIVE=3D2<BR> =
2 Hagrid-3  =
; /dev/rmt/1cbn =
hcart2 Yes &nbs=
p; UP<BR> TLD(0) =
Definition DRIVE=3D3<BR> =
3 Hagrid-4  =
; /dev/rmt/0cbn =
hcart2 Yes &nbs=
p; UP<BR> TLD(0) =
Definition DRIVE=3D4<BR><BR>Currently =
defined robotics are:<BR> TLD(0) robotic =
path =3D /dev/sg/c0tw2001005013e00369l1,<BR> &=
nbsp; volume database host =3D =
albus.ucdavis.edu<BR><BR>**************************************************=
*****************************<BR><BR>Media Server:# /usr/openv/volmgr/bin/t=
pconfig -d<BR>Index DriveName &nbs=
p; DrivePath &nb=
sp; Type &=
nbsp; Shared Status<BR>***** ********* &=
nbsp; **********  =
; =
**** ****** ******<BR> 0 =
Hagrid-1 &=
nbsp; /dev/st/nh1c0t0l2 &nbs=
p; hcart2 Yes UP<BR> &=
nbsp; TLD(0) Definition &nbs=
p; DRIVE=3D1<BR> 1 Hagrid-2 =
/dev/st/nh1c0t=
0l3 hcart2 Yes &=
nbsp; UP<BR> =
TLD(0) Definition DRIVE=3D2<BR> =
2 Hagrid-3  =
; /dev/st/nh1c0t0l4 &n=
bsp; hcart2 Yes =
UP<BR> TLD(0) Definition &nb=
sp; DRIVE=3D3<BR> 3 Hagrid-4 =
; &n=
bsp; /dev/st/nh1c0t0l5 hcart2&nbs=
p; Yes UP<BR> &n=
bsp; TLD(0) Definition =
DRIVE=3D4<BR><BR>Currently defined robotics are:<BR> TLD(0) &nbs=
p; robot control host =3D albus.ucdavis.edu<BR> &nbs=
p; volume database =
host =3D albus.ucdavis.edu<BR><BR>All I/O is still going through the =
device paths of the Master Server.<BR><BR><BR><BR>On Fri, 27 Jan 2006 =
Mark.Donaldson AT cexp DOT com wrote:<BR><BR>> Date: Fri, 27 Jan 2006
15:51:24 =
-0700<BR>> From: Mark.Donaldson AT cexp DOT com<BR>> To:
[email protected]=
du, veritas-bu AT mailman.eng.auburn DOT edu<BR>> Subject: RE: [Veritas-bu] =
Examples of SSO vm.conf files<BR>><BR>> It's not vm.conf, it's =
tpconfig.<BR>><BR>> Be sure which drives are the shared ones, ie =
/dev/rmt/x on server1 is<BR>> /dev/rmtY on server2. Then =
carefully setup the drives as shared drives via<BR>> tpconfig.<BR>><B=
R>> vm.conf is plain.<BR>><BR>> Really, the manual is your friend =
on an SSO setup.<BR>><BR>> -M<BR>><BR>> -----Original =
Message-----<BR>> From: veritas-bu-admin AT mailman.eng.auburn DOT
edu<BR>> =
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of
Kathryn<BR>>=
; Hemness<BR>> Sent: Friday, January 27, 2006 2:26 PM<BR>> To: =
veritas-bu AT mailman.eng.auburn DOT edu<BR>> Subject: [Veritas-bu] Examples
=
of SSO vm.conf files<BR>><BR>><BR>> Greetings -<BR>><BR>> =
I'm trying to setup SSO for an LTO2 library shared between a Solaris =
9<BR>> Master and a RHEL3 Linux Media server. Can someone give me =
examples of<BR>> the vm.conf files on each server?<BR>><BR>> =
Right now, I'm using an evaluation license and I can see drives<BR>> on =
both Master and Media servers and the robotic is controlled<BR>> by the =
Master. However, all of the traffic is still going through<BR>> =
the Master server. The Master server has a vm.conf but my Linux<BR>&g=
t; media server doesn't.<BR>><BR>><BR>> --kathy<BR>> __________=
_____________________________________<BR>> Veritas-bu maillist =
- Veritas-bu AT mailman.eng.auburn DOT edu<BR>>
http://mailman.eng.auburn=
.edu/mailman/listinfo/veritas-bu<BR>><BR><BR>--kathy<BR><BR>=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<BR>Kathryn Hemness &n=
bsp;  =
; kfhemness AT ucdavis DOT edu<BR>System
Administrator &nbs=
p; &=
nbsp; phone: 530.752.6547<BR>Campus Data Center & Client =
Services fax: 530.752.9154<BR>_____________________=
__________________________<BR>Veritas-bu maillist - Veritas-bu@=
mailman.eng.auburn.edu<BR>http://mailman.eng.auburn.edu/mailman/listinfo/ve=
ritas-bu<BR></DIV></BODY></HTML>
--=__PartDAF84E90.1__=--
|
|
|