Routing
Routing

Loss bypass-lsp via ldp

‎03-15-2019 02:23 AM

Hi 

 

I met one problem. We have three routers - HK/JP/TWa and connect each other with one link.

Moreover, runs MPLS/RSVP/LDP with dymanic-rsvp-lsp/IS-IS on these three routers.

 

One day, we lose bypass-lsp between HK and JP. But HK-TW and JP-TW is fine.

Also, session flag lost some function, and just can find lsp on table mpls.0 .

 

Could you give me some suggesstion to figure it out ?

 

Thanks

Cloud

 

HK> show route 192.168.131.10

inet.0: 746544 destinations, 3732194 routes (746544 active, 1 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.131.10/32 *[LDP/9] 00:24:29, metric 5
> to192.168.131.109 via xe-0/2/0.0
to192.168.131.37 via ae5.1, label-switched-path xe-0/2/0.0:BypassLSP->192.168.131.10

 

HK> show route 192.168.131.2

inet.0: 746544 destinations, 3732197 routes (746544 active, 1 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.131.2/32 *[LDP/9] 00:27:36, metric 5
> to192.168.131.37 via ae5.1

 

JP> show ldp session 192.168.131.4 extensive | match flag
Session flags: none

 

JP> show ldp session 192.168.131.10 extensive | match flag
Session flags: link protection, dynamic rsvp lsp

 

JP> show route192.168.131.10

inet.0: 746558 destinations, 3107965 routes (746558 active, 2 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.131.10/32 *[LDP/9] 00:29:16, metric 5
> to192.168.131.113 via xe-0/0/2.0
to 192.168.131.113 via xe-0/0/2.0, label-switched-path xe-0/0/2.0:BypassLSP->192.168.131.10

 

JP> show route192.168.131.4

inet.0: 746557 destinations, 3107963 routes (746557 active, 2 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.131.4/32 *[LDP/9] 00:29:23, metric 5
> to 192.168.131.38 via ae5.1

 

JP> show route table mpls.0

> to 192.168.131.38 via ae5.1, label-switched-path xe-1/2/2.0:BypassLSP->192.168.131.4
441008(S=0) *[RSVP/7/1] 05:44:00, metric 1
> to 192.168.131.38 via ae5.1, label-switched-path xe-1/2/2.0:BypassLSP->192.168.131.4
441024 *[RSVP/7/1] 05:34:00, metric 1

 

螢幕快照 2019-03-15 下午5.13.22.png

Attachments

4 REPLIES 4
Routing

Re: Loss bypass-lsp via ldp

‎03-15-2019 02:54 AM

Hi,

 

There is more information required in order to help you with this issue.

From attached configuration I do not see RSVP configuration and MPLS LSPs configuration.

Additionally, please provide output from "show mpls lsp extensive" from all routers.

 

Regards,

Roman

Routing

Re: Loss bypass-lsp via ldp

‎03-15-2019 03:22 AM

Hi 

 

I attach about mpls lsp extensive.

 

Thanks for your reply

Cloud

Attachments

Routing

Re: Loss bypass-lsp via ldp

‎03-15-2019 06:05 AM

Hi,

 

From "show mpls lsp extensive" output it is clearly seen there are no respective bypass LSPs. E.g. they are not down, but they are not present at all.

I tried to load your config in the lab and see bypass LSPs for all LDP sessions.

Do you have firewalls configured on lo0 or transit interfaces?

Are all isis adjacencies in up state?

Please provide following outputs from all routers:

show isis interface

show isis adjacency

show ldp neighbor

show ldp session extensive

show rsvp interface

show rsvp neighbor

show rsvp session

 

Thanks,

Roman

 

 

Routing

Re: Loss bypass-lsp via ldp

‎03-24-2019 07:23 PM

Hi 


@Roman Evsigneev wrote:

Hi,

 

From "show mpls lsp extensive" output it is clearly seen there are no respective bypass LSPs. E.g. they are not down, but they are not present at all.

I tried to load your config in the lab and see bypass LSPs for all LDP sessions.

Do you have firewalls configured on lo0 or transit interfaces?

Are all isis adjacencies in up state?

Please provide following outputs from all routers:

show isis interface

show isis adjacency

show ldp neighbor

show ldp session extensive

show rsvp interface

show rsvp neighbor

show rsvp session

 

Thanks,

Roman

 

 


 

I found the problem what RSVP session is stuck because we have private and public address on the same interface.

That causes RSVP session unstable and can't work normally.

 

Thanks for assistance.

Cloud