04-27-2025 07:04 AM
Hi, I have the topology with two orphan devices that are on different vlans but vpc peers would never seem to sync arp over cfsoip and hence the ping from one orphan device to another isn't working. Is it expected scenario? Config attached. The SW1 has no play in this, disregard it please.
Solved! Go to Solution.
04-27-2025 11:10 PM
As per configuration guide
TCAM should be carved in specific way for fabric peering. It seems there is no such lines in your configuration.
Also it could be issue with virtualization, as NX-OSv doesn't support all features of devices. Most common example - issues with multicast.
04-30-2025 08:27 AM
everything seems to be fine when working with actual hardware, thanks!
04-27-2025 09:32 AM
According to provided config, virtual peer-link used instead of physical one. In such case such interaction (between hosts connected with orphan ports) more like interaction between two independent VTEPs, not as two orphan ports in classical VPC domain with physical peer link.
I'd recommend to check all related tables (MAC address, l2 routes, BGP L2VPN EVPN, routing tables of corresponding VRF).
Also can H1 ping to H2? Can H1 and H2 ping their default gateways?
Additionally, how you get this incomplete record for 192.168.20.11 on LEAF-1? Most likely you tried to ping H2 from VTEP LEAF-1. But in such case source for such ARP request will be SVI for VLAN 20 with IP address shared between all VTEPs. And ARP reply could be consumed be LEAF-2.
04-27-2025 11:47 AM
Hi Pavel,
Ping from H1 to H2 fails.
I can ping the gateways:
I can see the MAC and IP addresses in l2rib. Meaning they are advertised and imported correctly
And I see the pings on the link among spines and leaves but these icmp requests are never being decapsulated and forwarded to an endpoints.
04-27-2025 11:10 PM
As per configuration guide
TCAM should be carved in specific way for fabric peering. It seems there is no such lines in your configuration.
Also it could be issue with virtualization, as NX-OSv doesn't support all features of devices. Most common example - issues with multicast.
04-28-2025 03:01 AM
I will try this on the hardware, I only tried it on the n9kv and the mentioned tcam carving is not available. Thanks!
04-30-2025 08:27 AM
everything seems to be fine when working with actual hardware, thanks!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide