I know this is minimal information, but I just set up MPLS on our network, i’m using LDP, the routing protocol is OSPF. Currently it seems to work fine other than a couple of odd issues i’m getting. I’ve gone through mpls mtu checks on all the active interfaces to make sure they are correct. For some reason bandwidth tests using tcp from router to router seems to run slow, a max of 3mbits, and I seem to be getting just as slow speeds from our servers on a connected interface at the edge router. All of our clients work fine out to the internet though from various connected interfaces throughout the network. I’m not even sure where to look for this issue anymore.
If you need more info, ask, any help is appreciated.
This is a wisp so there are bridged license ptp links in between the routers. When contacting the vendor they informed me the l2mtu on those is 9014.
So we have several hundred customer connected to each router, all speeds are fine out through the internet. When doing tcp bandwidth test router to router they are bad ~3mbit, all speeds to our webserver which is directly plugged in to the edge are bad through the network but fine out to the internet.
On the PowerEdge V3 I have no way to change the l2mtu nor does it list what it is? I changed the ip mtu to a little higher on the wireless network interface which links to the next mpls router but it dropped everything. Currently network wide the ip mtu is 1500 and the mpls-mtu is 1508. It seems that when I turn ldp of on the Power V3 everything works right, so i’m pretty sure this is the issue.
It’s odd because I had mpls on and was able to access winbox just fine on the edge, then we loaded the full routing tables and I lost winbox. Turning off mpls made it accessible again, so it seems there must be an issue l2mtu wise.
for mtu in powerrrouter v3 just type 9000 for example in MTU field ( replace 1500 ) if you are on daugther cards
or you can use the 2 standard copper ports whith default mtu aat 9514
for ospf all IP MTU must be same on both sides
best would be to have
IP MTU =1500
MPLS MTU = 1512 at minimum
L2 MTU = MPLS MTU + 4
so on powerouter just put value of L2 MTU in over mtu existing value
All the ports on that module show no l2mtu / max mtu
It’s greyed out.
If I set the mtu higher than 1500, i’m changing the ip mtu on that interface, so if I set it to 9000 i’d have to set the mtu on the opposite interface to 9000.
So I don’t see how I could have
IP MTU =1500
MPLS MTU = 1512 at minimum
L2 MTU = MPLS MTU + 4
Sorry, i’m just a bit confused and kind of angry the PowerRouter module doesn’t report the l2mtu, that would be much easier.
I have exactly the same problem using the PowerRouter V3. L2MTU is not configurable in all the module cards, I have both fiber and electrical modules.
I tried to change the IP MTUs and MPLS MTU but continue to have the problem. Where you able to fix this problem?
1530 is really the minimum MPLS mtu you want to set on an MPLS network if you want to use all of the ATOM feature set like EoMPLS and VPLS. It’s needed to be able to hand off a 1500 byte segment to the edge
I never did get this resolved actually, raised the MTU’s, messed around with a lot of different setups, the fix was to not use mpls on the v3, it was the edge so it wasn’t a huge deal. The whole core of the network runs mpls just fine. I was hoping possibly fastpath may help if they ever get a stable release of ROS6, but i’m not even clear on whether fastpath will work mpls on x86, so who knows.
I do have traffic engineering working on everything though, including the v3 on the edge.
