In the previous generation of CRS configuration, bridging was not the best way to configure the switch – using the port master/slave option would trigger hardware forwarding.Īfter MikroTik revamped the switch config for VLANs in 2018 to utilize the bridge, it more closely resembles the style of configuration for Metro Ethernet Layer 2 as well as vendors like Juniper that use the ‘bridge-domain’ style of config. 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.
Cisco mac address table associated vlan 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.
Cisco mac address table associated vlan 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. If you do the second one, it makes reading the ifAlias much more straight forward, however I have not done this globally.One of the most difficult configuration challenges for MikroTik equipment seems to be switching and VLANs in the CRS series. Set interfaces ge-0/0/36 unit 0 description "Description on the sub-interface"īoth are valid, but the GUI only does the first one similarly the GUI only displays the value from the first one. You can, if you are suitably detailed-oriented, apply your port descriptions to the sub-interfaces instead of the interfaces, eg: set interfaces ge-0/0/36 description "Description on the physical port" My script checks for ifAliases (since on other things like Dells and HPs it will find them) but the Junipers don't have them in the right place. This hoopage-jumpage is necessary because with simpler switches, the ifPort index is the same as the physical port index - ifPort 1 is port 1 on the switch. In this case the mac is associated with 0/0/36.0, while the label is associated with 0/0/36. The second is that on a Juniper the interface the mac address is associated is almost always a sub-interface, and port labels/descriptions are usually associated with the physical interface, so there isn't a trivial way to read the ifLabel off of the port description based on the portID (and glossing over the whole converting ifPort-to-ifIndex) you get back from the Q-Bridge-II.įor example: $ findmac -DEBUG -c MyPass sa4-39 00:07:e9:25:05:3c So you have to pull in the table and convert base-10 MACs to the base-16 MACs you are used to dealing with. Now you want to beware because there are a couple of wrinkles: firstly the MAC addresses are encoded as row specifications in the OIDs, the VALUES are the ifPort that that MAC address is reachable through. The OID you want is called the Q-Bridge-II MIB, at 1.3.6.1.2.1.17.7.1.2.2.1.2 - it returns a list of MAC addresses associated with the logical port those MAC addresses are listed on.