How Cisco Switches interconnect

Posted on 2014-04-15
Medium Priority
Last Modified: 2014-05-27
I would like to know how Cisco switches get connected in a production environment.

The way I thought they should be connected is:

1- Create VLANs on switches that computers will connect to.
2- If Switches are L3, then create SVIs and run the IP ROUTING command so that computers connected to separate VLANs can communicate with each other directly without taking a trip to the router.
3- Create a Trunk port on each switch where Vlans are created

4-Set up a backbone switch(HUB) and configure as many Trunk port as you have configured on other switches together.
5- Run CAT5 cables between the HUB switch Trunk Ports and all other Switches Trunk ports.
6- on the HUB switch , configure at least one port as a Routing port, by typing "NO SWITCHPORT" command.
7- Connect CAT5 cable between the routing port of the HUB switch to the end Router.

I believe that will work this way.. Please correct me if I am wrong

Thank you.
Question by:jskfan
  • 6
  • 2

Assisted Solution

by:Hassan Besher
Hassan Besher earned 668 total points
ID: 40001413
all what you've mentioned is valid but it's up to how your network designed in the first place, you may choose to configure your access layer as layer 2 only and depend on routing on distribution layer or core layer,

there are a lot of scenarios for what you can do, so for best practices check cisco design zone to get the full picture, and here is an example:

LVL 47

Assisted Solution

by:Craig Beck
Craig Beck earned 1332 total points
ID: 40001438
2- If Switches are L3, then create SVIs and run the IP ROUTING command so that computers connected to separate VLANs can communicate with each other directly without taking a trip to the router.
This will catch you out!

When trying to learn about how switches interconnect, try not to introduce L3 into the mix.  Try to get the fundamentals sorted first, then you can complicate things a bit more :-)

As Hassan Besher said, this is completely reliant on how your network is going to function.  Just because the switch can do L3 doesn't particularly mean it has to do L3, or indeed that you'd even want it to.

To help us help you a bit more, a diagram of what you're trying to achieve would help us to understand where everything is.

Author Comment

ID: 40002771

I wanted to know the general concept on how to connect Computers to the Network.

let's say we have a company that has 400 workstations and Servers together  and need to  be connected to the network.. I basically need to know the road map….

for instance connect computers to separate VLANs on switches , make computers capable of communicating between each other and the outside world…
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

LVL 47

Accepted Solution

Craig Beck earned 1332 total points
ID: 40002920
Again, it depends on how you want to separate everything.  If you want VLANs you'd need some routing, so you can use L3 switches for that.

We really would need to see how you'd like your network to look before we can advise on what you need to do to connect/configure the network.

Author Comment

ID: 40003002
Basically the rule is to have switches laid out this way :

Access Layer
Distribution Layer
Core Layer

However in small Network , Distribution and Core Layers can be just in one layer..

What I need is the road Map of the ports configuration. for instance :
Configure VLANs and access ports on Access layer switches
connect computers to Access Layer switches (to the appropriate ports)
create Trunk ports on access switches
create Trunk ports on distribution switches and connect Cat 5 cables between trunk ports on Access/Distribution switches.
and so on….

Author Comment

ID: 40014405
Something Like this:


Author Comment

ID: 40015890
Have done some research based on the diagram above:

All the Access switches will have redundant trunks to Distribution switches SW1 and SW2
the Distribution switches will have each a trunk to core switch (L3).
Core switch will be the VTP server and all other Switches will be VTP Clients.
Core Switch will be set up to priority 0 so that it will become root switch, Distro switches will have priority higher than Core switch, Access switches will have priority higher than Distro switches.
Create an SVI for VLAN management and assign it IP address, instead of the default VLAN1 management interface. We need to do this on each switch with different IP address for each VLAN Management interface.

In core switch create SVIs for each VLAN in the Network and assign them IP addresses, these SVI will server as the Default Gateway for the PCs.
To make access to the all switches secure we can configure on each switch user name and password and enable ssh:
Line vty 0 4
login local
transport input ssh
you can encrypt the login session to the switch by using crypto key:
Crypto key Generate rya

On each switch configure the Default Gateway Ip address that points back to Core Switch Management Interface IP address.

We need to type IP Routing command on Core Switch will this will enable us to route between all VLANs in the network since respective interface VLANs have been created on the core switch.
for the core switch interface connected to the Router, we can run NO switch port command on that interface and assign it an IP address.
On the core switch , for each interface VLAN (SVI) we create for a specific VLAN, we need to specify the IP helper Address that points to DHCP server IP address.This way each PC communicating with its DG can find the DHCP server.

On the core switch route everything to the Router interface :
IP Route
This way PCs can access resources that L3 switch does not know about.

On the router Interface facing ISP we can configure:
IP address DHCP (it gets IP from ISP DHCP server)
IP NAT Outside

On the Router Global config we'll create Access lists that permits traffic destined to the subnets inside the network
Acces list 1 permit
Acces list 1 permit

and always on the Router Global Config we'll route the traffic destined to the inside subnets to go to the interface of L3 switch
IP Route
IP Route

on the interface facing L3 Switch, we configure:
Ip address
IP NAT inside

Author Comment

ID: 40024633
I wonder if that 's correct

Author Closing Comment

ID: 40092968
Thank you

Featured Post

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Before I go to far, let's explain HA (High Availability) and why you should consider it.  High availability is the mechanism used to provide redundancy to any service at the same site and appears as a single service to the users of that service.  As…
Every server (virtual or physical) needs a console: and the console can be provided through hardware directly connected, software for remote connections, local connections, through a KVM, etc. This document explains the different types of consol…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question