

Check the configuration under the vpls routing-instance to verify the MAC aging timer. If the aging timer is too low, then MAC addresses will get flushed quickly which may result in unexpected behavior.
If you want to see the MAC table specific to some interface, you can use the command show vpls mac-table instanceTo correct this, look into any config changes done recently or any topology change that resulted in the MAC not learned on the correct routing-instance. Generally when there is configuration mistake or when there is topology change which results in the local router from learning a MAC address on a different routing-instance or on a different interface, we see this log.

If not, then enable traceoptions for the L2 learning on the local PE router and see if MAC learning is happening or not. Initiate traffic from CE to CE again and verify If MAC addresses are learned on the local PE.

In the above configuration under term2, the MAC address is for the remote CE device and the counter REMOTE_CE_count is incremented whenever frames from the remote CE hit the local PE.Īpply this filter under forwarding options inside the routing-instance on the PE show configuration routing-instances VPLS_INSTANCE forwarding-options family vpls Initiate traffic from CE to CE again. To do this, enter the ‘ show interfaces ge-X/Y/Z unit n’ command.Įncapsulation vlan-vpls show configuration firewall family vpls filter vpls Verify if VLAN encapsulations are used on the CE facing interface of the interested PE routers.
JUNIPER HOW TO CHECK MAC ADDRESS ON MX CODE
The MX’s loopback (lo0.0) IP is 1.2.3.4 and you want to create a VXLAN VNI (185) to a Linux router at 99.88.77.66.Note: While these troubleshooting steps can be applied for all code versions and all platforms, this troubleshooting guide is written primarily keeping MX platform in mind.Ĭonfirm you have initiated traffic from CE to remote CE, so that the PEs will learn or attempt to learn the MAC addresses. The switch is trunked to the MX on interface ae0. Servers are connected to a switch on VLAN 185. You’ll need to bridge a standard VLAN with a VXLAN VNI. Broadcast and Multicast traffic is flooded to all VTEPs. Once it gets a packet from a particular MAC address, it will store that MAC address against the VTEP in its table and only send subsequent packets to that address. If a MAC address is not found in its table (show ethernet-switching table) then it will flood the packet to all statically configured VTEPs.
JUNIPER HOW TO CHECK MAC ADDRESS ON MX MANUAL
Juniper MX manual VXLAN implementation uses flood-and-learn to discover MAC addresses. In my case, I wanted to create an L2 circuit from a firewall, across The Internet, to a Linux based router. The Internet) then a simple static configuration is quick to do. However, if you’re doing something small such as wanting to span an L2 link across an 元 network (e.g. On most VXLAN deployments, you’ll want to be using EVPN to distribute MAC addresses between devices.
