cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
709
Views
5
Helpful
8
Replies

3 routers connected with 3 switches

yari25160
Level 1
Level 1

1.png

I'm new to networking and currently setting up a small test lab with three Cisco routers and three Cisco switches.

Could someone guide me on the best way to configure. i have Layer 3 switches. I use router-on-stick concept.

I’d really appreciate any advice, config examples, or troubleshooting tips!

Thanks in advance!

2 Accepted Solutions

Accepted Solutions

Thank you for the quick reply.

I am using router-on-stick. Just want to confirm is there any other way we can perform this lab?

View solution in original post

you need
1- add same vlan in all SW 
2- config all link as trunk 
3- run PVST to make some load balance 
https://www.ii.pwr.edu.pl/~kano/course/module4/4.3.1.4/4.3.1.4.html

4- config subinterface in router with correct vlan tag

5- config IGP 

MHM

View solution in original post

8 Replies 8

M02@rt37
VIP
VIP

Thank you for the quick reply.

I am using router-on-stick. Just want to confirm is there any other way we can perform this lab?

@yari25160 

If you want inter vlan routing this is the only way in the cas of using L2 switch.

In the case of MultiLayer switch, ip routing could be perform by this platform...

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

Joseph W. Doherty
Hall of Fame
Hall of Fame

Yours would be a rather unusual topology for a router-on-a-stick, especially if the switches are L3 switches.  Further, it would be a bit unusual to use 3 routers, unless the routers are of such low capacity you need that many to provide a aggregate routing performance.

Regardless, configure all the shown switch ports as trunks, and insure a loop breaking technology, like STP, is used.  Configure the router ports as subinterfaces.

Each router will need minimally two sub interfaces but could have a sub interface in every VLAN.  If routers do not have sub interfaces in all VLANs, you'll need to route between some VLANs using multiple routers.

As to advice, outside of a lab for learning, such a topology is probably best avoided.  Further, with L3 switches being so common, LAN routing should avoid using routers.

As to troubleshooting, avoid, if possibly, complex out-of-date designs.  (This last doesn't mean don't study such, as you may run into one, but avoid using them for new network.)

Thank you for providing the information—it is greatly appreciated.

The reason I am exploring this approach is due to a specific scenario at work where we need to establish redundancy. While we could achieve this through a router link, we are currently limited by the number of available ports on the router.

Your feedback has been incredibly valuable and has provided me with an excellent learning opportunity. I truly appreciate your insights.

"The reason I am exploring this approach is due to a specific scenario at work where we need to establish redundancy. While we could achieve this through a router link, we are currently limited by the number of available ports on the router."

Yup, routers are often port limited, but for routing redundancy, a pair is often considered sufficient.  The pair could be two routers, two L3 switches, two stacked L3 switches, L3 switch and a router, etc.

As you now note you're trying to solve a real world redundancy problem, I would suggest you create a new posting describing it.  Your lab might not lead to an optimal solution or even have real world pitfalls.

For example, @MHM Cisco World mentioned you need an IGP, but if each router in the posted topology has an interface in all networks, they don't need to cooperate with other routers.  But, for hosts to get to other networks, they generally should have a defined gateway, and if they do, for redundancy, that's often provided by a FHRP.

As another example, @MHM Cisco World has you needing PVST root placement.  Very much NOT needed in a lab unless it's something being examined.  In real world, it could be a very important consideration, but there's much that can go into selecting root placements and interactions with other network considerations, such as the root switch is normally the gateway too.

There can be a huge difference, in real world networks, between a network that functions correctly and one that also does so well!  Also, laugh/sigh, there can be a huge difference in how a network might be ideally designed, technically, vs. real world budget restrictions.

On these forums, you'll likely obtain good responses to lab or real world issues, but don't assume answers to the former are always directly applicable to the latter.

you need
1- add same vlan in all SW 
2- config all link as trunk 
3- run PVST to make some load balance 
https://www.ii.pwr.edu.pl/~kano/course/module4/4.3.1.4/4.3.1.4.html

4- config subinterface in router with correct vlan tag

5- config IGP 

MHM

Some comments. . .

"3- run PVST to make some load balance"

Certainly worth considering!  However, the reference doesn't delve into the many considerations for picking root placement, including those that would have you NOT have the VLAN roots on different switches.  Also, PVST assumes Cisco switches.

"5- config IGP"

Not necessarily needed, as I described earlier, for just the OP topology.

What may be much more needed is a FHRP.

Review Cisco Networking for a $25 gift card