[c-nsp] default route behavoir

[Matlock, Kenneth L]

Currently both routes are equal cost, so the first packet (or flow,
can't remember which off the top of my head) takes the first route, and
the next packet (or flow) takes the 2nd route, and the 3rd packet (or
flow) takes the 1st route, etc.

In order to do it, you can change the metric on the non-preferred route
so it's only used if the other route is unavailable.

ip route 0.0.0.0 0.0.0.0 10.50.6.2
ip route 0.0.0.0 0.0.0.0 10.50.5.24 2

now, keep in mind that the switch will only determine that 10.50.6.2 is
down if the interface that 10.50.6.2 is connected changes state to down.
If the state doesn't change, that route's still valid even if 10.50.6.2
is no longer responding.

In order to solve that, you need to run a dynamic protocol between this
3560 and the upstream routers/switches. (I don't know off the top of my
head if/what the 3560 supports).


Ken Matlock
Network Analyst
(303) 467-4671
matlockk at exempla.org

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Dan Letkeman
Sent: Tuesday, December 11, 2007 4:01 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] default route behavoir

Hello,

I'm unsure how the default route behavior is supposed to be on a 3560
switch.  I have a remote office that is connected with two wireless
links to
a main building.  Right now I have this in my configuration for
redundancy,
but it is using both links and just randomly taking either one.

ip route 0.0.0.0 0.0.0.0 10.50.6.2
ip route 0.0.0.0 0.0.0.0 10.50.5.24

Is there a way to tell the switch to only use 10.50.6.2 and not use
10.50.5.24 unless 10.50.6.2 is down?

Thanks,
Dan.
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/