Junos OS

Hello

Does anybody tested VPLS load-balancing between two LSPs between srx650 and j2350 (or similar) and can provide working configuraiton of that lab?

I tested it on 2 computers with virtualbox with 4 nic-s in bridge mode

-- I tested it in vbox because I don't know how to set more MACs on one physical interface or something equal, for testing i use something like ping -i 0.1 IPADD -s 1400 or netperf.

In my configuration on both routers I have

 junos 10.3

2 LSPs, both with primary (strict to interface) and secondary path (strict to interface)

one vpls instance

and I want to load balance it somehow equaly. only want to see something like 1/4 of packet are going through one cable and 3/4 via other or other fraction (one direction). I know in real network with hundreds of macs the behavior will be more equal on both lines.

if you have any question on detailed configuration feel free to ask

Thanks for reply

Jozef

can you please post your config?  that way we can look at it and see what may (or may not be) missing.

Thanks,

Will

I attated srx650 and j2350 config + show mpls lsp, show vpls connections from j-series

Hope it helps.

Attachment(s)

srx650+j2350.txt   46 KB 1 version

I guess first thing -- is the traffic successfully making it across the MPLS network from one "machine" to the other?  is that working and you are just trying to configure and verify load-balancing of the two LSPs?

I have a similar lab setup to test things out, but have not tried LSP load-balancing.  I will try to tinker with that if I can find time to see what I find, however you might try this ---

verify in the forwarding table that both LSPs are installed.  I know for regular IPv4 routing, you would see two next-hops listed, so I would think you should see the labels listed for each LSP.

in my example, I have a VPLS instance configured, and for lsi.1049344, it only has one outer label as an option, since I only have 1 LSP setup:

admin@Lab-R1> show route forwarding-table family mpls      
Routing table: default.mpls
MPLS:
Destination        Type RtRef Next hop           Type Index NhRef Netif
default            perm     0                    dscd    50     1
0                  user     0                    recv    49     3
1                  user     0                    recv    49     3
2                  user     0                    recv    49     3
262150             user     0                   Pop     665     2 lsi.1049344
299840             user     0                    recv   534     1
299856             user     0 172.16.1.1        Pop     661     2 lt-0/0/0.101
lsi.1049344  (VPLS) user     0                   indr 262143     3
                              192.168.0.2       Push 262147, Push 300032(top)   663     2 ge-0/0/0.0

For some reason, I can't see egress statistics where the LSP exits, but I can see it both on ingress and transit:

INGRESS:
admin@Lab-R1> show mpls lsp statistics 
Ingress LSP: 1 sessions
To              From            State     Packets            Bytes LSPname
192.168.255.3   192.168.255.1   Up             24             2432 r1-to-r3
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To              From            State     Packets            Bytes LSPname
192.168.255.1   192.168.255.3   Up             NA               NA r3-to-r1
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

TRANSIT:


admin@Lab-R2> show mpls lsp statistics    
Ingress LSP: 1 sessions
To              From            State     Packets            Bytes LSPname
192.168.255.5   192.168.255.2   Dn             NA               NA r2-to-r5
Total 1 displayed, Up 0, Down 1

Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 2 sessions
To              From            State     Packets            Bytes LSPname
192.168.255.1   192.168.255.3   Up             24             2432 r3-to-r1
192.168.255.3   192.168.255.1   Up             24             2432 r1-to-r3
Total 2 displayed, Up 2, Down 0
************

