GNS3 switching setup and options Part 2: GNS3 unmanaged built-in switch

[Music] in a previous video which I've linked below I discussed the various switching options available in gns 3 also demonstrated the configuration of Cisco iOS V layer 2 switches in this video I'm going to discuss the junus 3 bolt-in switch this is an unmanaged switch in other words you can't configure it through the CLI it provides basic switch functionality to connect devices in a Jus 3 topology even though you can't configure the switch through the CLI you can configure the number of ports on the switch and other basic settings such as making some ports access ports and other ports 82.1 Q ports now note it's not running a switch operating system everything is emulated from scratch this means that some protocols could be buggy so only use this for basic operations don't try and set up a vtp domain or a complex spanning tree domain with the switch it's not going to support those protocols but if all you want to do is connect devices to one another in a Genus three topology this is a good choice the switch is available a under the switches category so select The Ether switch and drag it to the workspace now in this example I'm using Jus 32.0 so I can select where I want to host the ethernet switch I'm going to specify the gns3 VM and click okay so once again in this example I'm using gns 32.0 now for my host devices I'll simply use routers running in the junice 3 VM and we'll do some tests here to see if the ether switch works properly I'll also bring another router in which we can use for intervlan routing so here's my basic topology the first thing I'll do before I connect the devices is configure the switch so right click on the switch click configure and that shows you the various options for configuring the switch so you could configure the name you can add additional ports to the switch so as an example I could add Port 8 which would give me a nine Port switch or I could delete that Port so I'm back to an eight Port switch with port numbers 0 to 7 by default all ports are access ports in VLAN 1 now there is incorrect information on the internet some people will tell you that you can't change the port type through this interface that is incorrect it is possible to change the port type from access to editor1 Q as an example so all you do to make that change is double click on the port number change the type to editor1 Q as an example and click add so the port type is now changed in this example I'm going to leave port Z and Port one in VLAN 1 but to change Port two to another VLAN I'm going to double click on the port that changes the details over here I'm going to change the VLAN to VLAN 2 but leave it as an access port and click add I'll do the same with Port three double click on it Port numberers changed to three change the VLAN to two click add and the VLAN has not changed so notice we have VLAN one on Port zero and one VLAN 2 on ports two and three and we are using a native VLAN of one on our 802.1q trunk so perhaps we want to move the hosts to a separate VLAN so we could put that port in vline 2 this port on vline 2 and then simply change the other ports [Music] to another VLAN as desired click apply to apply your configuration changes and click okay now when you hover your mouse over the switch you'll see the ports that are configured at the moment the ports are empty but we could now start connecting devices to the switch and I'll put router one and router two on ports Zer and one and router three and four on ports ethernet 2 and ethernet 3 just remember that the port numbers start at zero on the switch so I have eanet zero ethernet one eanet 2 ethernet 3 and in this example I've got eanet 7 connected to router 5 which we could use for intervine riding when I hover my mouse over any connection I can see how it's connected and hovering over the switch once again we can see how devices are connected but I could once again right click on the switch click configure and I'll be able to see the configuration of the switch so you can make your topology look pretty I'm not going to worry about doing that here what I'll do now is start up the devices The Ether switch is by default on so just to show you that again if I power down the routers they all powered down and we can see that in the topology summary but the switch is powered on it's not a managed device so you can't power it on and power it off like you would with a normal device notice there's no power options here but on this device we do have a power option there's also no console available on the switch whereas we do have consoles available on The Cisco I'll open up a console to all the routers so as an example we can see that router one has booted so is router 2 and so have the other routers now one of the reasons I wanted to use susco routers rather than a device like vpcs is I want to show you what happens when a broadcast is sent so on the first router we can configure an IP address and then no shut to the interface the interface has now come up so the rouer as an example will be able to Ping itself on router 2 I'll also configure an IP address on the fast ethernet interface and I'll no shut the interface and hopefully R 2 will be able to Ping r one so there you go so if you're remember r 1 and R 2 are in the same VLAN they both in VLAN 2 if you have a problem where your devices can't ping each other other people would tell you that you have to reboot the entire topology now that may be required in some cases but otherwise just delete the connection and then reconnect the connection it's become a lot easier to do those kind of things in Gs 3 version 2 so by simply doing that now notice router 2 can ping router one but if I deleted that cable router 2 would no longer be able to Ping router one so I'll connect the router back again and rer 2 can ping r one we could do a debug IP icmp to prove that and notice now we see the debugs for the Ping now what I'm going to do here is do something you shouldn't typically do I'm going to put router 3 and router 4 in the same subnet as router 2 and router 1 and send a broadcast so that we can prove that the layer 2 switch is working and also see where traffic actually goes when a broadcast is sent so router 3 has got an IP address of 10113 router 4 IP address 10114 router four should be able to Ping router three and there we go so now let's do a test of a broadcast these four routers are in the same net but we've configured the switch with the first two ports in VLAN 2 and the second two ports in vline 3 so rou of 4 when it sends a broadcast should only get a reply back from router 3 but let's test that so ping 101. 255 notice we're getting a reply back from 10113 we are not getting a reply back from router 1 or router 2 if we do the same test on router one paying 10.1 255 we get a reply back from router 2 because I'm running a debug we see additional information I'll turn off debugging and notice now we simply get a reply from router 2 so broadcasts are contained by this gns3 layer 2 switch r one when sending a broadcast only gets a reply back from router two so router one can ping router two but can't ping router 3 because they're in different VLS and by the same token router 1 can't paying R of four now one limitation you have with this switch is you can't move ports from one VLAN to another while the ports are connected so what you could do if you want to move ports from one VLAN to another is remove the ports and then configure the switch so as an example if I want to move Port two to vline 2 I can double click on the port change the vline number number click add click apply and click okay and now I can recable the switch so it doesn't give you a nice easy option to move ports from one VLAN to another like you would have with a CLI switch but in a simple topology like this it doesn't take very long to to recable the topology so now on router one when I send a broadcast we're getting a reply from router 2 and router 3 because I've moved rer 3 from vline 3 to vline 2 so r 1 can ping R 3 and notice previously router 4 was getting a reply from router three when a broadcast was sent and it was able to Ping router fre directly but now we're not getting any replies to broadcast traffic and rer 4 is not able to Ping rer 3 and again it's because we've moved R 3 to VLAN 2 so that's a simple example of how to configure a layer 2 switch you can also set up inter VLAN routing between theay layer 2 switch and a router on a stick so you could simply configure this router for inter vline routing I hope you've enjoyed this video if it was of benefit to you please like it and please subscribe to my YouTube channel I wish you all the very [Music] best