Hello Everyone,
I have installed 2 routers each in remote location, WAN interface in different subnets. I am trying connect BGP address-families=l2vpn to propagate routes and VPLS . BGP establish connection, but none routes is coming up. Also VPLS interface set inactive.
Any help thank you.[
[volga629@canlrt03] > /routing bgp peer print status
Flags: X - disabled, E - established
0 E name="nl-peer01" instance=default remote-address=second router public ip remote-as=65524 tcp-md5-key="" nexthop-choice=default
multihop=no route-reflect=no hold-time=3m ttl=255 in-filter="" out-filter="" address-families=l2vpn
default-originate=never remove-private-as=no as-override=no passive=no use-bfd=no remote-id=ip addr of loop back
local-address=158.69.151.91 uptime=42m12s prefix-count=0 updates-sent=1 updates-received=1 withdrawn-sent=0
withdrawn-received=0 remote-hold-time=3m used-hold-time=3m used-keepalive-time=1m refresh-capability=yes
as4-capability=yes state=established
Thank you for reply.
I configured ldp to each side public ip as lsr-id, but it not completing negotiations, because 2 ends is in different subnet ranges. Is this make sense ?
I didn’t notice 10.1.254.1/32 in your OSPF LSA printout - so make sure that the remote router is also properly configured.
Get out of this habit now.
Routing protocols treat redistributed routes differently than they treat native-to-the-protocol routes. Make sure that all of your loopback interfaces’ IP addresses have corresponding OSPF networks that properly add them into your OSPF “cloud.”
There is a time and a place to redistribute a route into a protocol, but this is only for situations where the destination cannot be included in your protocol for technical reasons (the destination router doesn’t support OSPF) or for administrative reasons (the destination router belongs to another organization), and not just the fact that it’s easy to turn on “redistribute connected” to fire-and-forget it.
If you want the ‘proper’ “fire and forget” ospf configuration - set the default OSPF interface state to be passive, and specify network=0.0.0.0/0 area=router’s area, and then manually specify interfaces as active where you want them to form adjacencies.
I’d recommend that even if you do this, then the “adjacency” interfaces should be covered by their own network statements, just so that if you ever need to remove the blanket statement, you won’t break OSPF…
add area=backbone network=10.2.254.1/32
add area=backbone network=10.2.3.0/30
etc…
Both ends should use each other’s loopback addresses for iBGP, both as the source and as the destination.
If you’re using an interface IP now, and one side switches to source=loopback, then the other side needs to update the remote’s IP as well.
If you just change the source on R1, then R2 is going to start seeing iBGP requests from an “unknown peer”
(eBGP of course should use the IP of the interface between itself and the neighboring router)
But just to make sure this is the problem, and not a routing issue, try to ping R1 loop IP from R2, with R2’s loop IP as the source IP. If this ping test fails, then you have some other issue (vrf, firewall filters, nat, etc, missing routes, etc)
In y case I think it will not work, because both routers on WAN side in different networks. So I will need run some thing like GRE tunnel to reach each loop back. Or some thing else which I s on’t know about.
Yes - you cannot run MPLS across the Internet without some sort of tunneling protocol such as GRE.
That sure was an important detail.
I don’t know about other readers but when I read this, it means “two different locations, but with my own internal connectivity between them” - just because of the fact that we’re talking about MPLS and iBGP.
Your MTU is going to be low - be sure that your PE routers are able to adjust TCP MSS, or make sure that ICMP isn’t dropped inside of your network for PMTUD functionality - if you don’t do one of these, your CPU utilization is going to increase a lot if you have high bandwidth and the routers are forced to do fragmentation.
I got working case with ipip tunnel BGP come up and vpls link come up too, but from lan server ip I can’t ping another end same server says UNREACHABLE
[volga629@canlrt03] > /interface bridge port print
Flags: X - disabled, I - inactive, D - dynamic
# INTERFACE BRIDGE PRIORITY PATH-COST HORIZON
0 LAN-eth1 LAN-lo0 0x80 10 none
1 D vpls8 LAN-lo0 0x80 50 1
You should make a specific bridge for the VPLS to use, and not the lo0 bridge.
Out of curiosity - have you tried a simple EoIP tunnel between these two sites?
Are you trying to set this up so that you can use MPLS to sell layer2 vpn services to customers, or just to connect your sites together? This is a pretty involved topic if you’re just needing to bridge two sites together across the Internet…
Of course your next concern is security - remember that this traffic is going to be going un-encrypted across the public Internet…
I have 5 sites to connect together. I am trying get working at least 2 sites for right now. Encryption will done on application layer. Still doing some troubleshooting one side of vpls not established correctly, might be firewall issue.
