[j-nsp] Advertizing routing table in routing instance
Doug Marschke
doug at ipath.net
Mon Jan 16 14:49:43 EST 2006
Turn on icmp-tunneling on the PE and P routers.
set protocols mpls icmp-tunneling
lab at Montreal# help reference mpls icmp-tunneling
icmp-tunneling
Syntax
icmp-tunneling;
Hierarchy
[edit logical-routers logical-router-name protocols mpls],
[edit protocols mpls]
Description
Enables ICMP tunneling, which can be used for debugging and tracing
purposes.
Usage Guidelines
See "Configure ICMP Message Tunneling".
Required Privilege Level
routing--To view this statement in the configuration.
routing-control--To add this statement to the configuratio
-----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
More information about the juniper-nsp
mailing list