[j-nsp] OSPF Forwarding Address

2012-08-02 Thread Benny Amorsen
I have a weird problem where I can get IOS to set the Forwarding Address for an external type 2 route (LSA type 5) in OSPF, but I cannot get Junos to do the same. The test network has 3 devices. Two of them are VRF's in an MX80 (router1 10.10.200.10 and router2 10.10.200.11), the last one is a

Re: [j-nsp] OSPF Forwarding Address

2012-08-02 Thread Stefan Fouant
In this case, router 1 is originating external the LSA through redistribution of the static, hence the other routers will see R1 as the next hop. Although i have never done this myself, I think you should be able to manipulate your OSPF export policy to include a 'then next-hop 10.10.200.1' to

Re: [j-nsp] OSPF Forwarding Address

2012-08-02 Thread Benny Amorsen
Stefan Fouant sfou...@shortestpathfirst.net writes: In this case, router 1 is originating external the LSA through redistribution of the static, hence the other routers will see R1 as the next hop. I take it that this is expected behaviour in Junos? Although i have never done this myself, I

Re: [j-nsp] OSPF Forwarding Address

2012-08-02 Thread Jeff Wheeler
On Thu, Aug 2, 2012 at 7:59 AM, Benny Amorsen benny+use...@amorsen.dk wrote: If I replace router1 with a VRF on a Cisco 7600, Forwarding Address is set to 10.10.200.1 and everything works as I expected. This is obviously not my preferred solution :) Do router2 and router1 have an OSPF

Re: [j-nsp] OSPF Forwarding Address

2012-08-02 Thread Benny Amorsen
Jeff Wheeler j...@inconcepts.biz writes: Do router2 and router1 have an OSPF adjacency on the /27? This is required for forwarding-address to be set. Yes, right now that is their only OSPF adjacency. Right now the VRF's only have that single interface. /Benny

Re: [j-nsp] OSPF Forwarding Address

2012-08-02 Thread Benny Amorsen
Stefan Fouant sfou...@shortestpathfirst.net writes: Although i have never done this myself, I think you should be able to manipulate your OSPF export policy to include a 'then next-hop 10.10.200.1' to manipulate the forwarding-address. Alas, no luck with 'then next-hop 10.10.200.1'. It seems