[j-nsp] ICMPv6 & 6PE network

snort bsd snortbsd at yahoo.com.au
Wed Jun 4 03:35:35 EDT 2008


Thanks again. Yes, I missed one end of "family inet6" (core-facing interface). It is working.

The LSP uses lookpback, but the ICMPv6 uses interface.

Best


----- Original Message ----
From: Stacy W. Smith <stacy at acm.org>
To: snort bsd <snortbsd at yahoo.com.au>
Cc: juniper-nsp <juniper-nsp at puck.nether.net>
Sent: Tuesday, 3 June, 2008 7:03:37 PM
Subject: Re: [j-nsp] ICMPv6 & 6PE network


On Jun 3, 2008, at 7:46 PM, snort bsd wrote:

> Hello all:
>
> I used MPLS LSP connecting two different IPv6 domains (6PE,  
> RFC4798). Both sides (IPv6 domains) see each other IPv6 routes,  
> which means my IPv4 MPLS based backbone successfully delivered the  
> IPv6 routes. But for some reasons, both customers can't ping each  
> other even though they can see each other IPv6 routes. Somehow the  
> IPv4 MPLS backbone is blocking the ICMP traffic.
>
> Any ideas?

Is "family mpls" enabled on all interfaces that the LSP traverses? On  
the PE routers, do you have "family inet6" configured on both the CE- 
facing interfaces and the core-facing interfaces? "family inet6" is  
required on the core-facing interfaces in order to process the IPv6  
packets received with MPLS label 2.

http://www.juniper.net/techpubs/software/junos/junos83/feature-guide-83/html/fg-ipv6-over-mpls6.html

--Stacy


      Get the name you always wanted with the new y7mail email address.
www.yahoo7.com.au/mail


More information about the juniper-nsp mailing list