Community discussions

MUM Europe 2020
 
sthiem
just joined
Topic Author
Posts: 3
Joined: Fri Jun 05, 2009 10:15 am

VPLS Tunnel between different areas

Tue Aug 30, 2011 7:43 pm

Hi,
we would like to switch from EoIP to VPLS, but we encounter some serious problems with it.
If we try to establish a VPLS tunnel between 172.16.2.1 and 172.21.0.1 (or some other device in this area), the tunnel doesn't entry the running state.
Otherwise, a tunnel within an area works perfectly.
You can see a simplified network diagram in the attached image.
The problem seems to be at the border router (172.16.3.1 in this case).

Image

Now let me describe our setup.
All our routers are running on 4.17.
As you can see, the OSPF is splitted in 4 different areas.
The backbone area is located in a house, all devices are connected with ethernet cables.
The connections between the border area routers and the individual areas are established with wireless.
Each area (17, 18 and 21) contains ~10-20 routerboards.

configuration @ 172.16.2.1
/routing ospf instance print
Flags: X - disabled 
 0   name="default" router-id=172.16.2.1 distribute-default=never redistribute-connected=no redistribute-static=no redistribute-rip=no redistribute-bgp=no  redistribute-other-ospf=no metric-default=1 metric-connected=20 metric-static=2000 metric-rip=20 metric-bgp=20 metric-other-ospf=20 in-filter=ospf-in out-filter=ospf-out 

/routing ospf area print         
Flags: X - disabled, I - invalid 
 #   NAME               AREA-ID         TYPE    DEFAULT-COST
 1   backbone          0.0.0.0         default

 /routing ospf network print
Flags: X - disabled, I - invalid 
 #   NETWORK            AREA                                                                                                                                
 0   172.16.0.0/16      backbone     
 
 /mpls interface print
Flags: X - disabled 
 #   INTERFACE    MPLS-MTU
 0   all                1508    

/mpls ldp print
                       enabled: yes
                        lsr-id: 172.16.2.1
             transport-address: 172.16.2.1
             path-vector-limit: 255
                     hop-limit: 255
                   loop-detect: yes
             use-explicit-null: no
  distribute-for-default-route: no
  
  /mpls ldp interface print
Flags: X - disabled, I - invalid 
 #   INTERFACE          HELLO-INTERVAL       HOLD-TIME           
 1   ether1                5s                              15s   

  /interface vpls print
Flags: X - disabled, R - running, D - dynamic, B - bgp-signaled, C - cisco-bgp-signaled 
0     name="vpls1" mtu=1500 l2mtu=1500 mac-address=00:00:00:00:05:01 arp=enabled disable-running-check=no remote-peer=172.21.2.1 vpls-id=100:0 
       cisco-style=no cisco-style-id=0 advertised-l2mtu=1500 pw-type=raw-ethernet 
configuration @ 172.16.3.1
 /routing ospf instance print
Flags: X - disabled 
 0   name="default" router-id=172.16.3.1 distribute-default=never 
     redistribute-connected=as-type-1 redistribute-static=no 
     redistribute-rip=no redistribute-bgp=no redistribute-other-ospf=no 
     metric-default=1 metric-connected=20 metric-static=20 metric-rip=20 
     metric-bgp=auto metric-other-ospf=auto in-filter=ospf-in 
     out-filter=ospf-out 

/routing ospf area print    
Flags: X - disabled, I - invalid 
 #   NAME                                    AREA-ID         TYPE    DEFAULT-COST
 0   bahrdorf                                0.0.0.21        default
 1   backbone                                0.0.0.0         default

 /routing ospf network print
Flags: X - disabled, I - invalid 
 #   NETWORK            AREA                                                     
 0   172.16.0.0/16      backbone                                                 
 1   172.21.0.0/16      bahrdorf        
 
 /routing ospf area range print
Flags: X - disabled 
 #   AREA                                 RANGE              COST       ADVERTISE
 0   bahrdorf                             172.21.0.0/16      calculated yes      
 1   backbone                             172.16.0.0/16      calculated yes     

/mpls interface print
Flags: X - disabled 
 #   INTERFACE                                                           MPLS-MTU
 0   all                                                                 1508    
 
 /mpls ldp print          
                       enabled: yes
                        lsr-id: 172.16.3.1
             transport-address: 172.16.3.1
             path-vector-limit: 255
                     hop-limit: 255
                   loop-detect: no
             use-explicit-null: no
  distribute-for-default-route: no

 
 /mpls ldp interface print
Flags: X - disabled, I - invalid 
 #   INTERFACE                          HELLO-INTERVAL       HOLD-TIME           
 0   ether1                             5s                   15s                 
 1   wlan1                              5s                   15s 
