I purchased two CRS125-24G-1S-IN devices intending to use them as switches (not routers) on our network. I’ve been having such incredible trouble connecting them to my Cisco Catalyst device that I’ve decided to completely take it out of the equation. Surely it will be easier to VLAN two of the exact same Mikrotik products over the SFP port…
The word “nope” seems to be the answer to many things in the world of CRS VLANs. I am new to enterprise networking and yes this is my first Mikrotik, but boy has configuring the Cisco been a summer breeze in comparison.
Anyways, here’s my setup:
CRS x2 (connected via SPF)
PC x2 (one connected to each CRS, on ether2 after configuring them)
Besides their respective IP addresses (both Internet and Local) I’ve got the two CRS switches set up identically (is this correct?).
- All ports (Including SFP) are slave to ether1 (master), which I’m told configures the CRS for switching.
- Created a VLAN (ID:99) on interface ether1 (in the interfaces window -not the “Switch > VLAN” section that seems to be redundant? I’ve tried adding it there as well with no positive effect.)
- Configured Egress VLAN Tagging on sfp1 and switch1cpu for VLAN 99
- Set Ingress VLAN Translation (just on ether2 for now) to have Customer VID 0 and a New Customer VID of 99
- Set Egress VLAN Transation (just on ether2) to have Customer VID 99 and New Customer VID of 0 (tried with and without this setting)
- Added VLAN filtering on ether2 to drop invalid traffic
- Have two IP address ranges set up:
- One for ether1 (192.168.99.150/24 | 192.168.99.0) This being the IP of the CRS.
- Another for vlan99 (192.168.99.1/24 | 192.168.99.0)
In this configuration when connected to ether2 (on either device), I lose all connectivity. Nothing is pingable and I can’t even Winbox in via the MAC.
If I use any other port (bypassing the VLAN) I can ping both routers, but not PC to PC. I can’t even ping the other PC if I connect them to the same switch anymore.
So that’s where I’m at. Any help would be fantastic as I’m supposed to implement this on Saturday morning (with the Cisco no less, getting the Mikrotiks to play nice is only a preliminary troubleshooting measure).