Re: multihosting

Rob,

It sounds like you need to start/restart the Interface. Usually Domino
won't even start properly if the interface is not in an "Active" status.
Thus, I believe Domino is a victim here and the interface is the real
issue. If just starting the interface doesn't work then I'd suggest
bouncing TCP, but not knowing what else is on the LPAR that could be ugly.


The other thought that pops into mind is a duplicate IP on the network.
Maybe something conflicted when the interface originally tried to start
and that's how you got into this state?

Good luck!



Amy Hoerle
System Administrator
Think Mutual Bank
5200 Members Pkwy NW, Box 5949
Rochester, MN 55901

507-536-5815 or
800-288-3425 Ext 5815
ahoerle@xxxxxxxxxxxxx



From: rob@xxxxxxxxx
To: domino400@xxxxxxxxxxxx
Date: 01/21/2015 02:38 PM
Subject: multihosting
Sent by: "Domino400" <domino400-bounces@xxxxxxxxxxxx>



We have multiple websites. Let's say SiteA.com SiteB.com and SiteC.com.

On the outside they all have different IP addresses. These route to an
IBM Edge server which then redirects them to one of two Domino servers.
For example, let's say SiteA.com goes to xxx.yyy.101.5 on Edge. Edge then

load balances it between xxx.yyy.151.5 on one Domino server and
xxx.yyy.152.5 on another Domino server
SiteB goes to xxx.yyy.101.6 which is then load balanced between
xxx.yyy.151.6 on the same server running .151.5 and xxx.yyy.152.6 on the
same server running .152.5
and so on.

Stuff on the .151. server is running fine. I seem to be having issues
with the .152. server.
NETSTAT *IFC on the .151. server shows all the .151. addresses as
"Active".
NETSTAT *IFC on the .152. server is showing this one IP address for
SiteA.com as "Inactive". Not "Stopped", but "Inactive". Which I take it
to mean that there are no jobs listening for any ports on that interface.
Nope, not true.
NETSTAT *CNN and using F15 to subset by xxx.yyy.152.5 is showing
Remote Remote Local
Address Port Port Idle Time State
* * www-http 001:11:41 Listen
* * https 001:11:41 Listen

Option 8 then shows this job:
Current
Name User Number Type User
HTTP QNOTES 068343 *BCH QNOTES

What I do notice about all the IP addresses that are "Active" is they all
have this job, QSLPSVR, on ports 427 and 4800. There is no QSLPSVR job
bound to any port on the .152.5 interface. What I've read about QSLPSVR
doesn't seem to show any relevance.

I can work around using the Edge server. Meaning I can go to
xxx.yyy.151.5 directly and that works. I cannot pull up xxx.yyy.152.5 on
a browser though.
The lpar of IBM i running .152.5 can ping .151.5 and .152.5.
The lpar of IBM i running .151.5 can ping .151.5 but not .152.5.

I have bounced the Domino server serving up the .152.5 interface.
I've not tried any stopping/starting of TCP or IBM i as a whole.


Rob Berendt