11-21-2014 10:14 AM - edited 03-07-2019 09:36 PM
I have been placed into a network role for a customer while my expertise is much more desktop / server oriented. I do have my CCENT and have been working on the CCNA so I am not completely lost, but I cant figure this out and the deadline is approaching.
This network consists of one L2 switch & three L3 switches. Only one L3 has routing enabled. The one that has routing enabled is directly connected to the other three switches (and all of the VLANs they have on them).
The L3 switch that has routing enabled has a default route of 0.0.0.0 /0 that points to our firewall / internet. The other two L3's and the one L2 have a default gateway set that points to the L3 with routing.
How is it the L3 switch with routing enabled "knows" which switch to send packets destined for the internet too? What am I missing that would help explain this?
And the whole point of the post is to help answer this question:
This organization is moving ISP's shortly, the new demarc will be in a different building (it will go into where one of the L3's is at). I need to make sure I A) grasp the whole logical design here so that I can B) plan for this ISP switch and make sure the network will function on Monday when I am done.
I can post configs if it helps.
11-21-2014 11:42 AM
How is it the L3 switch with routing enabled "knows" which switch to send packets destined for the internet too?
The default route is used when the local router doesn't have a route that it knows about in it's table. For example, let's say you have a user who wants to go to a website located at 5.5.5.5. The user doesn't know how to get to that subnet, so it sends it to its default gateway. The default gateway for the user (the L3 switch with routing enabled) doesn't know how to get to 5.5.5.0/24, so it sends to its default route (the firewall).
If the L3 is the only routing switch, the other L3 and L2 switches are in L2 mode I'm assuming. That means that the hosts are using the L3 switch (more than likely) for their default gateway for their respective vlan.
HTH,
John
11-21-2014 12:46 PM
Thanks John.
This is what I am struggling with though:
The Routing L3 (I will just call it 3560 from here out) is in a logical daisy chain, and its on the end...wait I think i just got it.
Its on the end of the chain of switches like this:
SW1----SW2-----SW3--FW
SW1 is the routing L3 - SW2 is one of the non-routing L3 - SW3 is one of the non routing L3's
Each switch has an interface in the same subnet as the firewall (in this case that subnet is 10.0.128.0 /25). So for instance SW1 has an interface of 10.0.128.140, SW2 has an interface of 10.0.128.150 and SW3 has an interface of 10.0.128.160 and the firewall is 10.0.128.199.
Because each switch has an interface in the FW's subnet, SW1 is able to successfully send an "internet" bound packet through all the hops to the FW? Is this logic sound?
If this is the case, then aside from changing one interfaces configuration a on the SW2 switch my new ISP connection should just "pick up" right?
11-21-2014 02:33 PM
Yeah, in reality the only change that you're going to have is on the firewall and router possibly (depending on how those are set up).
Your current setup works because the L3 switch is the one doing the routing. All of your equipment is in the same subnet. The L2 switches have IP addresses on them only for management. If the other switch is a non-routing L3 switch, it also is really using its address as a management address as well. The only one, and like I said the workstations are probably using it as a gateway, that's routing is the L3 in routing mode.
HTH,
John
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