RE: Native Domino - to LPAR or not to LPAR, that is the question.

Rob,

Doesn't putting the Preferred Interface in the TCP Interface when you create it solve that problem? (You can't go back and change it to add Preferred Interface, you have to delete and recreate the interface).

...Neil

Neil Palmer, Cambridge, Ontario, Canada

(This account not monitored for personal mail,
remove the last two letters before @ for that)


--- On Wed, 6/4/08, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:

From: rob@xxxxxxxxx <rob@xxxxxxxxx>
Subject: RE: Native Domino - to LPAR or not to LPAR, that is the question.
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Received: Wednesday, June 4, 2008, 12:10 PM
One other issue with Domino on the same lpar...
If your network people are nuts about locking stuff down
and you've
created a separate tcp interface for each domino server and
one for i;
your client sessions emanating from the i may bind to one
of the domino ip
addresses, and drive the network people bonkers. For
example
10.10.1.5 may be an address for domino server A
10.10.1.6 may be the address for normal i stuff
Now, on the i I initiate a FTP client session to a barcode
printer
somewhere. Network people lock it down so that only
10.10.1.6 may talk to
the barcode printer. However, my ftp session comes from
10.10.1.5
because when I type in FTP I can't tell it which
interface to use so it
grabs the first one. Hint: No guarantees, but make your i
interface the
lowest one.
Been a recent discussion on this on the Domino list I need
to look at...

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Pete Massiello"
<pmassiello-ml@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/03/2008 11:46 PM
Please respond to
Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Native Domino - to LPAR or not to LPAR, that is the
question.






Neil,

We have it both ways in various accounts.
We used to
separate for
performance, but with today's large CPW numbers, we
haven't really had the
need. Don't forget, you can also run these partitions
uncapped, thereby
having the CPW move to each partition when required.
Unfortunately, not
yet
with memory. Domino likes memory.

I think the big reason for putting domino
in a separate
partition
is that you can leave the email side open to the internet,
but keep your
application partitions off the internet.

Pete
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Neil
Palmer
Sent: Tuesday, June 03, 2008 4:49 PM
To: Midrange Systems Technical Discussion
Subject: Native Domino - to LPAR or not to LPAR, that is
the question.

What is the general consensus on whether or not you need
(or should) run
Domino (for email & Sametime) in a separate LPAR? I
can't really think of
a
lot of advantages, just disadvantages like:

- more maintainance on the LPAR for release upgrades,
PTF's, etc.

- a more expensive system because of the LPAR driving
requirements for
additional disk controllers and disk, driving a requirement
for an
otherwise
unneeded expansion unit, etc.

- more PC server like in that you end up with unused
processor and disk
resources that would be better utilized if Domino was
running in teh main
system/partition.

I can't think of any cases where errors in Domino would
cause a production
system/partition to crash - but has anyone experienced that
?


Neil Palmer, Cambridge, Ontario, Canada

__________________________________________________________________
Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com