[j-nsp] evpn with vrf
Jason Lixfeld
jason-jnsp at lixfeld.ca
Mon Jun 10 18:15:25 EDT 2019
So JunOS supports draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-02 then?
> On Jun 10, 2019, at 4:21 PM, Aaron Gould <aaron1 at gvtc.com> wrote:
>
> Seems that I get an auto-export from evpn-learned destinations auto exported
> as /32's into the vrf that the IRB is attached to.
>
> Is this possibly with inet.0 global route table?
>
> In other words, in a vrf table I see evpn-learned routes listed like this...
>
> 172.223.10.10/32 *[EVPN/7] 00:00:03
>> via irb.0
>
> ... how would I get this same behavior if the irb.0 interface was in inet.0
> routing domain and not vrf ?
>
> -Aaron
>
>
>
>
>
> Details.....
>
>
> root at stlr-960-e> show evpn database
> Instance: 10
> VLAN DomainId MAC address Active source Timestamp
> IP address
> 10 00:00:00:00:00:01 irb.0 Jun 10
> 15:13:59 172.223.10.1
>
> 172.223.10.5
> 10 00:50:79:66:68:21 ae141.0 Jun 10
> 15:12:06
> 10 00:50:79:66:68:23 ae141.0 Jun 10
> 15:10:53
> 10 02:05:86:71:f1:02 10.103.128.9 Jun 10
> 14:10:25
>
> root at stlr-960-e> show route table one.inet.0
>
> one.inet.0: 3 destinations, 4 routes (3 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 172.223.10.0/24 *[Direct/0] 00:00:38
>> via irb.0
> [Direct/0] 00:00:38
>> via irb.0
> 172.223.10.1/32 *[Local/0] 00:00:38
> Local via irb.0
> 172.223.10.5/32 *[Local/0] 00:00:38
> Local via irb.0
>
> root at stlr-960-e> ping 172.223.10.10 routing-instance one
> PING 172.223.10.10 (172.223.10.10): 56 data bytes
> 64 bytes from 172.223.10.10: icmp_seq=0 ttl=64 time=391.814 ms
> 64 bytes from 172.223.10.10: icmp_seq=1 ttl=64 time=118.886 ms
> ^C
> --- 172.223.10.10 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 118.886/255.350/391.814/136.464 ms
>
> root at stlr-960-e> show route table one.inet.0
>
> one.inet.0: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 172.223.10.0/24 *[Direct/0] 00:00:58
>> via irb.0
> [Direct/0] 00:00:58
>> via irb.0
> 172.223.10.1/32 *[Local/0] 00:00:58
> Local via irb.0
> 172.223.10.5/32 *[Local/0] 00:00:58
> Local via irb.0
> 172.223.10.10/32 *[EVPN/7] 00:00:03
>> via irb.0
>
> root at stlr-960-e>
>
> root at stlr-960-e> ping 172.223.10.20 routing-instance one
> PING 172.223.10.20 (172.223.10.20): 56 data bytes
> 64 bytes from 172.223.10.20: icmp_seq=0 ttl=64 time=437.254 ms
> 64 bytes from 172.223.10.20: icmp_seq=1 ttl=64 time=161.525 ms
> ^C
> --- 172.223.10.20 ping statistics ---
> 3 packets transmitted, 2 packets received, 33% packet loss
> round-trip min/avg/max/stddev = 161.525/299.389/437.254/137.865 ms
>
> root at stlr-960-e> show route table one.inet.0
>
> one.inet.0: 5 destinations, 6 routes (5 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 172.223.10.0/24 *[Direct/0] 00:01:11
>> via irb.0
> [Direct/0] 00:01:11
>> via irb.0
> 172.223.10.1/32 *[Local/0] 00:01:11
> Local via irb.0
> 172.223.10.5/32 *[Local/0] 00:01:11
> Local via irb.0
> 172.223.10.10/32 *[EVPN/7] 00:00:16
>> via irb.0
> 172.223.10.20/32 *[EVPN/7] 00:00:03
>> via irb.0
>
> root at stlr-960-e>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list