Origin IGP, metric 500, localpref 100, valid, external, best
Extended Community: RT:65000:741
So both paths have same local pref (100), AS path length (2), origin (IGP), MED ( not applicable).
The next thing AFTER MED is not clear to mer; I bileve what matters is AS-PATH after addition of eBGP mutilpath feature in our case. But what is meant by AS-PATH ? Does it means that we have to equate AS-PATH patemeter for both paths ?
according to the descriptions above you can not load balance for one prefix when the two pathes are different. In fact your case looked to the peering router like "originated in 64600 and going through another SP: 64600". The point is here that the value of the ASes in the path does not matter (except own AS).
So the usual trick in the internet is to split the IP address space and do a sort of load sharing prefering one prefix through one ISP and the other prefix through the other ISP.
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 custome...