Within routers, bridging generally does rely on the CPU for forwarding and the throughput is limited to the size of the CPU.Ģ. It is often associated with CPU forwarding and is generally seen as something to be avoided if at all possible.ġ. Notes on hardware bridging in the CRS seriesīridging is a very confusing topic within the realm of MikroTik equipment. However in switching, we still have to use real hardware at least in the realm of MikroTik – Cisco has IOSvL2 images that can be used in EVE-NG for switching. In the last article, we began using EVE-NG instead of GNS3 to emulate both Cisco IOS and RouterOS so we could compare the different commands and ensure the translation was as close as possible. Since there isn’t always an exact match, sometimes you may have to run two or three commands to get the information needed. While many commands have almost the exact same information, others are as close as possible.
#Configure vlans cisco switch series#
Here are some of the others:Ĭlick here for the first article in this series – “ Cisco to MikroTik BGP command translation”Ĭlick here for the second article in this series – “Cisco to MikroTik OSPF command translation”Ĭlick here for the third article in the series – “Cisco to MikroTik MPLS command translation” This is the fourth post in a series that creates a Rosetta stone between IOS and RouterOS.
Therefore, it is helpful to compare the commands if you want to implement a network with a MikroTik and Cisco switches. If you’ve been in networking for a while, you probably started with learning the Cisco CLI. This will only cover VLAN configuration for CRS 3xx series switches in RouterOS as SwitchOS is not nearly as common in operational deployments.ĬRS 1xx/2xx series use an older style of configuration and seem to be on the way out so I’m not 100% sure whether or not i’ll write a similar guide on that series.
#Configure vlans cisco switch how to#
But, sometimes there is still confusion on how to configure VLANs and IP addresses in VLANs with MikroTik RouterOS operating on a switch. Admittedly, the revamp of VLAN configuration for MikroTik CRS switches in early 2018 made things a lot easier. In the picture above you can see that the Fa0/5 port on SW1 was configured as an access port and assigned to VLAN 2.One of the most difficult configuration challenges for MikroTik equipment seems to be switching and VLANs in the CRS series. It is also recommended to configure the port as an access (non-trunk) port using the switchport mode access command: You can also optionally use the name VLAN_NAME command from the VLAN submode to name your VLAN:Īfter you’ve created a new VLAN, you can configure a port to belong to that VLAN with the switchport access vlan ID interface submode command. Simply use the vlan ID command from the global configuration mode. It’s really easy to create a VLAN on a Cisco switch. In the picture above you can see that all of the 24 ports on the switch are in the VLAN 1. To verify that indeed all ports on a switch are in the VLAN 1 by default, you can use the show vlan command: VLAN 1 is the native VLAN of all Cisco switches and it can not be changed, deleted, or renamed.
By default, all ports on a Cisco switch are assigned to the VLAN 1.