Avatar of tolinrome
tolinromeFlag for United States of America asked on

ping layer 3 switch and hosts

I have a lab with different networks and on one network I have a layer 2 and layer 3 switch, the layer 3 switch is connected to a router. I have a few different vlans on this network. All vlans can communicate with each other and the switches and router.

I can ping externally to another client on another network form the layer 3 switch with no problem. However, I cannot ping from the layer 2 switch or computers on the vlans on the same network to these external hosts. What is it that is preventing replies when I ping externally?
There are no acl's on the routers.
Switches / HubsRoutersNetworking

Avatar of undefined
Last Comment
tolinrome

8/22/2022 - Mon
Trenton Knew

is the switchport access mode to the router a trunk or is it only assigned to one vlan?  If the layer 3 switch is not routing inter-vlan traffic, the port connected to the router will have to be trunked, and the router itself will have to support inter-vlan routing and trunking.
Trenton Knew

are there multiple vlans on the layer 2 switch also?  is the switchport access mode between the port on the L2 switch and L3 switch trunked as well?
jburgaard

Best gues is a missing route back on router to vlan with problem.

But please provide details: IP, dgw. and net-mask for a client with problem.
For L3-switch: IP & net-mask for involved vlans and dgw.
for router:IP & net-mask for involved vlans and IP routes back to client-network.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
ASKER
tolinrome

L3 switch is the DG for the vlans, I set up int vlans XX on it as below:
10.1.10.1
10..120.1
10.1.30.1 and etc

L2 switch has these vlans as well (obviously not int vlans, just vlans). host computers are connect to the L2 switch only.
On the L3 switch there is the "ip routing" command for internal vlan routing and the statement "ip route 0.0.0.0 0.0.0.0 10.1.60.2" which 10.1.60.2 is the internal interface of the router. Vlan 60 is the vlan that connects the L3 switch to the router. It is only 2 interfaces, the L3 switch and router.
jburgaard

So you have a number of networks with net-mask 255.255.255.0
your dgw of L3-sw is 10.1.60.2
For packets to come back from your router there must exist 'routes back' like
IP ROUTE 10.1.10.0  netmask 255.255.255.0  gw 10.1.60.1
The syntax probably is not exact , but to reach an address in the 10.1.10.0/24 range a packet arriving at router has no directly connected network to turn to and should not go via dgw (to internet) but via L3-switch.
Instead of a lot of routes like that you probably can bundle them with a broader net-mask than 255.255.255.0
HTH
ASKER
tolinrome

I already had "ip route 10.1.0.0 255.255.0.0 10.1.60.1" and it wasn't working and now I added:
R1(config)#ip route 10.1.20.0 255.255.255.0 10.1.60.1
R1(config)#ip route 10.1.30.0 255.255.255.0 10.1.60.1
R1(config)#ip route 10.1.10.0 255.255.255.0 10.1.60.1
R1(config)#ip route 10.1.40.0 255.255.255.0 10.1.60.1

and it still doesn't work.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
jburgaard

Could a there be a firewall-rule on the destination PC?
Did you try disable firewall or pinging printer instead of PC?
Did you try traceroute/tracert both ways?
ASKER CERTIFIED SOLUTION
tolinrome

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER
tolinrome

This was the solution.