Spoke Termination for IPv6-6VPE
This chapter provides information about spoke termination for IPv6-6VPE.
Topics in this chapter include:
Applicability
This chapter was originally written for SR OS Release 8.0, where Epipe Virtual Leased Line (VLL) is supported for IPv6 spoke termination within a Virtual Private Routed Network (VPRN). The CLI in the current edition corresponds to SR OS Release 21.10.R2.
Overview
RFC 4659, BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN, standardized the use of an IPv6 over IPv4 tunneling scheme. SR OS supports the standardized IPv6 over IPv4 tunneling scheme for VPRN services using Multi-Protocol Border Gateway Protocol (MP-BGP), also known as 6VPE.
SR OS supports pseudowire termination by a VPRN from an Epipe Virtual Leased Line (VLL) or VPLS spoke Service Distribution Point (spoke SDP) where the pseudowire can be given IPv6 addresses and run IPv6 protocols. In the example used in this chapter, any advertisements across the Multi-Protocol Labeled Switching (MPLS) network between VPRN Provider Edge (PE) devices will use 6VPE. This chapter describes the configuration for IPv6 spoke termination to a VPRN over an Epipe VLL and transporting IPv6 packets over 6VPE tunnels between PE devices.
This solution can be used where a service provider is providing VPRN services built on a transport network whose Interior Gateway Protocol (IGP) is using IPv4 addressing on the network interfaces. The customer’s CE and the service provider’s PE must support IPv6 pseudowires, IPv6 interfaces and in addition, the service provider also must be able to support the advertisements of IPv6 prefixes between CE-PE peerings and between the transport PE routers using MP-BGP. The advertisement of IPv6 prefixes across the MPLS network and the transport of IPv6 traffic is tunneled using 6VPE.
The VPRN PE supports spoke termination of Epipe VLL services on access with IPv6 addressing between the CE and VPRN PE. The IPv6 spoke termination on VPRN services has the same functionality as VPRN IPv4 spoke termination.
The example in Spoke termination for IPv6 illustrates a CE device that connects to a VPRN PE on an IPv6 interface addressing using spoke termination.
CE-1 is connected to the VPRN service on PE-3, using IPv6 interfaces. CE-1 reaches PE-3 by connecting to PE-2. PE-2 uses an Epipe VLL for transport to the VPRN on the PE-3. The connectivity between the VLL service on the VPRN service on PE-3 is using spoke termination with IPv6 addressing on the spoke SDP interface on PE-3.
IPv6 addressing and IPv6 prefixes shows the overall IPv6 addressing from interfaces to prefixes advertised from CE-1 and CE-5 across the VPRN network.
Link between CE-1 and PE-3: 2001:db8:1000::/64
Link between CE-5 and PE-4: 2001:db8:2000::/64
Advertised prefix from CE-1: 2001:db8:3000::/64
Advertised prefix from CE-5: 2001:db8:4000::/64
PE-3 has an MP-eBGP session with CE-1 to receive and advertise IPv6 routes. PE-3 also has an MP-iBGP peering session with PE-4 to use 6VPE to tunnel IPv6 routes and traffic to and from PE-4. PE-4 has an IPv6 SAP interface to CE-5 and uses MP-eBGP to advertise to and receive routes from CE-5 (no spoke termination). The configuration of PE-3 is included to provide examples of the end-to-end VPRN service using a 6VPE model.
This network topology illustrates the use of spoke termination using IPv6 interfaces and the tunneling of IPv6 traffic over a 6VPE MPLS network.
Configuration
First an MPLS network is established where the VPRN service can use 6VPE to tunnel traffic across the IPv4 IGP.
In MP-BGP VPN IPv6, PE-3 and PE-4 are edge routers running VPRN services on access with IPv6 interfaces. The MPLS network is configured using IPv4 link addressing. Interior Border Gateway Protocol (iBGP) peerings need to be established with MP-BGP for the VPN-IPv6 address family between PE-3 and PE-4.
# on PE-3:
configure
router Base
bgp
group "iBGP"
description "iBGP peering in AS 64502"
family vpn-ipv6
type internal
neighbor 192.0.2.4
description "PE-4"
exit
exit
no shutdown
exit
exit
# on PE-4:
configure
router Base
bgp
group "iBGP"
description "iBGP peering in AS 64502"
family vpn-ipv6
type internal
neighbor 192.0.2.3
description "PE-3"
exit
exit
no shutdown
exit
exit
Configuring address family VPN-IPv6 between VPRN PE edge routers in BGP enables MP-BGP for the Layer 3 VPNs supporting the customer’s IPv6 addressing (6VPE).
The following commands verify the BGP sessions for the VPN-IPv6 address family between PE-3 and PE-4:
*A:PE-3# show router bgp neighbor 192.0.2.4
===============================================================================
BGP Neighbor
===============================================================================
-------------------------------------------------------------------------------
Peer : 192.0.2.4
Description : PE-4
Group : iBGP
-------------------------------------------------------------------------------
Peer AS : 64502 Peer Port : 50662
Peer Address : 192.0.2.4
Local AS : 64502 Local Port : 179
Local Address : 192.0.2.3
Peer Type : Internal Dynamic Peer : No
State : Established Last State : Established
Last Event : recvOpen
Last Error : Cease (Connection Collision Resolution)
Local Family : VPN-IPv6
Remote Family : VPN-IPv6
---snip---
*A:PE-4# show router bgp neighbor 192.0.2.3
===============================================================================
BGP Neighbor
===============================================================================
-------------------------------------------------------------------------------
Peer : 192.0.2.3
Description : PE-3
Group : iBGP
-------------------------------------------------------------------------------
Peer AS : 64502 Peer Port : 179
Peer Address : 192.0.2.3
Local AS : 64502 Local Port : 50662
Local Address : 192.0.2.4
Peer Type : Internal Dynamic Peer : No
State : Established Last State : Active
Last Event : recvOpen
Last Error : Unrecognized Error
Local Family : VPN-IPv6
Remote Family : VPN-IPv6
---snip---
After the MP-BGP sessions are established for the VPN-IPv6 address-family, 6VPE tunnel support is provided between PE-3 and PE-4.
Spoke termination for IPv6 addressing illustrates the model for spoke termination for IPv6 using VPRN services.
CE-1 is configured with IPv6 addressing on the access interface facing the VPRN service. CE-1’s access is backhauled to the VPRN service on PE-3 using Epipe VLL with spoke termination. The configuration of the Epipe VLL on PE-2 is as follows:
# on PE-2:
configure
service
sdp 231 mpls create
far-end 192.0.2.3
ldp
no shutdown
exit
epipe 1 name "Epipe 1" customer 1 create
sap 1/1/2 create
no shutdown
exit
spoke-sdp 231:1 create
no shutdown
exit
no shutdown
exit
exit
Epipe 1 on PE-2 is configured with a SAP interface facing the customer and a spoke SDP facing PE-3. The spoke SDP is terminated into the customer’s VPRN service on PE-3.
The possible IPv6 options for spoke SDP interfaces on the CLI for VPRN Services are as follows (compliant with RFC 4213, Basic Transition Mechanisms for IPv6 Hosts and Routers <draft-ietf-v6ops-mech-v2-07.txt>):
Interface spoke SDP (IPv6 options only)
*A:PE-3>config>service>vprn# interface "int-PE-3-PE-2" ? ---snip--- [no] ipv6 + Enables/Configures IPv6 for a VPRN interface ---snip---*A:PE-3>config>service>vprn>if# ipv6 ? - ipv6 - no ipv6 [no] address - Assigns an IPv6 address to the VPRN interface. [no] bfd - Configure BFD parameters [no] dad-disable - Disable Duplicate Address Detection [no] dhcp6-relay + Configure DHCPv6 relay parameters for the VPRN interface [no] dhcp6-server + Configure DHCPv6 server parameters for the VPRN interface [no] forward-ipv4-p* - Enable/disable forwarding unencapsulated IPv4 packets icmp6 + Configure ICMPv6 parameters for the VPRN interface [no] link-local-add* - Configure link-local address [no] local-dhcp-ser* - Assign a DHCP server to the interface [no] local-proxy-nd - Enable/disable local proxy Neighbor Discovery on the VPRN interface nd-host-route + Configure ND host route to populate [no] nd-learn-unsol* - Configure neighbor discover learn unsolicited [no] nd-proactive-r* - Configure neighbor discovery proactive refresh [no] neighbor - Configure IPv6-to-MAC address mapping on the VPRN interface [no] neighbor-limit - Configures the maximum amount of IPv6 neighbor entries [no] proxy-nd-policy - Configure a proxy Neighbor Discovery policy for the VPRN interface [no] qos-route-look* - Enable/Disable Qos route lookup for the interface [no] reachable-time - Configure neighbor reachability detection timer [no] secure-nd + Configure Secure Neighbor Discovery (SEND) parameters for the interface [no] stale-time - Configure the time a neighbor discovery cache entry can remain stale before being removed [no] tcp-mss - Configure TCP maximum segment size for the interface [no] urpf-check + Enables/Configures unicast RPF check for an interface [no] vrrp + Context to create and configure VRRP virtual router instance on the interfaceIPv6 address
*A:PE-3>config>service>vprn>if>ipv6# address ? - address <ipv6-address/prefix-length> [eui-64] [track-srrp <srrp-instance>] [modifier <cga-modifier>] [dad-disable][primary-preference <primary-preference>] - no address <ipv6-address/prefix-length> <ipv6-address/pref*> : ipv6-address x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x [0..FFFF]H d [0..255]D (no multicast address) prefix-length [4..128] <eui-64> : keyword <srrp-instance> : [1..4294967295] <cga-modifier> : [0x0..0xFFFFFFFF...(32 hex nibbles)] <dad-disable> : keyword <primary-preference> : [1..4294967295]DHCPv6 relay parameters for the VPRN service (default settings)
*A:PE-3>config>service>vprn>if>ipv6>dhcp6-relay# info detail ---------------------------------------------- shutdown no description no lease-populate no neighbor-resolution option no interface-id no remote-id exit no source-address no link-address no user-db no python-policy no server ----------------------------------------------DHCPv6 server parameters for the VPRN service (default)
*A:PE-3>config>service>vprn>if>ipv6>dhcp6-server# info detail ---------------------------------------------- prefix-delegation shutdown exit max-nbr-of-leases 8000 ----------------------------------------------ICMPv6 (default)
*A:PE-3>config>service>vprn>if>ipv6>icmp6# info detail ---------------------------------------------- packet-too-big 100 10 param-problem 100 10 redirects 100 10 time-exceeded 100 10 unreachables 100 10 ----------------------------------------------Link-local-addressing, for the VPRN interface. By default, link-local addressing is assigned dynamically. Use this command if you want to add a static link-local-address.
*A:PE-3>config>service>vprn>if>ipv6# link-local-address ? - link-local-address <ipv6-address> [dad-disable] - no link-local-address <ipv6-address> : ipv6-address - x:x:x:x:x:x:x:x x:x:x:x:x:x:d.d.d.d x [0..FFFF]H d [0..255]D <dad-disable> : keywordNeighbor: IPv6 to MAC address mapping on the VRPN interface
*A:PE-3>config>service>vprn>if>ipv6# neighbor ? - neighbor <ipv6-address> <mac-address> - no neighbor <ipv6-address> <ipv6-address> : x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x [0..FFFF]H d [0..255]D prefix-length [1..128] <mac-address> : xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xxEnabling local proxy neighbor discovery
*A:PE-3>config>service>vprn>if>ipv6# local-proxy-nd ? - local-proxy-nd - no local-proxy-ndVRRP
*A:PE-3>config>service>vprn>if>ipv6# vrrp ? - no vrrp <virtual-router-id> - vrrp <virtual-router-id> [owner] [passive] <virtual-router-id> : [1..255] <owner> : keyword [no] backup - Configure virtual router IP addresses for the interface [no] bfd-enable - Configure a BFD interface [no] init-delay - Configure VRRP initialization delay timer [no] mac - Configure a Virtual MAC address to use in Neighbor Discovery [no] master-int-inh* - Allow/disallow the master instance to dictate the master down timer (non-owner context only) [no] message-interv* - Configure the interval for sending VRRP Advertisement messages [no] ntp-reply - Allow/disallow non-owner master to reply to NTP requests (non-owner context only) [no] oper-group - Associate group-name to VRRP [no] ping-reply - Allow/disallow non-owner master to reply to ICMP Echo requests (non-owner context only) [no] policy - Associate a VRRP Priority Control Policy with the virtual router instance (non-owner context only) [no] preempt - Allow/disallow the virtual router instance to override an existing non-owner master (non-owner context only) [no] priority - Configure the base priority for the virtual router instance (non-owner context only) [no] shutdown - Administratively enable/disable the virtual router instance (non-owner context only) [no] standby-forwar* - Allow/disallow the forwarding of packets by a standby router [no] telnet-reply - Allow/disallow non-owner master to reply to Telnet requests (non-owner context only) [no] traceroute-rep* - Allow/disallow non-owner master to reply to traceroute requests (non-owner context only)
The VPRN on PE-3 exports IPv6 routes (IPv6 route on CE-5) to CE-1 using the following route policy.
# on PE-3
configure
router Base
policy-options
begin
prefix-list "PE-3-CE-1"
prefix 2001:db8:4000::/64 exact
exit
policy-statement "PE-3-BGP-CE-1"
entry 10
from
prefix-list "PE-3-CE-1"
exit
action accept
origin igp
exit
exit
default-action drop
exit
exit
commit
exit
The configuration for the VPRN service on PE-3 with IPv6 interface (spoke SDP) as shown in Spoke termination for IPv6 addressing:
# on PE-3
configure
service
sdp 321 mpls create
far-end 192.0.2.2
ldp
no shutdown
exit
vprn 1 name "VPRN 1" customer 1 create
router-id 192.0.2.31
autonomous-system 64502
interface "loopback" create
address 192.0.2.31/32
loopback
exit
interface "int-PE-3-PE-2" create
description "Spoke SDP"
ipv6
address 2001:db8:1000::2/64
exit
spoke-sdp 321:1 create
no shutdown
exit
exit
bgp-ipvpn
mpls
auto-bind-tunnel
resolution-filter
ldp
exit
resolution filter
exit
route-distinguisher 64502:1
vrf-target target:64502:1
no shutdown
exit
exit
bgp
router-id 192.0.2.31
group "Spoke-CE-1-PE-3"
family ipv6
peer-as 64501
local-address 2001:db8:1000::2
neighbor 2001:db8:1000::1
as-override
type external
export "PE-3-BGP-CE-1"
exit
exit
no shutdown
exit
no shutdown
exit
exit
In the preceding configuration example, PE-3 has been configured with an IPv6 spoke SDP (spoke termination) with interface int-PE-3-PE-2. The VPRN configuration has also been set up for MP-eBGP peering to CE-1 through the IPv6 spoke interface. The MP-eBGP peering receives and advertises IPv6 prefixes from and to CE-1. The included route policy configuration shows how IPv6 routes are advertised to CE-1 from PE-3 (policy-statement PE-3-BGP-CE-1).
The configuration on PE-4 is similar, but with a SAP interface to CE-5 instead of a spoke-SDP.
The IPv6 configuration options for the SAP interface (int-PE-4-CE-5) are similar to those in the preceding example for the spoke SDP on PE-3. The PE-4 BGP export policy (PE-4-BGP-CE-5) is also similar to the example for PE-3 in advertising the learned IPv6 route to CE-5.
# on PE-4:
configure
router Base
policy-options
begin
prefix-list "PE-4-CE-5"
prefix 2001:db8:3000::/64 exact
exit
policy-statement "PE-4-BGP-CE-5"
entry 10
from
prefix-list "PE-4-CE-5"
exit
action accept
origin igp
exit
exit
default-action drop
exit
exit
commit
exit
configure
service
vprn 1 name "VPRN 1" customer 1 create
router-id 192.0.2.41
autonomous-system 64502
interface "loopback" create
address 192.0.2.41/32
loopback
exit
interface "int-PE-4-CE-5" create
ipv6
address 2001:db8:2000::1/64
exit
sap 1/1/1 create
exit
exit
bgp-ipvpn
mpls
auto-bind-tunnel
resolution-filter
ldp
exit
resolution filter
exit
route-distinguisher 64502:1
vrf-target target:64502:1
no shutdown
exit
exit
bgp
router-id 192.0.2.41
group "CE-5-PE-4"
family ipv6
peer-as 64501
local-address 2001:db8:2000::1
neighbor 2001:db8:2000::2
as-override
type external
export "PE-4-BGP-CE-5"
exit
exit
no shutdown
exit
no shutdown
exit
In this setup, the configuration on CE-1 is as follows.
# on CE-1:
configure
router Base
static-route 2001:db8:3000::/64
black-hole
no shutdown
exit
exit
policy-options
begin
prefix-list "CE-1-192.0.2.1"
prefix 2001:db8:3000::/64 exact
exit
policy-statement "CE-1-sys-to-eBGP"
entry 10
from
prefix-list "CE-1-192.0.2.1"
exit
action accept
origin igp
exit
exit
default-action drop
exit
exit
commit
exit
bgp
router-id 192.0.2.1
group "eBGP_to_64502"
description "eBGP_to_PE-3_AS64502"
family ipv6
type external
peer-as 64502
local-address 2001:db8:1000::1
neighbor 2001:db8:1000::2
export "CE-1-sys-to-eBGP"
exit
exit
no shutdown
exit
exit
exit
# on CE-1:
configure
service
ies 1 name "IES 1" customer 1 create
interface "int-CE-1-PE-2" create
description "SAP_toward_VPRN_Service"
ipv6
address 2001:db8:1000::1/64
exit
sap 1/1/1 create
exit
exit
no shutdown
exit
The configuration on CE-5 is similar.
The following command on PE-2 shows that the Epipe VLL is established with the SAP facing CE-1 and spoke SDP facing VPRN 1 on PE-3.
*A:PE-2# show service id 1 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 1 Vpn Id : 0
Service Type : Epipe
MACSec enabled : no
Name : Epipe 1
Description : (Not Specified)
Customer Id : 1 Creation Origin : manual
Last Status Change: 01/20/2022 13:57:46
Last Mgmt Change : 01/20/2022 13:57:32
Test Service : No
Admin State : Up Oper State : Up
MTU : 9190
Vc Switching : False
SAP Count : 1 SDP Bind Count : 1
Per Svc Hashing : Disabled
Vxlan Src Tep Ip : N/A
Force QTag Fwd : Disabled
Lcl Switch Svc St : sap
Oper Group : <none>
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2 null 9212 9212 Up Up
sdp:231:1 S(192.0.2.3) Spok 0 9190 Up Up
===============================================================================
The same command can be launched on PE-3 to verify that the VPRN service is up and that the spoke SDP is up (admin state up/oper state up).
*A:PE-3# show service id 1 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 1 Vpn Id : 0
Service Type : VPRN
MACSec enabled : no
Name : VPRN 1
Description : (Not Specified)
Customer Id : 1 Creation Origin : manual
Last Status Change: 01/20/2022 13:57:44
Last Mgmt Change : 01/20/2022 13:57:44
Admin State : Up Oper State : Up
Router Oper State : Up
Route Dist. : 64502:1 VPRN Type : regular
Oper Route Dist : 64502:1
Oper RD Type : configured
AS Number : 64502 Router Id : 192.0.2.31
ECMP : Enabled ECMP Max Routes : 1
Max IPv4 Routes : No Limit
Local Rt Domain-Id: None D-Path Lng Ignore : Disabled
Auto Bind Tunnel
Allow Flex-Alg-Fb : Disabled
Resolution : filter
Filter Protocol : ldp
Weighted ECMP : Disabled ECMP Max Routes : 1
Strict Tnl Tag : Disabled
Max IPv6 Routes : No Limit
Ignore NH Metric : Disabled
Hash Label : Disabled
Entropy Label : Disabled
Vrf Target : target:64502:1
Vrf Import : None
Vrf Export : None
MVPN Vrf Target : None
MVPN Vrf Import : None
MVPN Vrf Export : None
Car. Sup C-VPN : Disabled
Label mode : vrf
BGP VPN Backup : Disabled
BGP Export Inactv : Disabled
LOG all events : Disabled
SAP Count : 0 SDP Bind Count : 1
VSD Domain : <none>
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sdp:321:1 S(192.0.2.2) TLDP 0 9190 Up Up
===============================================================================
The following command shows that the IPv6 interface is established and its IPv6 address is preferred (2001:db8:1000::2/64). The IPv6 link local address (fe80::17:ffff:fe00:0/64) has been dynamically assigned and is in the preferred state.
*A:PE-3# show service id 1 interface
==============================================================================
Interface Table
==============================================================================
Interface-Name Adm Opr(v4/v6) Type Port/SapId
IP-Address PfxState
------------------------------------------------------------------------------
loopback Up Up/Down VPRN loopback
192.0.2.31/32 n/a
int-PE-3-PE-2 Up Down/Up VPRN spoke-321:1
2001:db8:1000::2/64 PREFERRED
fe80::17:ffff:fe00:0/64 PREFERRED
------------------------------------------------------------------------------
Interfaces : 2
==============================================================================
With the following command, an extensive list of parameters is displayed, including IPv6-related fields that can be checked if configured: DHCP6-relay, DHCP6-server, and so on. It is possible to use filters to reduce the output.
*A:PE-3# show service id 1 all
After verification of the services (Epipe, VPRN), the MP-eBGP peering connectivity (through IPv6 interfaces) on the VPRN between PE-3 and CE-1 can be verified as follows:
*A:PE-3# show router 1 bgp neighbor
===============================================================================
BGP Neighbor
===============================================================================
-------------------------------------------------------------------------------
Peer : 2001:db8:1000::1
Description : (Not Specified)
Group : Spoke-CE-1-PE-3
-------------------------------------------------------------------------------
Peer AS : 64501 Peer Port : 179
Peer Address : 2001:db8:1000::1
Local AS : 64502 Local Port : 49566
Local Address : 2001:db8:1000::2
Peer Type : External Dynamic Peer : No
State : Established Last State : Active
Last Event : recvOpen
Last Error : Unrecognized Error
Local Family : IPv6
Remote Family : IPv6
---snip---
Local Capability : RtRefresh MPBGP 4byte ASN
Remote Capability : RtRefresh MPBGP 4byte ASN
Local AddPath Capabi*: Disabled
Remote AddPath Capab*: Send - None
: Receive - None
Import Policy : None Specified - Default Accept
Export Policy : PE-3-BGP-CE-1
: Default Accept
---snip---
-------------------------------------------------------------------------------
Ingress prefix counters per family.
IPv4 received : 0 IPv6 received : 1
IPv4 active : 0 IPv6 active : 1
IPv4 suppressed : 0 IPv6 suppressed : 0
IPv4 rejected : 0 IPv6 rejected : 0
VPN-IPv4 received : 0 VPN-IPv6 received : 0
VPN-IPv4 active : 0 VPN-IPv6 active : 0
VPN-IPv4 suppressed : 0 VPN-IPv6 suppressed : 0
VPN-IPv4 rejected : 0 VPN-IPv6 rejected : 0
---snip---
Not only is the MP-eBGP session on the VPRN established, but the MP-BGP capabilities are also supported (locally and remotely). PE-3 and its BGP peer CE-1 have advertised and received an IPv6 prefix.
The same command can be launched on PE-4. The status of the VPRN service on PE-4 and its interface to CE-5 can be verified as follows:
*A:PE-4# show service id 1 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 1 Vpn Id : 0
Service Type : VPRN
MACSec enabled : no
Name : VPRN 1
Description : (Not Specified)
Customer Id : 1 Creation Origin : manual
Last Status Change: 01/20/2022 13:57:56
Last Mgmt Change : 01/20/2022 13:57:56
Admin State : Up Oper State : Up
Router Oper State : Up
Route Dist. : 64502:1 VPRN Type : regular
Oper Route Dist : 64502:1
Oper RD Type : configured
AS Number : 64502 Router Id : 192.0.2.41
ECMP : Enabled ECMP Max Routes : 1
Max IPv4 Routes : No Limit
Local Rt Domain-Id: None D-Path Lng Ignore : Disabled
Auto Bind Tunnel
Allow Flex-Alg-Fb : Disabled
Resolution : filter
Filter Protocol : ldp
Weighted ECMP : Disabled ECMP Max Routes : 1
Strict Tnl Tag : Disabled
Max IPv6 Routes : No Limit
Ignore NH Metric : Disabled
Hash Label : Disabled
Entropy Label : Disabled
Vrf Target : target:64502:1
Vrf Import : None
Vrf Export : None
MVPN Vrf Target : None
MVPN Vrf Import : None
MVPN Vrf Export : None
Car. Sup C-VPN : Disabled
Label mode : vrf
BGP VPN Backup : Disabled
BGP Export Inactv : Disabled
LOG all events : Disabled
SAP Count : 1 SDP Bind Count : 0
VSD Domain : <none>
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/1 null 9212 9212 Up Up
===============================================================================
The VPRN service is up and the SAP is up.
The following command shows that the IPv6 interface is established and its IPv6 address is in the preferred state.
*A:PE-4# show service id 1 interface
==============================================================================
Interface Table
==============================================================================
Interface-Name Adm Opr(v4/v6) Type Port/SapId
IP-Address PfxState
------------------------------------------------------------------------------
loopback Up Up/Down VPRN loopback
192.0.2.41/32 n/a
int-PE-4-CE-5 Up Down/Up VPRN 1/1/1
2001:db8:2000::1/64 PREFERRED
fe80::1b:ffff:fe00:0/64 PREFERRED
------------------------------------------------------------------------------
Interfaces : 2
==============================================================================
MP-iBGP, providing 6VPE is configured and built between PE-3 and PE-4 across the MPLS network. IPv6 prefixes are received on PE-3 from CE-1 (2001:db8:3000::/64) and on PE-4 from CE-5 (2001:db8:4000::/64) across the MPLS network using MP-iBGP (6VPE).
CE-1 advertises IPv6 prefix 2001:db8:3000::/64 and CE-5 advertises IPv6 prefix 2001:db8:4000::/64.
The following command on PE-3 shows whether VPN-IPv6 routes were received from and advertised to its iBGP peer PE-4:
*A:PE-3# show router bgp summary
===============================================================================
BGP Router ID:192.0.2.3 AS:64502 Local AS:64502
===============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 1
Total VPN Peer Groups : 1 Total VPN Peers : 1
Current Internal Groups : 1 Max Internal Groups : 1
Total BGP Paths : 23 Total Path Memory : 8168
---snip---
Total VPN-IPv4 Rem. Rts : 0 Total VPN-IPv4 Rem. Act. Rts: 0
Total VPN-IPv6 Rem. Rts : 2 Total VPN-IPv6 Rem. Act. Rts: 2
Total VPN-IPv4 Bkup Rts : 0 Total VPN-IPv6 Bkup Rts : 0
Total VPN Local Rts : 5 Total VPN Supp. Rts : 0
Total VPN Hist. Rts : 0 Total VPN Decay Rts : 0
---snip---
===============================================================================
BGP Summary
===============================================================================
Legend : D - Dynamic Neighbor
===============================================================================
Neighbor
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
-------------------------------------------------------------------------------
192.0.2.4
PE-4
64502 38 0 00h16m24s 2/2/2 (VpnIPv6)
40 0
-------------------------------------------------------------------------------
PE-3 has received and learned a valid and best IPv6 route for prefix 2001:db8:3000::/64 with a BGP next hop of 2001:db8:1000:: (CE-1), as follows:
*A:PE-3# show router 1 bgp routes ipv6
===============================================================================
BGP Router ID:192.0.2.31 AS:64502 Local AS:64502
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
u*>i 2001:db8:3000::/64 None None
2001:db8:1000::1 None 0
64501 -
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
The following output shows the 2001:db8:4000::/64 prefix as BGP IPv6 route advertised by PE-3 to eBGP peer CE-1.
*A:PE-3# show router 1 bgp neighbor 2001:db8:1000::1 advertised-routes ipv6
===============================================================================
BGP Router ID:192.0.2.31 AS:64502 Local AS:64502
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
i 2001:db8:4000::/64 n/a None
2001:db8:1000::2 None n/a
64502 64502 -
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
The IPv6 route 2001:db8:4000::/64 originates from CE-5 and was advertised from CE-5 to its eBGP peer PE-4, then from PE-4 as VPN-IPv6 route to its iBGP peer PE-3 with next-hop PE-4, as follows:
*A:PE-3# show router bgp routes vpn-ipv6
===============================================================================
BGP Router ID:192.0.2.3 AS:64502 Local AS:64502
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP VPN-IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
u*>i 64502:1:2001:db8:2000::/64 100 None
::ffff:192.0.2.4 None 10
No As-Path 524284
u*>i 64502:1:2001:db8:4000::/64 100 None
::ffff:192.0.2.4 None 10
64501 524284
-------------------------------------------------------------------------------
Routes : 2
===============================================================================
PE-3 is advertising the VPN-IPv6 route of 2001:db8:3000::/64 to its MP-iBGP peer PE-4, as follows. The IPv6 prefix 2001:db8:3000::/64 was learned from CE-1 in an MP-eBGP session:
*A:PE-3# show router bgp neighbor 192.0.2.4 advertised-routes vpn-ipv6
===============================================================================
BGP Router ID:192.0.2.3 AS:64502 Local AS:64502
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP VPN-IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
i 64502:1:2001:db8:1000::/64 100 None
::ffff:192.0.2.3 None n/a
No As-Path 524284
i 64502:1:2001:db8:3000::/64 100 None
::ffff:192.0.2.3 None n/a
64501 524284
-------------------------------------------------------------------------------
Routes : 2
===============================================================================
The list of VPN-IPv6 routes on PE-4 includes the VPN-IPv6 route that was learned from PE-3: 2001:db8:3000::/64, as follows:
*A:PE-4# show router bgp routes vpn-ipv6
===============================================================================
BGP Router ID:192.0.2.4 AS:64502 Local AS:64502
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP VPN-IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
u*>i 64502:1:2001:db8:1000::/64 100 None
::ffff:192.0.2.3 None 10
No As-Path 524284
u*>i 64502:1:2001:db8:3000::/64 100 None
::ffff:192.0.2.3 None 10
64501 524284
-------------------------------------------------------------------------------
Routes : 2
===============================================================================
The following output shows the advertised VPN-IPv6 route of 2001:db8:4000::/64 from PE-4 to PE-3.
*A:PE-4# show router bgp neighbor 192.0.2.3 advertised-routes vpn-ipv6
===============================================================================
BGP Router ID:192.0.2.4 AS:64502 Local AS:64502
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP VPN-IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
i 64502:1:2001:db8:2000::/64 100 None
::ffff:192.0.2.4 None n/a
No As-Path 524284
i 64502:1:2001:db8:4000::/64 100 None
::ffff:192.0.2.4 None n/a
64501 524284
-------------------------------------------------------------------------------
Routes : 2
===============================================================================
The following output from PE-4 shows the IPv6 prefix 2001:db8:4000::/64 learned from CE-5.
*A:PE-4# show router 1 bgp routes ipv6
===============================================================================
BGP Router ID:192.0.2.41 AS:64502 Local AS:64502
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
u*>i 2001:db8:4000::/64 None None
2001:db8:2000::2 None 0
64501 -
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
The following command on PE-4 confirms that IPv6 prefix 2001:db8:3000::/64 is advertised to CE-5.
*A:PE-4# show router 1 bgp neighbor 2001:db8:2000::2 advertised-routes ipv6
===============================================================================
BGP Router ID:192.0.2.41 AS:64502 Local AS:64502
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
i 2001:db8:3000::/64 n/a None
2001:db8:2000::1 None n/a
64502 64502 -
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
The final verification of CE-1 and CE-5 shows that IPv6 routes for AS 64501 have been received and are valid across the VPRN service, as follows:
*A:CE-1# show router bgp routes ipv6
===============================================================================
BGP Router ID:192.0.2.1 AS:64501 Local AS:64501
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
u*>i 2001:db8:4000::/64 None None
2001:db8:1000::2 None 0
64502 64502 -
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
*A:CE-5# show router bgp routes ipv6
===============================================================================
BGP Router ID:192.0.2.5 AS:64501 Local AS:64501
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
===============================================================================
BGP IPv6 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id IGP Cost
As-Path Label
-------------------------------------------------------------------------------
u*>i 2001:db8:3000::/64 None None
2001:db8:2000::1 None 0
64502 64502 -
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
Conclusion
Spoke termination for IPv6-6VPE extends the use of spoke terminated interfaces from an Epipe VLL into a VPRN service using IPv6 interfaces on the access. Supporting the requirement of IPv6 interfaces, routing of IPv6 prefixes and the use of 6VPE for IPv6 tunneling over an IPv4 network allows SR OS to provide capabilities supporting the growth of IPv6 architectures.