Community discussions

MikroTik App
 
typoon1426
just joined
Topic Author
Posts: 5
Joined: Wed Nov 10, 2021 8:46 pm

crs309 v7.1rc6 MPLS Problem

Thu Nov 11, 2021 7:18 pm

Hello everyone, I'm trying to set a lab with a RB4011 and two CRS309-1G-8S+ linked as following:

RB4011-1 sfp-sfpplus1 <-> sfp-sfpplus3 CRS-SW1 sfp-sfpplus1 <-> sfp-sfpplus1 CRS-SW2

With ROS version = 6.48.5 on 4011 and CRS-SW1 and v7.1rc6 on CRS-SW2 (l3hw disabled)

RB4011 and CRS-SW2 configured as MPLS PE and CRS-SW1 as MPLS P.

I try to connect via ebgp or ibgp peer(is not important at the moment) the 4011 and CRS-SW2 via their loopback address, but the peers never establish.

I check with a simple ping with commands:
[admin@4011-1]  /ping src-address=10.0.1.3 10.0.1.1
[admin@CRS309-SW2]  /ping src-address=10.0.1.1 10.0.1.3

but i have no reply from and to both endpoints.


Following i sniff packets on the interlink interface between all devices with test ping running and i found two different behaviors.

With ping run from 10.0.1.3 to 10.0.1.1 4011-> CRS-SW2, i can capture the packet in every interface on path with correct mpls label based on forwarding table of egress router
but i can not capture any reply from CRS-SW2, it appears to be reject packets or do not send replies

With ping run from opposite direction CRS-SW2 -> 4011, i can capture the packets and the replies on entire path again with correct mpls label, but CRS-SW2 print timeout,.

I attach the conf of all device and the MPLS Forwarding table .

Thanks a lot in advance.

[admin@4011-1] /mpls forwarding-table> print 
 0    expl-null                                     
 1  L 106                                            expl-null                                      10.0.1.0/32                    sfp-sfpplus1                                  10.255.255.5   
 2  L 109   
                                          74                                             10.0.1.1/32                    sfp-sfpplus1                                  10.255.255.5  
# CONFIGURATION
/interface bridge
add comment=LOOPBACK name=loopback protocol-mode=none

/interface ethernet
set [ find default-name=sfp-sfpplus1 ] l2mtu=1584

/routing bgp instance
set default as=4200000000 router-id=10.0.1.3

/routing ospf instance
set [ find default=yes ] router-id=10.0.1.3

/ip address
add address=192.168.88.11/24 comment=MANAGEMENT interface=ether10 network=192.168.88.0
add address=10.0.1.3 comment=LOOPBACK interface=loopback network=10.0.1.3
add address=10.255.255.6/30 comment="to: CRS-SW1" interface=sfp-sfpplus1 network=10.255.255.4

/mpls
set propagate-ttl=no

/mpls interface
set [ find default=yes ] mpls-mtu=1580

/mpls ldp
set enabled=yes lsr-id=10.0.1.3 transport-address=10.0.1.3 use-explicit-null=yes

/mpls ldp advertise-filter
add prefix=10.0.1.0/24
add advertise=no

/mpls ldp interface
add interface=sfp-sfpplus1

/routing bgp peer
add multihop=yes name=TO-CRS-2 remote-address=10.0.1.1 remote-as=4210000100 update-source=10.0.1.3

/routing ospf interface
add interface=loopback passive=yes
add interface=sfp-sfpplus1 network-type=point-to-point

/routing ospf network
add area=backbone comment=LOOPBACK network=10.0.1.0/24
add area=backbone comment=P2P network=10.255.255.0/24
##############################################

[admin@CRS309-SW1] /mpls forwarding-table> print
 0    expl-null                                     
 1  L 73                                             expl-null                                      10.0.1.3/32                    sfp-sfpplus3                                  10.255.255.6   
 2  L 74                                             expl-null                                      10.0.1.1/32                    sfp-sfpplus1                                  10.255.255.2

# CONF
/interface bridge
add name=loopback protocol-mode=none

/routing ospf instance
set [ find default=yes ] router-id=10.0.1.0

/ip address
add address=192.168.88.10/24 comment=MANAGEMENT interface=ether1 network=192.168.88.0
add address=10.0.1.0 comment=LOOPBACK interface=loopback network=10.0.1.0
add address=10.255.255.1/30 comment="to: CRS-SW2" interface=sfp-sfpplus1 network=10.255.255.0
add address=10.255.255.5/30 comment="to: 4011-1" interface=sfp-sfpplus3 network=10.255.255.4