EGRESS (can't see Egress stats for some reason, but ingress going back the other way matches):

admin@Lab-R3> show rsvp session statistics 
Ingress RSVP: 1 sessions
To              From            State     Packets            Bytes LSPname
192.168.255.1   192.168.255.3   Up             24             2432 r3-to-r1
Total 1 displayed, Up 1, Down 0

Egress RSVP: 1 sessions
To              From            State     Packets            Bytes LSPname
192.168.255.3   192.168.255.1   Up             NA               NA r1-to-r3
Total 1 displayed, Up 1, Down 0

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Again i'm not exactly sure why I can't see bytes egressing an LSP, but I should think you would be able to see the counters incrementing on the ingress of both LSPs.

Will

> I guess first thing -- is the traffic successfully making it across the MPLS network from one "machine" to the other?
Yes. Also if i disconnect one cable, traffic flows through another cable and so on. (failover)

I also can't see Egress statistics in my lab. ... Unfortunately I didn't changed anything and it is still going only through one LSP

root@aa> show mpls lsp statistics                   
Ingress LSP: 2 sessions
To              From            State     Packets            Bytes LSPname
172.28.1.3      172.28.1.1      Up             90             6480 dcd1-old-str
172.28.1.3      172.28.1.1      Up        2736963       3033460969 dcd1-new-str
Total 2 displayed, Up 2, Down 0

Egress LSP: 4 sessions, 4 detours
To              From            State     Packets            Bytes LSPname
172.28.1.1      172.28.1.3      Up             NA               NA str-new-dcd1
172.28.1.1      172.28.1.3      Up             NA               NA str-old-dcd1
172.28.1.1      172.28.1.3      Up             NA               NA str-new-dcd1
172.28.1.1      172.28.1.3      Up             NA               NA str-old-dcd1
Total 4 displayed, Up 4, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down  

root@aa> show route forwarding-table family mpls    
Routing table: default.mpls
MPLS:
Destination        Type RtRef Next hop           Type Index NhRef Netif
default            perm     0                    dscd    50     1
0                  user     0                    recv    49     3
1                  user     0                    recv    49     3
2                  user     0                    recv    49     3
262147             user     0                   Pop     670     2 lsi.1048576
262155             user     0                   Pop     678     2 lsi.1048577
262163             user     0                   Pop     688     2 lsi.1048578
262171             user     0                   Pop     696     2 lsi.1048579
262179             user     0                   Pop     704     2 lsi.1048580
262187             user     0                   Pop     712     2 lsi.1048581
262195             user     0                   Pop     720     2 lsi.1048582
262203             user     0                   Pop     728     2 lsi.1048583
262211             user     0                   Pop     736     2 lsi.1048584
262219             user     0                   Pop     744     2 lsi.1048585
262227             user     0                   Pop     752     2 lsi.1048586
262235             user     0                   Pop     760     2 lsi.1048587
262243             user     0                   Pop     768     2 lsi.1048588
262251             user     0                   Pop     776     2 lsi.1048589
lsi.1048576  (VPLS) user     0                   indr 262143     5
                                                 ulst 262142     2
                              10.0.10.3         Push 262145   661     1 ge-0/0/0.10
                              10.0.11.3         Push 262145   662     1 ge-0/0/1.11
                              10.0.11.3         Push 262145   663     1 ge-0/0/1.11
                              10.0.10.3         Push 262145   664     1 ge-0/0/0.10
                              10.0.11.3         Push 262145   665     1 ge-0/0/1.11
                              10.0.10.3         Push 262145   666     1 ge-0/0/0.10
                              10.0.10.3         Push 262145   815     1 ge-0/0/0.10
                              10.0.11.3         Push 262145   814     1 ge-0/0/1.11
lsi.1048577  (VPLS) user     0                   indr 262145     4
                              10.0.11.3         Push 262153   672     1 ge-0/0/1.11
lsi.1048578  (VPLS) user     0                   indr 262147     3
                              10.0.10.3         Push 262161   680     1 ge-0/0/0.10
lsi.1048579  (VPLS) user     0                   indr 262149     3
                              10.0.10.3         Push 262169   689     1 ge-0/0/0.10
lsi.1048580  (VPLS) user     0                   indr 262151     3
                              10.0.10.3         Push 262177   697     1 ge-0/0/0.10
lsi.1048581  (VPLS) user     0                   indr 262153     3
                              10.0.10.3         Push 262185   705     1 ge-0/0/0.10
lsi.1048582  (VPLS) user     0                   indr 262155     3
                              10.0.10.3         Push 262193   713     1 ge-0/0/0.10
lsi.1048583  (VPLS) user     0                   indr 262157     3
                              10.0.10.3         Push 262201   721     1 ge-0/0/0.10
lsi.1048584  (VPLS) user     0                   indr 262159     3
                              10.0.10.3         Push 262209   729     1 ge-0/0/0.10
lsi.1048585  (VPLS) user     0                   indr 262161     3
                              10.0.10.3         Push 262217   737     1 ge-0/0/0.10
lsi.1048586  (VPLS) user     0                   indr 262163     3
                              10.0.11.3         Push 262225   746     1 ge-0/0/1.11
lsi.1048587  (VPLS) user     0                   indr 262165     3
                              10.0.11.3         Push 262233   754     1 ge-0/0/1.11
lsi.1048588  (VPLS) user     0                   indr 262167     3
                              10.0.11.3         Push 262241   762     1 ge-0/0/1.11
lsi.1048589  (VPLS) user     0                   indr 262169     3
                              10.0.11.3         Push 262249   770     1 ge-0/0/1.11

I don't know if this will ultimately work but I have a few ideas.  BGP is the key here - it is the protocol that is determining which LSP to take.

I would enable ECMP & maybe BGP multipath.  When BGP does the lookup in inet.3 it will need both LSPs marked as active under the far-end routers loopback address.

I have a thunderstorm (and power surges) going on at my house so I cannot power up my gear or I would test.

I was told that load-balancing VPLS on srx100 - 650 with 10.3 and earlier releases is not possible