Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

MPLS VPNV6 (IPv6-Fwd: Encapsulation failed.)

Hi,

I have tried to install MPLS VPNV6 between different MPLS PE I can see the routes inside the VRF and also the next-hope is reachable but I can’t ping between  two VRFs  in two different PEs

PE1# ping vrf ABC ipv6  2002:172:9::10 source  2002:172:9::1

………………………….

PE1#sh ipv6 route vrf AAA

LC  2002:172:9::1/128 [0/0]

     via Loopback1, receive

B   2002:172:9::10/128 [200/0]

     via 2002:9:9::10%default, indirectly connected

B   2002:172:116::/64 [200/0]

     via 2002:9:9::10%default, indirectly connected

L   FF00::/8 [0/0]

     via Null0, receive

PE2#sh ipv6 route vrf AAA

B   2002:172:9::1/128 [200/0]

     via 2002:9:9::1%default, indirectly connected

LC  2002:172:9::10/128 [0/0]

     via Loopback1, receive

C   2002:172:116::/64 [0/0]

     via Ethernet1/2, directly connected

L   2002:172:116::10/128 [0/0]

     via Ethernet1/2, receive

L   FF00::/8 [0/0]

     via Null0, receiv

and the below output for the debug in PE1 for IPV6 packet details

*Aug 19 17:28:45.639: IPv6-Fwd: Destination lookup for 2002:172:9::10 : i/f=Null0, nexthop=2002:9:9::10

*Aug 19 17:28:45.643: IPv6-Fwd: nexthop 2002:9:9::10,

*Aug 19 17:28:45.643: IPV6: source 2002:172:9::1 (local)

*Aug 19 17:28:45.643:       dest 2002:172:9::10 (Null0)

*Aug 19 17:28:45.643:       traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating

*Aug 19 17:28:45.643: IPv6-Fwd: Encapsulation failed.

  • MPLS
Everyone's tags (1)
6 REPLIES
Cisco Employee

MPLS VPNV6 (IPv6-Fwd: Encapsulation failed.)

Hi,

From above descriptio, Am I assuming right that you are trying to send the IPv6 traffic from one PE to otehr PE via MPLS cloud?.

It appears to have the nexthop as IPv6 which is not currently supported over mpls cloud. It should be set as v4-mapped-v6 address.

Can you share the configuration from both PEs?.

Regards,

Nagendra

New Member

MPLS VPNV6 (IPv6-Fwd: Encapsulation failed.)

Thank u Nagendra

this is PE1

router bgp 100

bgp router-id 9.9.0.1

no bgp default ipv4-unicast

bgp log-neighbor-changes

neighbor 9.9.0.8 remote-as 100

neighbor 9.9.0.8 update-source Loopback0

neighbor 9.9.0.9 remote-as 100

neighbor 9.9.0.9 update-source Loopback0

neighbor 9.9.0.10 remote-as 100

neighbor 9.9.0.10 update-source Loopback0

neighbor 9.9.12.2 remote-as 9

neighbor 2002:9:9::6 remote-as 100

neighbor 2002:9:9::6 update-source Loopback0

neighbor 2002:9:9::8 remote-as 100

neighbor 2002:9:9::8 update-source Loopback0

neighbor 2002:9:9::9 remote-as 100

neighbor 2002:9:9::9 update-source Loopback0

neighbor 2002:9:9::10 remote-as 100

neighbor 2002:9:9::10 update-source Loopback0

neighbor 2002:9:12::2 remote-as 9

!

address-family ipv4

  no synchronization

  network 9.9.0.1 mask 255.255.255.255

  neighbor 9.9.0.8 activate

  neighbor 9.9.0.8 send-community

  neighbor 9.9.0.8 route-reflector-client

  neighbor 9.9.0.8 next-hop-self

  neighbor 9.9.0.9 activate

  neighbor 9.9.0.9 send-community

  neighbor 9.9.0.9 route-reflector-client

  neighbor 9.9.0.9 next-hop-self

  neighbor 9.9.0.10 activate

  neighbor 9.9.0.10 send-community

  neighbor 9.9.0.10 route-reflector-client

  neighbor 9.9.0.10 next-hop-self

  neighbor 9.9.12.2 activate

  neighbor 9.9.12.2 send-community

  no auto-summary

exit-address-family

!

address-family vpnv4

  neighbor 9.9.0.8 activate

  neighbor 9.9.0.8 send-community both

  neighbor 9.9.0.8 next-hop-self

