F5 Logo MyF5
Search
  1. MyF5 Home
  2. Planning a Centralized Management and Visibility Deployment
  3. Routing Considerations for a BIG-IQ solution
Manual Chapter : Routing Considerations for a BIG-IQ solution

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 7.1.0
Manual Chapter

Routing Considerations for a BIG-IQ solution

Routing requirements overview

To simplify the task of creating the required routing for your BIG-IQ solution, consider the following set of diagrams and tables that describe a typical BIG-IQ solution. These diagrams illustrate the subnets that the components use to communicate in a BIG-IQ solution that uses four NICs. The accompanying table then details the static routing assignments that need to be made.
This example system has two BIG-IQ instances, four BIG-IQ data collection devices, and "several" BIG-IP devices. These devices are deployed to two data centers as part of a disaster recovery solution and use four subnets. These figures illustrate the subnet topology and the tables detail the static routing assignments for one of the data centers. The details for the other data center are symmetric. Understanding the illustrations and analysis for data center 1 (DC1) in this hypothetical system should provide you with all you need to know to determine the requirements for data center (DC2) in the same system.
We strongly encourage you to use a similar organizational aide to help you visualize and record the static routing requirements needed for your solution. To further grasp the way to use this aide, refer to
DC1 BIG-IQ CM routing analysis.

DC1 BIG-IQ CM routing analysis

This discussion examines the routing table for the BIG-IQ CM in data center 1 (DC1). The discussion references diagrams and tables that you can link to below.
A quick look at either of the routing tables reveals that a number of the routes needed for the system illustrated in the corresponding routing diagram are not included in the table. That's because devices that are on the same subnet do not need a static route.
eth1 to DC2 BIG-IQ CM & DCDs on the Discovery subnet
The entry for this route is in cell A5. The static route goes from the eth1 NIC in data center 1 to the discovery subnet in data center 2. It is specified in the table as:
10.101.101
.0 255.255.255.0 10.1.1.254
.
  • The first octet
    10.101.101
    .0
     specifies the destination IP address used to communicate with the Discovery subnet in data center 1.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.1.1.254
     is the gateway for this subnet.
This route uses the Discovery subnet to go from BIG-IQ Centralized Management (CM) device in DC1 to BIG-IQ and DCDs in DC2. The BIG-IQ CM in DC1 uses this route to discover DCDs in DC2 and to negotiate elastic search management with the BIG-IQ CM in DC2 in disaster recovery scenarios.
eth1 interface to BIG-IP devices on the Discovery subnet
The entry for this route is in cell A6. The static route for the eth2 NIC is
10.104.104
.0 255.255.255.0 10.1.1.254
.
  • The first octet
    10.104.104
    .0
     specifies the destination IP address used to communicate with the Cluster subnet in data center 2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.1.1.254
     is the gateway for this subnet.
This route uses the Discovery subnet to go from BIG-IQ CM in DC1 to the BIG-IPs in DC2. This route also plays a role in disaster recovery scenarios.
eth1 interface to DC1 BIG-IP devices on the Discovery subnet
The entry for this route is in cell A7. The static route for the eth2 NIC is
10.4.4
.0 255.255.255.0 10.1.1.254
.
  • The first octet
    10.4.4
    .0
     specifies the destination IP address used to communicate with the Cluster subnet in data center 2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.1.1.254
     is the gateway for this subnet.
This route uses the Discovery subnet to go from BIG-IQ CM in DC1 to the BIG-IPs in DC1. This route also plays a role in disaster recovery scenarios.
eth2 interface to DC2 DCDs on the Cluster subnet
The entry for this route is in cell A8. The static route for the eth2 NIC is
10.102.102
.0 255.255.255.0 10.2.2.254
.
  • The first octet
    10.102.102
    .0
     specifies the destination IP address used to communicate with the cluster subnet in DC2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.2.2.254
     is the gateway for this subnet.
This route uses the Cluster subnet to go from BIG-IQ in DC1 to the BIG-IQ and DCDs in DC2. DCDs in DC1 use this route to exchange and manage data stored on DCDs in DC2. This route also plays a role in disaster recovery scenarios.

DC1 BIG-IQ DCD routing analysis

