SRv6 transport for EVPN services
Note: SRv6 as transport for EVPN-VPWS is only supported on
7730 SXR
platforms.
EVPN-VPWS with SRv6 encapsulation has the same considerations as EVPN-VPWS for MPLS in
terms of the following:
- connection-points
- MTU
- attachment circuit configuration and state
- Layer 2 attribute mismatches
- Link Loss Forwarding (LLF)
The following considerations apply to EVPN-VPWS services with SRv6 encapsulation:
- Only one subinterface can be configured with SRv6 in the VPWS.
- MPLS cannot be enabled with SRv6 in the same VPWS.
- Only one SRv6 instance is supported per VPWS.
- SRv6 cannot be enabled without the configuration of a default locator under the local-ac.
The following considerations apply to SRv6:
- For SRv6 full segments, the block length can be any multiple of eight from 0 to 96.
- For micro-segments, only a block length of 32 is supported.
- Configured static function values cannot exceed the static-function max-entries value.
- Up to seven SRv6 source IP addresses are supported and the default-source-address must be one of those seven.
- A maximum of 16 SRv6 full-segment locators and 8 SRv6 micro-segment blocks are supported.
For more information about SRv6 and segment routing, see "Segment routing with IPv6 data plane (SRv6)" in the Segment Routing Guide.
EVPN multihoming is supported with VPWS network instances for SRv6 (single and all-active). For more information, see EVPN multihoming for IPv6 and non-system IPv4 next-hops.