how to configure MPLS VPN3 over MPLS TE?
I can’t find any information, and the commands are outdated and don’t work on RouterOS version 7.
Thanks.
Good day, please How can network traffic be prioritized over the TE-MPLS tunnel over the LDP tunnel? mikrotik routerOS 7.12.2
Traffic will be automatically routed through the TE tunnel. You must establish the tunnel against the PE.
Thanks for your answer but, the problem is that it does not relate automatically, the vpn forwarding still takes the LSP generated by LDP, I comment that the vpn label does appear in the mpls forwarding table but the traffic-eng one does not appear. I am using OSPF in the core of the IP/MPLS and EBGP between the client and the provider, and the RouterOS is version 7.18.2.
[admin@PE1] > mpls forwarding-table/print
Flags: L - LDP, P - VPN
Columns: LABEL, VRF, PREFIX
LABEL VRF PREFIX
0 L 9005 main 192.170.0.3
1 L 9006 main 192.170.0.4
2 L 9007 main 192.170.0.5
3 L 9008 main 192.170.0.6
4 L 9001 main 60.0.0.0/30
5 L 9002 main 70.0.0.0/30
6 L 9003 main 80.0.0.0/30
7 L 9004 main 90.0.0.0/30
8 L 9000 main 40.0.0.0/30
9 P 9009 VRF-CE1
[admin@PE1] > mpl traffic-eng/flow/print detail
Flags: N - ingress, E - egress; F - forwarding; R - reservation
0 N R vrf=main session="192.170.0.6|2|192.170.0.2"
sender="192.170.0.2|1" out-labels=5008
out-nexthop=50.0.0.2%ether1 bw=30.0Mbps style=shared
psb="ttl=64 SenderTspec={rate=3750000,size=1000,peak=3750000,
policed=0,maxpacket=2147483647} LabelReq=0x800 SessionAttr={setup=3,
hold=3,flags=0x6,name=} RecRoute={} ExplRoute={192.170.0.2|strict,
50.0.0.2|strict,60.0.0.1|strict,60.0.0.2|strict,70.0.0.1|strict,
70.0.0.2|strict} Adspec={brk=0,hops=0,pathbw=0,lat=2147483647,
mtu=1500,other=05000000} out.RecRoute={50.0.0.1%*2}
out.ExplRoute={50.0.0.2|strict,60.0.0.1|strict,60.0.0.2|strict,
70.0.0.1|strict,70.0.0.2|strict} out.Adspec={brk=0,hops=1,pathbw=0,
lat=2147483647,mtu=1500,other=05000000} "
resv="r=0x3005ad90,iface=*2,bw=3750000"
rsb="iface=*2 FlowSpec={rate=3750000,size=1000,peak=3750000,
policed=0,maxpacket=2147483647} RecRoute={60.0.0.1,5008,70.0.0.1,
7008,70.0.0.2,0} Label=5008 NHop=50.0.0.2|2 "
1 E vrf=main session="192.170.0.2|3|192.170.0.6"
sender="192.170.0.6|1" label=0 bw=30.0Mbps style=shared
psb="iface=*2 ttl=61 SenderTspec={rate=3750000,size=1000,
peak=3750000,policed=0,maxpacket=2147483647} LabelReq=0x800
SessionAttr={setup=3,hold=3,flags=0x6,name=} RecRoute={50.0.0.2,
5009,60.0.0.2,7009,70.0.0.2} Adspec={brk=0,hops=3,pathbw=0,
lat=2147483647,mtu=1500,other=05000000} PHop=50.0.0.2|2 "
rsb="FlowSpec={rate=3750000,size=1000,peak=3750000,policed=0,
maxpacket=2147483647} RecRoute={} out.RecRoute={50.0.0.1%*2,0} "
, I comment that the vpn label does appear in the mpls forwarding table but the traffic-eng one does not appear.
admin@PE1] > mpl traffic-eng/flow/print detail
Flags: N - ingress, E - egress; F - forwarding; R - reservation
it’s difficult to help you if we don’t know your exact mpls topology. from the te output it seems they weren’t in forwarding state. or maybe that’s why you asked?? at least give us real time monitoring output for each mpls-te node that you saw didn’t have any traffic passed through it.
for simplicity, any mpls network requires at minimum 5 routers involved to work properly. 2 pe 1 p 2 ce. otherwise you can troubleshoot any problem any time.
Hi, here a work over the topic: