You need a policy exported to the forwarding table. This policy is required for all flow-based load-balancing as well as for FRR. The "per-packet" keyword is misleading. It doesent really mean per-packet.
Add this to your config and it should take care of the load-balancing. policy-options { policy-statement LOAD-BALANCE { then { load-balance per-packet; } } } routing-options { forwarding-table { export LOAD-BALANCE; } } -Ariff On Jan 28, 2008, at 6:52 PM, a. r.isnaini. rangkayo sutan wrote: > Hi, > > Any suggestion will be very appreciated. > > Here's the scheme : > Ports aggregation with trunking was success between Juniper - Cisco > Catalyst, but i'm having problem with the load that is not balanced on > each port. > > It might be the config still missing one line somewhere :) > > interfaces { > fe-0/2/0 { > fastether-options { > 802.3ad ae1; > } > } > fe-0/2/1 { > fastether-options { > 802.3ad ae1; > } > } > > ae1 { > description FAST-ETHER-CHANNEL-2FE-AGGREGATED; > vlan-tagging; > aggregated-ether-options { > minimum-links 2; > link-speed 100m; > > - a. r. i. rangkayo sutan > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp