[j-nsp] LDP issues

Christian Malo chris at fiberpimp.net
Thu Jan 25 10:13:53 EST 2007


I do get the routes in the ldp database and to Reply to Sergio's email:

**@**> show ldp database | match "Input|L2CKT" 
Input label database, x.x.x.109:0--x.x.x.110:0
Input label database, x.x.x.109:0--x.x.x.124:0
Input label database, x.x.x.109:0--x.x.x.125:0

Neighbor: x.x.x.124
    Interface                 Type  St     Time last up          # Up trans
    fe-0/0/3.0(vc 500)        rmt   VC-Dn  -----                          0
      Local interface: fe-0/0/3.0, Status: Up, Encapsulation: ETHERNET
      Remote PE: x.x.x.124, Negotiated control-word: No
      Incoming label: 310240, Outgoing label: 195

-chris


-----Original Message-----
From: Doug Marschke [mailto:doug at ipath.net] 
Sent: Wednesday, January 24, 2007 5:35 PM
To: 'Christian Malo'; juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] LDP issues

Are the routes also installed as IGP routes?
Due to ordered control, the L2circuit neighbor must be an IGP route.

Do you see labels advertised with show ldp database?

Doug


-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Christian Malo
Sent: Wednesday, January 24, 2007 2:12 PM
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] LDP issues

That's the simple setup I have


         6500-sup720
 	    |
 	    |
 	    |
            m5 -------- m20------> bunch of other routers



I have ldp enabled on every router and the m20 has no problems setting up 
l2circuits to every router except the m5 and 6500.

I noticed on the m5 that it doesn't have any LDP routes from the m20 but 
has 1 from the 6509.

The configuration for both interfaces are the same and the mpls/ldp 
configs are similar.


**@***# run show route protocol ldp

inet.0: 206261 destinations, 411236 routes (206240 active, 0 holddown, 21 
hidden)
+ = Active Route, - = Last Active, * = Both

x.x.x.x125/32   [LDP/9] 00:20:08, metric 1
                     > to x.x.x.78 via ge-0/2/0.0

inet.1: 163 destinations, 163 routes (163 active, 0 holddown, 0 hidden)

inet.3: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

x.x.x.125/32   [LDP/9] 00:20:09, metric 1
                     > to x.x.x.78 via ge-0/2/0.0

inet.4: 163 destinations, 163 routes (163 active, 0 holddown, 0 hidden)

mpls.0: 17 destinations, 17 routes (17 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

310464             *[LDP/9] 00:20:09, metric 1
                     > to x.x.x.78 via ge-0/2/0.0, Pop
310464(S=0)        *[LDP/9] 00:20:09, metric 1
                     > to x.x.x.78 via ge-0/2/0.0, Pop

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

__juniper_private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 
holddown, 0 hidden)

l2circuit.0: 1 destinations, 1 routes (0 active, 0 holddown, 1 hidden)

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


125 is the loopback address of the 6509
110 is the loopback address of the m20
124 is the loopback address of a router being the m20

**@**# run show ldp neighbor
Address            Interface          Label space ID         Hold time
x.x.x.124     lo0.0              x.x.x.124:0         89
x.x.x.74      ge-0/3/0.0         x.x.x.110:0         10
x.x.x.78      ge-0/2/0.0         x.x.x.125:0         12


**@**# run show ldp session
   Address           State        Connection     Hold time
x.x.x.110      Operational  Open             22
x.x.x.124      Operational  Open             172
x.x.x.125      Operational  Open             174


m5 is running 6.3
m20 is running 7.4r1.7


Do you guys have any idea?


-chris
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp



More information about the juniper-nsp mailing list