Manual:Interface/VPLS: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
← Older edit
No edit summary
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Versions|v3, v4}}
{{Versions|v3, v4 +}}


<div class=manual>


<h2>Summary</h2>
==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>


<h2>General</h2>
==General==
<p><b>Sub-menu:</b> <code>/interface vpls</code></p>
<p id="shbox"><b>Sub-menu:</b> <code>/interface vpls</code></p>




List of all VPLS interfaces. This menu shows also dynamically created BGP based VPLS interfaces.
List of all VPLS interfaces. This menu shows also dynamically created BGP based VPLS interfaces.


<h3>Properties</h3>
===Properties===
 
 
{{Mr-arg-table-h
{{Mr-arg-table-h
|prop=Property
|prop=Property
Line 44: Line 44:
{{Mr-arg-table
{{Mr-arg-table
|arg=arp
|arg=arp
|type=<nowiki>disabled | enabled | proxy-arp | reply-only</nowiki>
|type=disabled {{!}} enabled {{!}} proxy-arp {{!}} reply-only
|default=enabled
|default=enabled
|desc=Address Resolution Protocol
|desc=Address Resolution Protocol
Line 51: Line 51:
{{Mr-arg-table
{{Mr-arg-table
|arg=cisco-style
|arg=cisco-style
|type=<nowiki>yes | no</nowiki>
|type=yes {{!}} no
|default=no
|default=no
|desc=Specifies whether to use cisco style VPLS.
|desc=Specifies whether to use cisco style VPLS.
Line 72: Line 72:
{{Mr-arg-table
{{Mr-arg-table
|arg=disable-running-check
|arg=disable-running-check
|type=<nowiki>yes | no</nowiki>
|type=yes {{!}} no
|default=no
|default=no
|desc=Specifies whether to detect if interface is running or not. If set to <b>no</b> interface will always have <code>running</code> flag.
|desc=Specifies whether to detect if interface is running or not. If set to <b>no</b> interface will always have <code>running</code> flag.
Line 79: Line 79:
{{Mr-arg-table
{{Mr-arg-table
|arg=disabled
|arg=disabled
|type=<nowiki>yes | no</nowiki>
|type=yes {{!}} no
|default=yes
|default=yes
|desc=Defines whether item is ignored or used. By default VPLS interface is disabled.
|desc=Defines whether item is ignored or used. By default VPLS interface is disabled.
Line 114: Line 114:
{{Mr-arg-table
{{Mr-arg-table
|arg=pw-type
|arg=pw-type
|type=<nowiki>raw-ethernet | tagged-ethernet</nowiki>
|type=raw-ethernet {{!}} tagged-ethernet
|default=raw-ethernet
|default=raw-ethernet
|desc=Pseudowire type.
|desc=Pseudowire type.
Line 127: Line 127:


{{Mr-arg-table
{{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>]].
}}
{{Mr-arg-table-end
|arg=vpls-id
|arg=vpls-id
|type=<nowiki>AsNum | AsIp</nowiki>
|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
}}
}}


</table>
===Monitoring===


<h3>Monitoring</h3>


<p>
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
</p>
 
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 148: Line 184:


{{Mr-arg-ro-table
{{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=
}}
}}
</table>


<h2>BGP VPLS</h2>
{{Mr-arg-ro-table
<p><b>Sub-menu:</b> <code>/interface vpls bgp-vpls</code></p>
|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.
}}
 
 
==BGP VPLS==
 
<p id="shbox"><b>Sub-menu:</b> <code>/interface vpls bgp-vpls</code></p>


List of BGP signaled VPLS instances. Configured instance makes router advertise VPLS BGP NLRI that advertises that particular router belongs to some VPLS.
List of BGP signaled VPLS instances. Configured instance makes router advertise VPLS BGP NLRI that advertises that particular router belongs to some VPLS.


<h3>Properties</h3>
===Properties===
 
 
{{Mr-arg-table-h
{{Mr-arg-table-h
|prop=Property
|prop=Property
Line 167: Line 242:
{{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 181: Line 256:
{{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 195: Line 270:
{{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 203: Line 278:
{{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 210: Line 285:
{{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 220: Line 295:
|default=
|default=
|desc=
|desc=
}}
{{Mr-arg-table
|arg=pw-mtu
|type=integer[32..65535]
|default=1500
|desc=Advertised pseudowire MTU value.
}}
{{Mr-arg-table
|arg=pw-type
|type=raw-ethernet {{!}} tagged-ethernet {{!}} vpls
|default=vpls
|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.
Line 236: Line 325:
}}
}}


</table>
{{Mr-arg-table-end
|arg=use-control-word
|type=yes {{!}} no
|default=yes
|desc=Enables/disables Control Word usage. [[Manual:VPLS_Control_Word | <code>Read more >></code>]]
}}
 
==Cisco Style BGP VPLS==
<p id="shbox"><b>Sub-menu:</b> <code>/interface cisco-bgp-vpls</code></p>
 
 
===Properties===


<h2>Cisco Style BGP VPLS</h2>
<p><b>Sub-menu:</b> <code>/interface cisco-bgp-vpls</code></p>


<h3>Properties</h3>
{{Mr-arg-table-h
{{Mr-arg-table-h
|prop=Property
|prop=Property
Line 249: 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 263: 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 277: 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 285: 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 292: 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 310: 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 320: 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 326: 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]]


<h2>See also</h2>
<ul class="bullets">
<li> [[M:MPLSVPLS|MPLSVPLS]]
<li> [[M:BGP_based_VPLS | BGP based VPLS]]
<li> [[M:Cisco_VPLS | Cisco style BGP based VPLS]]
</ul>
</div>




Line 340: Line 448:
{{Cont}}
{{Cont}}


[[Category:Manual]]
[[Category:Manual|V]]
[[Category:MPLS]]
[[Category:MPLS|V]]
[[Category:Internetworking]]
[[Category:Internetworking|V]]
[[Category:VPN]]
[[Category:VPN|V]]
[[Category:Interface|V]]

Latest revision as of 13:05, 13 May 2013

Applies to RouterOS: v3, v4 +


Summary

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:

  • LDP signaling (RFC 4762), see LDP based VPLS
  • pseudowire fragmentation and reassembly (RFC 4623)
  • MP-BGP based autodiscovery and signaling (RFC 4761), see BGP based VPLS

Since version 3.17:

  • Cisco style static VPLS pseudowires (RFC 4447 FEC type 0x80), see static Cisco VPLS
  • Cisco VPLS BGP-based auto-discovery (draft-ietf-l2vpn-signaling-08), see BGP based Cisco style VPLS
  • support for multiple import/export route target extended communities for BGP based VPLS (both, RFC 4761 and draft-ietf-l2vpn-signaling-08)


General

Sub-menu: /interface vpls


List of all VPLS interfaces. This menu shows also dynamically created BGP based VPLS interfaces.

Properties

Property Description
advertised-l2mtu (integer; Default: 1500) L2MTU value advertised to remote peer.
arp (disabled | enabled | proxy-arp | reply-only; Default: enabled) Address Resolution Protocol
cisco-style (yes | no; Default: no) Specifies whether to use cisco style VPLS.
cisco-style-id (integer; Default: 0) VPLS tunnel ID, used if cisco-style is set to yes.
comment (string; Default: ) Short description of the item
disable-running-check (yes | no; Default: no) Specifies whether to detect if interface is running or not. If set to no interface will always have running flag.
disabled (yes | no; Default: yes) Defines whether item is ignored or used. By default VPLS interface is disabled.
l2mtu (integer; Default: 1500)
mac-address (MAC; Default: )
mtu (integer; Default: 1500)
name (string; Default: ) Name of the interface
pw-type (raw-ethernet | tagged-ethernet; Default: raw-ethernet) Pseudowire type.
remote-peer (IP; Default: ) IP address of remote peer.
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.


Read-only properties

Property Description
cisco-bgp-signaled (yes | no)
vpls (string) name of the bgp-vpls instance used to create dynamic vpls interface

Monitoring

Command /interface vpls monitor [id] will display current VPLS interface status

For example: 

[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

Available read only properties:

Property Description
imposed-label (integer) VPLS imposed label
local-label (integer) Local VPLS label
remote-group ()
remote-label (integer) Remote VPLS label
remote-status (integer)
transport-nexthop (IP prefix) 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.
name (string; Default: )
pw-mtu (integer[32..65535]; Default: 1500) Advertised pseudowire MTU value.
pw-type (raw-ethernet | tagged-ethernet | vpls; Default: vpls) 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.
use-control-word (yes | no; Default: yes) Enables/disables Control Word usage. Read more >>

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: )
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.
use-control-word (yes | no; Default: yes) Enables/disables Control Word usage. Read more >>
vpls-id (integer; Default: ) Unique number that identifies VPLS tunnel.

See also



[ Top | Back to Content ]

Retrieved from "https://wiki.mikrotik.com/index.php?title=Manual:Interface/VPLS&oldid=25391"