Re: [c-nsp] EVPN-VPWS PW and AC status coupling

2018-02-16 Thread Marco Marzetti
Adam,

You're right. I didn't explain it well.
PW is UP, but LDP propagates AC status to the other end.

Anyway it doesn't look to be supported by EVPNs, which is a pity.

Regards


On Fri, Feb 9, 2018 at 2:29 PM,   wrote:
>> Marco Marzetti
>> Sent: Friday, February 09, 2018 10:34 AM
>>
>> Hello,
>>
>> It's been a few weeks I've been working on EVPNs and IOS-XR 6.1 and i
>> wonder if ther's a way to couple AC and PW status so that you can
> propagate
>> PE-CE link failures end-to-end.
>>
>> I know it's supported for "regular" EVPNs (RFC7432), but EVPN-VPWS
>> (RFC8214) is definitely a special case.
>>
>> Here's my configuration snippets
>>
>> !
>> hostname XRV1
>> !
>> interface GigabitEthernet0/0/0/0.200 l2transport  encapsulation dot1q 200
> !
>> router bgp 64496
>>  bgp router-id 192.0.2.1
>>  address-family l2vpn evpn
>>  !
>>  neighbor 192.0.2.2
>>   remote-as 64496
>>   local address 192.0.2.1
>>   address-family l2vpn evpn
>>   !
>>  !
>> !
>> l2vpn
>>  xconnect group test
>>   p2p test
>>interface GigabitEthernet0/0/0/0.200
>>neighbor evpn evi 100 target 300 source 200
>>   !
>>  !
>> !
>>
>>
>> !
>> hostname XRV2
>> !
>> interface GigabitEthernet0/0/0/0.300 l2transport  encapsulation dot1q 300
> !
>> router bgp 64496
>>  bgp router-id 192.0.2.2
>>  address-family l2vpn evpn
>>  !
>>  neighbor 192.0.2.1
>>   remote-as 64496
>>   local address 192.0.2.2
>>   address-family l2vpn evpn
>>   !
>>  !
>> !
>> l2vpn
>>  xconnect group test
>>   p2p test
>>interface GigabitEthernet0/0/0/0.300
>>neighbor evpn evi 100 target 200 source 300
>>   !
>>  !
>> !
>>
>>
>> What i'd expect is XRV1 to turn Gi0/0/0/0.200 down when XRV2 withdraws
>> the BGP advertisements.
>>
>> Is that supported?
>>
> Hmm I'm getting a bit rusty on the Carrier-Ethernet stuff but isn't that the
> other way around?
> I mean what I remember is that if AC goes down that in turn brings down the
> PW -but the bit where the PW failure propagating to the other end then in
> turn brings the AC down on that end too  -that one I don't recall to be
> honest.  (Would I need to enable that with some knob first?)
> And what if the other end is configured with PW-redundancy -in that case I'd
> need the AC at remote end to stay up and just use the backup PW.
>
> Sure if you run LFM or the whole CFM suite end-to-end, then that could bring
> down ACs at both ends in case any component along the path fails.
>
>
> adam
>
> netconsultings.com
> ::carrier-class solutions for the telecommunications industry::
>



-- 
Marco
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] EVPN-VPWS PW and AC status coupling

2018-02-09 Thread adamv0025
> Marco Marzetti
> Sent: Friday, February 09, 2018 10:34 AM
> 
> Hello,
> 
> It's been a few weeks I've been working on EVPNs and IOS-XR 6.1 and i
> wonder if ther's a way to couple AC and PW status so that you can
propagate
> PE-CE link failures end-to-end.
> 
> I know it's supported for "regular" EVPNs (RFC7432), but EVPN-VPWS
> (RFC8214) is definitely a special case.
> 
> Here's my configuration snippets
> 
> !
> hostname XRV1
> !
> interface GigabitEthernet0/0/0/0.200 l2transport  encapsulation dot1q 200
!
> router bgp 64496
>  bgp router-id 192.0.2.1
>  address-family l2vpn evpn
>  !
>  neighbor 192.0.2.2
>   remote-as 64496
>   local address 192.0.2.1
>   address-family l2vpn evpn
>   !
>  !
> !
> l2vpn
>  xconnect group test
>   p2p test
>interface GigabitEthernet0/0/0/0.200
>neighbor evpn evi 100 target 300 source 200
>   !
>  !
> !
> 
> 
> !
> hostname XRV2
> !
> interface GigabitEthernet0/0/0/0.300 l2transport  encapsulation dot1q 300
!
> router bgp 64496
>  bgp router-id 192.0.2.2
>  address-family l2vpn evpn
>  !
>  neighbor 192.0.2.1
>   remote-as 64496
>   local address 192.0.2.2
>   address-family l2vpn evpn
>   !
>  !
> !
> l2vpn
>  xconnect group test
>   p2p test
>interface GigabitEthernet0/0/0/0.300
>neighbor evpn evi 100 target 200 source 300
>   !
>  !
> !
> 
> 
> What i'd expect is XRV1 to turn Gi0/0/0/0.200 down when XRV2 withdraws
> the BGP advertisements.
> 
> Is that supported?
> 
Hmm I'm getting a bit rusty on the Carrier-Ethernet stuff but isn't that the
other way around?
I mean what I remember is that if AC goes down that in turn brings down the
PW -but the bit where the PW failure propagating to the other end then in
turn brings the AC down on that end too  -that one I don't recall to be
honest.  (Would I need to enable that with some knob first?) 
And what if the other end is configured with PW-redundancy -in that case I'd
need the AC at remote end to stay up and just use the backup PW. 

Sure if you run LFM or the whole CFM suite end-to-end, then that could bring
down ACs at both ends in case any component along the path fails. 
 
 
adam

netconsultings.com
::carrier-class solutions for the telecommunications industry::

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


[c-nsp] EVPN-VPWS PW and AC status coupling

2018-02-09 Thread Marco Marzetti
Hello,

It's been a few weeks I've been working on EVPNs and IOS-XR 6.1 and i
wonder if ther's a way to couple AC and PW status so that you can
propagate PE-CE link failures end-to-end.

I know it's supported for "regular" EVPNs (RFC7432), but EVPN-VPWS
(RFC8214) is definitely a special case.

Here's my configuration snippets

!
hostname XRV1
!
interface GigabitEthernet0/0/0/0.200 l2transport
 encapsulation dot1q 200
!
router bgp 64496
 bgp router-id 192.0.2.1
 address-family l2vpn evpn
 !
 neighbor 192.0.2.2
  remote-as 64496
  local address 192.0.2.1
  address-family l2vpn evpn
  !
 !
!
l2vpn
 xconnect group test
  p2p test
   interface GigabitEthernet0/0/0/0.200
   neighbor evpn evi 100 target 300 source 200
  !
 !
!


!
hostname XRV2
!
interface GigabitEthernet0/0/0/0.300 l2transport
 encapsulation dot1q 300
!
router bgp 64496
 bgp router-id 192.0.2.2
 address-family l2vpn evpn
 !
 neighbor 192.0.2.1
  remote-as 64496
  local address 192.0.2.2
  address-family l2vpn evpn
  !
 !
!
l2vpn
 xconnect group test
  p2p test
   interface GigabitEthernet0/0/0/0.300
   neighbor evpn evi 100 target 200 source 300
  !
 !
!


What i'd expect is XRV1 to turn Gi0/0/0/0.200 down when XRV2 withdraws
the BGP advertisements.

Is that supported?

Thank you

Regards


-- 
Marco
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/