Re: [j-nsp] LDP issues
I disabled RSVP on the interface facing the m20 and it works now . why would that affect ldp operations? -chris From: Sergio D. [mailto:[EMAIL PROTECTED] Sent: Thursday, January 25, 2007 11:34 AM To: [EMAIL PROTECTED]; juniper-nsp@puck.nether.net Subject: Re: [j-nsp] LDP issues Chris, Was this output from the M20 or M5? a "show configuration protocols ldp" from both routers will help also. I do get the routes in the ldp database and to Reply to Sergio's email: [EMAIL PROTECTED]> 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 -- Sergio Danellli JNCIE #170 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] LDP issues
Chris, Was this output from the M20 or M5? a "show configuration protocols ldp" from both routers will help also. I do get the routes in the ldp database and to Reply to Sergio's email: [EMAIL PROTECTED]> 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 -- Sergio Danellli JNCIE #170 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] LDP issues
[EMAIL PROTECTED]> show ldp session detail Address: x.x.x.110, State: Operational, Connection: Open, Hold time: 29 Session ID: x.x.x.109:0--x.x.x.110:0 Next keepalive in 1 seconds Passive, Maximum PDU: 4096, Hold time: 30, Neighbor count: 1 Keepalive interval: 10, Connect retry interval: 1 Local address: x.x.x.109, Remote address: x.x.x.110 Up for 17:33:55 Local - Restart: disabled, Helper mode: enabled Remote - Restart: enabled, Helper mode: enabled, Reconnect time: 6 Local maximum recovery time: 24 msec Next-hop addresses received: x.x.x.65 x.x.x.69 x.x.x.74 x.x.x.85 x.x.x.89 x.x.x.110 Address: x.x.x.124, State: Operational, Connection: Open, Hold time: 176 Session ID: x.x.x.109:0--x.x.x.124:0 Next keepalive in 2 seconds Passive, Maximum PDU: 4096, Hold time: 180, Neighbor count: 1 Keepalive interval: 10, Connect retry interval: 1 Local address: x.x.x.109, Remote address: x.x.x.124 Up for 17:33:56 Local - Restart: disabled, Helper mode: enabled Remote - Restart: disabled, Helper mode: disabled Local maximum recovery time: 24 msec Next-hop addresses received: x.x.x.124 x.x.x.90 x.x.x.5 Address: x.x.x.125, State: Operational, Connection: Open, Hold time: 175 Session ID: x.x.x.109:0--x.x.x.125:0 Next keepalive in 2 seconds Passive, Maximum PDU: 4096, Hold time: 180, Neighbor count: 1 Keepalive interval: 10, Connect retry interval: 1 Local address: x.x.x.109, Remote address: x.x.x.125 Up for 17:33:57 Local - Restart: disabled, Helper mode: enabled Remote - Restart: disabled, Helper mode: disabled Local maximum recovery time: 24 msec Next-hop addresses received: x.x.x.125 x.x.x.78 [EMAIL PROTECTED]> show route table inet.3 inet.3: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both x.x.x.110/32 *[RSVP/7] 8w5d 22:31:53, metric 1 > to x.x.x.74 via ge-0/3/0.0, label-switched-path X.Y to x.x.x.74 via ge-0/3/0.0, label-switched-path X.Y x.x.x.111/32 *[RSVP/7] 7w5d 19:20:03, metric 2 > to x.x.x.74 via ge-0/3/0.0, label-switched-path X.Y x.x.x.112/32 *[RSVP/7] 7w5d 19:19:58, metric 2 > to x.x.x.74 via ge-0/3/0.0, label-switched-path X.Y x.x.x.125/32 *[RSVP/7] 5w1d 17:47:25, metric 2 > to x.x.x.78 via ge-0/2/0.0, label-switched-path X.Y [LDP/9] 17:35:30, metric 1 > to x.x.x.78 via ge-0/2/0.0 As you can see, I get the LDP route on ge-0/2/0 (6509). -chris From: Sergio D. [mailto:[EMAIL PROTECTED] Sent: Thursday, January 25, 2007 1:51 AM To: [EMAIL PROTECTED]; juniper-nsp@puck.nether.net Subject: Re: [j-nsp] LDP issues This can also be an extended LDP discovery issue. Can you possibly share your ldp configuration for the problem juniper routers, a show ldp database | match "Input|L2CKT" , and a show l2circuit connections. 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. [EMAIL PROTECTED] 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 [EMAIL PROTECTED] run show ldp neighbor AddressInterface
Re: [j-nsp] LDP issues
I do get the routes in the ldp database and to Reply to Sergio's email: [EMAIL PROTECTED]> 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:[EMAIL PROTECTED] Sent: Wednesday, January 24, 2007 5:35 PM To: 'Christian Malo'; juniper-nsp@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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Malo Sent: Wednesday, January 24, 2007 2:12 PM To: juniper-nsp@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. [EMAIL PROTECTED] 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 [EMAIL PROTECTED] run show ldp neighbor AddressInterface 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 [EMAIL PROTECTED] run show ldp session Address StateConnection 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] LDP issues
This can also be an extended LDP discovery issue. Can you possibly share your ldp configuration for the problem juniper routers, a show ldp database | match "Input|L2CKT" , and a show l2circuit connections. 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. [EMAIL PROTECTED] 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 [EMAIL PROTECTED] run show ldp neighbor AddressInterface 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 [EMAIL PROTECTED] run show ldp session Address StateConnection 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 -- Sergio Danellli JNCIE #170 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Malo Sent: Wednesday, January 24, 2007 2:12 PM To: juniper-nsp@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. [EMAIL PROTECTED] 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 [EMAIL PROTECTED] run show ldp neighbor AddressInterface 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 [EMAIL PROTECTED] run show ldp session Address StateConnection 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[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. [EMAIL PROTECTED] 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 [EMAIL PROTECTED] run show ldp neighbor AddressInterface 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 [EMAIL PROTECTED] run show ldp session Address StateConnection 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
