RE: Virtual IP for Failover Questions

Ok,

That makes sense then.  You're using indirect routing to the iSeries and it
in effect has no local clients.

Actually, I suppose the iSeries does have local clients.  At least in the
sense that when the iSeries is sending out a packet, it goes directly to the
client.  But when the client is sending to the iSeries it goes to the router
first.

In any event, that configuration isn't going to work for me I'm afraid.

Thanks anyways,
Charles


> -----Original Message-----
> From: Chris Bipes [mailto:chris.bipes@xxxxxxxxxxxxxxx]
> Sent: Monday, January 26, 2004 4:24 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Virtual IP for Failover Questions
> 
> 
> The 10.99.99.x subnet does not exist.  I used host routes 
> thru the physical
> interfaces to get to the virtual IP address.  Both subnets 
> know how to get
> to each other.  Both subnets have a local primary router and 
> secondary route
> thru the router to the other subnet.  If the local interface 
> / route is
> down, the dft router sends the packets to the other subnet.  The other
> subnet send the packet to the local interface on that subnet. 
>  99.999% of
> the time the packets stay on the local subnet.  Now if both 
> interfaces are
> down.  The dft routers can start a loop of sending the 
> packets back and
> forth with out some routing protocol reporting that the local 
> route is down,
> don't send it to me.  In which case you should get a message 
> from the local
> default route that no route is available.
> 
> Chris Bipes
> 
> -----Original Message-----
> From: CWilt@xxxxxxxxxxxx
> 
> Chris,
> 
> Thanks for the info.  But I'm wondering how this works; how 
> are the clients
> on both subnets configured? Are there any clients on the 
> 10.99.99.x subnet
> with the iSeries?
> _______________________________________________
> 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.
>