configuration @ 172.21.2.1
 
/routing ospf instance print
Flags: X - disabled 
 0   name="default" router-id=172.21.2.1 distribute-default=never redistribute-connected=as-type-1 
     redistribute-static=no redistribute-rip=no redistribute-bgp=no redistribute-other-ospf=no metric-default=1 
     metric-connected=20 metric-static=20 metric-rip=20 metric-bgp=auto metric-other-ospf=auto in-filter=ospf-in 
     out-filter=ospf-out 

/routing ospf area print    
Flags: X - disabled, I - invalid 
 #   NAME                                                                          AREA-ID         TYPE    DEFAULT-COST
 0   bahrdorf                                                                      0.0.0.21        default
 1   backbone                                                                      0.0.0.0         default

 /routing ospf network print
Flags: X - disabled, I - invalid 
 #   NETWORK            AREA                                                                                           
 0   172.21.0.0/16      bahrdorf                                                                                       
 
 /mpls interface print
Flags: X - disabled 
 #   INTERFACE                                                                                                 MPLS-MTU
 0   all                                                                                                           1508
 
 /mpls ldp print
                       enabled: yes
                        lsr-id: 172.21.2.1
             transport-address: 172.21.2.1
             path-vector-limit: 255
                     hop-limit: 255
                   loop-detect: no
             use-explicit-null: no
  distribute-for-default-route: no

/mpls ldp interface print
Flags: X - disabled, I - invalid 
 #   INTERFACE                                                                HELLO-INTERVAL       HOLD-TIME           
 0   wlan1                                                                   5s                   15s   
 
/interface vpls print
Flags: X - disabled, R - running, D - dynamic, B - bgp-signaled, C - cisco-bgp-signaled 
 0     name="vpls1" mtu=1500 l2mtu=1500 mac-address=00:00:00:00:05:00 arp=enabled disable-running-check=no 
       remote-peer=172.16.2.1 vpls-id=100:0 cisco-style=no cisco-style-id=0 advertised-l2mtu=1500 
       pw-type=raw-ethernet 
Hope we can figure out the problem together.

Best regards,
Sebastian
 
Mplsguy
MikroTik Support
MikroTik Support
Posts: 226
Joined: Fri Jun 06, 2008 5:06 pm

Re: VPLS Tunnel between different areas

Wed Aug 31, 2011 11:09 am

Probably MPLS LSP is "broken" on area border router. There is no limitation for VPLS to work between routers in different areas - actually MPLS (and therefore VPLS) does not care what IGP is used to exchange routes. What matters is that there must be "complete" MPLS LSP between VPLS endpoints and usually it means that all routers between VPLS endpoints MUST have /32 routes to VPLS endpoints. Make sure that area border routers are properly distributing /32 routes for VPLS endpoints into neighboring area.

To some extent this has been explained here: http://forum.mikrotik.com/viewtopic.php?f=14&t=36993
 
sthiem
just joined
Topic Author
Posts: 3
Joined: Fri Jun 05, 2009 10:15 am

Re: VPLS Tunnel between different areas

Wed Aug 31, 2011 2:59 pm

Hi Mplsguy,
thank you for your reply. I checked my configuration and noticed, that i've used /30 for loopback addresses. I changed it to /32 on all intermediate devices and now one side of the tunnel is running (@172.16.2.1).

Please have a look at the images, they show you the considerable routing entries, the remote binding list and the interface status.

Status @ 172.16.2.1
Image

Status @ 172.21.2.1
Image
 
sthiem
just joined
Topic Author
Posts: 3
Joined: Fri Jun 05, 2009 10:15 am

Re: VPLS Tunnel between different areas

Fri Sep 09, 2011 7:08 pm

The problem still exists... :(
 
sup5
Member
Member
Posts: 322
Joined: Sat Jul 10, 2010 12:37 am

Re: VPLS Tunnel between different areas

Wed May 02, 2012 5:49 pm

I try to setup a similar network using OSPF route summarization.
If a LSP has to be announced as /32 througout the whole network,
where is the sense in doing route summarization?

How can I just announce /32 loopback routes and still just summarize any /30 and /24 routes of a given area?
 
User avatar
sten
Forum Veteran
Forum Veteran
Posts: 920
Joined: Tue Jun 01, 2004 12:10 pm

Re: VPLS Tunnel between different areas

Sat May 05, 2012 2:34 am

Give your routers loopback ip addresses in a different subnet than your link addresses.
Move along. Nothing to see here.

Who is online

Users browsing this forum: No registered users and 4 guests