[j-nsp] per-packet load balancing over multiple l2tp tunnels
Dave Kruger
dave.kruger at za.verizonbusiness.com
Wed Aug 27 02:20:48 EDT 2008
Hi Arda
thanks for your response - I suspected this might be the case. I'll give
mlppp a go to see if that meets the requirement.
And that's bad about the ospf interfaces!
Regards,
Dave
Arda Balkanay wrote:
> I have a case about that issue (Case #2008-0703-0196 ) and Juniper
> said that:
> -round robin load sharing isn't supported for dynamic interfaces;
> alternate solution can be to use MLPPP
> for my case MLPPP is not possible because the incumbent who owns LAC
> does not permit it.
>
>
> Also for dynamic subscriber interfaces I have another case about
> dynamic routing protocols which has a similar answer:
> - OSPF cannot be run on dynamic IP interfaces. (because of KA26012
> Juniper removed this feature)
>
> I think these two problem is unacceptable and I cannot find any
> meaningful reason for this kind of lack.
>
>
>
>
> On Tue, Aug 26, 2008 at 11:59 AM, Dave Kruger
> <dave.kruger at za.verizonbusiness.com
> <mailto:dave.kruger at za.verizonbusiness.com>> wrote:
>
> Hi All
>
> Has anyone ever tried to do change the load balancing technique over
> l2tp tunnels on an ERX?
>
> the default is obviously per-flow:
>
> sh ip interface tun l2tp:139254/1105340/1016347 | i Multipath
> Multipath mode = hashed
>
> It seems enabling per-packet on the physical interface over which the
> l2tp tunnel terminates, with the command "ip multipath
> round-robin" has
> no effect:
>
> sh ip int FastEthernet4/3.302 | i Multipa
> Multipath mode = round-robin
>
> And I see no place to do this under the l2tp destination profile
> or the
> profile it references
>
> thanks for your time and any feedback
>
> Regards,
> Dave
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> <mailto:juniper-nsp at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
More information about the juniper-nsp
mailing list