Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
well, anything is possible, but considering the type of question asked by Vicky and the attached topology I don't think that PfR is a realistic solution in this case due to the considerable efforts required in term of hardware and software requirements and the completely new subset of networking knowlegde and skills (which is not straightforward nor intuitive...).
OeR/PfR might be something a little more solid than "anything is possible". It's also realistic as I've run OER/PfR on 2811s working with dual MPLS (L3 VPN) vendors. I didn't find hardware and software requirements much of an impediment.
"type of question" Well a question included "can you suggest best method to achieve that for forward and reverse traffic." IMO, working with just Cisco routers, it doesn't get much better.
Does it require new knowledge and skills? Indeed it may. I don't see Vicky's questions discounting a possible solution if new knowledge and/or skills would be needed. I didn't find a basic OER/PfR load sharing configuration that complex.
"not straightforward nor intuitive" - ah, touche - you've read Cisco's OER/PfR documentation? - laugh.
Using a metaphor nuclear power is an excellent way to warm up water, but I am not sure it is a wise idea to suggest building a nuclear plant in your back garden to have hot water for your shower....
I'm not quite sure OER/PfR is as complex as building your own backyard nuclear power plant to warm up water for you shower; maybe a better metaphor would be a solar water heater .
Anyway, to recap, and given what the OP's diagram seems to show.
GLBP might be the "easiest" solution.
Multipath routing would be more complex and might (statically) balance flows better. What Riccardo was suggesting, using the L3 switch(es?) as gateway would simplify multipath routing, but it might also be done from a gateway router (i.e. either via EIGRP's variance, or "fibbing" to other routing protocols that only support ECMP [I've done the latter pre GLBP and OER technologies]).
OER/PfR can do dynamic load balancing and analyze (and tune) for performance. It can be used alone, but personally, I like to start with GLBP or routing multipath and then allow OER/PfR to optimize/tune.
