New and Changed VPN Features
|
Feature |
Description |
Changed in Release |
Where Documented |
|---|---|---|---|
|
EVPN Out of Service |
The EVPN Out of Service feature enables you to control the state of bundle interfaces that are part of an Ethernet segment that have Link Aggregation Control protocol (LACP) configured. |
Release 6.1.31 |
|
|
EVPN RPL Support |
The EVPN RPL Support feature provides the route policy support for address-family L2VPN EVPN. |
Release 6.1.31 |
|
|
Flexible Cross-Connect Service - All-Active Multihoming |
The Flexible Cross-Connect Service All-Active Multihoming feature enables you to connect a customer edge (CE) device to two or more provider edge (PE) devices to provide load balancing and redundant connectivity. |
Release 6.1.31 |
|
|
Local Switching |
Traffic between the two ACs is locally switched within the PE when two ACs belonging to different Ethernet Segment have the same normalization VLANs. Local switching is supported only on FXC VLAN-aware. |
Release 6.1.31 |
|
|
EVPN VPWS - All-Active Multihoming |
The EVPN VPWS feature supports all-active multihoming capability that enables you to connect a customer edge device to two or more provider edge (PE) devices to provide load balancing and redundant connectivity. |
Release 6.1.31 |
|
|
VM Mobility |
VM mobility is the ability of virtual machines to migrate between one server and another while retaining their existing MAC and IP addresses. |
Release 6.1.31 |
|
|
EVPN IRB Distributed Anycast Gateway |
EVPN IRB for the given subnet is configured on all the EVPN PEs that are hosted on this subnet. To facilitate optimal routing while supporting transparent virtual machine mobility, hosts are configured with a single default gateway address for their local subnet. That single (anycast) gateway address is configured with a single (anycast) MAC address on all EVPN PE nodes locally supporting that subnet. This process is repeated for each locally defined subnet requires Anycast Gateway support. |
Release 6.1.31 |
|
|
Enable Auto BGP RT with Manual ESI Configuration |
Configuring an ES-Import RT was previously mandatory for Type 0 ESI. From Release 6.1.31, the ES-Import RT is now auto-extracted by default, and the configuration serves to override the default value. This is feature is based on RFC 7432 but applied specifically to ESI Type 0. For more information, see Section 5 of RFC 7432. |
Release 6.1.31 |
|
|
Virtual Circuit Connection Verification on L2VPN |
Virtual Circuit Connection Verification (VCCV) is an L2VPN Operations, Administration, and Maintenance (OAM) feature that allows network operators to run IP-based provider edge-to-provider edge (PE-to-PE) keepalive protocol across a specified pseudowire to ensure that the pseudowire data path forwarding does not contain any faults. |
Release 6.1.31 |
Feedback