Virtual Private Lan Service (VPLS) interface can be considered tunnel interface just like EoIP interface. To achieve transparent ethernet segment forwarding between customer sites.
MikroTik RouterOS implements following VPLS features:
Command /interface vpls monitor [id] will display current VPLS interface status
Available read only properties:
Property
Description
mm ()
BGP VPLS
Sub-menu:/interface vpls bgp-vpls
List of BGP signaled VPLS instances. Configured instance makes router advertise VPLS BGP NLRI that advertises that particular router belongs to some VPLS.
Properties
Property
Description
bridge (none | string; Default: none)
If set to none VPLS interface is not added to bridge ports.
bridge-cost (integer; Default: 50)
bridge-horizon (none | integer; Default: none)
If set to none bridge horizon will not be used.
comment (string; Default: )
Short description of the item
disabled (yes | no; Default: no)
Defines whether item is ignored or used.
export-route-target (AsNum | AsIp; Default: )
Setting is used to tag BGP NLRI with one or more route targets.
import-route-target (AsNum | AsIp; Default: )
Setting is used to determine if BGP NLRI is related to particular VPLS, by comparing route targets received from BGP NLRI.
name (string; Default: )
pw-mtu (integer[32..65535]; Default: 1500)
Advertised pseudowire MTU value.
route-distinguisher (AsNum | AsIp; Default: )
Specifies value that gets attached to VPLS NLRI so that receiving routers can distinguish advertisements that may otherwise look the same. This implies that unique route-distinguisher for every VPLS must be used. It is not necessary to use the same route distinguisher for some VPLS on all routers forming that VPLS as distinguisher is not used for determining if some BGP NLRI is related to particular VPLS (Route Target attribute is used for this), but it is mandatory to have different distinguishers for different VPLSes.
site-id (integer; Default: 1)
Unique site identifier. Each site must have unique site-id.
use-control-word (yes | no; Default: yes)
Cisco Style BGP VPLS
Sub-menu:/interface cisco-bgp-vpls
Properties
Property
Description
bridge (none | string; Default: none)
If set to none VPLS interface is not added to bridge ports.
bridge-cost (integer; Default: 50)
bridge-horizon (none | integer; Default: none)
If set to none bridge horizon will not be used.
comment (string; Default: )
Short description of the item
disabled (yes | no; Default: no)
Defines whether item is ignored or used.
export-route-target (AsNum | AsIp; Default: )
Setting is used to tag BGP NLRI with one or more route targets.
import-route-target (AsNum | AsIp; Default: )
Setting is used to determine if BGP NLRI is related to particular VPLS, by comparing route targets received from BGP NLRI.
l2router-id (IP; Default: 0.0.0.0)
name (string; Default: )
route-distinguisher (AsNum | AsIp; Default: )
Specifies value that gets attached to VPLS NLRI so that receiving routers can distinguish advertisements that may otherwise look the same. This implies that unique route-distinguisher for every VPLS must be used. It is not necessary to use the same route distinguisher for some VPLS on all routers forming that VPLS as distinguisher is not used for determining if some BGP NLRI is related to particular VPLS (Route Target attribute is used for this), but it is mandatory to have different distinguishers for different VPLSes.
