Community discussions

MikroTik App
 
volga629
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 77
Joined: Tue Nov 19, 2013 6:21 am

LDP VPLS CHR OS 7rc6

Fri Nov 19, 2021 5:37 am

Hello Everyone,
On latest CHR RC6 LDP for VPLS is trying init and failing. I defined log and recorded my screen. I need help to identify if it this bug.
[admin@aitmuosmt01] > /log/print 
 03:34:06 route,ldp,debug     192.31.2.1
 03:34:06 route,ldp,debug     72.139.93.26
 03:34:06 route,ldp,debug     10.41.100.1
 03:34:06 route,ldp,debug     10.1.1.1
 03:34:06 route,ldp,debug     10.180.180.1
 03:34:06 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:06 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:06 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:06 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:06 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:06 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:06 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:06 route,ldp,debug     GenericLabel 16
 03:34:06 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:06 route,ldp,debug     Status 0x80000005
 03:34:06 route,ldp,debug 10.1.1.1/10.1.1.1:0 attempt active connect 10.1.1.3->10.1.1.1
 03:34:06 route,ldp,debug 10.1.1.1:0 operational
 03:34:07 route,ldp,debug 10.1.1.1:0 Address message
 03:34:07 route,ldp,debug     10.0.29.2
 03:34:07 route,ldp,debug     192.31.2.1
 03:34:07 route,ldp,debug     72.139.93.26
 03:34:07 route,ldp,debug     10.41.100.1
 03:34:07 route,ldp,debug     10.1.1.1
 03:34:07 route,ldp,debug     10.180.180.1
 03:34:07 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:07 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:07 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:07 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:07 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:07 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:07 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:07 route,ldp,debug     GenericLabel 16
 03:34:07 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:07 route,ldp,debug     Status 0x80000005
 03:34:07 route,ldp,debug 10.1.1.1/10.1.1.1:0 attempt active connect 10.1.1.3->10.1.1.1
 03:34:07 route,ldp,debug 10.1.1.1:0 operational
 03:34:08 route,ldp,debug 10.1.1.1:0 Address message
 03:34:08 route,ldp,debug     10.0.29.2
 03:34:08 route,ldp,debug     192.31.2.1
 03:34:08 route,ldp,debug     72.139.93.26
 03:34:08 route,ldp,debug     10.41.100.1
 03:34:08 route,ldp,debug     10.1.1.1
 03:34:08 route,ldp,debug     10.180.180.1
 03:34:08 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:08 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:08 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:08 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:08 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:08 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:08 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:08 route,ldp,debug     GenericLabel 16
 03:34:08 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:08 route,ldp,debug     Status 0x80000005
 03:34:08 route,ldp,debug 10.1.1.1/10.1.1.1:0 attempt active connect 10.1.1.3->10.1.1.1
 03:34:08 route,ldp,debug 10.1.1.1:0 gre-tun1 Hello, transport 10.1.1.1, HoldTime 15, preferred AF <unspecified>
 03:34:08 route,ldp,debug 10.1.1.1:0 operational
 03:34:09 route,ldp,debug 10.1.1.1:0 Address message
 03:34:09 route,ldp,debug     10.0.29.2
 03:34:09 route,ldp,debug     192.31.2.1
 03:34:09 route,ldp,debug     72.139.93.26
 03:34:09 route,ldp,debug     10.41.100.1
 03:34:09 route,ldp,debug     10.1.1.1
 03:34:09 route,ldp,debug     10.180.180.1
 03:34:09 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:09 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:09 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:09 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:09 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:09 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:09 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:09 route,ldp,debug     GenericLabel 16
 03:34:09 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:09 route,ldp,debug     Status 0x80000005
 03:34:09 route,ldp,debug 10.1.1.1/10.1.1.1:0 attempt active connect 10.1.1.3->10.1.1.1
 03:34:09 route,ldp,debug 10.1.1.1:0 targeted Hello, transport 10.1.1.1, HoldTime 45, preferred AF <unspecified>
 03:34:09 route,ldp,debug 10.1.1.1:0 operational
 03:34:10 route,ldp,debug 10.1.1.1:0 Address message
 03:34:10 route,ldp,debug     10.0.29.2
 03:34:10 route,ldp,debug     192.31.2.1
 03:34:10 route,ldp,debug     72.139.93.26
 03:34:10 route,ldp,debug     10.41.100.1
 03:34:10 route,ldp,debug     10.1.1.1
 03:34:10 route,ldp,debug     10.180.180.1
 03:34:10 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:10 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:10 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:10 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:10 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:10 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:10 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:10 route,ldp,debug     GenericLabel 16
 03:34:10 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:10 route,ldp,debug     Status 0x80000005
 03:34:10 route,ldp,debug 10.1.1.1/10.1.1.1:0 attempt active connect 10.1.1.3->10.1.1.1
 03:34:10 route,ldp,debug 10.1.1.1:0 operational
 03:34:11 route,ldp,debug 10.1.1.1:0 Address message
 03:34:11 route,ldp,debug     10.0.29.2
 03:34:11 route,ldp,debug     192.31.2.1
 03:34:11 route,ldp,debug     72.139.93.26
 03:34:11 route,ldp,debug     10.41.100.1
 03:34:11 route,ldp,debug     10.1.1.1
 03:34:11 route,ldp,debug     10.180.180.1
 03:34:11 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:11 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:11 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:11 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:11 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:11 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:11 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:11 route,ldp,debug     GenericLabel 16
 03:34:11 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:11 route,ldp,debug     Status 0x80000005
 03:34:11 route,ldp,debug 10.1.1.1/10.1.1.1:0 attempt active connect 10.1.1.3->10.1.1.1
 03:34:11 route,ldp,debug 10.1.1.1:0 operational
 03:34:12 route,ldp,debug 10.1.1.1:0 Address message
 03:34:12 route,ldp,debug     10.0.29.2
 03:34:12 route,ldp,debug     192.31.2.1
 03:34:12 route,ldp,debug     72.139.93.26
 03:34:12 route,ldp,debug     10.41.100.1
 03:34:12 route,ldp,debug     10.1.1.1
 03:34:12 route,ldp,debug     10.180.180.1
 03:34:12 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:12 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:12 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:12 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:12 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:12 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:12 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:12 route,ldp,debug     GenericLabel 16
 03:34:12 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:12 route,ldp,debug     Status 0x80000005
 03:34:12 route,ldp,debug 10.1.1.1/10.1.1.1:0 attempt active connect 10.1.1.3->10.1.1.1
 03:34:12 route,ldp,debug 10.1.1.1:0 operational
 03:34:13 route,ldp,debug 10.1.1.1:0 Address message
 03:34:13 route,ldp,debug     10.0.29.2
 03:34:13 route,ldp,debug     192.31.2.1
 03:34:13 route,ldp,debug     72.139.93.26
 03:34:13 route,ldp,debug     10.41.100.1
 03:34:13 route,ldp,debug     10.1.1.1
 03:34:13 route,ldp,debug     10.180.180.1
 03:34:13 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:13 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:13 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:13 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:13 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:13 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:13 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:13 route,ldp,debug     GenericLabel 16
 03:34:13 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:13 route,ldp,debug     Status 0x80000005
 03:34:13 route,ldp,debug 10.1.1.1/10.1.1.1:0 attempt active connect 10.1.1.3->10.1.1.1
 03:34:13 route,ldp,debug 10.1.1.1:0 gre-tun1 Hello, transport 10.1.1.1, HoldTime 15, preferred AF <unspecified>
 03:34:13 route,ldp,debug 10.1.1.1:0 operational
 03:34:14 route,ldp,debug 10.1.1.1:0 Address message
 03:34:14 route,ldp,debug     10.0.29.2
 03:34:14 route,ldp,debug     192.31.2.1
 03:34:14 route,ldp,debug     72.139.93.26
 03:34:14 route,ldp,debug     10.41.100.1
 03:34:14 route,ldp,debug     10.1.1.1
 03:34:14 route,ldp,debug     10.180.180.1
 03:34:14 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:14 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:14 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:14 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:14 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:14 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:14 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:14 route,ldp,debug     GenericLabel 16
 03:34:14 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:14 route,ldp,debug     Status 0x80000005
 03:34:14 route,ldp,debug 10.1.1.1/10.1.1.1:0 attempt active connect 10.1.1.3->10.1.1.1
 03:34:14 route,ldp,debug 10.1.1.1:0 operational
 03:34:15 route,ldp,debug 10.1.1.1:0 Address message
 03:34:15 route,ldp,debug     10.0.29.2
 03:34:15 route,ldp,debug     192.31.2.1
 03:34:15 route,ldp,debug     72.139.93.26
 03:34:15 route,ldp,debug     10.41.100.1
 03:34:15 route,ldp,debug     10.1.1.1
 03:34:15 route,ldp,debug     10.180.180.1
 03:34:15 route,ldp,debug 10.1.1.1:0 address 10.0.29.2
 03:34:15 route,ldp,debug 10.1.1.1:0 address 192.31.2.1
 03:34:15 route,ldp,debug 10.1.1.1:0 address 72.139.93.26
 03:34:15 route,ldp,debug 10.1.1.1:0 address 10.41.100.1
 03:34:15 route,ldp,debug 10.1.1.1:0 address 10.1.1.1
 03:34:15 route,ldp,debug 10.1.1.1:0 address 10.180.180.1
 03:34:15 route,ldp,debug 10.1.1.1:0 LabelMapping message
 03:34:15 route,ldp,debug     GenericLabel 16
 03:34:15 route,ldp,debug 10.1.1.1:0 Notification message
 03:34:15 route,ldp,debug     Status 0x80000005


