Got it

LSP tracert command does not work

Created: Sep 20, 2021 11:11:37Latest reply: Sep 20, 2021 11:17:36 209 5 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

Hello



I have a problem wanting to check the MPLS connection and accessibility with static LSP using the tracert command.


I attach a capture of the error as well as the topology used.


Thank you very much for the help.


tracert error

topology


LSP status



Thank you.



Featured Answers
E.DR_91
MVE Author Created Sep 20, 2021 11:13:48

Hi

Could you try pinging towards the ip 10.20.30.0 please?

I remember that you do not test a point ip but the mpls tunnel itself.



View more
  • x
  • convention:

tubaboraka
tubaboraka Created Sep 20, 2021 11:21:06 (0) (0)
Thank you

I do it , It's work now

<PE1>ping lsp ip 20.20.30.0 24 nexthop 10.10.10.10 LSP PING FEC: IPV4 PREFIX 20.20.30.0/24/ : 100 data bytes, press CTRL_C to br eak Reply from 10.10.80.1: bytes=100 Sequence=1 time=70 ms Reply from 10.10.80.1: bytes=100 Sequence=2 time=40 ms Reply from 10.10.80.1: bytes=100 Sequence=3 time=30 ms Reply from 10.10.80.1:
bytes=100 Sequence=4 time=40
ms Reply from 10.10.80.1: bytes=100 Sequence=5 time=30 ms

--- FEC: IPV4 PREFIX 20.20.30.0/24 ping 

Recommended answer

AymanOT
MVE Author Created Sep 20, 2021 11:17:36

Hello my dear, for it to work you must add the next-hop to your command, I send you an example:


<Router>ping lsp ip 10.2.1.138 32 nexthop 10.2.18.10

LSP PING FEC: IPV4 PREFIX 10.2.1.138/32/ : 100 data bytes, press CTRL_C to break

Reply from 10.2.1.138: bytes=100 Sequence=1 time=2 ms Reply from 10.2.1.138: bytes=100 Sequence=2 time=1 ms Reply from 10.2.1.138: bytes=100 Sequence=3 time=1

ms Reply from 10.2.1.138: bytes=100 Sequence=4 time=1 ms

Reply from 10.2.1.138: bytes=100

Sequence=5 time=1 ms --- FEC: IPV4 PREFIX 10.2.1.138/32 ping statistics ---

5 packet(s) transmitted

5 packet(s) received

0.00% packet loss

round-trip min/avg/max = 1/1/2 ms
View more
  • x
  • convention:

All Answers
Hi,
We've noticed about your problem, and we're processing on.
View more
  • x
  • convention:

E.DR_91
E.DR_91 MVE Author Created Sep 20, 2021 11:13:48

Hi

Could you try pinging towards the ip 10.20.30.0 please?

I remember that you do not test a point ip but the mpls tunnel itself.



View more
  • x
  • convention:

tubaboraka
tubaboraka Created Sep 20, 2021 11:21:06 (0) (0)
Thank you

I do it , It's work now

<PE1>ping lsp ip 20.20.30.0 24 nexthop 10.10.10.10 LSP PING FEC: IPV4 PREFIX 20.20.30.0/24/ : 100 data bytes, press CTRL_C to br eak Reply from 10.10.80.1: bytes=100 Sequence=1 time=70 ms Reply from 10.10.80.1: bytes=100 Sequence=2 time=40 ms Reply from 10.10.80.1: bytes=100 Sequence=3 time=30 ms Reply from 10.10.80.1:
bytes=100 Sequence=4 time=40
ms Reply from 10.10.80.1: bytes=100 Sequence=5 time=30 ms

--- FEC: IPV4 PREFIX 20.20.30.0/24 ping 
tubaboraka
tubaboraka MVE Author Created Sep 20, 2021 11:15:13

.

View more
  • x
  • convention:

AymanOT
AymanOT MVE Author Created Sep 20, 2021 11:17:36

Hello my dear, for it to work you must add the next-hop to your command, I send you an example:


<Router>ping lsp ip 10.2.1.138 32 nexthop 10.2.18.10

LSP PING FEC: IPV4 PREFIX 10.2.1.138/32/ : 100 data bytes, press CTRL_C to break

Reply from 10.2.1.138: bytes=100 Sequence=1 time=2 ms Reply from 10.2.1.138: bytes=100 Sequence=2 time=1 ms Reply from 10.2.1.138: bytes=100 Sequence=3 time=1

ms Reply from 10.2.1.138: bytes=100 Sequence=4 time=1 ms

Reply from 10.2.1.138: bytes=100

Sequence=5 time=1 ms --- FEC: IPV4 PREFIX 10.2.1.138/32 ping statistics ---

5 packet(s) transmitted

5 packet(s) received

0.00% packet loss

round-trip min/avg/max = 1/1/2 ms
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.