# ISP Link Load Blancing Use Case

**URL:** <https://community.f5.com/t/isp-link-load-blancing-use-case/77171>\
**Category:** Technical Forums\
**Tags:** application-delivery\
**Created:** [June 5, 2026, 8:47am UTC](https://community.f5.com/t/isp-link-load-blancing-use-case/77171 "2026-06-05T08:47:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![himanshugandhi](https://avatars.discourse-cdn.com/v4/letter/h/e8c25b/32.png) [@himanshugandhi](https://community.f5.com/u/himanshugandhi)\
**Post date:** [June 5, 2026, 8:47am UTC](https://community.f5.com/t/isp-link-load-blancing-use-case/77171/1 "2026-06-05T08:47:09Z")

</div>

Hello everyone,

I have a requirement to implement source-based outbound routing across two ISP links on a BIG-IP LTM and I am looking for guidance on the correct way to achieve this

Environment:

- BIG-IP LTM (version: fill in your version)

- Two ISP links: ISP-1 (Airtel) and ISP-2 (TCL)

- Behind the BIG-IP there is a firewall

- Behind the firewall there are two internal subnets:

- 10.20.0.0/24 — this subnet should use ISP-1 (Airtel) for internet access

- 10.50.0.0/24 — this subnet should use ISP-2 (TCL) for internet access

- The firewall’s default gateway points to the BIG-IP internal interface

Requirement:

1. When both ISP links are UP:

- Traffic from 10.20.0.0/24 must go out via ISP-1 (Airtel)

- Traffic from 10.50.0.0/24 must go out via ISP-2 (TCL)

2. When ISP-1 (Airtel) goes DOWN:

- Traffic from 10.20.0.0/24 should automatically failover and go out via ISP-2 (TCL)

3. When ISP-2 (TCL) goes DOWN:

- Traffic from 10.50.0.0/24 should automatically failover and go out via ISP-1 (Airtel)

4. When the failed link recovers, traffic should automatically return to its preferred ISP.

In short — each subnet has a preferred ISP, but if that ISP is down, it should fall back to the other ISP automatically. Both failover directions must work.

What I want to know:

1. What is the correct and recommended way to achieve this on BIG-IP LTM?

2. What objects need to be configured — Virtual Servers, Pools, SNAT, iRules, routes?

3. How does the BIG-IP detect that an ISP link is down and trigger the failover automatically?

4. Are there any gotchas or common mistakes to avoid in this type of setup?

Any help, working configuration examples, or pointers to relevant documentation would be greatly appreciated.

Thank you!

---

<div class="post-metadata">

**Author:** ![Anoop\_Jayadharan](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/anoop_jayadharan/32/17359_2.png) [@Anoop\_Jayadharan](https://community.f5.com/u/Anoop_Jayadharan)\
**Post date:** [June 5, 2026, 3:04pm UTC](https://community.f5.com/t/isp-link-load-blancing-use-case/77171/2 "2026-06-05T15:04:25Z")

</div>

@himanshugandhi

I reckon [myF5](https://my.f5.com/manage/s/article/K56062259) would provide enough fuel to get off the mark.

---

<div class="post-metadata">

**Author:** ![Paulius](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/paulius/32/21698_2.png) [@Paulius](https://community.f5.com/u/Paulius)\
**Post date:** [June 9, 2026, 3:37pm UTC](https://community.f5.com/t/isp-link-load-blancing-use-case/77171/3 "2026-06-09T15:37:01Z")

</div>

Is the BIG-IP device your perimeter device? You can use the option that Anoop\_Jayadharan provided but the F5 is not really a routing device even though it’s capable of performing this function. You’re better off using a router to perform the function of routing traffic between two ISP connections.