[j-nsp] Advertizing routing table in routing instance

[Harry Reynolds]

Hello,

I believe that icmp message tunneling, which shipped in 6.2 I believe,
should work.  The description in the manual is rather poor. As I
understand, the TTL exceeded message will have the original label stack
added back on my the P router, where the message is label switched on
towards the destination. When it hits the end, the CE routes the message
back to the source with the correct label stack.

http://www.juniper.net/techpubs/software/junos/junos63/swconfig63-mpls-a
pps/html/mpls-signaled-config68.html#1061762


HTHs

 

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> Nugroho Wahyu Hidayat Adisubrata
> Sent: Monday, January 16, 2006 9:45 AM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Advertizing routing table in routing instance
> 
> Hi,
> I'm doing MPLS lab with MPLS like this.
> CE1----PE1----P1----P2----PE2-----CE2
> 
> Both of routing instance in PE can ping each other. But when 
> I do traceroute from CE1 to CE2, the result is like this:
>   1   <10 ms   <10 ms   <10 ms  30.1.1.1
>   2     *        *        *     Request timed out.
>   3     *        *        *     Request timed out.
>   4     *        *        *     Request timed out.
>   5     *        *        *     Request timed out.
>   6    15 ms    15 ms    15 ms  30.1.2.3
> 
> I think VRF in PE1 don't know P1 and P2 MPLS path.
> 
> What I should do to make routing-instance in PE1 cannot do 
> complete traceroute to routing-instance in PE2.
> 
> 
> Thanks for helping me :)
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>