|Q:||I'm having trouble controlling paths with routing costs. How to debug how path-costs are being compared?|
The Router's verbosity level 3 shows you the
costs as it compares paths.
router -v 3 netinfo
Certainly for a large network, this would be
tedious to follow. I suggest the following
trick: Give your path's cost a unique numeric
sequence, for example, instead of 10000, use
something like 123450.
You should see just the path comparisons
which contain your suspected link.
Note that the Router considers 1e9 (=1000000000.0) as the infinite, or not-connected distance. (All paths are initialized to that distance which is replaced as shorter paths are found.)
Also note that the paths involving your link get costs of 123450, 123451, 123452, etc., as unity-cost links are added to make paths, so don't search for 123450 as your cost, but truncate the lower digit(s). One digit gives you ten hops. Two digits would give a hundred, assuming your other links are unity. Obviously, all bets are off if you have other links with costs much higher than 1 which would destroy your match pattern more quickly.
Here are some other things to check:
(Questions, Comments, & Suggestions: firstname.lastname@example.org)