Manual Chapter :
Overview of TMOS Routing
Applies To:
Show Versions
BIG-IP AAM
- 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1
BIG-IP APM
- 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1
BIG-IP GTM
- 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1
BIG-IP Analytics
- 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1
BIG-IP Link Controller
- 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1
BIG-IP LTM
- 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1
BIG-IP PEM
- 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1
BIG-IP AFM
- 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1
BIG-IP ASM
- 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1
Overview of routing administration in TMOS
As a BIG-IP system administrator, you typically manage routing on the system by configuring these BIG-IP system features.
| BIG-IP system feature | Benefit |
|---|---|
| Interfaces | For the physical interfaces on the BIG-IP system, you can configure properties such as flow control and sFlow polling intervals. You can also configure the Link Layer Discovery Protocol (LLDP), globally for all interfaces and on a per-interface basis. |
| Trunks | A trunk is a logical grouping of interfaces on the BIG-IP system. When you create a trunk, this logical group of interfaces functions as a single interface. The BIG-IP system uses a trunk to distribute traffic across multiple links, in a process known as link aggregation. |
| VLANs | You create VLANs for the external and internal BIG-IP networks, as well as for high-availability communications in a BIG-IP device clustering configuration. The BIG-IP system supports VLANs associated with both tagged and untagged interfaces. |
| Virtual and self IP addresses | You can create two kinds of IP addresses locally on the BIG-IP system. A virtual IP address is the address associated with a virtual server. A self IP address is an IP address on the BIG-IP system that you associate with a VLAN or VLAN group, to access hosts in that VLAN or VLAN group. Whenever you create virtual IP addresses and self IP addresses on the BIG-IP system, the system automatically adds routes to the system that pertain to those addresses, as directly-connected routes. |
| DHCP support | You can configure the BIG-IP system to function as a DHCP relay or renewal agent. You can also force the renewal of the DHCP lease for the BIG-IP system management port. |
| Packet filtering |
Using packet filters, you can specify whether a BIG-IP system interface should accept or reject certain packets based on criteria such as source or destination IP address. Packet filters enforce an access policy on incoming traffic. |
| IP address translation | You can configure network address translation (NATs) and source network address translation (SNATs) on the BIG-IP system. Creating a SNAT for a virtual server is a common way to ensure that pool members return responses to the client through the BIG-IP system. |
| Route domains | You create route domains to segment traffic associated with different applications and to allow devices to have duplicate IP addresses within the same network. |
| Static routes | For destination IP addresses that are not on the directly-connected network, you can explicitly add static routes. You can add both management (administrative) and TMM static routes to the BIG-IP system. |
| Dynamic routing | You can configure the advanced routing modules (a set of dynamic routing protocols and core daemons) to ensure that the BIG-IP system can learn about routes from other routers and advertise BIG-IP system routes. These advertised routes can include BIG-IP virtual addresses. |
| Spanning Tree Protocol (STP) | You can configure any of the Spanning Tree protocols to block redundant paths on a network, thus preventing bridging loops. |
| The ARP cache | You can manage static and dynamic entries in the ARP cache to resolve IP addresses into MAC addresses. |
| WCCPv2 support | WCCPv2 is a content-routing protocol developed by Cisco Systems. It provides a mechanism to redirect traffic flows in real time. The primary purpose of the interaction between WCCPv2-enabled routers and a BIG-IP system is to establish and maintain the transparent redirection of selected types of traffic flowing through those routers. |
About BIG-IP system routing tables
The BIG-IP system contains two sets of routing tables:
- The Linux routing tables, for routing administrative traffic through the management interface
- A special TMM routing table, for routing application and administrative traffic through the TMM interfaces
As a BIG-IP administrator, you configure the system so that the BIG-IP system can use these routing tables to route both management and application traffic successfully.
About BIG-IP management routes and TMM routes
The BIG-IP system maintains two kinds of routes:
- Management routes
- Management routes are routes that the BIG-IP system uses to forward traffic through the special management interface. The BIG-IP system stores management routes in the Linux (that is, kernel) routing table.
- TMM routes
- TMM routes are routes that the BIG-IP system uses to forward traffic through the Traffic Management Microkernel (TMM) interfaces instead of through the management interface. The BIG-IP system stores TMM routes in both the TMM and kernel routing tables.
Viewing routes on the BIG-IP system
You can use the tmsh utility to view different kinds of routes on the BIG-IP system.
- Open a console window, or an SSH session using the management port, on the BIG-IP system.
- Use your user credentials to log in to the system.
-
Perform one of these actions at the command prompt:
- To view all routes on the system, type: tmsh show /net route
- To view all configured static routes on the system, type: tmsh list /net route
You are now able to view BIG-IP system routes.
