Hi team, I am testing load-balancing VPLS traffic over multiple RSVP LSPs on 2 x MX5, but can not get it to work.
The key piece of configuration to enable load-balance VPLS traffic is documented at the link below: http://www.juniper.net/techpubs/en_US/junos11.4/topics/task/configuration/load-balancing-vpls-mx-series-configuring.html forwarding-options { hash-key { family multiservice { payload { ip { layer-3; layer-4; } } } } } We run multiple streams using traffic generators from testers with different IPs and port numbers, as well trying simple extended pings between two end points (SW1 and SW2), again using different IP addresses. However, I can not manage to get the traffic load-balanced. It always follows one path only. The topology I use is as below: ge-1/0/7 ge-1/0/6 -------------------- ge-1/0/6 SW1 ---------------- PE1 PE2 ------------------SW2 -------------------- ge-1/1/7 The router version, and configuration for PE2 is as below. The config for PE1 is almost identical (just need to use different IP addresses). Could you please let me know if I miss something. Alternatively, if you can confirm that this is supported or not supported on this platform, it would be grateful as well. Regards, Huan lab@PE2> show version Hostname: PE2 Model: mx5-t JUNOS Base OS boot [11.4R6.6] JUNOS Base OS Software Suite [11.4R6.6] JUNOS Kernel Software Suite [11.4R6.6] JUNOS Crypto Software Suite [11.4R6.6] JUNOS Packet Forwarding Engine Support (MX80) [11.4R6.6] JUNOS Online Documentation [11.4R6.6] JUNOS Routing Software Suite [11.4R6.6] lab@PE1> show version Hostname: MX5 Model: mx5-t JUNOS Base OS boot [11.4R7.5] JUNOS Base OS Software Suite [11.4R7.5] JUNOS Kernel Software Suite [11.4R7.5] JUNOS Crypto Software Suite [11.4R7.5] JUNOS Packet Forwarding Engine Support (MX80) [11.4R7.5] JUNOS Online Documentation [11.4R7.5] JUNOS Routing Software Suite [11.4R7.5] lab@PE2# show interfaces { ge-1/0/6 { vlan-tagging; encapsulation vlan-vpls; unit 600 { description "vpls interface to SW2"; encapsulation vlan-vpls; vlan-id 600; family vpls; } } ge-1/0/7 { description "LINK - PE1 ge-1/0/7"; unit 0 { family inet { address 10.10.101.2/24; } family mpls; } } ge-1/1/7 { description "LINK - PE1 ge-1/1/7"; unit 0 { family inet { address 10.10.102.2/24; } family mpls; } } lo0 { unit 0 { family inet { address 10.1.1.22/32; } } } } forwarding-options { hash-key { family multiservice { payload { ip { layer-3; layer-4; } } } } } routing-options { autonomous-system 65000; forwarding-table { export per-flow-load-balance; } } protocols { rsvp { load-balance bandwidth; interface all; } mpls { label-switched-path PE2-to-PE1-LSP1 { to 10.1.1.11; bandwidth 200m; no-cspf; primary via-Ge1; } label-switched-path PE2-to-PE1-LSP2 { to 10.1.1.11; bandwidth 200m; no-cspf; primary via-Ge2; } path via-Ge1 { 10.10.101.1; } path via-Ge2 { 10.10.102.1; } interface ge-1/0/7.0; interface ge-1/1/7.0; } bgp { local-as 65000; group PEs { type internal; local-address 10.1.1.22; family inet { unicast; } family inet-vpn { unicast; } family l2vpn { signaling; } neighbor 10.1.1.11; } } ospf { traffic-engineering; area 0.0.0.0 { interface ge-1/0/7.0; interface ge-1/1/7.0; interface lo0.0; } } lldp { interface all; } } policy-options { policy-statement per-flow-load-balance { then { load-balance per-packet; } } } routing-instances { VPLS-1 { instance-type vpls; interface ge-1/0/6.600; route-distinguisher 10.1.1.22:22; vrf-target target:65000:100; protocols { vpls { site-range 10; site Site2 { site-identifier 2; } } } } } lab@PE2> show mpls lsp statistics Ingress LSP: 2 sessions To From State Packets Bytes LSPname 10.1.1.11 10.1.1.22 Up 11027 8785386 PE2-to-PE1-LSP1 10.1.1.11 10.1.1.22 Up 0 0 PE2-to-PE1-LSP2 Total 2 displayed, Up 2, Down 0 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
