Correct so you have to enable mpls ldp discovery targeted-hello accept in
your network so the router can setup the tunnels.
Here's what it looks like;
cr-no-osl-hmgv9-1#sh ip ospf fast-reroute remote-lfa tunnels
OSPF Router with ID (12.209.169.141) (Process ID 100)
Area with ID (0.0.0.0)
Base Topology (MTID 0)
Interface MPLS-Remote-Lfa25
Tunnel type: MPLS-LDP
Tailend router ID: 12.209.169.129
Termination IP address: 12.209.169.129
Outgoing interface: TenGigabitEthernet2/2
First hop gateway: 12.209.181.6
Tunnel metric: 8
Protects:
12.209.181.4 TenGigabitEthernet2/1, total metric 14
Interface MPLS-Remote-Lfa26
Tunnel type: MPLS-LDP
Tailend router ID: 12.209.169.239
Termination IP address: 12.209.169.239
Outgoing interface: TenGigabitEthernet2/1
First hop gateway: 12.209.181.4
Tunnel metric: 6
Protects:
12.209.181.6 TenGigabitEthernet2/2, total metric 14
Fredrik Vöcks
Senior IP Network Engineer
On 30 November 2012 10:17, Saku Ytti <[email protected]> wrote:
> On (2012-11-30 09:39 +0100), Adam Vitkovsky wrote:
>
> > I believe it has to work the same as with mpls-te frr
> > Where the merge point router has to tell you what label he'll use to swap
> > and forward towards the final PE
>
> My best guess is, that once it has chosen rLFA nodes, it makes targeted LDP
> session to them.
> But I'd love to hear from someone who has deployed/labbed this.
>
> --
> ++ytti
> _______________________________________________
> cisco-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
