RE: switched ethernet interfaces

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

Yea what a pain.  If you run your applications bound to * or all interfaces,
you have no way of controlling what interface is used at time of
establishing an outbound connection.  If you create a virtual IP and add
routes for each of the Physical connection and bind your client application
to the Virtual IP you will always know the outbound IP and don't care about
the route, (interface), taken.  Unfortunately you cannot force IBM Client
Applications such as Telnet to use only the Virtual IP, UNLESS you define IP
Security Policies and lock down the physical IPs to restrict all access.

The easiest thing to do is to add all three IP address to the reverse lookup
tables on your DNS server.

Chris Bipes

-----Original Message-----
From: Jerome Draper

It appears that the model 830 at V5R1 has mysteriously switched ethernet 
interfaces that are used for outbound network connections.  I cannot seem to

find any failure in qhst or qsysopr msgq.

We have three ethernet adapters in this AS400 all running TCP/IP.  The
default 
gateway (172.16.1.1) is in the same subnet as two of them (172.16.1.10 and 
172.16.1.13).  The first one, 172.16.1.10, up until now, had been used for 
outbound network connections.  Now or all of the sudden the AS400 has
started 
using the other adapter 172.16.1.13.  Why?  How could this be?

The fully qualified domain name is (now?) tied to the 172.16.1.13 adapter.

How could this have changed and where would I find evidence of when and why 
this happened?  Nothing in qhst or qsysopr msgq.