Cloud Router Switch (CRS) is a high-performance Smart Switch Series device from Mikrotik that has many ethernet ports (up to 24 ports). This CRS device is a Multilayer Switch, which in addition to work on layer 2, can also work on layer 3 switches and unique OS that is used also RouterOS so that all features on RouterOS can also be applied in this device.
Key Features of Cloud Router Switch
Ports on CRS can be configured for switching and routing that support Full non-blocking wire-speed switching. All forwarding databases support IVL and SVL. Port-based MAC learning limits that can be configured up to 1024 MAC per port. In addition, CRS also supports frames with jumbo size (CRS1xx: 4064 Bytes; CRS2xx: 9204 Bytes).
CRS supports various types of mirroring ports, such as Port-Based Mirroring, VLAN Based Mirroring, and MAC-Based Mirroring. In addition, CRS also has 2 independent mirroring analyzer ports.
3. Virtual LAN (VLAN)
Mikrotik CRS is compatible with IEEE802.1Q and IEEE802.1ad VLAN standards. CRS is able to create active VLANs up to 4000 VLANs. Supports Port-Based VLANs, Protocol-Based VLANs, MAC Based VLANs, and VLAN filtering.
4. Port Isolation & Leakage
CRS can be applied to implement private VLANs with 3 port profiles: Promiscuous, Isolated and Community. Supports up to 28 Comunity Profile.
CRS supports trunking with static link aggregation groups. Can create up to 8 Trunk group ports and 8 ports per trunk group. Supports Hardware automatic failover and load balancing.
6. Quality of Service (QoS)
Mikrotik CRS also supports bandwidth management with QoS implementation based on port, MAC, VLAN, Protocol, PCP / DEI, DSCP, ACL.
7. Shaping & Scheduling \
Supports 8 queues on each physical port, Shaping per port, per queue, and per queue group.
8. Access Control List (ACL)
CRS supports Ingress and Egress ACL tables, and up to 512 ACL rules. Classification by port, L2, L3, L4 protocol header. ACL actions include filtering, forwarding, and modifications to the protocol header fields.
Model Cloud Router Switch (CRS)
Here are some differences in the model of Mikrotik Cloud Router Switch (CRS):
|Model||CPU||Wireless||SFP + port||Access Control List||Jumbo Frame (Bytes)|
In CRS, tagged and untagged features can be created based on ports, protocols or Mac-based addresses, to make it easy to custom in our network.
For example, the topology that we will form as follows:
Configuration on the RB450G side
Configuration in CRS
SLAVE-PORT) with another non-switch mode ethernet interface.
slavewith master-port in ether10. That is, ether10, ether12, and ether14 have become a switch and communication between these ports can be
full wire speedwithout burdening the router CPU again.
VLANs based on Port
tagged / trunk port), and vice versa, since the devices connected in ether12 and ether14 are ordinary PC devices, means we must set all traffic out of both ports must be removed first VLAN-id (
untagged / access port).
Ingress VLAN Translation
new-customer-vid = 1 (VLAN-id = 1 / tagged)
Egress VLAN Translation
From the visible image, all traffic coming out of ether12 and ether14 is set to new 0 customers (VLAN-id), so the traffic coming out of ether12 and ether14 is acceptable to ordinary PCs. This is equivalent to making ether12 and ether14 being access port / untagged.
Final Results By enabling the above configuration, client PCs in vlan1 and vlan2 communications are no longer via layer 2 even though they are in 1 physical switch, but must be inter-VLAN communication via