Hello- If you have a multi-layer switch (one that can perform its own routing between its SVIs, then you won't need an external router (the ROAS). If you have a trunk between 2 or more switches, that is carrying all the VLANs, you can have a single ROAS or a single multilayer switch that is performing routing between all the VLANs. Keith
The "PC" and the "Server" are actual routers simulating being a PC (ip routing off). Keith clarified that in one of the previous videos of this series.
First of all, THANK YOU for your explanations, they are revealing!!!! Secondly, the question: If you have a CISCO ASA and MLS, and you have also a good network design using layers (core, aggregation and access) what would be the best practice, use ASA as routing or transparent mode? Does the chosen solution depend on what? Any comment would be appreciated. Thank you again.
@Xtil I attempted to re-create this lab using a 3550 but had no luck pinging from client to server from one vlan to the next. Interesting thing is that the from the CLI i can ping to everything, client server included. What am i doing wrong?
Hi Keith - great video. Much more informative detail than many other folks on the tube. Can you share how you setup the Wireshark sniffer for the trunk ports? I presume you haven't got any GNS3 stuff going on there, as you're using physical switches, or are you? :-) RSPAN sessions? Thanks.
Hi Rob. I used GNS3 for this demo, and in GNS3 we can just right click any link (including a trunk) and capture the packets right there. Simple and easy. :) There is some basic switch functionality in GNS3 0.8.x and I leveraged most of it for this video. I have another RU-vid video on switching in GNS3 that you may want to check out as well. Keith
sorry, but can i ask if i have a ROAS connected to a switch vlan 3,4,5 and the same router connected to another switch vlan 6, when the 2 switch are trunked. if i configured the SVI, do i still need to configure the router sub int?? since u said SVI allow a switch to route packets.
Excellent video one of the best explanations of inter v-lan routing utilising multiswitch layers. How is this actually more effective than router on a stick? is it because it is easier to implement within a corporate infrastructure network?
Hello Monsieur- This is similar to router on a stick, with an integrated router built into the switch (no external router needed). Most networks (current networks) won't send traffic to an external router for routing, as the routing feature is built in to the multi-layer switches.
I have public IP 1.1.1.1/252 connected to my my internet facing 2911 router,which inturn is connected to l3 3560 switch using routing port on l3 switch.I have multi vlans and multi dhcp pools defined in separate microsoft dhcp server.The client gets its ip from one of the pool in its correspoding VLAN ,but its not getting connection to the internet.What could be the issue.Some times the internet is not reachable even from the 2911 (internet facing router). 2911# Configuration: int g0/0 ip add 1.1.1.2 ! default gateway 1.1.1.1 ip route 0.0.0.0 0.0.0.0 1.1.1.1 ! ip name-server 8.8.8.8 4.2.2.2 ! !............. Please help me resolve the issue....... regards
