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

[Alexandre Guimaraes]

Saku,

	You are correct, they have.  To many things to tshoot.  I aways try to keep my configuration simple and clean. Things have to be more fast, reliable, available, 200% uptime, with no downtime with a good price.

This is a part of a QFX5110 protocol configuration, it represents a part of a 100Gbps P ring of QFX5110 in a specific area collecting all traffic that’s will jump to another city. The rest of configuration are system login access and filters 

set protocols rsvp interface et-0/0/30.0 bandwidth 100g
set protocols rsvp interface et-0/0/31.0 bandwidth 100g
set protocols rsvp interface ae16.0 bandwidth 40g
set protocols mpls log-updown syslog
set protocols mpls optimize-aggressive
set protocols mpls optimize-timer 21600
set protocols mpls interface et-0/0/31.0
set protocols mpls interface et-0/0/30.0
set protocols mpls interface ae16.0
set protocols isis interface et-0/0/30.0 level 1 metric 10
set protocols isis interface et-0/0/30.0 level 2 metric 10
set protocols isis interface et-0/0/31.0 level 1 metric 10
set protocols isis interface et-0/0/31.0 level 2 metric 10
set protocols isis interface ae16.0 level 1 metric 30
set protocols isis interface ae16.0 level 2 disable
set protocols isis interface lo0.0 passive
set protocols ldp interface lo0.0

> show mpls lsp | match transit 
Transit LSP: 181 sessions, 19 detours

I am not here to make my words the rule, I am just sharing my -Real World Deployment and Operation- knowledge and experience.


Att
Alexandre


-----Mensagem original-----
De: Saku Ytti <saku at ytti.fi> 
Enviada em: sábado, 7 de julho de 2018 18:24
Para: Alexandre Guimaraes <alexandre.guimaraes at ascenty.com>
Cc: Mark Tinka <mark.tinka at seacom.mu>; Juniper List <juniper-nsp at puck.nether.net>
Assunto: Re: [j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag)

Hey Alexandre,


> When we use l2circuits, you remove some layer of routing protocol troubleshooting. In just few command you know what’s going on.
> In a flap, BGP session will be dropped after timers reached.
>
> RSVP/ISIS/LDP will be affect immediately.  Also ISIS is the fundamental key of everything over here....
> With BGP, you have to check everything twice, including filters everywhere if someone change this or change that.

All these protocols have hello timers, LDP, ISIS, RSVP, BGP. And each of them you'd like to configure to trigger from events without delay when possible, instead of relying on timers. Indeed you can have BGP next-hop invalidated the moment IGP informs it, allowing rapid convergence.

--
  ++ytti