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

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 8.3.0, 8.2.0, 8.1.0, 8.0.0
Manual Chapter

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.
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