Configures VPLS or VPWS parameters.
|vpls_name||Identifies the VPLS within the switch (character string).|
|vpws_name||Identifies the VPWS within the switch (character string).|
|dot1q||Specifies the action the switch performs with respect to the 802.1Q ethertype or tag.|
|ethertype||Overwrites the ethertype value for the customer traffic sent across the PW|
|hex_number||Identifies the ethertype, uses the format of 0xN.|
|tag||Specifies the action the switch performs with respect to the 802.1Q tag.|
|include||Includes the 802.1Q tag when sending packets over the VPLS L2 VPN.|
|exclude||Strips the 802.1Q tag before sending packets over the VPLS L2 VPN.|
|mtu||Specifies the MTU value of the VPLS transport payload packet.|
|number||The size (in bytes) of the MTU value. The configurable MTU range is 1492 through 9216. The default VPLS MTU value is 1500.|
dot1q tag - excluded.
ethertype - the configured switch ethertype is used.
number (MTU) - 1500.
This command configures the VPLS and VPWS parameters. PWs are point-to-point links used to carry VPN traffic between two devices within the VPLS. Each device must be configured such that packets transmitted between the endpoints are interpreted and forwarded to the local service correctly. The optional ethertype keyword may be used to overwrite the Ethertype value for the customer traffic sent across the PW. By default, the configured switch ethertype is used. If configured, the ethertype in the outer 802.1q field of the customer packet is overwritten using the configured ethertype value. The ethertype value is ignored on receipt.
Optionally, the switch can be configured to strip the 802.1q tag before sending packets over the VPLS or VPWS Layer 2 VPN. This capability may be required to provide interoperability with other vendor products or to emulate port mode services. The default configuration is to include the 802.1q tag.
The mtu keyword optionally specifies the MTU value of the VPLS or VPWS transport payload packet (customer packet). The MTU value is exchanged with VPLS-configured peer nodes. All VPLS peer nodes must be configured with the same MTU value. If the MTU values do not match, PWs cannot be established between peers. The MTU values are signaled during PW establishment so that endpoints can verify that MTU settings are equivalent before establishing the PW. By default the MTU is set to 1500. The configurable MTU range is 1492 through 9216. Changing the MTU setting causes established PWs to terminate. Payload packets might be dropped if the VPLS or VPWS MTU setting is greater than the MPLS MTU setting for the PW interface.
NoteThe maximum MTU value supported depends on the current configuration options. For more information, see “Configuring the Layer 2 VPN MTU” in the Switch Engine 32.3 User Guide .
The l2vpn keyword was introduced in ExtremeXOS Release 12.4 and is required when enabling a VPWS. For backward compatibility, the l2vpn keyword is optional when enabling a VPLS. However, this keyword will be required in a future release, so we recommend that you use this keyword for new configurations and scripts.
The following commands change the various parameters of a particular VPLS:
configure vpls vpls1 dot1q ethertype 0x8508 configure vpls vpls1 dot1q ethertype 0x8509 mtu 2500 configure vpls vpls1 dot1q tag exclude mtu 2430 configure vpls vpls1 dot1q mtu 2500
This command was first available in ExtremeXOS 11.6.
The l2vpn and vpws keywords were first available in ExtremeXOS 12.4.
This command is available only on the platforms that support MPLS as described in the Switch Engine 32.3 Feature License Requirements document.