Re: [j-nsp] SRGB Allocation

On 11/Aug/20 15:57, Andrew Alston wrote: > > HI Mark, > >   > > Long time no talk. > >   > > So – there are fundamentally different things to consider in SR-MPLS – > for one thing – and this is kinda lacking in the market – because Node > SID’s are typically static – you need a system to track

Re: [j-nsp] SRGB Allocation

I vote for static Adj-SID allocations for the SR-MPLS. It makes operations much more convenient as one might arrange a map of interface name (index) to an Adj-SID. -- Vladimir Blazhkun (via iPhone). > On 11 Aug 2020, at 16:58, Andrew Alston > wrote: > > Adjacency SID’s are less of a

Re: [j-nsp] SRGB Allocation

burning through blocks of 256 labels at a time and its getting deaggregated – this can get used pretty fast in a large network. Thanks Andrew From: juniper-nsp On Behalf Of Mark Tinka Sent: Tuesday, 11 August 2020 16:51 To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] SRGB Allocation

Re: [j-nsp] SRGB Allocation

On 11/Aug/20 15:42, Andrew Alston wrote: > Sorry for starting a new thread - I wasn't actually subscribed and your email > querying about SRGB allocation was brought to my attention by one of your > friendly Juniper Ambassadors, so hopped on to give you my thoughts. Welcome to the list,

[j-nsp] SRGB Allocation

(Apologies if this appears twice, seems my subscription wasn't right the first time!) Hi Antti, Sorry for starting a new thread - I wasn't actually subscribed and your email querying about SRGB allocation was brought to my attention by one of your friendly Juniper Ambassadors, so hopped on to

Re: [j-nsp] SRGB allocation

On 11/Aug/20 13:54, Vladimir Blazhkun wrote: > 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

Re: [j-nsp] SRGB allocation

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

[j-nsp] SRGB allocation

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