Last edited by volga629 on Fri Nov 19, 2021 5:42 am, edited 1 time in total.
 
volga629
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 77
Joined: Tue Nov 19, 2013 6:21 am

Re: LDP VPLS OS 7rc6

Fri Nov 19, 2021 5:38 am

On remote router I see in log

Nov 18 23:28:32 canlrt01 LDP[11601]:  LDP-3: ldp_message_label_mapping_recv: LDP Label Mapping message decode error -2
Nov 18 23:28:32 canlrt01 LDP[11601]:  LDP-6:
Nov 18 23:28:32 canlrt01 LDP[11601]:  LDP-6: 00 01 00 34 0a 01 01 03 00 00 04 00 00 2a
Nov 18 23:28:32 canlrt01 LDP[11601]:  LDP-6: 00 01 c9 a6 01 00 00 12 81 80 05 0e 01 08
Nov 18 23:28:32 canlrt01 LDP[11601]:  LDP-6: 00 00 00 00 00 00 00 00 01 00 01 00 02 00
Nov 18 23:28:32 canlrt01 LDP[11601]:  LDP-6: 00 04 00 00 00 10 09 6a 00 04 00 00 00 00
Nov 18 23:28:32 canlrt01 LDP[11601]:  LDP-6:
Nov 18 23:28:32 canlrt01 LDP[11601]:  LDP-4: ldp_message_notification_send: Fatal notification code 5 being sent to peer 10.1.1.3
Nov 18 23:28:33 canlrt01 LDP[11601]:  LDP-3: Panic !! Accept count is negative !!
Nov 18 23:28:33 canlrt01 LDP[11601]:  LDP-3: ldp_message_label_mapping_recv: LDP Label Mapping message decode error -2

 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: LDP VPLS CHR OS 7rc6

