load-balancing at device-interface or service-policy
At device-interface | https://docs.128technology.com/docs/config_reference_guide/#load-balancing |
---|---|
enable TE | traffic-engineering enabled true |
set water-mark ( dev-if BW ) | utilization-high-water-mark: 0 to 100% dev-if bw usage ( if > will no longer be used as an egress point for new session assignments ) utilization-low-water-mark ( if < will be eligible path for new session assignments ) |
if "traffic-engineering transmit-cap" is set, the water-mark will be based on the tx-cap | |
service route policy ( at router level) | |
| |
At the service-policy | https://docs.128technology.com/docs/config_reference_guide/#service-policy |
Justin Blog | |
lb-strategy | hunt: "next-hop targets : Service Agents " ( fill the first server, then the second, . . . based on server capability ) 1- Enter the session capability / servers 2- 128T will load balance sessions based on server capability: 2a- Will fill the first server to the Max number of session 2b- then fill the second , then third server. |
proportional: ( Every server get a proportion / percentage of sessions ) 1- Enter the session capability / servers ( work out the total number of TOTAL sessions capacity across all the servers ) 2- 128T will weighted-round robin the sessions/ Load balance over the different servers. | |
Service route ploicy | |