Difference between revisions of "Manual:CRS1xx/2xx VLANs with Trunks"

From MikroTik Wiki
Jump to: navigation, search
(Jumbo frames)
(Port switching: Switch Trunking and STP limitations)
 
(27 intermediate revisions by one other user not shown)
Line 4: Line 4:
  
  
===Summary===
+
=Summary=
  
 
This page will show how to configure multiple switches to use port trunking and port based VLANs, it will also show a working example with a DHCP-Server, interVLAN routing, management IP and invalid VLAN filtering  configuration.
 
This page will show how to configure multiple switches to use port trunking and port based VLANs, it will also show a working example with a DHCP-Server, interVLAN routing, management IP and invalid VLAN filtering  configuration.
  
{{Warning | This article applies to CRS1xx and CRS2xx series switches and not to CRS3xx series switches.}}
+
{{Warning | This article applies to CRS1xx and CRS2xx series switches and not to CRS3xx series switches. For a similar setup for CRS3xx series switches you can check the [[Manual:CRS3xx_VLANs_with_Bonds | CRS3xx VLANs with Bonds]] guide.}}
  
 
[[File:Crs1xx crs2xx trunk vlan.png|700px|thumb|center|alt=Alt text|CRS1xx/CRS2xx port trunking with port based VLANs]]
 
[[File:Crs1xx crs2xx trunk vlan.png|700px|thumb|center|alt=Alt text|CRS1xx/CRS2xx port trunking with port based VLANs]]
Line 16: Line 16:
 
In this setup SwitchA and SwitchC will tag all traffic from ports ether3-ether6 to VLAN ID 10, ether7-ether12 to VLAN ID 20, ether13-ether18 to VLAN ID 30, ether19-ether24 to VLAN ID 40. SwitchB will tag all traffic from ports ether9-ether12 to VLAN ID 10, ether13-ether16 to VLAN ID 20, ether17-ether20 to VLAN ID 30, ether21-ether24 to VLAN ID 40. Management will only be possible if user is connecting with tagged traffic with VLAN ID 99. SFP port is not used in this setup at all, consider disabling it if not being used.
 
In this setup SwitchA and SwitchC will tag all traffic from ports ether3-ether6 to VLAN ID 10, ether7-ether12 to VLAN ID 20, ether13-ether18 to VLAN ID 30, ether19-ether24 to VLAN ID 40. SwitchB will tag all traffic from ports ether9-ether12 to VLAN ID 10, ether13-ether16 to VLAN ID 20, ether17-ether20 to VLAN ID 30, ether21-ether24 to VLAN ID 40. Management will only be possible if user is connecting with tagged traffic with VLAN ID 99. SFP port is not used in this setup at all, consider disabling it if not being used.
  
===Port switching===
+
=Port switching=
  
 
All switches in this setup require that all used ports are switched together. Use these commands on '''SwitchA''', '''SwitchB''', '''SwitchC''':
 
All switches in this setup require that all used ports are switched together. Use these commands on '''SwitchA''', '''SwitchB''', '''SwitchC''':
 
<pre>
 
<pre>
/interface ethernet
+
/interface bridge
set [ find default-name=ether2 ] master-port=ether1
+
add name=bridge protocol-mode=none
set [ find default-name=ether3 ] master-port=ether1
+
/interface bridge port
set [ find default-name=ether4 ] master-port=ether1
+
add bridge=bridge interface=ether1 hw=yes
set [ find default-name=ether5 ] master-port=ether1
+
add bridge=bridge interface=ether2 hw=yes
set [ find default-name=ether6 ] master-port=ether1
+
add bridge=bridge interface=ether3 hw=yes
set [ find default-name=ether7 ] master-port=ether1
+
add bridge=bridge interface=ether4 hw=yes
set [ find default-name=ether8 ] master-port=ether1
+
add bridge=bridge interface=ether5 hw=yes
set [ find default-name=ether9 ] master-port=ether1
+
add bridge=bridge interface=ether6 hw=yes
set [ find default-name=ether10 ] master-port=ether1
+
add bridge=bridge interface=ether7 hw=yes
set [ find default-name=ether11 ] master-port=ether1
+
add bridge=bridge interface=ether8 hw=yes
set [ find default-name=ether12 ] master-port=ether1
+
add bridge=bridge interface=ether9 hw=yes
set [ find default-name=ether13 ] master-port=ether1
+
add bridge=bridge interface=ether10 hw=yes
set [ find default-name=ether14 ] master-port=ether1
+
add bridge=bridge interface=ether11 hw=yes
set [ find default-name=ether15 ] master-port=ether1
+
add bridge=bridge interface=ether12 hw=yes
set [ find default-name=ether16 ] master-port=ether1
+
add bridge=bridge interface=ether13 hw=yes
set [ find default-name=ether17 ] master-port=ether1
+
add bridge=bridge interface=ether14 hw=yes
set [ find default-name=ether18 ] master-port=ether1
+
add bridge=bridge interface=ether15 hw=yes
set [ find default-name=ether19 ] master-port=ether1
+
add bridge=bridge interface=ether16 hw=yes
set [ find default-name=ether20 ] master-port=ether1
+
add bridge=bridge interface=ether17 hw=yes
set [ find default-name=ether21 ] master-port=ether1
+
add bridge=bridge interface=ether18 hw=yes
set [ find default-name=ether22 ] master-port=ether1
+
add bridge=bridge interface=ether19 hw=yes
set [ find default-name=ether23 ] master-port=ether1
+
add bridge=bridge interface=ether20 hw=yes
set [ find default-name=ether24 ] master-port=ether1
+
add bridge=bridge interface=ether21 hw=yes
 +
add bridge=bridge interface=ether22 hw=yes
 +
add bridge=bridge interface=ether23 hw=yes
 +
add bridge=bridge interface=ether24 hw=yes
 +
add bridge=bridge interface=sfp1 hw=yes
 
</pre>
 
</pre>
 +
 +
{{ Warning | Bridge (R)STP is not aware of underlying switch trunking configuration and some trunk ports can move to discarding or blocking state. When trunking member ports are connected to other bridges, you should either disable the (R)STP or filter out any BPDU between trunked devices (e.g. with [[Manual:CRS1xx/2xx_series_switches#Access_Control_List | ACL rules]]).}}
  
 
Disable SFP interface for security reasons (in case it is not being used):
 
Disable SFP interface for security reasons (in case it is not being used):
Line 51: Line 57:
 
</pre>
 
</pre>
  
 
+
=Port trunking=
===Port trunking===
 
  
 
Port trunking is used when a larger amount of bandwidth is required, this is done by creating a static link aggregation group, which also provides hardware automatic failover and load balancing for CRS1xx/CRS2xx series switches. By adding two 1Gbps interfaces to a trunk, you can increase the theoretical bandwidth limit to 2Gbps. Make sure that all trunked interfaces are linked to the same speed rates.
 
Port trunking is used when a larger amount of bandwidth is required, this is done by creating a static link aggregation group, which also provides hardware automatic failover and load balancing for CRS1xx/CRS2xx series switches. By adding two 1Gbps interfaces to a trunk, you can increase the theoretical bandwidth limit to 2Gbps. Make sure that all trunked interfaces are linked to the same speed rates.
Line 77: Line 82:
 
</pre>
 
</pre>
  
===Management IP===
+
=Management IP=
  
 
It is very useful to create a management interface and assign an IP address to it in order to preserve access to the switch. This is also very useful when updating your switches since such traffic to the switch will be blocked when enabling invalid VLAN filtering.
 
It is very useful to create a management interface and assign an IP address to it in order to preserve access to the switch. This is also very useful when updating your switches since such traffic to the switch will be blocked when enabling invalid VLAN filtering.
Line 84: Line 89:
 
<pre>
 
<pre>
 
/interface vlan
 
/interface vlan
add interface=ether1 name=Vlan99 vlan-id=99
+
add interface=bridge1 name=VLAN99 vlan-id=99
 
</pre>
 
</pre>
 
{{Note | VLAN interface must be created on the master-port interface since it is the only interface that will be able to communicate the CPU.}}
 
  
 
For this guide we are going to use these addresses for each device:
 
For this guide we are going to use these addresses for each device:
Line 110: Line 113:
 
<pre>
 
<pre>
 
/ip address
 
/ip address
add address=192.168.99.X/24 interface=Vlan99
+
add address=192.168.99.X/24 interface=VLAN99
 
</pre>
 
</pre>
  
Line 124: Line 127:
 
<pre>
 
<pre>
 
/ip address
 
/ip address
add address=192.168.99.1/24 interface=Vlan99
+
add address=192.168.99.1/24 interface=VLAN99
 
</pre>
 
</pre>
  
===Bonding===
+
=Bonding=
  
 
Unlike CRS1xx/CRS2xx series switches that use the built-in Switch Chip to create a aggregated link group, a router will use the CPU to create the aggregated link group.
 
Unlike CRS1xx/CRS2xx series switches that use the built-in Switch Chip to create a aggregated link group, a router will use the CPU to create the aggregated link group.
Line 138: Line 141:
 
</pre>
 
</pre>
  
{{Warning | Don't use bonding interfaces on CRS series devices, bonding interface does NOT use the built-in Switch Chip to create aggregated link group and will overload the CPU instantly. For CRS series device use only port trunking.}}
+
{{Warning | Don't use bonding interfaces on CRS1xx/CRS2xx series devices, bonding interface does NOT use the built-in Switch Chip to create aggregated link group and will overload the CPU instantly. For CRS series device use only port trunking.}}
  
Now add a VLAN interface can be created on the newly created bonding interface for management and assign an IP address to it, use these commands on the '''Router''':
+
Now a VLAN interface can be created on the newly created bonding interface for management and assign an IP address to it, use these commands on the '''Router''':
 
<pre>
 
<pre>
 
/interface vlan
 
/interface vlan
add interface=bond1 name=Vlan99 vlan-id=99
+
add interface=bond1 name=VLAN99 vlan-id=99
 
/ip address
 
/ip address
add address=192.168.99.1/24 interface=Vlan99
+
add address=192.168.99.1/24 interface=VLAN99
 
</pre>
 
</pre>
  
===Port based VLAN===
+
=Port based VLAN=
  
 
When using port trunks, the main difference is that access ports are now trunk ports and they should be used in the Egress VLAN tag table, Ingress VLAN translation table and VLAN table instead of physical Ethernet interfaces.
 
When using port trunks, the main difference is that access ports are now trunk ports and they should be used in the Egress VLAN tag table, Ingress VLAN translation table and VLAN table instead of physical Ethernet interfaces.
Line 212: Line 215:
 
{{Note | It is required to specify <code>switch1-cpu</code> port in the VLAN table in order to allow access the the previously created VLAN interface for management purposes.}}
 
{{Note | It is required to specify <code>switch1-cpu</code> port in the VLAN table in order to allow access the the previously created VLAN interface for management purposes.}}
  
===Invalid VLAN filtering===
+
=Invalid VLAN filtering=
  
 
If ingress VLAN translation table, egress VLAN tag table and VLAN table is properly set, invalid VLAN filtering can be enabled, which will drop any other packet that does not a suitable entry in the VLAN table.
 
If ingress VLAN translation table, egress VLAN tag table and VLAN table is properly set, invalid VLAN filtering can be enabled, which will drop any other packet that does not a suitable entry in the VLAN table.
  
{{Warning | Double check if port based VLAN is set up properly. If a mistake was made, you might loose access to the switch and can only be regained by resetting configuration or using the serial console.}}
+
{{Warning | Double check if port based VLANs are set up properly. If a mistake was made, you might loose access to the switch and it can only be regained by resetting theconfiguration or by using the serial console.}}
  
 
To enable invalid VLAN filtering, use these commands on '''SwitchA''', '''SwitchB''', '''SwitchC''':
 
To enable invalid VLAN filtering, use these commands on '''SwitchA''', '''SwitchB''', '''SwitchC''':
Line 226: Line 229:
 
</pre>
 
</pre>
  
===InterVLAN routing===
+
=InterVLAN routing=
  
 
To create InterVLAN routing, VLAN interface for each customer VLAN ID must be created on the router and must have an IP address assigned to it. The VLAN interface must be created on the bonding interface created previously.
 
To create InterVLAN routing, VLAN interface for each customer VLAN ID must be created on the router and must have an IP address assigned to it. The VLAN interface must be created on the bonding interface created previously.
Line 233: Line 236:
 
<pre>
 
<pre>
 
/interface vlan
 
/interface vlan
add interface=bond1 name=Vlan10 vlan-id=10
+
add interface=bond1 name=VLAN10 vlan-id=10
add interface=bond1 name=Vlan20 vlan-id=20
+
add interface=bond1 name=VLAN20 vlan-id=20
add interface=bond1 name=Vlan30 vlan-id=30
+
add interface=bond1 name=VLAN30 vlan-id=30
add interface=bond1 name=Vlan40 vlan-id=40
+
add interface=bond1 name=VLAN40 vlan-id=40
 
/ip address
 
/ip address
add address=192.168.10.1/24 interface=Vlan10
+
add address=192.168.10.1/24 interface=VLAN10
add address=192.168.20.1/24 interface=Vlan20
+
add address=192.168.20.1/24 interface=VLAN20
add address=192.168.30.1/24 interface=Vlan30
+
add address=192.168.30.1/24 interface=VLAN30
add address=192.168.40.1/24 interface=Vlan40
+
add address=192.168.40.1/24 interface=VLAN40
 
</pre>
 
</pre>
  
 
{{Note | These commands are required for DHCP-Server. In case interVLAN routing is not desired but a DHCP-Server on a single router is required, then use [[Manual:IP/Firewall/Filter| Firewall Filter]] to block access between different subnets.}}
 
{{Note | These commands are required for DHCP-Server. In case interVLAN routing is not desired but a DHCP-Server on a single router is required, then use [[Manual:IP/Firewall/Filter| Firewall Filter]] to block access between different subnets.}}
  
===DHCP-Server===
+
=DHCP-Server=
  
 
To get the DHCP-Server working for each VLAN ID, the server must be set up on the previously created VLAN interfaces (one server for each VLAN ID). Preferably each VLAN ID should have its own subnet and its own IP pool. DNS Server could be specified as the router's IP address for particular VLAN ID or a global DNS Server could be used, but this address must be reachable.
 
To get the DHCP-Server working for each VLAN ID, the server must be set up on the previously created VLAN interfaces (one server for each VLAN ID). Preferably each VLAN ID should have its own subnet and its own IP pool. DNS Server could be specified as the router's IP address for particular VLAN ID or a global DNS Server could be used, but this address must be reachable.
Line 253: Line 256:
 
<pre>
 
<pre>
 
/ip pool
 
/ip pool
add name=Vlan10_pool ranges=192.168.10.100-192.168.10.200
+
add name=VLAN10_pool ranges=192.168.10.100-192.168.10.200
add name=Vlan20_pool ranges=192.168.20.100-192.168.20.200
+
add name=VLAN20_pool ranges=192.168.20.100-192.168.20.200
add name=Vlan30_pool ranges=192.168.30.100-192.168.30.200
+
add name=VLAN30_pool ranges=192.168.30.100-192.168.30.200
add name=Vlan40_pool ranges=192.168.40.100-192.168.40.200
+
add name=VLAN40_pool ranges=192.168.40.100-192.168.40.200
 
/ip dhcp-server
 
/ip dhcp-server
add address-pool=Vlan10_pool disabled=no interface=Vlan10 name=Vlan10_DHCP
+
add address-pool=VLAN10_pool disabled=no interface=VLAN10 name=Vlan10_DHCP
add address-pool=Vlan20_pool disabled=no interface=Vlan20 name=Vlan20_DHCP
+
add address-pool=VLAN20_pool disabled=no interface=VLAN20 name=Vlan20_DHCP
add address-pool=Vlan30_pool disabled=no interface=Vlan30 name=Vlan30_DHCP
+
add address-pool=VLAN30_pool disabled=no interface=VLAN30 name=Vlan30_DHCP
add address-pool=Vlan40_pool disabled=no interface=Vlan40 name=Vlan40_DHCP
+
add address-pool=VLAN40_pool disabled=no interface=VLAN40 name=Vlan40_DHCP
 
/ip dhcp-server network
 
/ip dhcp-server network
 
add address=192.168.10.0/24 dns-server=192.168.10.1 gateway=192.168.10.1
 
add address=192.168.10.0/24 dns-server=192.168.10.1 gateway=192.168.10.1
Line 283: Line 286:
 
</pre>
 
</pre>
  
===Jumbo frames===
+
=Jumbo frames=
  
 
One can increase the total throughput in such a setup by enabling jumbo frames. This reduces the packet overhead by increasing the Maximum Transmission Unit (MTU). If a device in your network does not support jumbo frames, then it will not benefit from a larger MTU. Usually the whole network does not support jumbo frames, but you can still benefit when sending data between devices that support jumbo frames, including all switches in the path.
 
One can increase the total throughput in such a setup by enabling jumbo frames. This reduces the packet overhead by increasing the Maximum Transmission Unit (MTU). If a device in your network does not support jumbo frames, then it will not benefit from a larger MTU. Usually the whole network does not support jumbo frames, but you can still benefit when sending data between devices that support jumbo frames, including all switches in the path.
Line 289: Line 292:
 
In this case, if clients behind SwitchA and client behind SwitchC supports jumbo frames, then enabling jumbo frames will be beneficial. Before enabling jumbo frames, determine the MAX-L2MTU by using this command:
 
In this case, if clients behind SwitchA and client behind SwitchC supports jumbo frames, then enabling jumbo frames will be beneficial. Before enabling jumbo frames, determine the MAX-L2MTU by using this command:
 
<pre>
 
<pre>
[admin@MikroTik] /interface> print  
+
[admin@MikroTik] > /interface> print  
 
Flags: D - dynamic, X - disabled, R - running, S - slave  
 
Flags: D - dynamic, X - disabled, R - running, S - slave  
 
  #    NAME                                TYPE      ACTUAL-MTU L2MTU  MAX-L2MTU       
 
  #    NAME                                TYPE      ACTUAL-MTU L2MTU  MAX-L2MTU       
Line 297: Line 300:
 
{{Note | More information can be found in [[Manual:Maximum_Transmission_Unit_on_RouterBoards| MTU manual]] page.}}
 
{{Note | More information can be found in [[Manual:Maximum_Transmission_Unit_on_RouterBoards| MTU manual]] page.}}
  
When MAX-L2MTU is determined, use this command on '''SwitchA''', '''SwitchB''' and '''SwitchC''':
+
When MAX-L2MTU is determined, choose the MTU size depending on the traffic on your network, use this command on '''SwitchA''', '''SwitchB''' and '''SwitchC''':
 
<pre>
 
<pre>
 
/interface ethernet
 
/interface ethernet
Line 304: Line 307:
  
 
{{Note | Don't forget to change the MTU on your client devices too, otherwise above mentioned settings will not have any effect.}}
 
{{Note | Don't forget to change the MTU on your client devices too, otherwise above mentioned settings will not have any effect.}}
 +
 +
=See also=
 +
 +
* [[M:Interface/Bonding | Bonding]]
 +
* [[M:CRS_examples | CRS examples]]
 +
* [[M:CRS_features | CRS features]]
 +
* [[M:Switch_Chip_Features | Switch Chip Features]]
 +
* [[M:IP/DNS | IP/DNS]]
 +
* [[M:IP/Firewall/NAT#Basic_examples | NAT examples]]
 +
* [[M:IP/Firewall/Filter#Basic_examples | Firewall filter examples]]
 +
* [[M:Interface/VLAN | VLAN]]
 +
* [[M:Maximum_Transmission_Unit_on_RouterBoards | MTU on RouterBOARD]]
 +
 +
{{cont}}
 +
 +
[[Category:Bridging and switching]]
 +
[[Category:Examples]]

Latest revision as of 09:53, 31 July 2019

Version.png

Applies to RouterOS: v6.32 +


Summary

This page will show how to configure multiple switches to use port trunking and port based VLANs, it will also show a working example with a DHCP-Server, interVLAN routing, management IP and invalid VLAN filtering configuration.

Icon-warn.png

Warning: This article applies to CRS1xx and CRS2xx series switches and not to CRS3xx series switches. For a similar setup for CRS3xx series switches you can check the CRS3xx VLANs with Bonds guide.


Alt text
CRS1xx/CRS2xx port trunking with port based VLANs
Icon-note.png

Note: Configuration is written for CRS125-24G-1S and CRS226-24G-2S+, but will work on other CRS1xx/CRS2xx series switches as well.


In this setup SwitchA and SwitchC will tag all traffic from ports ether3-ether6 to VLAN ID 10, ether7-ether12 to VLAN ID 20, ether13-ether18 to VLAN ID 30, ether19-ether24 to VLAN ID 40. SwitchB will tag all traffic from ports ether9-ether12 to VLAN ID 10, ether13-ether16 to VLAN ID 20, ether17-ether20 to VLAN ID 30, ether21-ether24 to VLAN ID 40. Management will only be possible if user is connecting with tagged traffic with VLAN ID 99. SFP port is not used in this setup at all, consider disabling it if not being used.

Port switching

All switches in this setup require that all used ports are switched together. Use these commands on SwitchA, SwitchB, SwitchC:

/interface bridge
add name=bridge protocol-mode=none
/interface bridge port
add bridge=bridge interface=ether1 hw=yes
add bridge=bridge interface=ether2 hw=yes
add bridge=bridge interface=ether3 hw=yes
add bridge=bridge interface=ether4 hw=yes
add bridge=bridge interface=ether5 hw=yes
add bridge=bridge interface=ether6 hw=yes
add bridge=bridge interface=ether7 hw=yes
add bridge=bridge interface=ether8 hw=yes
add bridge=bridge interface=ether9 hw=yes
add bridge=bridge interface=ether10 hw=yes
add bridge=bridge interface=ether11 hw=yes
add bridge=bridge interface=ether12 hw=yes
add bridge=bridge interface=ether13 hw=yes
add bridge=bridge interface=ether14 hw=yes
add bridge=bridge interface=ether15 hw=yes
add bridge=bridge interface=ether16 hw=yes
add bridge=bridge interface=ether17 hw=yes
add bridge=bridge interface=ether18 hw=yes
add bridge=bridge interface=ether19 hw=yes
add bridge=bridge interface=ether20 hw=yes
add bridge=bridge interface=ether21 hw=yes
add bridge=bridge interface=ether22 hw=yes
add bridge=bridge interface=ether23 hw=yes
add bridge=bridge interface=ether24 hw=yes
add bridge=bridge interface=sfp1 hw=yes
Icon-warn.png

Warning: Bridge (R)STP is not aware of underlying switch trunking configuration and some trunk ports can move to discarding or blocking state. When trunking member ports are connected to other bridges, you should either disable the (R)STP or filter out any BPDU between trunked devices (e.g. with ACL rules).


Disable SFP interface for security reasons (in case it is not being used):

/interface ethernet set [find where name~"sfp"] disabled=yes

Port trunking

Port trunking is used when a larger amount of bandwidth is required, this is done by creating a static link aggregation group, which also provides hardware automatic failover and load balancing for CRS1xx/CRS2xx series switches. By adding two 1Gbps interfaces to a trunk, you can increase the theoretical bandwidth limit to 2Gbps. Make sure that all trunked interfaces are linked to the same speed rates.

Icon-note.png

Note: CRS1xx/CRS2xx series switches aggregate traffic using the built-in Switch Chip without using CPU resources, to route the traffic a router with a powerful CPU is required to handle the aggregated traffic.


To create a 2Gbps port trunk from ether1 and ether2 between SwitchA, SwitchB and SwitchC, use these commands on SwitchA and SwitchC:

/interface ethernet switch trunk
add member-ports=ether1,ether2 name=trunk-1-2

To create a 4Gbps port trunk from ether1,ether2,ether3,ether4 between SWitchB and the Router, use these commands on SwitchB:

/interface ethernet switch trunk
add member-ports=ether1,ether2,ether3,ether4 name=trunk-1-2-3-4

On SwitchB ether5 and ether6 will be used to connect with SwitchA at 2Gbps and ether7,ether8 will be used to connect with SwitchC at 2Gbps. Use these command on SwitchB:

/interface ethernet switch trunk
add member-ports=ether5,ether6 name=trunk-5-6
add member-ports=ether7,ether8 name=trunk-7-8

Management IP

It is very useful to create a management interface and assign an IP address to it in order to preserve access to the switch. This is also very useful when updating your switches since such traffic to the switch will be blocked when enabling invalid VLAN filtering.

Create a VLAN interface on SwitchA, SwitchB, SwitchC:

/interface vlan
add interface=bridge1 name=VLAN99 vlan-id=99

For this guide we are going to use these addresses for each device:

Address Device
192.168.99.1 Router
192.168.99.2 SwitchA
192.168.99.3 SwitchB
192.168.99.4 SwitchC

Add an IP address for each device on the VLAN interface (change X to appropriate number):

/ip address
add address=192.168.99.X/24 interface=VLAN99

Don't forget to add the default gateway and specify a DNS server:

/ip route
add gateway=192.168.99.1
/ip dns
set servers=192.168.99.1

Add the IP address on the Router:

/ip address
add address=192.168.99.1/24 interface=VLAN99

Bonding

Unlike CRS1xx/CRS2xx series switches that use the built-in Switch Chip to create a aggregated link group, a router will use the CPU to create the aggregated link group.

To create a bonding interface for ether1,ether2,ether3,ether4, use these commands on the Router:

/interface bonding
add mode=balance-xor name=bond1 slaves=ether1,ether2,ether3,ether4\
transmit-hash-policy=layer-2-and-3
Icon-warn.png

Warning: Don't use bonding interfaces on CRS1xx/CRS2xx series devices, bonding interface does NOT use the built-in Switch Chip to create aggregated link group and will overload the CPU instantly. For CRS series device use only port trunking.


Now a VLAN interface can be created on the newly created bonding interface for management and assign an IP address to it, use these commands on the Router:

/interface vlan
add interface=bond1 name=VLAN99 vlan-id=99
/ip address
add address=192.168.99.1/24 interface=VLAN99

Port based VLAN

When using port trunks, the main difference is that access ports are now trunk ports and they should be used in the Egress VLAN tag table, Ingress VLAN translation table and VLAN table instead of physical Ethernet interfaces.

To create each trunk port as access port, use these commands on SwitchA and SwitchC:

/interface ethernet switch egress-vlan-tag
add tagged-ports=trunk-1-2 vlan-id=10
add tagged-ports=trunk-1-2 vlan-id=20
add tagged-ports=trunk-1-2 vlan-id=30
add tagged-ports=trunk-1-2 vlan-id=40

Similarly add entries to the Egress VLAN tag table for SwitchB, use these commands on SwitchB:

/interface ethernet switch egress-vlan-tag
add tagged-ports=trunk-1-2-3-4,trunk-5-6,trunk-7-8 vlan-id=10
add tagged-ports=trunk-1-2-3-4,trunk-5-6,trunk-7-8 vlan-id=20
add tagged-ports=trunk-1-2-3-4,trunk-5-6,trunk-7-8 vlan-id=30
add tagged-ports=trunk-1-2-3-4,trunk-5-6,trunk-7-8 vlan-id=40
Icon-note.png

Note: Management VLAN ID is not addedd to Egress VLAN tag table since a VLAN interface has been already created that will only send out tagged traffic either way.


Specify for each Ethernet interface a VLAN ID that will be assigned for a device that uses the port, use these commands for SwitchA and SwitchC:

/interface ethernet switch ingress-vlan-translation
add new-customer-vid=10 ports=ether3,ether4,ether5,ether6
add new-customer-vid=20 ports=ether7,ether8,ether9,ether10,ether11,ether12
add new-customer-vid=30 ports=ether13,ether14,ether15,ether16,ether17,ether18
add new-customer-vid=40 ports=ether19,ether20,ether21,ether22,ether23,ether24

Similarly specify a VLAN ID for each Ethernet interface on SwitchB, use these commands on SwitchB:

/interface ethernet switch ingress-vlan-translation
add new-customer-vid=10 ports=ether9,ether10,ether11,ether12
add new-customer-vid=20 ports=ether13,ether14,ether15,ether16
add new-customer-vid=30 ports=ether17,ether18,ether19,ether20
add new-customer-vid=40 ports=ether21,ether22,ether23,ether24

It is required add allowed VLAN IDs to the VLAN table in order for VLAN filtering to work properly. Specify each VLAN ID and each port that is allowed to forward a certain VLAN ID. Use trunk ports instead of physical Ethernet interfaces. Use these commands on SwitchA and SwitchC:

/interface ethernet switch vlan
add ports=trunk-1-2,ether3,ether4,ether5,ether6 vlan-id=10
add ports=trunk-1-2,ether7,ether8,ether9,ether10,ether11,ether12 vlan-id=20
add ports=trunk-1-2,ether13,ether14,ether15,ether16,ether17,ether18 vlan-id=30
add ports=trunk-1-2,ether19,ether20,ether21,ether22,ether23,ether24 vlan-id=40
add ports=trunk-1-2,switch1-cpu vlan-id=99

Similarly add entries to the VLAN table for SwitchB, use the commands on SwitchB:

/interface ethernet switch vlan
add ports=trunk-1-2-3-4,trunk-5-6,trunk-7-8,ether9,ether10,ether11,ether12 vlan-id=10
add ports=trunk-1-2-3-4,trunk-5-6,trunk-7-8,ether13,ether14,ether15,ether16 vlan-id=20
add ports=trunk-1-2-3-4,trunk-5-6,trunk-7-8,ether17,ether18,ether19,ether20 vlan-id=30
add ports=trunk-1-2-3-4,trunk-5-6,trunk-7-8,ether21,ether22,ether23,ether24 vlan-id=40
add ports=trunk-1-2-3-4,trunk-5-6,trunk-7-8,switch1-cpu vlan-id=99
Icon-note.png

Note: It is required to specify switch1-cpu port in the VLAN table in order to allow access the the previously created VLAN interface for management purposes.


Invalid VLAN filtering

If ingress VLAN translation table, egress VLAN tag table and VLAN table is properly set, invalid VLAN filtering can be enabled, which will drop any other packet that does not a suitable entry in the VLAN table.

Icon-warn.png

Warning: Double check if port based VLANs are set up properly. If a mistake was made, you might loose access to the switch and it can only be regained by resetting theconfiguration or by using the serial console.


To enable invalid VLAN filtering, use these commands on SwitchA, SwitchB, SwitchC:

/interface ethernet switch
set drop-if-invalid-or-src-port-not-member-of-vlan-on-ports="ether1,ether2,ether3,ether4\
,ether5,ether6,ether7,ether8,ether9,ether10,ether11,ether12,ether13\
,ether14,ether15,ether16,ether17,ether18,ether19,ether20,ether21,ether22,ether23,ether24"

InterVLAN routing

To create InterVLAN routing, VLAN interface for each customer VLAN ID must be created on the router and must have an IP address assigned to it. The VLAN interface must be created on the bonding interface created previously.

Use these commands on the Router:

/interface vlan
add interface=bond1 name=VLAN10 vlan-id=10
add interface=bond1 name=VLAN20 vlan-id=20
add interface=bond1 name=VLAN30 vlan-id=30
add interface=bond1 name=VLAN40 vlan-id=40
/ip address
add address=192.168.10.1/24 interface=VLAN10
add address=192.168.20.1/24 interface=VLAN20
add address=192.168.30.1/24 interface=VLAN30
add address=192.168.40.1/24 interface=VLAN40
Icon-note.png

Note: These commands are required for DHCP-Server. In case interVLAN routing is not desired but a DHCP-Server on a single router is required, then use Firewall Filter to block access between different subnets.


DHCP-Server

To get the DHCP-Server working for each VLAN ID, the server must be set up on the previously created VLAN interfaces (one server for each VLAN ID). Preferably each VLAN ID should have its own subnet and its own IP pool. DNS Server could be specified as the router's IP address for particular VLAN ID or a global DNS Server could be used, but this address must be reachable.

To set up the DHCP-Server, use these commands on the Router:

/ip pool
add name=VLAN10_pool ranges=192.168.10.100-192.168.10.200
add name=VLAN20_pool ranges=192.168.20.100-192.168.20.200
add name=VLAN30_pool ranges=192.168.30.100-192.168.30.200
add name=VLAN40_pool ranges=192.168.40.100-192.168.40.200
/ip dhcp-server
add address-pool=VLAN10_pool disabled=no interface=VLAN10 name=Vlan10_DHCP
add address-pool=VLAN20_pool disabled=no interface=VLAN20 name=Vlan20_DHCP
add address-pool=VLAN30_pool disabled=no interface=VLAN30 name=Vlan30_DHCP
add address-pool=VLAN40_pool disabled=no interface=VLAN40 name=Vlan40_DHCP
/ip dhcp-server network
add address=192.168.10.0/24 dns-server=192.168.10.1 gateway=192.168.10.1
add address=192.168.20.0/24 dns-server=192.168.20.1 gateway=192.168.20.1
add address=192.168.30.0/24 dns-server=192.168.30.1 gateway=192.168.30.1
add address=192.168.40.0/24 dns-server=192.168.40.1 gateway=192.168.40.1

In case the router's DNS Server is being used, don't forget to allow remote requests and make sure DNS Servers are configured on the router. Use these commands on the Router:

/ip dns
set allow-remote-requests=yes servers=8.8.8.8
Icon-warn.png

Warning: Make sure to secure your local DNS Server with Firewall from the outside when using allow-remote-requests set to yes since your DNS Server can be used for DDoS attacks if it is accessible from the Internet by anyone.


Don't forget to create NAT, assuming that sfp-sfpplus1 is used as WAN port, use these commands on the Router:

/ip firewall nat
add action=masquerade chain=srcnat out-interface=sfp-sfpplus1

Jumbo frames

One can increase the total throughput in such a setup by enabling jumbo frames. This reduces the packet overhead by increasing the Maximum Transmission Unit (MTU). If a device in your network does not support jumbo frames, then it will not benefit from a larger MTU. Usually the whole network does not support jumbo frames, but you can still benefit when sending data between devices that support jumbo frames, including all switches in the path.

In this case, if clients behind SwitchA and client behind SwitchC supports jumbo frames, then enabling jumbo frames will be beneficial. Before enabling jumbo frames, determine the MAX-L2MTU by using this command:

[admin@MikroTik] > /interface> print 
Flags: D - dynamic, X - disabled, R - running, S - slave 
 #     NAME                                TYPE       ACTUAL-MTU L2MTU  MAX-L2MTU      
 0  R  ether1                              ether            1500  1580       4064
Icon-note.png

Note: More information can be found in MTU manual page.


When MAX-L2MTU is determined, choose the MTU size depending on the traffic on your network, use this command on SwitchA, SwitchB and SwitchC:

/interface ethernet
set [ find ] l2mtu=4064 mtu=4040
Icon-note.png

Note: Don't forget to change the MTU on your client devices too, otherwise above mentioned settings will not have any effect.


See also

[ Top | Back to Content ]