301A practice question 11 of 25

An LTM device configured with a management IP address and route and a series of self-IPs and TMM routes. Both management and TMM have a routing entry for 101 10/24 Application traffic is being load balanced and sent to pool member 10.1.1.123 with SNAT Automap and configured. Which route will the LTM device use?

Full set: 147 questions
Answer options
A: TMM route regardless of the management port status Correct answer
B: both routes, which will duplicate traffic on both management and TMM interface
C: equal cost multipath load balancing via both routes
D: management route when TMM interface is down or TMM is offline
E: management route regardless of the management port status
Correct Answer:
A. TMM route regardless of the management port status
Explanation

The F5 BIG-IP architecture maintains a strict separation between the management plane and the data plane, which is handled by the Traffic Management Microkernel (TMM). Application traffic, such as the load-balanced and SNAT-processed traffic described in the scenario, is exclusively handled by TMM. Consequently, TMM uses its own routing table to forward this traffic. The management interface and its associated routing table are reserved for administrative traffic only (e.g., GUI, SSH, NTP) and are never used for forwarding application data. Therefore, the TMM route to 10.1.1.0/24 will be used, irrespective of the management port's status.

Why Incorrect

B. The BIG-IP system does not duplicate traffic across the management and TMM interfaces; it uses distinct routing tables for each plane.
C. Equal-cost multi-path (ECMP) operates on multiple routes within the same routing table, not across the separate management and TMM routing tables.
D. The management interface is not a failover path for application traffic. If the TMM interface or process is down, application traffic will cease to flow.
E. Application traffic is explicitly handled by TMM and its routing table, not the management route.

References

1. F5 Knowledge Base, K13284: Overview of management interface routing (11.x - 17.x).

Section: "Description"

Quote: "The BIG-IP system maintains a separate routing table for the management interface... The management interface is not used for BIG-IP LTM application traffic." This article explicitly states that application traffic does not use the management route.

2. F5 Knowledge Base, K15040: The BIG-IP system maintains a separate routing table for the management interface.

Section: "Description"

Quote: "The BIG-IP system uses the management port for administrative traffic. The Traffic Management Microkernel (TMM) interfaces are used to process application traffic... The BIG-IP system does not use the management route for application traffic." This confirms the strict separation of traffic types.

3. F5 BIG-IP TMOS: Routing Administration, v17.1.

Chapter: "BIG-IP Routing Overview" > "About BIG-IP routing"

Reference: This section details that the BIG-IP system has two routing tables: one for the management interface and one for the TMM interfaces, reinforcing the architectural separation that dictates routing behavior for different traffic types.

Scroll to Top