vss

[dkblee]

hi! I'm running vss in the core sw and i've 2 static route to a pair of dist sw.

ip route 0.0.0.0 0.0.0.0 192.168.150.38 track 81

ip route 0.0.0.0 0.0.0.0 192.168.150.39 11 track 82

Based on the 2 static routes above configured in the vss sw, the prefered path to reach the dist sw will be through the 192.168.150.38 right? (because for static route the distance is default 1). What's the track 81 and 82 mean? What would happen if i didn't specify the distance metric of 11 in the second ip route command? If both static routes are having the same metric what would be the prefered path to the dist sw?

Thanks.

[spremkumar]

Hi

I see the usage of ip tracking feature being used to track the route and enforce the traffic flow accordingly.

You can check out for the tracking config in the beginning of your show run (config) to understand what is being tracked and whats the resultant of configuring the tracking feature.

As per your understanding the first route will be used to route the traffic and second route will come into act as a result of object tracking feature.

If the ip or the interface being tracked goes off then your first route may go off and you will have your second route (with 11 admin distance) to forward the traffic.

if you dont have the admin distance there it will try to force the traffic through both the paths (but i haven't come across or tried this scenario yet and dont think its wise to do so in a production network).

regds