We have found when using multiple interfaces, and when the iSeries initiates the connection, we need to have a static route, or else results our unpredictable.
CFGTCP
Option 2. Work with TCP/IP routes
ADDTCPRTE RTEDEST('10.5.xxx.x') SUBNETMASK(*HOST) NEXTHOP('10.5.yy.yyy') BINDIFC('10.5.yy.yyy') TEXT('PSIJDEDEV01')
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Monday, May 09, 2016 3:30 PM
To: Midrange Systems Technical Discussion
Subject: Re: Multiple TCPIP Interfaces... how does the system choose which one to use?
And both routing and bind specific 'properties' files are probably both items which cannot be replicated in a High Availability environment. So the simpler the better. That's why I would prefer a system environment variable or some such thing to hold default 'bind specific' information.
Time to submit request...
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: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/09/2016 03:15 PM
Subject: Re: Multiple TCPIP Interfaces... how does the system
choose which one to use?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Routes are the magic. You can create routes for a specific target to use
a specific local interface and further set the priority so that if one
isn't available another can be used. You can really make it complicated,
and hard to understand too!
However, you are setting up a scenario though that I refer to as
*LANDMINE. If you end up with many static routes and anything changes
you're stuck with many static changes. Clearly some static routes may be
needed in various situations but fewer is always better. None is the
best number if you can make that work.
Note that the routes are used only for connections initiated from IBM i.
Also note that IBM i will NOT respond to an inbound packet if there is
no configured route available in IBM i. This is different (and better)
behavior from most other O/Ss found in the average shop.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 5/9/2016 2:50 PM, Rob Berendt wrote:
There is some potential for that, but routing is not a cure all.
Suppose I want to ftp from LparA to LparB and I want it to use interface
34 when it goes out from LparA.
Now I want to use one of my Domino servers (let's say 37) and I want to
open a DB2 connection to LparB. That should come from 37.
Rob Berendt
midrange.com
