Manual:Interface/VPLS: Difference between revisions
Line 140: | Line 140: | ||
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 157: | ||
}} | }} | ||
{{Mr-arg-ro-table- | {{Mr-arg-ro-table | ||
|arg= | |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 | |||
|arg=transport | |||
|type=string | |||
|desc=Name of the transport interface. Set if VPLS is running over Traffic Engineering tunnel. | |||
}} | }} | ||
Revision as of 14:00, 24 April 2012
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. |
vpls-id (AsNum | AsIp; Default: ) | Unique number that identifies VPLS tunnel. |
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:
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 |
---|---|
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. |
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. |
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 ]