Configuring a Floating Static Route for Backup Connectivity to the 10.10.0.0/16 Network in Case of R1-Branch2 Link Failure

exhibit. Currently router R1 uses an EIGRP route learned from Branch2 to reach the 10.10.0.0/16 network. Which floating static route would create a backup route to the 10.10.0.0/16 network in the event that the link between R1 and Branch2 goes down?

To create a backup route to the 10.10.0.0/16 network in the event that the link between router R1 and Branch2 goes down, you can add a floating static route on router R1.

A floating static route is a backup route that only becomes active if the primary route is unavailable.

First, let’s assume that the interface on R1 connected to Branch2 is interface GigabitEthernet0/1 with IP address 192.168.1.1/24 and the interface on Branch2 connected to R1 is interface GigabitEthernet0/1 with IP address 192.168.1.2/24.

To configure a floating static route on R1, follow these steps:

1. Determine the IP address of the next hop router or gateway to reach the 10.10.0.0/16 network if the link to Branch2 goes down. Let’s assume the next hop IP address is 192.168.2.1.

2. Configure the static route using the following command on R1:

“`
ip route 10.10.0.0 255.255.0.0 192.168.2.1 200
“`

In this command, `10.10.0.0/16` is the destination network, `255.255.0.0` is the subnet mask, `192.168.2.1` is the next hop IP address, and `200` is the administrative distance (AD) of the floating static route. The AD value of 200 is higher than the AD of the EIGRP route learned from Branch2, ensuring that the floating static route is only used when the primary route is unavailable.

3. Save the configuration on R1 to make the changes persistent, depending on the router’s operating system. For example, on a Cisco IOS router, you can use the `copy running-config startup-config` command.

Now, if the link between R1 and Branch2 goes down, the floating static route on R1 will take effect, and traffic destined to the 10.10.0.0/16 network will be routed through the next hop IP address (192.168.2.1) specified in the static route.

More Answers: