Community discussions

MikroTik App
 
haiderasyed
just joined
Topic Author
Posts: 4
Joined: Mon Apr 23, 2018 1:51 pm

L2VPN -- Targeted LDP

Thu Apr 26, 2018 2:40 pm

Dear All,

We are trying to configure l2vpn by using targeted ldp between two CEs using mikrotik as PE on one side and juniper on other side.


Image

L2circuit is up but the CE devices are not able to ping each other. Below given is the configuration of both ends. Do anyone have any idea what is missing?

Mikrotik:
/mpls ldp
set enabled=yes lsr-id=192.168.112.254 transport-address=192.168.112.254

/mpls ldp neighbor
add transport=202.163.74.254

/mpls traffic-eng interface
add bandwidth=700Mbps interface=gre-tunnel1

/interface vpls
add advertised-l2mtu=1550 cisco-style=yes cisco-style-id=513 disabled=no l2mtu=1550 mac-address=02:98:F3:FD:8D:60 mtu=1550 name=l2-qta pw-type=tagged-ethernet \
remote-peer=202.163.74.254

/routing bgp peer
add address-families=l2vpn,vpnv4 name=quetta remote-address=202.163.74.254 remote-as=9541 tcp-md5-key=cyb3rn3t ttl=default update-source=192.168.112.254

Juniper:
show configuration protocols bgp
group internal {
type internal;
local-address 202.163.74.254;
log-updown;
family inet {
unicast;
}
family inet-vpn {
unicast;
}
authentication-key "$9$Escyrvdb2oaUVb.5z6u0X7N-Yo"; ## SECRET-DATA
export NHS;
tcp-mss 512;
neighbor 192.168.112.254 {
description " *** mikrotik-engg-lab ***";
}
}

show configuration protocols mpls label-switched-path qtacore-mikrotik-engg-lab-loose
from 202.163.74.254;
to 192.168.112.254;
metric 250;
no-cspf;
optimize-timer 300;
adaptive;

show configuration protocols l2circuit
neighbor 192.168.112.254 {
interface ge-0/0/1.513 {
virtual-circuit-id 513;
description mikrotik-engg-l2;
no-control-word;
mtu 1550;
}
}

show configuration interfaces ge-0/0/1.513
description "*** mikrotik-engg-l2 ***";
encapsulation vlan-ccc;
vlan-id 513;
family ccc;

l2circuit status:

Juniper:

Neighbor: 192.168.112.254
Interface Type St Time last up # Up trans
ge-0/0/1.513(vc 513) rmt Up Apr 23 17:19:50 2018 1
Local interface: ge-0/0/1.513, Status: Up, Encapsulation: VLAN
Description: mikrotik-engg-l2
Remote PE: 192.168.112.254, Negotiated control-word: No
Incoming label: 188288, Outgoing label: 6711

Mikrotik:

[admin@MikroTik] /interface vpls> monitor 2
remote-label: 188288
local-label: 6711
remote-status:
You do not have the required permissions to view the files attached to this post.
 
User avatar
Anumrak
Forum Guru
Forum Guru
Posts: 1174
Joined: Fri Jul 28, 2017 2:53 pm

Re: L2VPN -- Targeted LDP

Thu Apr 26, 2018 3:45 pm

Try it "pw-type=tagged-ethernet" with raw type. And bridge ether ports with vpls interface to client side.
 
haiderasyed
just joined
Topic Author
Posts: 4
Joined: Mon Apr 23, 2018 1:51 pm

Re: L2VPN -- Targeted LDP

Fri Apr 27, 2018 9:54 am

Dear, already done but no luck!!

name="l2-qta" mtu=1550 l2mtu=1550 mac-address=02:87:04:C1:F2:8E arp=enabled arp-timeout=auto disable-running-check=no remote-peer=202.163.74.254 cisco-style=yes
cisco-style-id=513 advertised-l2mtu=1550 pw-type=tagged-ethernet use-control-word=default
add bridge=mikrotik-quetta interface=eth1.513
add bridge=mikrotik-quetta interface=l2-qta
 
haiderasyed
just joined
Topic Author
Posts: 4
Joined: Mon Apr 23, 2018 1:51 pm

Re: L2VPN -- Targeted LDP

Wed May 16, 2018 8:48 am

Same configuration is working fine with huawei... but not with juniper... do anyone have some solution?

Who is online

Users browsing this forum: No registered users and 56 guests