03-02-2023 05:20 AM
Dear all,
we have following NEXUS:
NEXUS# sh ver
Cisco Nexus Operating System (NX-OS) Software
Software
BIOS: version 2.12.0
kickstart: version 8.2(1)
system: version 8.2(1)
Hardware
cisco Nexus7000 C7009 (9 Slot) Chassis ("Supervisor Module-2")
Intel(R) Xeon(R) CPU with 12296612 kB of memory.
Configured with a tunnel GRE as follows:
NEXUS# sh int tun 55
Tunnel55 is up
Description: tunnel per MEB
Admin State: up
Internet address is 10.250.250.14/30
MTU 1476 bytes, BW 9 Kbit
Tunnel protocol/transport GRE/IP
Tunnel source 10.250.1.61, destination 10.50.100.200
What we experience is that communications from NEXUS go to Tunnel55, while communication coming from another device belonging to the same VLAN doesn’t transit to Tunnel 55 (as you can see follow):
NEXUS# traceroute 10.50.100.1 source vl5
traceroute to 10.50.100.1 (10.50.100.1) from 10.50.160.1 (10.50.160.1), 30 hops max, 40 byte packets
1 10.250.250.13 (10.250.250.13) 4.41 ms 5.358 ms 3.755 ms
2 10.50.100.1 (10.50.100.1) 4.321 ms 3.358 ms 3.638 ms
PSP-CORE#
Other-Device#traceroute 10.50.100.1 source vlan 5
Type escape sequence to abort.
Tracing the route to 10.50.100.1
VRF info: (vrf in name/id, vrf out name/id)
1 10.50.160.1 2 msec 3 msec 3 msec
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 10.50.100.1 7 msec 4 msec 4 msec
The question is, do we need to enable something on NEXUS that we don’t, or need to get some particular license ?
Thank you for your kind help.
03-15-2023 02:37 AM
Just a thought, can you try to remove your static route to tunnel55 and add them with destination ip instead.
ip route 10.50.0.0/16 10.250.250.13
ip route 10.50.100.0/24 10.250.250.13
03-15-2023 05:10 AM
Tried, unfortunatly it doesn't work.
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