exit-address-family

!       

address-family ipv6

  no synchronization

  network 2002:9:9::1/128

  neighbor 2002:9:9::8 activate

  neighbor 2002:9:9::8 send-community

  neighbor 2002:9:9::8 next-hop-self

  neighbor 2002:9:12::2 activate

  neighbor 2002:9:12::2 send-community

exit-address-family

!

address-family vpnv6

  neighbor 2002:9:9::10 activate

  neighbor 2002:9:9::10 send-community both

  neighbor 2002:9:9::10 next-hop-self

exit-address-family

!

address-family ipv4 vrf AAA

  no synchronization

  redistribute connected

exit-address-family

!

address-family ipv6 vrf AAA

  redistribute connected

  no synchronization

exit-address-family

----------------------------------------------------------------------------------------

this is PE2

router bgp 100

bgp router-id 9.9.0.10

no bgp default ipv4-unicast

bgp log-neighbor-changes

neighbor 9.9.0.1 remote-as 100

neighbor 9.9.0.1 update-source Loopback0

neighbor 9.9.0.8 remote-as 100

neighbor 9.9.0.8 update-source Loopback0

neighbor 2002:9:9::1 remote-as 100

neighbor 2002:9:9::1 update-source Loopback0

neighbor 2002:9:9::8 remote-as 100

neighbor 2002:9:9::8 update-source Loopback0

!

address-family ipv4

  no synchronization

  network 9.9.0.10 mask 255.255.255.255

  neighbor 9.9.0.1 activate

  neighbor 9.9.0.1 send-community

  neighbor 9.9.0.8 activate

  neighbor 9.9.0.8 send-community

  no auto-summary

exit-address-family

!

address-family vpnv4

  neighbor 9.9.0.8 activate

  neighbor 9.9.0.8 send-community both

exit-address-family

!

address-family ipv6

  no synchronization

  network 2002:9:9::10/128

  neighbor 2002:9:9::8 activate

  neighbor 2002:9:9::8 send-community

exit-address-family

!

address-family vpnv6

  neighbor 2002:9:9::1 activate

  neighbor 2002:9:9::1 send-community both

exit-address-family

!

address-family ipv4 vrf AAA

  no synchronization

  redistribute connected

exit-address-family

!

address-family ipv6 vrf AAA

  redistribute connected

  no synchronization

exit-address-family

Cisco Employee

MPLS VPNV6 (IPv6-Fwd: Encapsulation failed.)

Hi,

address-family vpnv6

  neighbor 2002:9:9::1 activate

  neighbor 2002:9:9::1 send-community both

exit-address-family

As you might be aware, VPN services (ipv4 or IPv6) will be labeled before traversing the MPLS core. In otehr words, there will be 2 labels imposed before traversing the core. bottom label will be VPN labela nd top label will be IGP label to nexthop address (which will be your remote PE address).

In your case, nexthop or remote PE address will IPv6 address which is not currently supported as MPLS enabled on IPv6 core is yet to be supported.  You need to enable vpnv6 between IPv4 neighbor.

Can you try the VPNv6 session between IPv4 neighbor?.

HTH,

Nagendra

New Member

MPLS VPNV6 (IPv6-Fwd: Encapsulation failed.)

Hi Nagendra

but in this case you will have MPLS 6VPE technology if u enable IPV4 in VPNV6 , but I think the 6VPE technology u used it incase u don't have full IPV6 connection in your core but in my case I have full connection IPV6 BGP unicast

is this right ?

Cisco Employee

MPLS VPNV6 (IPv6-Fwd: Encapsulation failed.)

Hi,

Currently we need to use 6VPE if you need VPN service for IPv6. IPv6 in MPLS core is yet to be supported. As mentioned in my previous post, if nexthop is IPv6, we need label assigned to that IPv6 prefix which can be used as top label or IGP label.

LDP for IPv6 is not yet supported. So assigning/advertising  a label for IPv6 prefix is not supported yet.

Below is the link for LDP for IPv6,

http://tools.ietf.org/html/draft-ietf-mpls-ldp-ipv6-07

HTH,

Nagendra

New Member

MPLS VPNV6 (IPv6-Fwd: Encapsulation failed.)

Hi Nagendra,

yes you are right , i have also tried this and it's working

thank u very much for your suport

1619
Views
5
Helpful
6
Replies