The most annoying thing is that this is inet.0 table, not inet.3
Best regards,
Misak Khachatryan,
On Mon, Dec 11, 2023 at 7:30 PM Tom Beecher
mailto:beec...@beecher.cc>> wrote:
This is correct, they exist for the bypass LSPs.
I wouldn't characterize it as a dirty hack though. RFC4090 fast rerou
This is correct, they exist for the bypass LSPs.
I wouldn't characterize it as a dirty hack though. RFC4090 fast reroute
requires the backup pathways to be pre-computed for a sub-10ms switchover.
You put an export policy in place to make sure all labels (including
bypass) are in the FIB already. O
Hi Misak,
I think what you're seeing is normal for protection LSPs, "dirty hack on the
control plane side", but I'm looking forward to be humbled on this list that my
conclusion is incorrect.
We use "ldp interface link-protection dynamic-rsvp-lsp" and for all my bypass
LSPs, 'show route hidden
Hello,
Recently I implemented RSVP in my network, nothing so fancy - automesh and
autobandwidth with node-link protection.
By doing final review i saw output of show route summary:
inet.0: 296 destinations, 298 routes (275 active, 0 holddown, 21 hidden)
Direct: 6 routes,
4 matches
Mail list logo