This routing analysis examines the routing table for the BIG-IQ DCDs in data center 1(DC1). The discussion references diagrams and tables that you can link to below.
A quick look at either of the routing tables reveals that a number of the routes needed for the system illustrated in the corresponding routing diagram are not included in the table. That's because devices that are on the same subnet do not need a static route.
eth1 to DC2 BIG-IQ CM & DCDs on the Discovery subnet
The entry for this route is in cell A13. The static route goes from the eth1 NIC in DC1 to the discovery subnet in DC2. It is specified in the table as:
10.101.101
.0 255.255.255.0 10.1.1.254
  • The first octet
    10.101.101
    .0
     specifies the destination IP address used to communicate with the Discovery subnet in DC1.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.1.1.254
     is the gateway for this subnet.
This route uses the Discovery subnet to go from the DCDs in DC1 to the BIG-IQ systems and DCDs in DC2. As the subnet name implies this route is mostly used for discovery, but also plays a role in disaster recovery scenarios.
eth1 interface to DC2 BIG-IP devices on the Discovery subnet
The entry for this route is in cell A14. The static route for the eth2 NIC is
10.104.104
.0 255.255.255.0 10.1.1.254
.
  • The first octet
    10.104.104
    .0
     specifies the destination IP address used to communicate with the cluster subnet in DC2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.1.1.254
     is the gateway for this subnet.
This route uses the Discovery subnet to go from the BIG-IQ systems in DC1 to the BIG-IP devices in DC2. As the subnet name implies this route is mostly used for discovery, but also plays a role in disaster recovery scenarios.
eth1 interface to DC1 BIG-IP devices on the Discovery subnet
The entry for this route is in cell A15. The static route for the eth2 NIC is
10.4.4
.0 255.255.255.0 10.1.1.254
.
  • The first octet
    10.4.4
    .0
     specifies the destination IP address used to communicate with the cluster subnet in DC2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.1.1.254
     is the gateway for this subnet.
This route uses the Discovery subnet to go from the BIG-IQ systems in DC1 to the BIG-IP devices in DC1. As the subnet name implies this route is mostly used for discovery, but also plays a role in disaster recovery scenarios.
eth2 interface to DC2 DCDs on the Cluster subnet
The entry for this route is in cell A16. The static route for the eth2 NIC is
10.102.102
.0 255.255.255.0 10.2.2.254
.
  • The first octet
    10.102.102
    .0
     specifies the destination IP address used to communicate with the cluster subnet in DC2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.2.2.254
     is the gateway for this subnet.
This route uses the Cluster subnet to go from BIG-IQ in DC1 to the BIG-IQ and DCDs in DC2. DCDs in DC1 use this route to exchange and manage data stored on DCDs in DC2. This route also plays a role in disaster recovery scenarios.
eth3 interface to DC2 BIG-IPs on the Listener subnet
The entry for this route is in cell A17. The static route for the eth3 NIC is
10.5.5
.0 255.255.255.0 10.3.3.254
.
  • The first octet
    10.5.5
    .0
     specifies the destination IP address used to communicate with the listener subnet in DC2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.3.3.254
     is the gateway for this subnet.
This route uses the Listener subnet to go from BIG-IQ DCDs in DC1 to the BIG-IP devices in DC1. DCDs in DC1 use this route to communicate event, alert, and performance analytics data generated by BIG-IP devices in DC1. This route also plays a role in disaster recovery scenarios.
eth3 interface to DC2 BIG-IPs on the Listener subnet
The entry for this route is in cell A18. The static route for the eth3 NIC is
10.105.105
.0 255.255.255.0 10.3.3.254
.
  • The first octet
    10.105.105
    .0
     specifies the destination IP address used to communicate with the listener subnet in DC2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.3.3.254
     is the gateway for this subnet.
This route uses the Listener subnet to go from BIG-IQ DCDs in DC1 to the BIG-IP devices in DC2. DCDs in DC1 use this route to communicate event, alert, and performance analytics data generated by BIG-IP devices in DC2. This route also plays a role in disaster recovery scenarios.

DC1 BIG-IP routing analysis

This discussion examines the routing table for the BIG-IP devices in data center 1 (DC1). The discussion references diagrams and tables that you can link to below.
A quick look at either of the routing tables reveals that a number of the routes needed for the system illustrated in the corresponding routing diagram are not included in the table. That's because devices that are on the same subnet do not need a static route.
eth0 to DC1 BIG-IP devices on the Discovery subnet
The entry for this route is in cell A23. The static route goes from the eth0 NIC in DC1 to the discovery subnet in DC1. It is specified in the table as:
10.1.1
.0 255.255.255.0 10.4.4.254
  • The first octet
    10.1.1
    .0
     specifies the destination IP address used to communicate with the Discovery subnet in DC1.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.0.0.254
     is the gateway for this subnet.
