Vxlan with cisco Nexus border leaf to border leaf

[mcusine]

Hello everyone,

I am trying to set up a vpc topology where I connect two borders leafsdirectly to different cpds using level 3 and vxlan. The vpc is for traditional vlans.
The problem I have is that I don't see traffic on nve interface 1.

nve1 is up
admin state is up, Hardware: NVE
MTU 9216 bytes
Encapsulation VXLAN
Auto-mdix is turned off
RX
ucast: 0 pkts, 0 bytes - mcast: 0 pkts, 0 bytes
TX
ucast: 0 pkts, 0 bytes - mcast: 0 pkts, 0 bytes

I see that the mac apparently announces itself but it seems that the next hop is not valid.

I see the next error:

Nexus3# show bgp l2vpn evpn detail
BGP routing table information for VRF default, address family L2VPN EVPN
Route Distinguisher: 11.1.1.1:33067 (L2VNI 300)
BGP routing table entry for [2]:[0]:[0]:[48]:[5021.ba00.1400]:[0]:[0.0.0.0]/216,
version 27
Paths: (1 available, best #0)
Flags: (0x000102) (high32 00000000) on xmit-list, is not in l2rib/evpn, is not i
n HW

Path type: local, path is invalid(rnh not resolved), no labeled nexthop
AS-Path: NONE, path locally originated
100.1.1.1 (inaccessible, metric 4294967295) from 0.0.0.0 (11.1.1.1)
Origin IGP, MED not set, localpref 100, weight 32768
Received label 300
Extcommunity: RT:65003:300 ENCAP:8

BGP routing table entry for [2]:[0]:[0]:[48]:[5021.ba00.1400]:[32]:[192.168.0.2]
/248, version 28
Paths: (1 available, best #0)
Flags: (0x000102) (high32 00000000) on xmit-list, is not in l2rib/evpn, is not i
n HW

Path type: local, path is invalid(rnh not resolved), no labeled nexthop
AS-Path: NONE, path locally originated
100.1.1.1 (inaccessible, metric 4294967295) from 0.0.0.0 (11.1.1.1)
Origin IGP, MED not set, localpref 100, weight 32768
Received label 300
Extcommunity: RT:65003:300 ENCAP:8

I tryed to add ipv4 adress family unicast and neighbord but don't work.

Any idea?.

I attach the nexus 1 and 3 config.

Thanks in advance,

Topology

[Pavel Tarakanov]

Announce Lo1 to ISIS

interface lo1
ip router isis prueba

[mcusine]

Hi,

Sorry i forget to add this command on the configuration i sent but was configure and i deleted when testing. I will put again.

Thanks, any other idea?.

King regards

[mcusine]

Hi,

Good morning,
I have added the command to the config that I had deleted and I pass it through now. Something very strange happens, Nexus 1 stops receiving the announcement of loopback 1 from router Nexus 3 if I apply loopback one on router 3 as a source of interdace nve1, and bgp must be reachable. It happens every time I do that but only from router 3. Router 1 does it fine.

Thanks and king regards,

Mauricio

[Pavel Tarakanov]

Also for VPC source loopback for NVE interface should be configured in specific way

vPC Considerations for VXLAN Deployment

• The loopback address used by NVE needs to be configured to have a primary IP address and a secondary IP address.

  The secondary IP address is used for all VXLAN traffic that includes multicast and unicast encapsulated traffic

https://www.cisco.com/c/en/us/td/docs/dcn/nx-os/nexus9000/103x/configuration/vxlan/cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-release-103x/m_configuring_vxlan_93x.html

[mcusine]

Thanks, ok i will try to add a secondary ip address on lo1.

Thanks and king regards,

Mauricio

[mcusine]

Good morning,
I have added the command to the config that I had deleted and I pass it through now. Something very strange happens, Nexus 1 stops receiving the announcement of loopback 1 from router Nexus 3 if I apply loopback one on router 3 as a source of interdace nve1, and bgp must be reachable. It happens every time I do that but only from router 3. Router 1 does it fine.