Load sharing between two ISPs

[Learner09]

We have two edge routers from two ISPs with static default routes for internet, both the routers are connected to a layer 3 switch. Currently we have configured HSRP between two routers with default route in the switch towards the virtual IP to achieve active passive scenario between the two ISPs, now we have a requirement to make them as active active so that the traffic load will be shared between the two ISPs. How can we achieve this? Thanks in advance.

[Learner09]

After applying no ip route-cache, I still get the same results. And unfortunately the switch ios is not taking the command

Ip cef load-sharing per-packet '

Switch#sh run int gig0/1
Building configuration...

Current configuration : 127 bytes
!
interface GigabitEthernet0/1
no switchport
ip address 10.50.10.2 255.255.255.252
no ip route-cache
negotiation auto
end

Switch#sh run int gig0/0
Building configuration...

Current configuration : 127 bytes
!
interface GigabitEthernet0/0
no switchport
ip address 10.50.20.2 255.255.255.252
no ip route-cache
negotiation auto
end

[MHM Cisco World]

Ip route-cache cef

Then

Ip cef load-sharing per-packet

MHM

[Learner09]

Thank you, but still I couldn't get through

Ip cef load-sharing per-packet

command

Switch(config)#ip cef load-sharing ?
algorithm Per-destination load sharing algorithm selection
key-control Configure algorithm control values

Switch(config)#ip cef load-sharing al
Switch(config)#ip cef load-sharing algorithm ?
dpi Deep Packet Inspection
include-ports Algorithm that includes layer 4 ports
original Original algorithm
tunnel Algorithm for use in tunnel only environments
universal Algorithm for use in most environments

Switch(config)#ip cef load-sharing algorithm

[MHM Cisco World]

Switch(config)

#ip cef load-sharing algorithm

universal 

Select universal.

You need to add this command to both interface toward two ISP1/2

MHM

[Learner09]

Still the same results unfortunately

[Learner09]

@MHM Cisco World My bad, sorry for being a noob. Its working as expected, load sharing when the destinations are different, which I haven't tried earlier, now I see taking different paths upon tracing different destinations. I haven't focused when you said 'per-destination'

[Joseph W. Doherty]

BTW, highly recommend you do NOT do per packet load sharing especially between two different ISPs.  TCP packets are the often delivered out of order which then often leads to sender believing packets were lost in transit.

[paul driver]

Hello
Alternative solution (see attached file) -  using iplsa/object tracking and policy based routing: