help with Windows Routes and Metrics
Posted on 2013-10-26
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?