Implementation Inject Redundancy and load balancing
business
Description
Implementation Inject
Redundancy and load balancing –
A customer has 2 routers (R3 and R4). Both routers connect to 2 ISPs routers (R1 and R2) that provide them with "public" IP addresses via DHCP in the 88.88.88.0/24 range (ISP1) and 99.99.99.0/24 (ISP2).
The ISP space is also PATed to the 100.1.0.0/16 range on R1 and R2.
R5 is used at the customer to represent a host or server that will be pinging the web (8.8.8.8).
This mission (I mean inject), if you choose to accept it, is to configure all the routers to achieve load balancing and redundancy WITHOUT USING ANY DYNAMIC PROTOCOLS!
For credits: demonstrates pinging working and load balancing in the following situations:
- With all connected pings from R5 to 8.8.8.8 should equally travel:
- via R3-R1
- via R3-R2
- via R4-R1
- via R4-R2
- With R1 inside interface disconnected: verify no failures
- With R2 inside interface disconnected: verify no failures
- With R3 outside interface disconnected: verify no failures
- With R4 outside interface disconnected: verify no failures