Fri Nov 19, 2021 5:49 am

Yes,

VPLS is broken in rc6 and the other rc's before. It doesn't transmit for a bit and then causes spontaneous reboots of the routers. I'm hoping to see improvements in rc7.
 
volga629
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 77
Joined: Tue Nov 19, 2013 6:21 am

Re: LDP VPLS CHR OS 7rc6

Fri Nov 19, 2021 5:54 am

Thank you for quick reply. I will keep topic open for future releases.
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 2096
Joined: Mon Jan 14, 2008 1:53 pm
Location: Over the Rainbow
Contact:

Re: LDP VPLS CHR OS 7rc6

Sat Nov 20, 2021 3:40 am

Hrmm, I'm surprised to see this post.

VPLS is working very stable for me in 7.1rc6 on CHR. Running with PCIe pass-thru of Intel NIC's

I had to add the tunnel from the CLI as WinBox was flaky
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: LDP VPLS CHR OS 7rc6

Sat Nov 20, 2021 12:34 pm

VPLS is working very stable for me in 7.1rc6 on CHR. Running with PCIe pass-thru of Intel NIC's
I haven't tried with CHR, but for both me and another user who are testing, VPLS has not worked successfully since it turned "green" on the v7 Routing Protocol Status page. It is a simple config with static routes (no OSPF) for the loopbacks and LDP, just two routers with the VPLS tunnel in between - the tunnel comes up after bouncing it, but the moment a packet gets sent across and received successfully by the other side, both routers crash and reboot. I have to disable the VPLS tunnel using the console port on one side before the VPLS interface comes up to prevent both routers from booting up again, the tunnel coming up and then the crash and reboot repeating.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: LDP VPLS CHR OS 7rc6

Thu Nov 25, 2021 6:59 am

VPLS is working very stable for me in 7.1rc6 on CHR. Running with PCIe pass-thru of Intel NIC's
I had someone else confirm it works on CHR but is broken on all of the hardware routers. It still should not be green on the v7 Routing Protocol Status page if it only works on CHR and nothing else.
 
volga629
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 77
Joined: Tue Nov 19, 2013 6:21 am

Re: LDP VPLS CHR OS 7rc6

Mon Nov 29, 2021 5:11 am

Hrmm, I'm surprised to see this post.

VPLS is working very stable for me in 7.1rc6 on CHR. Running with PCIe pass-thru of Intel NIC's

I had to add the tunnel from the CLI as WinBox was flaky
The differences that remote end is not mikrotik
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 2096
Joined: Mon Jan 14, 2008 1:53 pm
Location: Over the Rainbow
Contact:

Re: LDP VPLS CHR OS 7rc6

Mon Nov 29, 2021 6:40 am

I have it running from a CHR to a RB5009 and it is stable on both platforms.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: LDP VPLS CHR OS 7rc6

Mon Nov 29, 2021 7:14 am

I have it running from a CHR to a RB5009 and it is stable on both platforms.
Are you running it with static routing only? Or OSPF? The instability that myself and others are experiencing is with static routing only, no OSPF. It just crashes the entire device, it doesn't pass anything. We are testing static routing with MPLS as the basic config.

Who is online

Users browsing this forum: No registered users and 18 guests