11-19-2024 01:07 AM - edited 11-25-2024 01:03 AM
Hi all,
I have a 9500 setup and traffic destined for 10.220.0.1 from a local vlan 7 (10.80.58.x) needs to be routed to the internet/default route.
I'm trying to determine with debug or otherwise what is happening to this traffic and why the next hop doesnt show on a traceroute from an end user device on vlan7.
Solved! Go to Solution.
11-20-2024 09:34 AM
11-19-2024 01:12 AM
traceroutes from end user device on vlan7;
traffic to 10.220.0.1 failing
normal traffic;
11-19-2024 01:25 AM
Your exit interface for 10.220.0.0 is a layer 2 interface. Where is the layer3? Do you have interface vlan 300 on this switch?
Or the layer3 is in another device? Where is the 10.220.0.0? Is it outside your organization? Does it requires NAT?
11-19-2024 02:36 AM - edited 11-25-2024 01:22 AM
10.220.0.0 is a remote network, remote subnet of a VPN over the internet.
VLAN 300 interface is on this switch yes. I updated my comment above.
!
!
11-19-2024 02:54 AM - edited 11-19-2024 02:54 AM
Assuming you have "ip routing" command on the switch, which I believe you do, the next step is to understand how the switch communicate with its gateway.
If you have interface vlan on the switch and a access interface on vlan 300 as the exit, where is this interface connected?
Where is 10.80.56.34 configured? it is an interface vlan on another device? If you can draw a simple topology would be helpfull
11-19-2024 05:22 AM - edited 11-25-2024 01:22 AM
.
11-19-2024 05:39 AM
@terrykj Definitively you need "ip routing" command. Switch will not routing between vlan, if "ip routing" is not in place.
"10.80.56.34 is the internet router"
if this IP addess is in one router´s interface, I would recommend you to change the interface config TwentyFiveGigE1/0/30
interface TwentyFiveGigE1/0/30
no switchport
ip address 10.80.56.33 255.255.255.248
instead using interface vlan on switch
11-19-2024 06:23 AM
Ip routing is not run' then how ping to 8.8.8.8 is success??
It seem to me there are two GW in your network' check by ping limit broadcast of user subnet.
MHM
11-19-2024 06:37 AM
I'm not sure what you mean by this exactly 'check by ping limit broadcast of user subnet.' ?
Would would be the steps exactly
11-19-2024 06:40 AM
10.80.56.x <<- ping broadcast of this subnet
See the IP reply to this ping
MHM
11-19-2024 07:26 AM - edited 11-19-2024 07:39 AM
Apologies. ip routing is actually enabled.
I ran show run all -to see all the hidden default commands and I can see the line 'ip routing'.
I didnt realise that it doesnt show in the standard config output.
From my perspective, the switch should be handing 10.220.0.x traffic over to its route 10.80.56.34, just like it does with all other internet bound traffic.
I'd like to determine where it's actually attempting to send that traffic with a debug or otherwise.
11-20-2024 09:34 AM
I send you PM check it
MHM
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