SRv6 VPRN Services

VPRN services support SRv6 End.DT4, End.DT6, and End.DT46 behaviors. VPRNs support IPv4 and IPv6 routes that are advertised in VPN-IPv4 and VPN-IPv6 families. The following CLI configures a VPRN for SRv6 with the VPN-IP families.

configure
+--service
|   +---vprn <service-id>
|   |   +---segment-routing-v6 <instance-id>
|   |   |   +---locator <locator-name>
|   |   |   |   +---function
|   |   |   |   |   +---end-dt4 <integer>
|   |   |   |   |   +---end-dt6 <integer>
|   |   |   |   |   +---end-dt46 <integer>
|   |   +---bgp-ipvpn
|   |   |   +---segment-routing-v6 <bgp-instance-id>
|   |   |   |   +---srv6-instance <id> default-locator <name>
|   |   |   |   +---source-address <ipv6-address>
|   |   |   |   +---route-distinguisher <rd>  
|   |   |   |   +---vrf-export  
|   |   |   |   +---vrf-import  
|   |   |   |   +---vrf-target  
|   |   |   |   +---default-route-tag <number>
|   |   |   |   +---shutdown

The associated locator must be configured to enable SRv6 on the VPRN service. In addition, the following rules apply.

• The function value can be statically configured, or it is dynamically allocated.

• Any Layer 3 function behavior can be configured, although VPN-IPv4 routes are advertised with end-dt4 or end-dt46 in that preference order (if they exist) and VPN-IPv6 is advertised with end-dt6 or end-dt46 in that preference order.

• The VPRN/label-mode is not relevant to SRv6 and setting it has no effect on the behavior of the SRv6 feature.

• The following is supported:

  • BGP-IPVPN and BGP-EVPN (EVPN-IFL) families are simultaneously supported in the same VPRN where SRv6 is enabled

  • up to two BGP instances per VPRN are supported

  • the two BGP instances can be associated to the same family or different families

  • a family cannot have two BGP instances of the same encapsulation, however, two bgp-ipvpn instances can be configured with SRv6 and MPLS encapsulations respectively

• VPRN feature interaction with SRv6:

  • Commands under the VPRN context that only operate on MPLS encapsulations:

    • class-forwarding

    • entropy-label

    • hash-label

    • label-mode

    • ttl-propagate

  • Commands under the VPRN context that are mutually exclusive with SRv6:

    • carrier-carrier-vpn

    • network-interface

    • export-inactive-bgp

  • VPRN features that work for MPLS and SRv6 encapsulations:

    • vprn-type

    • allow-export-bgp-vpn

    • ecmp-unequal-cost

    • bgp-vpn-backup

    • Unicast protocols on PE-CE interfaces

    • Commands such as ipsec/nat/subscriber-interfaces are supported (no interaction).

    • ECMP and edge PIC are supported for SRv6 and also across routes of the same family with different encapsulations; for example, the same prefix resolved to SRv6 and MPLS tunnels.

    • Route-target based leaking is supported for SRv6 routes in the VPRN.