The first thing you need to do is remove the delay from both links so R1 can see both R2's LANs via both links.
So from R1 you should something like this:
R1#show ip route eigrp
D 192.168.10.0/24 [90/2195456] via 192.168.1.2, 00:00:46, Serial1/0
[90/2195456] via 192.168.1.6, 00:00:46, Serial2/0
D 192.168.11.0/24 [90/2195456] via 192.168.1.2, 00:00:05, Serial1/0
[90/2195456] via 192.168.1.6, 00:00:05, Serial2/0
Now, you want R1 to reach 192.168.11.0 via 192.168.1.2 and 192.168.10.0 via 192.168.1.6, then you do the following:
router eigrp 1
offset-list Subnet10 in 2195456 Serial1/0
offset-list Subnet11 in 2195456 Serial2/0
ip access-list standard Subnet10
permit 192.168.10.0 0.0.0.255
ip access-list standard Subnet11
permit 192.168.11.0 0.0.0.255
Now, you have in R1's routing table:
R1#show ip route eigrp
D 192.168.10.0/24 [90/2195456] via 192.168.1.6, 00:01:07, Serial2/0
D 192.168.11.0/24 [90/2195456] via 192.168.1.2, 00:01:07, Serial1/0
If I bring one of the interfaces down:
*Aug 11 18:48:06.215: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.1.6 (Serial2/0) is down: interface down
*Aug 11 18:48:08.203: %LINK-5-CHANGED: Interface Serial2/0, changed state to administratively down
*Aug 11 18:48:09.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to down
R1(config-if)#do show ip route eigrp
D 192.168.10.0/24 [90/4390912] via 192.168.1.2, 00:00:35, Serial1/0
D 192.168.11.0/24 [90/2195456] via 192.168.1.2, 00:02:00, Serial1/0
Therefore, R1 is taken care of - however with R2 the situation is different since you have to alter routing based on the source and dynamic routing protocols can only alter routing based on the destination. On R2, you need to use Policy Based Routing (PBR).
R2's routing table
R2#show ip route eigrp
D 192.168.0.0/24 [90/2195456] via 192.168.1.1, 00:05:08, Serial2/0
[90/2195456] via 192.168.1.5, 00:05:08, Serial3/0
ip prefix-list Subnet10 seq 5 permit 192.168.10.0/24
ip prefix-list Subnet11 seq 5 permit 192.168.10.0/24
route-map Subnet10 permit 10
match ip address prefix-list Subnet10
set ip next-hop 192.168.1.5
route-map Subnet11 permit 10
match ip address prefix-list Subnet11
set ip next-hop 192.168.1.1
ip address 192.168.10.1 255.255.255.0
ip policy route-map Subnet10
ip address 192.168.11.1 255.255.255.0
ip policy route-map Subnet11
Now, we verify it works and turn debug on R2 and ping from a device behind R2 from both subnets 192.168.10.0 and 192.168.11.0
I'm afraid PBR won't provide load-balancing for you. The best it can offer is failover to a secondary next-hop by inserting another next-hop ip address in the set ip next-hop command under the route-map.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...