/mpls
set propagate-ttl=no

/mpls interface
set [ find default=yes ] mpls-mtu=1580

/mpls ldp
set enabled=yes lsr-id=10.0.1.0 transport-address=10.0.1.0 use-explicit-null=yes

/mpls ldp advertise-filter
add prefix=10.0.1.0/24
add advertise=no

/mpls ldp interface
add interface=sfp-sfpplus1
add interface=sfp-sfpplus3

/routing ospf interface
add interface=loopback passive=yes
add interface=sfp-sfpplus1 network-type=point-to-point
add interface=sfp-sfpplus3 network-type=point-to-point

/routing ospf network
add area=backbone comment=LOOPBACK network=10.0.1.0/24
add area=backbone comment=P2P network=10.255.255.0/24
############################################

[admin@CRS309-SW2] /mpls/forwarding-table> print 

0 L    16  main  10.0.1.0  { label=expl-null; nh=10.255.255.1; interface=sfp-sfpplus1 }
1 L    17  main  10.0.1.3  { label=73; nh=10.255.255.1; interface=sfp-sfpplus1 }   

# CONF

/interface bridge
add name=loopback protocol-mode=none

/routing bgp template
set default as=4210000100 disabled=no name=default output.network=bgp-networks

/routing ospf instance
add name=default-v2 router-id=10.0.1.1

/routing ospf area
add instance=default-v2 name=backbone-v2

/routing table
add fib name=""

/ipv6 settings
set disable-ipv6=yes

/ip address
add address=192.168.88.12/24 comment=MANAGEMENT interface=ether1 network=192.168.88.0
add address=10.0.1.1 comment=LOOPBACK interface=loopback network=10.0.1.1
add address=10.255.255.2/30 comment="to: CRS-SW1" interface=sfp-sfpplus1 network=10.255.255.0

/mpls interface
add interface=all mpls-mtu=1580

/mpls ldp
add disabled=no lsr-id=10.0.1.1 transport-addresses=10.0.1.1 use-explicit-null=yes

/mpls ldp advertise-filter
add advertise=yes prefix=10.0.1.0/24
add advertise=no prefix=0.0.0.0/0

/mpls ldp interface
add accept-dynamic-neighbors=yes disabled=no interface=sfp-sfpplus1

/routing bgp connection
add disabled=no local.address=10.0.1.1 .role=ebgp multihop=yes name=TO-4011-1 remote.address=10.0.1.3 .as=4200000000 templates=default

/routing ospf interface-template
add area=backbone-v2 comment=LOOPBACK networks=10.0.1.0/24 passive
add area=backbone-v2 comment=P2P networks=10.255.255.0/24 type=ptp

/system identity
set name=CRS-SW2
 
typoon1426
just joined
Topic Author
Posts: 5
Joined: Wed Nov 10, 2021 8:46 pm

Re: crs309 v7.1rc6 MPLS Problem

Sun Nov 14, 2021 10:19 am

I repeated the test replacing the ros 7.1 with ros 6.48.5 and the problem disappeared. I can reach IP: 10.0.1.1 from 10.0.1.3 without any issue.
The problem is on crs with ros 7, can anyone help me?

Thanks a lot in advance
 
oreggin
Member Candidate
Member Candidate
Posts: 172
Joined: Fri Oct 16, 2009 9:21 pm

Re: crs309 v7.1rc6 MPLS Problem

Sun Nov 14, 2021 8:59 pm

Hi, I experiencing the same issue with my CHR lab. The first node after the packet source drops the packet. I can't debugging it, so I opened a support ticket.
 
mkamau
just joined
Posts: 5
Joined: Wed Mar 10, 2021 10:22 am
Location: nairobi, kenya
Contact:

Re: crs309 v7.1rc6 MPLS Problem

Mon Nov 15, 2021 9:23 pm

With v7.1rc6 try without setting mpls mtu or adding the interfaces under mpls, have the interfaces in mpls ldp only, works for me
 
typoon1426
just joined
Topic Author
Posts: 5
Joined: Wed Nov 10, 2021 8:46 pm

Re: crs309 v7.1rc6 MPLS Problem

Tue Nov 16, 2021 1:10 pm

Thanks mkamau i applied your suggestion and now is running.

Next i modified the lab to add a CE router connected to CRS-SW2 switch, called 4011-4 with established bgp peer to CRS-SW2, that announce his loopback address 192.168.255.255/32 and set 4011-1 to announce an other loopback address 10.100.1.1/32 to CRS-SW2.

these are the routing table of 4011-1, 4011-4 and crs-sw2
[admin@4011-1] /ip route> print 
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 
 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADo  10.0.1.0/32                        10.255.255.5            110
 1 ADo  10.0.1.1/32                        10.255.255.5            110
 2 ADC  10.0.1.3/32        10.0.1.3        loopback                  0
 3 ADC  10.100.1.1/32      10.100.1.1      loopback                  0
 4 ADo  10.255.255.0/30                    10.255.255.5            110
 5 ADC  10.255.255.4/30    10.255.255.6    sfp-sfpplus1              0
 6 ADo  10.255.255.12/30                   10.255.255.5            110
 7 ADb  192.168.255.255/32                 10.0.1.1                 20
 
 [admin@4011-4] /ip route> print 
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 
 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADb  10.100.1.1/32                      10.200.200.2             20
 1 ADC  10.200.200.0/30    10.200.200.1    sfp-sfpplus1              0
 2 ADC  192.168.255.255/32 192.168.255.255 loopback                  0
 
 [admin@CRS309-SW2] /ip/route> print 
Flags: D - DYNAMIC; A - ACTIVE; c, s, b, o, y - COPY
Columns: DST-ADDRESS, GATEWAY, DISTANCE
#     DST-ADDRESS         GATEWAY                    DISTANCE
  DAo 10.0.1.0/32         10.255.255.1%sfp-sfpplus1       110
  DAc 10.0.1.1/32         loopback                          0
  DAo 10.0.1.3/32         10.255.255.1%sfp-sfpplus1       110
  DAb 10.100.1.1/32       10.0.1.3                         20
  DAc 10.200.200.0/30     sfp-sfpplus2                      0
  DAc 10.255.255.0/30     sfp-sfpplus1                      0
  DAo 10.255.255.4/30     10.255.255.1%sfp-sfpplus1       110
  DAb 192.168.255.255/32  10.200.200.1                     20
the bgp is running correctly. But if i try to ping from 4011-1 with target address = 192.168.255.255 and src-address = 10.100.1.1, i have no response
[admin@4011-1] /ip route> /ping 192.168.255.255 src-address=10.100.1.1                                
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                                                            
    0 192.168.255.255                                         timeout                                                                                                                           
    1 192.168.255.255                                         timeout                                                                                                                           
    2 192.168.255.255                                         timeout                                                                                                                           
    3 192.168.255.255                                         timeout                                                                                                                           
    4 192.168.255.255                                         timeout                                                                                                                           
    sent=5 received=0 packet-loss=100% 
    
    [admin@4011-4] /ip route> /ping 10.100.1.1 src-address=192.168.255.255
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                                                            
    0 10.100.1.1                                              timeout                                                                                                                           
    1 10.100.1.1                                              timeout                                                                                                                           
    2 10.100.1.1                                              timeout                                                                                                                           
    sent=3 received=0 packet-loss=100% 

To better analize the problem i started to sniff packets on CRS-SW2 and i discover that if the sniffer on sfp-sfplus1 is active the ping on both endpoints is running correctly.
My hypotesis is that without sniffer the mpls side of path are hw accelerated and do not transit from cpu with probably some problems, instead with sniffer active traffic is forced to transit from cpu, then ping is running.
Someone has noted similar issues?

The goal of my tests is to have a PE router hw accelerated from mpls to ip and viceversa, the next step of lab would be to enable l3-hw
thanks in advance
 
typoon1426
just joined
Topic Author
Posts: 5
Joined: Wed Nov 10, 2021 8:46 pm

Re: crs309 v7.1rc6 MPLS Problem

Fri Nov 19, 2021 10:52 am

Someone who has had similar problems?
 
typoon1426
just joined
Topic Author
Posts: 5
Joined: Wed Nov 10, 2021 8:46 pm

Re: crs309 v7.1rc6 MPLS Problem

Thu Dec 02, 2021 6:01 pm

I've upgraded CRS-SW2 to ROS 7.1 testing but the problem remain. Someone had similar issues? Thanks

Who is online

Users browsing this forum: No registered users and 9 guests