Hi, Antti, We have considered multiple options, including the graceful automated RSVP-TE LSP restart, etc. But, in the end, reboot wins.
I would also recommend thinking about allocating the Segment IDentifiers and corresponding SR-MPLS labels in advance to ensure cross-vendor transparency (as they have different default SRGB ranges). It is also important to consider different MPLS implementation specifics, e.g. how MPLS label manager actually allocates the labels. -- Vladimir Blazhkun (via iPhone). > On 11 Aug 2020, at 12:27, Antti Ristimäki <antti.ristim...@csc.fi> wrote: > > Hi list, > > For those that have already deployed SR-MPLS, I would be curious to know > which methodology you have followed when defining the SRGB label range? Have > you just consciously taken an overlapping label range and then during a > maintenance window restarted RPD so that other protocols using the > overlapping dynamic label range would re-program, or have you managed to find > a big enough contiguous unused label range in your network to be used as SRGB? > > In our very modestly sized network, the currently running protocols (LDP, > RSVP, BGP-LU, MP-BGP) seem to occupy the dynamic label pool 16-999999 very > sparsely, leaving not-so-many contiguous free ranges. I'm not having > particularly hard time in finding an unused label range in our network, but > I'd just be curious to hear how others have managed this. > > Antti > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
