Re: [mpls-linux-general] Loss of next hop information if rebooting next hop router

[James R. L. <jl...@mi...>]

This is behaving as designed.  When the interface goes down, MPLS needs to
release all of the info for that interface.  In the case of out segments
it just removed the nexthop info.

On Fri, Mar 19, 2004 at 04:54:40PM +1100, Jon...@cs... wrote:
> Dear all,
>=20
> Just wondering if this is a desirable feature or not...
>=20
> I use mplsadm2 to set up a LSP across three Linux mpls boxes (say, A, B
> and C). If I rebooted box B, the next hop information of box A
> "sometimes" disappeared!!!
>=20
> For example, the original information of /proc/net/mpls_out was like
> this:
>=20
> 0x0000000e 0/0/0 2 PUSH(gen 712111) SET(eth2,10.70.10.1)=20
> 0x0000000f 0/0/0 2 PUSH(gen 712112) SET(eth2,10.70.10.1)=20
> 0x00000010 0/0/0 2 SET(eth1,10.60.10.2)=20
>=20
> If I rebooted the next hop mpls router (10.70.10.1), the section
> "SET(eth2,10.70.10.1)" was automatically removed from the
> /proc/net/mpls_out. i.e. the file looked like this:
>=20
> 0x0000000e 1476/157256/0 2 PUSH(gen 712111)=20
> 0x0000000f 1549/168728/0 2 PUSH(gen 712112)=20
> 0x00000010 2977/311864/0 2 SET(eth1,10.60.10.2)=20
>=20
> Is it supposed to be like this??
>=20
> Thanks for your comments...
>=20
> Best Regards,
> Jonathan
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op?k
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu
jl...@mi...