[j-nsp] OSPF Confusion

[Eduardo Barrios]

Hi Christ,

This from Juniper about exporting into ospf and metrics:

http://www.juniper.net/techpubs/en_US/junos13.1/topics/concept/ospf-routing-external-metrics-overview.html


So if you exported your static routes into OSPF they will be a Type 2 external metric (you can check with "show ospf database external detail"), use only external cost and not take into account the link-state metric in your diagram. 

* You might have to write an export policy: from protocol static + any route-filter that you need, then accept and also add metric xx

Thanks,
Eduardo

Eduardo Barrios, EIT, JNCIP-SP
Telecommunications Specialist
Lower Colorado River Authority  | 3505 Montopolis Dr. |  Austin, TX 78744
512.730.6332 ph  



-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Crist Clark
Sent: Tuesday, February 25, 2014 5:12 PM
To: <juniper-nsp at puck.nether.net> Puck
Subject: [External] [j-nsp] OSPF Confusion

.

The problem is that R3 sees R2 as the best next hop for all of the statics
on R2. I don't understand why. The cost of the path from R3 to R2 is lowest
via R1, 11 vs. 20, right?

.