...
| Property | Description |
|---|---|
| bridge (name) | Name of the bridge where dynamically created VPLS interfaces should be added as ports. |
| bridge-cost (integer [0..4294967295]) | |
| bridge-horizon (none | integer [0..4294967295]) | If set to none bridge horizon will not be used. |
| cisco-id () | Unique identifier. A A parameter must be set for cisco-style VPLS signaling. In most cases this should not be used, any modern software supports RFC 4761 style signaling (see site-id parameter). Parameter is a merge of l2-router-id and RD, for example: 10.155.155.1&6550:123 |
| comment (string) | Short description of the item. |
| disabled (yes | no) | Defines whether an item is ignored or used. |
| export-route-target (list of RTs) | The setting is used to tag BGP NLRI with one or more route targets which on the remote side is used by import-route-targets. |
| import-route-targets (list of RTs) | The setting is used to determine if BGP NLRI is related to particular VPLS, by comparing route targets received from BGP NLRI. |
| local-pref (integer[0..4294967295]) | |
| name (string; Default: ) | |
| pw-control-word (default | disabled | enabled) | Enables/disables Control Word usage. Read more in the VPLS Control Word article. |
| pw-l2mtu (integer[32..65535]) | Advertised pseudowire MTU value. |
| pw-type (raw-ethernet | tagged-ethernet | vpls) | The parameter is available starting from v5.16. It allows choosing advertised encapsulation in NLRI used only for comparison. It does not affect the functionality of the tunnel. See pw-type usage example >> |
| rd (string) | Specifies the value that gets attached to VPLS NLRI so that receiving routers can distinguish advertisements that may otherwise look the same. This implies that a 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 a particular VPLS (Route Target attribute is used for this), but it is mandatory to have different distinguishers for different VPLSes. Accepts 3 types of formats. Read more>> |
| site-id (integer [0..65535]) | Unique site identifier. Each site must have a unique site-id. A parameter must be set for RFC 4761 style VPLS signaling. |
| vrf (name) | Name of the VRF table. |
...