Hot answers tagged

3

TLDR: Updated JunOS to the latest recommended version for QFX 5110 as per this JTAC document: https://kb.juniper.net/InfoCenter/index?page=content&id=KB21476&actp=METADATA#qfx_series Junos 18.4R2-S5 and subsequent service releases / 20.2R2 This is how I fixed the initial empty MAC table bug: After rebooting both switches, I started seeing type 2 ...


3

It looks like you're configuring EVPN Pure Type-5 routes (i.e. https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-prefix-advertisement-11#section-4.4.1) with VXLAN transport, this is not supported on MX80/104 until 18.2R1 (see the related feature explorer entry). MPLS transport, however, is supported as of 17.1R1.


3

It depends on how you want to use the link. You can configure your MLAG normally, then have a dedicated VLAN run atop this MLAG and configure routing on this VLAN. This will work for static routing using the virtual IP as a next hop. If you perform dynamic routing, like BGP, then it's still possible, but then you have to establish a session with each ...


2

First of all, you got 6 switches but you named them in pairs. If these switches are not stacked, just use leaf-1 to leaf -4 and boarder leaf-1 boarder-leaf 2.Better notation. I am assuming that you are thinking of using eVPN in your topology. you can use all topology as you suggested as a layer 2 network, do not use any VLAN IP address, and set your ...


2

First of all, when I configure non double-wide arp-ether region the following warning pops up which is quite self-explanatory with the conclusion being -- we have to use double-wide for VxLAN. WARNING: Configuring the arp-ether region without "double-wide" is deprecated and can result in silent non-vxlan packet drops. Use the "double-wide&...


1

VPC is a mechanism to achieve L2 multihoming. Connecting to an ISP with eBGP is very much an L3 exercise - and, as such, you're likely better off just establishing a second peering to another leaf. This is both a more scalable and simpler mechanism to establish connectivity. Leave VPC (or really any mLAG) for dual-attaching end-hosts and connecting to ...


1

ASNs Regarding the ASNs, you have a lot of options. The least-complex choice is to treat ASN 65000 as a downstream private ASN customer of ASN 98765, accept Internet-bound routes from it, announce default (or DFZ, if you must) routes to it, and remove-private the ASN 65000 from AS_PATHs when you export them to your transit. At the other end of the ...


Only top voted, non community-wiki answers of a minimum length are eligible