This route uses the Discovery subnet to go from BIG-IQ CM and DCD devices in DC1 to the BIG-IP devices in DC1. As the subnet name implies this route is mostly used for discovery, but also plays a role in disaster recovery scenarios.
eth0 to DC2 BIG-IP devices on the Discovery subnet
The entry for this route is in cell A24. The static route goes from the eth0 NIC in DC1 to the discovery subnet in DC2. It is specified in the table as:
10.101.101
.0 255.255.255.0 10.4.4.254
  • The first octet
    10.101.101
    .0
     specifies the destination IP address used to communicate with the Discovery subnet in DC2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.4.4.254
     is the gateway for this subnet.
This route uses the Discovery subnet to go from BIG-IQ BIG-IP devices in DC1 to the BIG-IP devices in DC2. As the subnet name implies this route is mostly used for discovery, but also plays a role in disaster recovery scenarios.
eth3 interface to DC2 DCDs on the Listener subnet
The entry for this route is in cell A26. The static route for the eth3 NIC is
10.103.103
.0 255.255.255.0 10.5.5.254
.
  • The first octet
    10.103.103.0
     specifies the destination IP address used to communicate with the cluster subnet in DC2.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.3.3.254
     is the gateway for this subnet.
This route uses the Listener subnet to go from BIG-IP devices in DC1 to the DCDs in DC2. BIG-IP devices in DC1 use this route to communicate event, alert, and performance analytics data to DCDs in DC2. This route also plays a role in disaster recovery scenarios.
eth3 interface to DC1 DCDs on the Listener subnet
The entry for this route is in cell A27. The static route for the eth3 NIC is
10.3.3
.0 255.255.255.0 10.5.5.254
.
  • The first octet
    10.3.3
    .0
     specifies the destination IP address used to communicate with the cluster subnet in DC1.
  • The next octet
    255.255.255.0
     specifies the network mask for this subnet.
  • The last octet,
    10.5.5.254
     is the gateway for this subnet.
This route uses the Listener subnet to go from BIG-IP devices in DC1 to the DCDs in DC1. BIG-IP devices in DC1 use this route to communicate event, alert, and performance analytics data to DCDs in DC1. This route also plays a role in disaster recovery scenarios.

Data center 1 routing diagram and table

You can use this diagram and routing table as a visual aid as you analyze the static route requirements for a typical, four-NIC, BIG-IQ deployment. For a description of these routes, refer to To see the diagram and table for the second data center, refer to
Data center 2 routing diagram and table
 on
askf5.com
.
This figure illustrates the network topology for a four subnet deployment.
Data center 1 network topology
This table illustrates the routing table for a four subnet deployment.
The table uses a standard syntax to express a static route. The route expression is comprised by three octets:
<destination address> <decimal subnet mask> <gateway>
. In this expression:
  • the first octet specifies the destination IP address used to communicate with the subnet the route needs to reach.
  • The next octet specifies the network mask in decimal format for the subnet the route needs to reach.
  • The last octet specifies the gateway for the subnet on which the route originates.
Data center 1 routing table

Data center 2 routing diagram and table

You can use this diagram and routing table as a visual aid as you analyze the static route requirements for a typical, four-NIC, BIG-IQ deployment. For a description of these routes, refer to To see the diagram and table for the second data center, refer to
Data center 1 routing diagram and table
 on
askf5.com
.
This figure illustrates the network topology for a four subnet deployment.
Data center 2 network topology
This table illustrates the routing table for a four subnet deployment.
The table uses a standard syntax to express a static route. The route expression is comprised by three octets:
<destination address> <decimal subnet mask> <gateway>
. In this expression:
  • the first octet specifies the destination IP address used to communicate with the subnet the route needs to reach.
  • The next octet specifies the network mask in decimal format for the subnet the route needs to reach.
  • The last octet specifies the gateway for the subnet on which the route originates.
Data center 2 routing table
Contact Support Contact Support

Have a Question?

Support and Sales >

About F5

Education

F5 Sites

Support Tasks




©2023 F5, Inc. All rights reserved.


Trademarks Policies Privacy California Privacy Do Not Sell My Personal Information