Re: [j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag)

2018-07-05 Thread Mark Tinka
On 5/Jul/18 10:15, James Bensley wrote: > > If you get any feedback you can publicly share I'm all ears! Will do. I'm currently working on getting those that have deployed it in the wild to do a preso at an upcoming conference. > As far as a greenfield deployment goes I'm fairly convinced

Re: [j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag)

2018-07-05 Thread James Bensley
On 4 July 2018 at 18:13, Mark Tinka wrote: > > > On 4/Jul/18 18:28, James Bensley wrote: > > Also > > Clarence Filsfils from Cisco lists some of their customers who are > happy to be publicly named as running SR: > > https://www.youtube.com/watch?v=NJxtvNssgA8=youtu.be=11m50s > > > We've been

Re: [j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag)

2018-07-05 Thread adamv0025
> Of James Bensley > Sent: Thursday, July 05, 2018 9:15 AM > > - 100% rFLA coverage: TI-LA covers the "black spots" we currently have. > Yeah that's an interesting use case you mentioned, that I haven't considered, that is no TE need but FRR need. But I guess if it was business critical to get

Re: [j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag)

2018-07-05 Thread adamv0025
> Of Gustav Ulander > Sent: Wednesday, July 04, 2018 10:46 PM > > Has anyone actually managed to verify a business case with SR? Im guessing > those mentioned bellow did? > How I see it, currently the only feasible business case to go with SR is if you outgrew your scaling limits with regards

Re: [j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag)

2018-07-05 Thread Aaron Gould
Thanks a lot James, that's very nice of you to explain all that to me and the community. I have Cisco and Juniper network. MX960 - (5 nodes) supercore ACX5048 - (~40 nodes) distribution ASR9k - (15 nodes) core ME3600 - (~50 nodes) distribution Aaron > On Jul 5, 2018, at 2:46 AM, James

Re: [j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag)

2018-07-05 Thread Aaron Gould
I really like the simplicity of my ldp-based l2vpn's... eline and elan You just made me realize how that would change if I turned off ldp. So, SR isn't able to signal those l2circuits, and manual vpls instances ? ... I would have to do all that with bgp ? I use bgp in some cases for rfc4762,

Re: [j-nsp] format of minimum and maximum value of math:random() in SLAX

2018-07-05 Thread Phil Shafer
Michael Loftis writes: >idk if there's a floor function but the general solution is floor(rand() * >16) when rand() produces values 0-1(exclusive) IE if random does not >generate 1.0 - dunno implementation details for slax Yes, XPath has a floor() function that can be used directly in SLAX.

[j-nsp] format of minimum and maximum value of math:random() in SLAX

2018-07-05 Thread Martin T
Hi! According to the documentation, math:random() function returns a random number with a minimum value of 0 and a maximum value of 1. Larger values than 0 and smaller values than 1 have a format similar to 0.663341003779015. What is the format of minimum and maximum value? Simply 0 and 1?

Re: [j-nsp] format of minimum and maximum value of math:random() in SLAX

2018-07-05 Thread Michael Loftis
idk if there’s a floor function but the general solution is floor(rand() * 16) when rand() produces values 0-1(exclusive) IE if random does not generate 1.0 - dunno implementation details for slax On Thu, Jul 5, 2018 at 13:43 Martin T wrote: > Hi! > > According to the documentation,

Re: [j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag)

2018-07-05 Thread Gustav Ulander
Hello James. Interesting feedback, thank you. //Gustav -Ursprungligt meddelande- Från: juniper-nsp För James Bensley Skickat: den 5 juli 2018 10:15 Till: juniper-nsp@puck.nether.net Ämne: Re: [j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag) On 4 July 2018 at 18:13, Mark