Manual Chapter : DC1 BIG-IQ CM routing analysis

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 8.0.0
Manual Chapter

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.