On 10/Jul/18 12:39, Saku Ytti wrote:
> I'd say this is true if you compare full-mesh iBGP and LDP, if you
> compare RR iBGP and LDP, it's not true, RR iBGP has signalling
> redundancy LDP does not have.
Agreed on that point.
Perhaps an option for the LDP heads is LDP Session Protection, which is
supported by the major vendors. I don't use it in my network, though.
Again, my main focus is maintaining a super stable IGP, one that can
converge quickly enough for the upper-layer protocols (and data plane)
not to notice. Features in upper-layer protocols that speed up
convergence are also exploited in my network to ensure data plane
changes happen as quickly (but as simply) as possible, e.g., the
Indirect Next Hop feature.
As an example, below is a revenue-generating p2p LDP-based EoMPLS
circuit that has been up 46.5 weeks:
tinka@device-re0# run show l2circuit connections neighbor aaa.bb.c.129
extensive
<snip>
...
Neighbor: aaa.bb.c.129
Interface Type St Time last up # Up trans
ae2.62(vc 22) rmt Up Aug 18 23:59:44 2017 1
<snip>
...
Connection History:
*Aug 18 23:59:44 2017 status update timer**
** Aug 18 23:59:43 2017 PE route changed**
** Aug 18 23:59:43 2017 Out lbl Update 299776**
** Aug 18 23:59:43 2017 In lbl Update 299824**
** Aug 18 23:59:43 2017 loc intf up ae2.62*
{master}[edit]
tinka@device-re0#
tinka@device-re0# run show ldp session aaa.bb.c.129 extensive
Address: aaa.bb.c.129, State: Operational, Connection: Open, Hold time: 27
<snip>
...
*Up for 46w3d 11:12:55*
*Last down 46w3d 11:12:59 ago*; Reason: received notification from peer
Capabilities advertised: p2mp, make-before-break
Capabilities received: p2mp, make-before-break
Protection: disabled
Session flags: none
<snip>
...
{master}[edit]
tinka@device-re0#
Have the backbone links carrying this pw been 46.5 weeks stable? That's
a firm NO!
Mark.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
