× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. January 2013

Re: How to handle MOUNTs in a High Availability (HA) environment.

ok, I am sayiing prod lpar has a folder called prod, test lpar has a folder
called test. Each one of these with different IP address/DNS name could
have netsever running each with it's own mapped drive to each one.

On Fri, Jan 25, 2013 at 4:34 PM, <rob@xxxxxxxxx> wrote:

by using netserver to map over an IFS folder are you talking about what I
have to do on the client? Or, are you talking about what I have to do on
the server to 'share' a particular folder? My understanding of Netserver
is that if an lpar of IBM i is a client to another lpar of IBM i as the
server then it accesses it with qntc. qntc will not work in this case for
reasons discussed in threads this week.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/25/2013 04:20 PM
Subject: Re: How to handle MOUNTs in a High Availability (HA)
environment.
Sent by: midrange-l-bounces@xxxxxxxxxxxx



You could use netserver to map over an IFS folder. I am not sure if this
would suffice to what you want to do via using mount(NFS) between your
systems. Are you mimix'n your IFS between systems??

On Fri, Jan 25, 2013 at 4:16 PM, <rob@xxxxxxxxx> wrote:

In what way?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/25/2013 04:07 PM
Subject: Re: How to handle MOUNTs in a High Availability (HA)
environment.
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Rob, had you thought about using netserver.

On Fri, Jan 25, 2013 at 3:06 PM, <rob@xxxxxxxxx> wrote:

I got tired of difficulties presented by QNTC and by QFileSvr.400 and
decided to explore using MOUNT instead. So far I'm impressed. I have
one
more hurdle to jump though. Let me give you some setup information. I
have three lpars. Let's call them: PRIMARY, BACKUP and CLIENT.
PRIMARY
is replicated to BACKUP by our HA software. CLIENT uses MOUNT to
access
stream files in the IFS on the others.
For the sake of our example, let's say the IP address for PRIMARY is
10.10.1.23 and the IP address for BACKUP is 10.17.1.23. Let's say
we've
created an additional DNS entry for TESTSWITCH and set it's IP address
to
10.10.1.23, which is also currently the address for PRIMARY.

I'll go through some setup.

On PRIMARY I run the following:
STRNFSSVR *ALL
EXPORTFS OPTIONS('-I -O') DIR('/mydatadir')

On CLIENT I run the following:
md '/testswitch'
md '/testswitch/mydatadir'
MOUNT TYPE(*NFS) MFS('testswitch:/mydatadir')
MNTOVRDIR('/testswitch/mydatadir')
WRKLNK '/testswitch/mydatadir'
So far, great. I can see the contents of the mydatadir on PRIMARY.

Now I'll simulate a HA switch.
On PRIMARY I run:
EXPORTFS OPTIONS('-U FORCE -F') DIR('/mydatadir')

In the DNS I change TESTSWITCH from 10.10.1.23 to 10.17.1.23, which is
currently the IP address for BACKUP.

On BACKUP I run:
STRNFSSVR *ALL
EXPORTFS OPTIONS('-I -O') DIR('/mydatadir')

On CLIENT I run:
PING TESTSWITCH and it returns 10.17.1.23, the ip address for BACKUP.
WRKLNK '/testswitch/mydatadir/*'
Object handle rejected by file server. (CPFA0E6)
The message text alludes that I have a handle to an existing object
that
is no longer valid and I need to close and reopen it.
I attempt to resolve it by a signoff and sign back on to CLIENT and
try
again.
Nope. Same error.
UNMOUNT TYPE(*NFS) MNTOVRDIR('/testswitch/mydatadir')
MOUNT TYPE(*NFS) MFS('testswitch:/mydatadir')
MNTOVRDIR('/testswitch/mydatadir')
wrklnk '/testswitch/mydatadir/*'

Now it works. This presents a challenge. Not only do I need to do
stuff
on the server, and on the dns; but I also need to perform actions on
all
clients that access this server after the switch.
And, since the clients will include Domino servers running on both IBM
i
and Linux, solutions utilizing remote command execution will have to
be
tailored for each individual clients OS and local directory structure.
An alternative would be error trapping within Domino script to
unmount/mount. Concerns with that could include:
- Can the domino server script execute MOUNT commands or is that
limited
to personnel with special authority?
- Does UNMOUNT and MOUNT have the same parameters on Linux as on IBM
i?
For example if you try to run UNMOUNT TYPE(*NFS) on Linux I would
expect
undesirable results due to the command structure itself.

I'm open to suggestions.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.