[j-nsp] TRAFFIC DISTRIBUTION ACROSS AGREGATTED LINKS

[Doan Nguyen]

Mario,

we've just finished testing a similar setup except with aggregate ethernet.
There isn't anything wrong with your configs but make sure your traffic flow
does simulate a good range of source/destination IP space.  This is the same
for your source/destination port range.  We had around 2000 source/destination
bgp flows along with dynamic layer 4 port ranges.


-Doan



________________________________
From: Mario Andres Rueda Jaimes <maeve2009 at gmail.com>
To: juniper-nsp at puck.nether.net
Sent: Monday, September 26, 2011 12:58 PM
Subject: [j-nsp] TRAFFIC DISTRIBUTION ACROSS AGREGATTED LINKS

Hi Experts,

We configured an Agreggated Sonet with 2 OC-12 Channels between an M320
and M20 Router.

The traffic flood, is fine in two ways, but we have an issue with MPLS
Traffic, There is not MPLS Load sharing acrooss both Links, instead the
MPLS Traffic (each LSP ) is established only for one of links, so the
Load Balance is pretty unequal.

The MPLS Forwanding options are setting like this:

forwarding-options    
hash-key {
    family inet {
        layer-3;
        layer-4;
    }
    family mpls {
        label-1;
        label-2;
        payload {
            ip;
        }
    }
}



Does anyone performed this kind of configuration before, what would be
the best practice to configure this kinds of scenarios ?

Thanks in advice

Mario

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp