help with Windows Routes and Metrics

i have a single device sitting on a network with a firewall (cisco asa) between it and a device that sends data to it.  For an example (not real IP's) here is info

Destination device = 10.10.10.100
source device network card 1 = 192.168.10.10, firewall gateway 192.168.10.1
source device network card 2 = 192.168.20.10, firewall gateway 192.168.20.1

there are basically two routes for the firewall that we want to prioritize to always go over card 1 unless it is down.  In the route tables on windows we issued these commands

route add -p 10.10.10.100 mask 255.255.255.255 192.168.10.1 metric 1
route add -p 10.10.10.100 mask 255.255.255.255 192.168.20.1 metric 2

after the persistent route tables show the correct entries as expect.

what we expected was for the route to take metric 1 on card1 if available and if card 1 fails to automatically pick communications using card 2 which has a metric of 2 (more expensive)

it doesn't work, we disconnected the cable off of card 1 and ping to device fails
if we make them both metric 1, it looks like it at least pings and gets through, but how do we prioritize using the metric then??

Any help would be appreciated, maybe i'm expecting too much from Windows networking.
Do you think just disconnecting the card is not enough for windows to take the next metric?

thanks
rknealAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
QlemoConnect With a Mentor Batchelor, Developer and EE Topic AdvisorCommented:
It should work that way. As soon as you disconnect the physical network connection for card 1, all according routes should get invalid, even if persistent. But no dice, proper routing is only done with non-persisting routes, because those are dismissed (of course) as soon as the associated network connection has gone. A workaround is to to use non-persistent routes, and set those on a regular base in case the connection comes back again.

Anyway, is it likely the connection to the ASA will fail? More probably the connections behind ASA are down, and that would not help you at all.
0
 
Darr247Commented:
Try
route add -p 0.0.0.0 mask 0.0.0.0 192.168.10.1 metric 1
route add -p 0.0.0.0 mask 0.0.0.0 192.168.20.1 metric 2

instead.
0
 
QlemoConnect With a Mentor Batchelor, Developer and EE Topic AdvisorCommented:
Default gateway failover doesn't work for the same reason, so I don't think that makes any difference.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.