Looks like you already know what to do but would like it to be
"nicer."
Well, TCP/IP is designed to seek new routes automatically, behind the
scenes when things go down. Now if you want to see what goes on
underneath, in a "nice" manner, you are entering the realm of
commercial, expensive, network tools.
I can't think of a PING-using-this-route utility but look, it may
exist. To me, since this is only used for troubleshooting, and doesn't
happend often, I personally wouldn't mind doing the temporary changes.
Rather than changing the the priority by the method u mentioned, I'd
use the ROUTE command, or simply physically unplugging the segment I
don't want.
As far as it telling u what failed, my employer has made us available
a usd$15,000 network monitoring workstation (HP Openview) that has a
map of the whole network with the different "pipes," If anything goes
down, that pipe turns to red. Pretty nifthy stuff.
|