The MAC entry is associated with a vtep logical interface and shows a remote active source IP, indicating it was learned from a remote VTEP. As a result, traffic destined to that MAC is encapsulated and forwarded across the fabric using a VXLAN tunnel toward the remote VTEP.

You need to configure a next-hop self policy: When using EBGP, the next-hop IP address in the routing advertisements might not be reachable from the receiving device, causing the routes to be marked as hidden. By configuring the next-hop-selfpolicy, the leaf devices will change the next-hop IP to their own IP address for the routes they advertise, making them reachable within the fabric and allowing the routes to be installed in the routing table.
You need to configure loops 2: When all leaves share the same AS (common-AS design), BGP loop prevention drops routes learned from the same AS. Configuring loops 2 allows the leaf to accept routes with its own AS in the path twice, which is needed in an eBGP IP fabric with repeated AS numbers.

The configuration provided in the exhibit shows an EVPN-VXLAN setup where IP prefix routes are exchanged between two sites. The advertise direct-nexthop option and the VNI (Virtual Network Identifier) settings are crucial in this context.
Option A: The advertise direct-nexthop option ensures that the next-hop route is resolved using only the information carried in the EVPN Type 5 route. Type 5 routes are used for IP prefix advertisement in EVPN, which is key to enabling Layer 3 interconnectivity between different VXLAN segments.
VNI Consistency:
Option C: For the same customer across different devices, the VNI must be consistent. This consistency ensures that all devices can correctly map traffic to the appropriate VXLAN segment, maintaining seamless Layer 2 and Layer 3 connectivity.

In an eBGP EVPN overlay, the spine will, by default, rewrite the BGP next-hop when advertising EVPN routes to other peers, which makes the spine appear as the VTEP and causes VXLAN tunnels to form toward it. Enabling the no-nexthop-change behavior preserves the original leaf's VTEP next-hop so VXLAN tunnels form between the leaf VTEPs instead of to the spine.