Timeline for Juniper - ECMP with BGP
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 17, 2023 at 12:24 | comment | added | Benjamin Dale | Juniper will treat each ping request as a seperate flow (even though a continuous stream of pings from one host to another can be technically grouped into a "flow" by the Identifier field). A default iPerf test is generally only a single flow, but multiple can be initiated in parallel via command-line options. When you see both links being utilised, it may be that the client-server session is going over one link, but the return server-client traffic is being balanced over the other link. | |
| Aug 11, 2023 at 13:18 | comment | added | Jordan Head | Generally speaking for IPv4 it's Src/Dst IP and Src/Dst Port, but technically it also depends upon the packet's encapsulation on ingress and egress (i.e. is it IPv4 in and IPv4 out or is it IPv4 in and MPLS out, etc.) There are also configurable items like interface that can be added to the hash algorithm. | |
| Aug 10, 2023 at 14:48 | comment | added | Seathorn | So if a Juniper router identifies a traffic flow, then it will push the traffic only one connection. A second flow however will use the other next-hop. But how does the router differentiate the traffic flows. Based on the combination of source IP+port and destination IP+port? | |
| Aug 9, 2023 at 20:43 | history | answered | Jordan Head | CC BY-SA 4.0 |