I configured evpn/vlxan virtual gateways on QFX10008, it works fine.
I am doing some training lab where vMX is used. I could not get it working.
set interfaces irb unit 100 virtual-gateway-accept-data (training material)
set interfaces irb unit 100 family inet address 10.200.100.250/24 virtual-gateway-address 10.200.100.254
set interfaces irb unit 101 proxy-macip-advertisement (JNCIE Tech site)
set interfaces irb unit 101 family inet address 10.200.101.250/24 virtual-gateway-address 10.200.101.254
which is a right approach? what differences ?
On the client, I can see the arp.
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.200.101.3 - aabb.cc00.b000 ARPA Ethernet0/0.101
Internet 10.200.101.250 5 2c6b.f57b.b3f0 ARPA Ethernet0/0.101
Internet 10.200.101.254 125 0000.5e00.0101 ARPA Ethernet0/0.101
On vMX, I can see MAC for server-3
root@vMX7# run show bridge mac-table
MAC flags (S -static MAC, D -dynamic MAC, L -locally learned, C -Control MAC
O -OVSDB MAC, SE -Statistics enabled, NM -Non configured MAC, R -Remote PE MAC)
Routing instance : overlay
Bridging domain : BD-101, VLAN : 101
MAC MAC Logical Active
address flags interface source
aa:bb:cc:00:b0:00 DL ae0.0
But ping does not work.
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.200.101.254, timeout is 2 seconds:
Success rate is 0 percent (0/5)
root@vMX7# show routing-instances | display set
set routing-instances overlay vtep-source-interface lo0.0
set routing-instances overlay instance-type virtual-switch
set routing-instances overlay interface ae0.0
set routing-instances overlay interface ae1.0
set routing-instances overlay route-distinguisher 10.200.0.7:7
set routing-instances overlay vrf-target target:64513:1
set routing-instances overlay vrf-target auto
set routing-instances overlay protocols evpn encapsulation vxlan
set routing-instances overlay protocols evpn extended-vni-list all
set routing-instances overlay protocols evpn multicast-mode ingress-replication
set routing-instances overlay protocols evpn default-gateway no-gateway-community
set routing-instances overlay bridge-domains BD-100 vlan-id 100
set routing-instances overlay bridge-domains BD-100 routing-interface irb.100
set routing-instances overlay bridge-domains BD-100 vxlan vni 5100
set routing-instances overlay bridge-domains BD-100 vxlan ingress-node-replication
set routing-instances overlay bridge-domains BD-101 vlan-id 101
set routing-instances overlay bridge-domains BD-101 routing-interface irb.101
set routing-instances overlay bridge-domains BD-101 vxlan vni 5101
thanks in advance !!
thanks for taking a look.
I did have this line
set interfaces irb unit 101 virtual-gateway-accept-data.
But it did not work, I removed and tried proxy-macip-advertisement;
Unfortunately, not work either.
Not sure whether because of vMX image.
Can you see any configuration issue if I add virtual-gateway-accept-data back ?
Not sure if this is because of the vMX environment but you should be able to ping just with the accept data statement, it is safe to add it back as it is needed, you should not face any configuration constrain. Actually the proxy-macip-advertisement is needed In case of Non-Collapsed deployments, if you are using a collapsed environment ( L2 and L3 gateway on the same device) this would not make a lot of sense.
Something else you could try is to upgrade to the latest and greatest. then I would have the following knob configured: virtual-gateway-v4-mac.
You can explicitly configure an IPv4 or IPv6 MAC address for a default gateway by using the virtual-gateway-v4-mac or virtual-gateway-v6-mac configuration statement at the [edit interfaces name irb unit logical-unit-number] hierarchy level. After you perform this configuration, the automatically generated MAC address is overridden by the configured MAC address.
If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/
Lil DexxJNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB
Sorry it is my bad. I found my vtep-source-interface wrong. It should be lo0.0. I entered lo0 instead in one of the routers.
thanks so much !!