cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
318
Views
0
Helpful
3
Replies

2 orphan host on a nexus 9k vpc domain not able to ping eachother

DennisDammers
Level 1
Level 1

Hi,

I try to produce an situation where i have 2 orphan hosts. Each orphan host is connected to a leaf switch (for example leaf1 and leaf2). So host1(mac: 0c:89:34:41:00:00) is is connected to leaf1 and host2(mac:  00:50:79:66:68:00) to leaf2. Leaf1 and Leaf2 form an vpc domain. Both hosts are connected to vlan8 as an access port.

The problem i encounter is that host1 is not able to ping host2. I see that all mac's are learned on both leaf switches. When i try to monitor traffic within gns3 i see arp responses, but it seems like the pc connected to the primary switch learn's the mac of host2, but host2 not of host1. 

I know this isn't a best practise, but i want to know if it's possible and if not why it's not possible.

 

vpc config:

vpc domain 101
peer-switch
peer-keepalive destination 10.10.10.62 source 10.10.10.63 vrf default
virtual peer-link destination 10.10.10.62 source 10.10.10.63 dscp 56
peer-gateway
ipv6 nd synchronize
ip arp synchronize

interface port-channel999
vpc peer-link

LEAF3 MAC's:

Route Distinguisher: 10.10.10.63:32775 (L2VNI 10008)
*>l[2]:[0]:[0]:[48]:[0050.7966.6800]:[0]:[0.0.0.0]/216
10.10.10.83 100 32768 i
*>i[2]:[0]:[0]:[48]:[0c15.9bc3.0000]:[0]:[0.0.0.0]/216
10.10.10.60 2000 100 0 65535 i
*>i[2]:[0]:[0]:[48]:[0c3d.1419.0000]:[0]:[0.0.0.0]/216
10.10.10.60 2000 100 0 65535 i
*>i[2]:[0]:[0]:[48]:[0c45.6421.0000]:[0]:[0.0.0.0]/216
10.10.10.81 100 0 i
*>i[2]:[0]:[0]:[48]:[0c55.0000.1b08]:[0]:[0.0.0.0]/216
10.10.10.69 100 0 i
*>i[2]:[0]:[0]:[48]:[0c80.0000.1b08]:[0]:[0.0.0.0]/216
10.10.10.60 100 0 65535 i
*>i[2]:[0]:[0]:[48]:[0c89.3441.0000]:[0]:[0.0.0.0]/216
10.10.10.82 100 0 i
*>l[2]:[0]:[0]:[48]:[0cae.0000.1b08]:[0]:[0.0.0.0]/216
10.10.10.89 100 32768 i

leaf2 mac's: 

Route Distinguisher: 10.10.10.62:32775 (L2VNI 10008)
*>i[2]:[0]:[0]:[48]:[0050.7966.6800]:[0]:[0.0.0.0]/216
10.10.10.83 100 0 i
*>i[2]:[0]:[0]:[48]:[0c15.9bc3.0000]:[0]:[0.0.0.0]/216
10.10.10.60 2000 100 0 65535 i
*>i[2]:[0]:[0]:[48]:[0c45.6421.0000]:[0]:[0.0.0.0]/216
10.10.10.81 100 0 i
*>i[2]:[0]:[0]:[48]:[0c55.0000.1b08]:[0]:[0.0.0.0]/216
10.10.10.69 100 0 i
*>i[2]:[0]:[0]:[48]:[0c80.0000.1b08]:[0]:[0.0.0.0]/216
10.10.10.60 100 0 65535 i
*>l[2]:[0]:[0]:[48]:[0c89.3441.0000]:[0]:[0.0.0.0]/216
10.10.10.82 100 32768 i
*>l[2]:[0]:[0]:[48]:[0cbb.0000.1b08]:[0]:[0.0.0.0]/216
10.10.10.89 100 32768 i

Host port:

interface Ethernet1/5
switchport access vlan 8
vpc orphan-port suspend

 

 

 

3 Replies 3

Giuseppe Larosa
Hall of Fame
Hall of Fame

Hello @DennisDammers ,

at first sight the following command can cause the issue

>> vpc orphan-port suspend

Hope to help

Giuseppe

 

DennisDammers
Level 1
Level 1

Hi @Giuseppe Larosa,

I tried to remove it on the interface, but still no difference. 

DennisDammers
Level 1
Level 1

I have worked around the problem, by creating a dedicated vpc, instead of using vpc fabric peering with virtual-link. 

Review Cisco Networking for a $25 gift card