(17 intermediate revisions by the same user not shown)
Line 1:
Line 1:
{{Versions|v3, v4 +}}
{{Versions|v3, v4 +}}
<div class=manual>
==Summary==
==Summary==
<p>
Virtual Private Lan Service (VPLS) interface can be considered tunnel interface just like [[M:Interface/EoIP | EoIP]] interface. To achieve transparent ethernet segment forwarding between customer sites.
Virtual Private Lan Service (VPLS) interface can be considered tunnel interface just like [[M:Interface/EoIP | EoIP]] interface. To achieve transparent ethernet segment forwarding between customer sites.
</p>
<p>
MikroTik RouterOS implements following VPLS features:
MikroTik RouterOS implements following VPLS features:
<ul class="bullets">
<ul class="bullets">
Line 21:
Line 20:
</ul>
</ul>
</p>
==General==
==General==
Line 126:
Line 124:
|default=
|default=
|desc=IP address of remote peer.
|desc=IP address of remote peer.
}}
{{Mr-arg-table
|arg=use-control-word
|type=yes {{!}} no {{!}} default
|default=default
|desc=Enables/disables Control Word usage.
Default values for regular and cisco style VPLS tunnels differ. Cisco style by default has control word usage disabled. [[Manual:VPLS_Control_Word | <code>Read more >></code>]].
}}
}}
Line 132:
Line 138:
|type=AsNum {{!}} AsIp
|type=AsNum {{!}} AsIp
|default=
|default=
|desc=Unique number that identifies VPLS tunnel.
|desc=Unique number that identifies VPLS tunnel. Encoding is 2byte+4byte or 4byte+2byte number.
}}
'''Read-only properties'''
{{Mr-arg-table-h
|prop=Property
|desc=Description
}}
{{Mr-arg-ro-table
|arg=cisco-bgp-signaled
|type=yes {{!}} no
|desc=
}}
{{Mr-arg-ro-table-end
|arg=vpls
|type=string
|desc=name of the [[#BGP_VPLS | bgp-vpls instance]] used to create dynamic vpls interface
}}
}}
Line 140:
Line 166:
Command <code>/interface vpls monitor [id]</code> will display current VPLS interface status
Command <code>/interface vpls monitor [id]</code> will display current VPLS interface status
For example:
<pre>
[admin@10.0.11.23] /interface vpls> monitor vpls2
remote-label: 800000
local-label: 43
remote-status:
transport: 10.255.11.201/32
transport-nexthop: 10.0.11.201
imposed-labels: 800000
</pre>
Available read only properties:
Available read only properties:
Line 147:
Line 183:
}}
}}
{{Mr-arg-ro-table-end
{{Mr-arg-ro-table
|arg=mm
|arg=imposed-label
|type=integer
|desc=VPLS imposed label
}}
{{Mr-arg-ro-table
|arg=local-label
|type=integer
|desc=Local VPLS label
}}
{{Mr-arg-ro-table
|arg=remote-group
|type=
|type=
|desc=
|desc=
}}
}}
{{Mr-arg-ro-table
|arg=remote-label
|type=integer
|desc=Remote VPLS label
}}
{{Mr-arg-ro-table
|arg=remote-status
|type=integer
|desc=
}}
{{Mr-arg-ro-table
|arg=transport-nexthop
|type=IP prefix
|desc=Shows used transport address (typically Loopback address).
}}
{{Mr-arg-ro-table-end
|arg=transport
|type=string
|desc=Name of the transport interface. Set if VPLS is running over Traffic Engineering tunnel.
|desc=Parameter is available starting from v5.16. It allows to choose advertised encapsulation in NLRI used only for comparison. It does not affect functionality of the tunnel. [[M:MPLS_L2VPN_vs_Juniper | <code>See pw-type usage example >></code>]]
}}
}}
{{Mr-arg-table
{{Mr-arg-table
|arg=route-distinguisher
|arg=route-distinguisher
|type=<nowiki>AsNum | AsIp</nowiki>
|type=AsNum {{!}} AsIp
|default=
|default=
|desc=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.
|desc=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.
}}
}}
{{Mr-arg-table-end
{{Mr-arg-table
|arg=site-id
|arg=site-id
|type=integer
|type=integer
Line 246:
Line 329:
|type=yes {{!}} no
|type=yes {{!}} no
|default=yes
|default=yes
|desc=
|desc=Enables/disables Control Word usage. [[Manual:VPLS_Control_Word | <code>Read more >></code>]]
}}
}}
Line 254:
Line 337:
===Properties===
===Properties===
{{Mr-arg-table-h
{{Mr-arg-table-h
|prop=Property
|prop=Property
Line 261:
Line 346:
{{Mr-arg-table
{{Mr-arg-table
|arg=bridge
|arg=bridge
|type=<nowiki>none | string</nowiki>
|type=none {{!}} string
|default=none
|default=none
|desc=If set to <b>none</b> VPLS interface is not added to [[M:Interface/Bridge | bridge]] ports.
|desc=If set to <b>none</b> VPLS interface is not added to [[M:Interface/Bridge | bridge]] ports.
Line 275:
Line 360:
{{Mr-arg-table
{{Mr-arg-table
|arg=bridge-horizon
|arg=bridge-horizon
|type=<nowiki>none | integer</nowiki>
|type=none {{!}} integer
|default=none
|default=none
|desc=If set to <b>none</b> bridge horizon will not be used.
|desc=If set to <b>none</b> bridge horizon will not be used.
Line 289:
Line 374:
{{Mr-arg-table
{{Mr-arg-table
|arg=disabled
|arg=disabled
|type=<nowiki>yes | no</nowiki>
|type=yes {{!}} no
|default=no
|default=no
|desc=Defines whether item is ignored or used.
|desc=Defines whether item is ignored or used.
Line 297:
Line 382:
{{Mr-arg-table
{{Mr-arg-table
|arg=export-route-target
|arg=export-route-target
|type=<nowiki>AsNum | AsIp</nowiki>
|type=AsNum {{!}} AsIp
|default=
|default=
|desc=Setting is used to tag BGP NLRI with one or more route targets.
|desc=Setting is used to tag BGP NLRI with one or more route targets.
Line 304:
Line 389:
{{Mr-arg-table
{{Mr-arg-table
|arg=import-route-target
|arg=import-route-target
|type=<nowiki>AsNum | AsIp</nowiki>
|type=AsNum {{!}} AsIp
|default=
|default=
|desc=Setting is used to determine if BGP NLRI is related to particular VPLS, by comparing route targets received from BGP NLRI.
|desc=Setting is used to determine if BGP NLRI is related to particular VPLS, by comparing route targets received from BGP NLRI.
Line 322:
Line 407:
|default=
|default=
|desc=
|desc=
}}
{{Mr-arg-table
|arg=pw-mtu
|type=integer[32..65535]
|default=1500
|desc=Advertised pseudo-wire MTU.
}}
}}
{{Mr-arg-table
{{Mr-arg-table
|arg=route-distinguisher
|arg=route-distinguisher
|type=<nowiki>AsNum | AsIp</nowiki>
|type=AsNum {{!}} AsIp
|default=
|default=
|desc=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.
|desc=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.
Line 332:
Line 424:
{{Mr-arg-table
{{Mr-arg-table
|arg=use-control-word
|type=yes {{!}} no
|default=yes
|desc=Enables/disables Control Word usage. [[Manual:VPLS_Control_Word | <code>Read more >></code>]]
}}
{{Mr-arg-table-end
|arg=vpls-id
|arg=vpls-id
|type=integer
|type=integer
Line 338:
Line 437:
}}
}}
</table>
==See also==
* [[M:MPLSVPLS|MPLSVPLS]]
* [[M:BGP_based_VPLS | BGP based VPLS]]
* [[M:Cisco_VPLS | Cisco style BGP based VPLS]]
* [[M:MPLS_L2VPN_vs_Juniper | L2VPN vs Juniper]]
==See also==
<ul class="bullets">
<li> [[M:MPLSVPLS|MPLSVPLS]]
<li> [[M:BGP_based_VPLS | BGP based VPLS]]
<li> [[M:Cisco_VPLS | Cisco style BGP based VPLS]]
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:
use-control-word (yes | no | default; Default: default)
Enables/disables Control Word usage.
Default values for regular and cisco style VPLS tunnels differ. Cisco style by default has control word usage disabled. Read more >>.
vpls-id (AsNum | AsIp; Default: )
Unique number that identifies VPLS tunnel. Encoding is 2byte+4byte or 4byte+2byte number.
Shows used transport address (typically Loopback address).
transport (string)
Name of the transport interface. Set if VPLS is running over Traffic Engineering tunnel.
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.
Parameter is available starting from v5.16. It allows to choose advertised encapsulation in NLRI used only for comparison. It does not affect functionality of the tunnel. See pw-type usage example >>
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.
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: )
pw-mtu (integer[32..65535]; Default: 1500)
Advertised pseudo-wire MTU.
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.
