Ping Issue between mt VDC-COR and SW-Campus

[MKERKACHE]

Hello,

I have connected my Switch campus C3850 to my VDC-COR (Nexus 7710) L3 , the isssue that i have from my VDC-COR i can ping my  SVI that are located in my SW-campus, however others address that are located on mt campus not joinable this an example

From my SW-campus

SW-CMP-1#ping 10.99.101.250
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.99.101.250, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms

from VDC-COR i can ping my SVI

loobpack 0: 172.16.45.1

SW-COR-1# ping 10.99.101.1 source 172.16.45.1
PING 10.99.101.1 (10.99.101.1) from 172.16.45.1: 56 data bytes
64 bytes from 10.99.101.1: icmp_seq=0 ttl=253 time=2.435 ms
64 bytes from 10.99.101.1: icmp_seq=1 ttl=253 time=2.076 ms

SW-COR-1# traceroute 10.99.101.250 source loopback 0
traceroute to 10.99.101.250 (10.99.101.250) from 172.16.45.1 (172.16.45.1), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
64 bytes from 10.99.101.1: icmp_seq=2 ttl=253 time=2.043 ms
64 bytes from 10.99.101.1: icmp_seq=3 ttl=253 time=2.03 ms
64 bytes from 10.99.101.1: icmp_seq=4 ttl=253 time=2.132 ms
^C
--- 10.99.101.1 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 2.03/2.143/2.435 ms

SW-COR-1# show ip route 10.99.101.250
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>

10.99.101.0/24, ubest/mbest: 1/0
*via 10.98.10.2, [1/0], 00:51:36, static

[nazimkha]

Not sure how is your topology and IP addressing being used on the 3850 and VDC-COR. Share your topology with IP addresses

[MKERKACHE]

Hello,

find  in the atteched file the toplogy

also i created a loobpack 0 on SW-campus for test only, I was able to ping it from my COR

SW-COR-1# ping 10.99.155.1
PING 10.99.155.1 (10.99.155.1): 56 data bytes
64 bytes from 10.99.155.1: icmp_seq=0 ttl=253 time=2.952 ms

64 bytes from 10.99.155.1: icmp_seq=1 ttl=253 time=2.227 ms
64 bytes from 10.99.155.1: icmp_seq=2 ttl=253 time=2.247 ms
64 bytes from 10.99.155.1: icmp_seq=3 ttl=253 time=2.189 ms
64 bytes from 10.99.155.1: icmp_seq=4 ttl=253 time=2.11 ms
^C
--- 10.99.155.1 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 2.11/2.344/2.952 ms
SW-COR-1# show ip route 10.99.155.1
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>

10.99.155.1/32, ubest/mbest: 1/0
*via 10.98.10.2, [1/0], 00:48:47, static

Thanks

[nazimkha]

Thanks for the topology. I think the problem is that you have the same subnet on either side of 3850 and VDC-COR. however the subnets are disjointed as you have a layer-3 link between the 3850 and the VDC-COR.
You may try using proxy ARP
https://www.cisco.com/c/en/us/support/docs/ip/dynamic-address-allocation-resolution/13718-5.html