RE: switched ethernet interfaces

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>]

Jerry,

If you accept the defaults when you set up your routes, you don't have
much control over which of two interfaces would be used.  The operating
system will do whatever it feels is appropriate.  There are two
parameters on the ADDTCPIFC (Add TCP Interface) command which may be of
value.  The first is BINDIFC (Binding Interface) which directs a route to
bind itself to a particular IP interface.  The second is DUPRTEPTY
(Duplicate Route Priority) which defines which route is to have priority
for outbound connections if more than one route would satisfy a request.
If you create two routes, one for each interface, you should be able to
control your outbound connections.  The two routes would be identical
except for the interface (172.16.1.13 or 172.16.1.10) and the route
priority.  The route priority can be a number between 1 and 10.  Avoid
the default of 5 and give the preferred route a lower (I think) number.
All outbound traffic should then use the preferred route unless you have
a failure on the interface.

I don't think that your DNS is going to have much of an impact on
outbound route selection.

Regards,
Andy Nolen-Parkhouse

> Jerome Draper
> Subject: switched ethernet interfaces
> 
> 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.
> 
> Perplexed.
> 
> 
> Jerry