[c-nsp] Fast Reroute Behavior when link is recovered

[Peter Salanki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Will it recover when you reoptimize? The MPLS-TE implementation in  
7600 SUCKS imo. Causes my boxes to crash and puts wrong labels on  
traffic causing really big f**ups.

2 nov 2006 kl. 18.24 skrev <Alaerte.Vidali at nokia.com>  
<Alaerte.Vidali at nokia.com>:

> Greetings,
> I have tested Fast Reroute on 7600 with IOS 12.2(18) SXF5 and after
> recovering the link from a failure, the original tunnel path is
> recovered. For example:
> OSRa-----------------OSR1---- -------------OSR2---------OSRb
> | |
> | |
> --------------------OSR3
> Tunnel is between OSRa and OSRb. One explicit path is used, no dynamic
> tunnel at all.
> FRR is configured to protect link between OSR1--OSR2 using link
> OSR1-OSR3.
> When link OSR1--OSR2 fails, FRR recover from the failure using
> OSR1--OSR3--OSR2.
> When link OSR1--OSR2 is recovered, FRR is deactivated and original
> tunnel again follow original path: OSRa--OSR1--OSR2--OSRb.
> That was the result during tests, simulating failures.
> But there are user reports saying that when link OSR1--OSR2 is
> recovered, FRR keeps active and original path is not recovered.
> Have you seen this situation?
> Thanks,
> Alaerte
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

Med vänliga hälsningar

Peter Salanki
Nätansvarig
Bahnhof AB (AS8473)
www.bahnhof.se
Kontor: +46855577132
Mobil: +46709174932



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)

iD8DBQFFSnCBiQKhdiFGiogRAvj1AJ9CLFh8esMMlR7EKlGNphPqb/MhrgCeKJdE
IpL+pJ+/6nkd55UbJE35Qv8=
=zswQ
-----END PGP SIGNATURE-----