[j-nsp] OSPF Metric in Juniper.

[Lars Erik Gullerud]

On Wed, 2004-01-21 at 11:04, Milind Deshpande wrote:

[snip]
> When we issue ping from Router A to Router D, ideally as per OSPF metric
> which is cost, it should follow the "Router B & Router D" path, but it is
> following "Router C & Router D"
> What could be the reason of taking path which are having both STM1 links,
> instead of Gigabit & STM1 path?

Unless you have increased the OSPF reference bandwidth in your network
or manually assigned metrics to interfaces, anything >= 100Mbit has a
metric of 1 (100Mbit is the default reference-bandwidth for OSPF cost
calculation). Which means A-C-D and A-B-D are equal-cost paths (same
number of hops, all hops are metric 1). Then  router A will load-balance
between the two, a "show route <ip of D>" should show you both paths.

/leg