Re: Routing

[Philipp Rusch <philipp.rusch@xxxxxxxxxxxx>]

Hi Chris,

sounds like a DNS problem, or, more generally speaking, like a name 
resolution
problem. How do the machines "find" each other by name ? through DNS, 
hosts files
or by ip-address ?  If, for instance, the name of "AS400-1" is still 
resolving
to the inactive/defunct interface, then you will watch  excatly the 
behaviour
you described below. Having routes setup properly is the one side of the 
medal.
setting up DNS to support multi-homed hosts is the other. Both work hand 
in hand,
if setup properly, DNS "round robin" algorhythm will "switch over" to the
active interface after a short time.

HTH, Philipp

Chris Bipes schrieb:

> I have two routes to a remote location.  One is faster than the other.  We
> set up the routing table as such:  As400 1 = 10.10.1.1, As400 2 = 10.10.2.1
> Destination     Subnet          Hop             Available       Metric  Dup
> Rte Pty
> 10.10.1.0       255.255.255.0   10.10.1.200     *YES    2               5
> 10.10.1.0       255.255.255.0   10.10.1.201     *YES    3               5
>
> The other end:
> Destination     Subnet          Hop             Available       Metric  Dup
> Rte Pty
> 10.10.2.0       255.255.255.0   10.10.2.200     *YES    2               5
> 10.10.2.0       255.255.255.0   10.10.2.201     *YES    3               5
>
> The WAN ports on 10.10.1.200 is connected to 10.10.2.200
> The WAN ports on 10.10.1.201 is connected to 10.10.2.201
>
> Now why would a trace show as400 1 using 200 and a trace from as400 2 using
> 201?  Also when one route dropped today, AS400 2 did not switch routes.
> The failure was at AS400 1 side of the network.
>
> Will running RouteD help to resolve these routing issues?
>
> Christopher K. Bipes 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>