[j-nsp] Any sort of EVPN Success with: vMX 16.x and QFX5100
Alain Hebert
ahebert at pubnix.net
Mon Jul 31 08:02:46 EDT 2017
Place a sniffer between the vMX and the QFX, you'll see:
the ARP go from vMX to QFX and get an answer;
the ARP go from QFX to the vMX and you wont get an answer,
99.9999% of the time;
( It worked once for me and only for a while, but at this point
I pretty much feel like I'm getting trolled by J. That whole
QFX+L2TP+VCF really didn't help )
PS: We pretty much gave up on that whole <beep> none of the
whitepaper from J work in a lab setting since they forgot to list the
hardware and the Junos version they used.
-----
Alain Hebert ahebert at pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443
On 07/27/17 05:47, Anand Beedi wrote:
> Hello,
>
> I am facing similar problem with EVPN over MPLS. I am using 17.1R1.8 Junos build. The control plane, mac table looks fine. I see ARP resolved on one-end but other is not happening....
>
> Issues with both instance-type as EVPN or Virtual-switch with EVPN. No IRB configured.
>
> Any help????
>
> Output of Ping and tcpdump on both sides
>
> ******************************************************************************
> Ping f=> 21.1.1.1
> ******************************************************************************
>
> root at cuttack> ping 21.1.1.1 interface ge-2/0/4.2345
> PING 21.1.1.1 (21.1.1.1): 56 data bytes
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> root at cuttack:~ # tcpdump -i ge-2/0/4.2345 -s 1500
> Listening on ge-2/0/4.2345, capture size 1500 bytes
>
> 09:58:38.787719 Out arp who-has 21.1.1.1 tell 21.1.1.2
> 09:58:39.588860 Out arp who-has 21.1.1.1 tell 21.1.1.2
> 09:58:40.388273 Out arp who-has 21.1.1.1 tell 21.1.1.2
> 09:58:41.188860 Out arp who-has 21.1.1.1 tell 21.1.1.2
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> root at kochin% tcpdump -i ge-0/0/6.2345 -s 1500
> Listening on ge-0/0/6.2345, capture size 1500 bytes
>
> arp who-has 21.1.1.1 tell 21.1.1.2
> arp reply 21.1.1.1 is-at 80:71:1f:16:38:06
> arp who-has 21.1.1.1 tell 21.1.1.2
> arp reply 21.1.1.1 is-at 80:71:1f:16:38:06
> arp who-has 21.1.1.1 tell 21.1.1.2
> arp reply 21.1.1.1 is-at 80:71:1f:16:38:06
> arp who-has 21.1.1.1 tell 21.1.1.2
>
> ******************************************************************************
> Ping => 21.1.1.2
> ******************************************************************************
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> root at kochin> ping 21.1.1.2
> PING 21.1.1.2 (21.1.1.2): 56 data bytes
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> root at kochin% tcpdump -i ge-0/0/6.2345 -s 1500
>
> IP 21.1.1.1 > 21.1.1.2: ICMP echo request, id 26512, seq 4, length 64
> IP 21.1.1.1 > 21.1.1.2: ICMP echo request, id 26512, seq 5, length 64
> IP 21.1.1.1 > 21.1.1.2: ICMP echo request, id 26512, seq 6, length 64
> IP 21.1.1.1 > 21.1.1.2: ICMP echo request, id 26512, seq 7, length 64
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> root at cuttack:~ # tcpdump -i ge-2/0/4.2345 -s 1500
>
> Listening on ge-2/0/4.2345, capture size 1500 bytes
>
> ^C
> 0 packets received by filter
> 0 packets dropped by kernel
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> Cheers,
> Anand
>
> ________________________________
> Anand Beedi
> o +91 80 612 10427
> m +91 97396 77746
> abeedi at juniper.net
> www.juniper.net
>
>
> -----Original Message-----
> From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Alexander Marhold
> Sent: Friday, October 7, 2016 20:46
> To: ahebert at pubnix.net; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Any sort of EVPN Success with: vMX 16.x and QFX5100
>
> Hi
> As far as I know the paper deals with EVPN over VXLAN And As far as I know the vMX 16.1 does NOT support EVPN over VXLAN ( at least that I was told by some Juniper SEs and by the PLM manager for EVPN)
>
> Regards
>
> Alexander
> INDC
>
> -----Ursprüngliche Nachricht-----
> Von: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] Im Auftrag von Alain Hebert
> Gesendet: Freitag, 7. Oktober 2016 16:24
> An: juniper-nsp at puck.nether.net
> Betreff: [j-nsp] Any sort of EVPN Success with: vMX 16.x and QFX5100
>
> Hi,
>
> We've been working on a lab re-creating a Juniper whitepaper on the subject of EVPN, but we cannot figure out where we messed up =D
>
> Everything show up correctly in the core, spines/leafs, but L2 broadcast's are not propagated/managed as expected by the Core.
>
> aka: cannot ping between test devices on access ports for the Tenant since ARP broadcast are not answered.
>
> Anyone got any success? Or do we have the wrong white paper?
>
> Thank for your time.
>
> ------
>
> PS: I wish Juniper would adopt the standard to list the devices and their firmware to those whitepapers. Took 1/2 a day to figure out we needed 16.x for the vMX part of the equation. Oh and some peer review =D
>
> White paper in question:
>
>
> https://www.juniper.net/assets/us/en/local/pdf/whitepapers/2000606-en.pdf
>
> -----
> Alain Hebert ahebert at pubnix.net
> PubNIX Inc.
> 50 boul. St-Charles
> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
> Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
> _______________________________________________
> 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