Configures a VPLS instance to provide protected access using the EAPS redundancy type, the specified ESRP domain, or STP.
| vpls_name | Specifies the VPLS for which you are configuring protection. |
| esrpDomain | Configures a VPLS instance to provide protected access using the specified ESRP domain. |
| eaps | Configures a VPLS instance to use the EAPS redundancy type. |
| stp | Configures a VPLS instance to request an FDB relearning process on an adjacent node when STP responds to a topology change for a VLAN. |
Redundancy disabled.
Only one redundancy mode can be configured at a time on a VPLS, and the VPLS must be disabled when the redundancy mode is configured. If you attempt to configure a second mode, an error appears. The current redundancy mode must be unconfigured before you configure a different redundancy mode.
The ESRP domain specified must be a valid ESRP domain of type vpls-redundancy. If not, the command is rejected with an appropriate error message. When a VPLS instance is associated with an ESRP domain, the user cannot delete the ESRP domain unless the VPLS redundancy has been unconfigured. For VPLS access protection to become fully functional, VPLS redundancy must also be configured on a second VPLS peer using the same VPLS name and ESRP domain.
Specify the redundancy type as EAPS when using redundant EAPS access rings. This configuration requires EAPS shared links to be configured between redundant VPLS nodes. This configures VPLS to use a PW between VPLS attachment nodes instead of using a customer VLAN. This configuration is only required when there is an EAPS ring on the VPLS service VLAN.
Note
The EAPS master should not be on a VPLS node.The STP option enables VPLS interfaces to respond appropriately to STP topology changes in a VLAN. For example, if STP detects a link failure, it will flush the appropriate FDB entries to initiate relearning on the STP protected interfaces. When this option is selected and STP initiates relearning, the VPLS interfaces on the same VLAN also initiate relearning so that a new VLAN path to the VPLS core can be learned. For more information, including limitations and restrictions, see the “VPLS STP Redundancy Overview” Section in the ExtremeXOS 30.7 User Guide .
The l2vpn keyword was introduced in ExtremeXOS Release 12.4. For backward compatibility, the l2vpn keyword is optional when configuring a VPLS instance. 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 command adds redundancy to the vpls1 VPLS using the esrp1 domain:
configure l2vpn vpls vpls1 redundancy esrp esrp1
The following command specifies the EAPS redundancy type for the vpls2 VPLS:
configure l2vpn vpls vpls2 redundancy eaps
The following command specifies the STP redundancy type for the vpls3 VPLS:
configure l2vpn vpls vpls3 redundancy STP
This command was first available in ExtremeXOS 12.1.
The l2vpn keyword and the STP option were added in ExtremeXOS 12.4.
This command is available only on the platforms that support MPLS as described in the ExtremeXOS 30.7 Feature License Requirements document.