running bgp, and have the 2 t1's using load sharing however they dont seem to be sharing the traffic..can anyone point me in direction of any sample configs, or some things that need to be done to make this work?
The easiest way to get the Load Sharing on the Internet Links is to divide the traffic from the point of origin i.e. using the VLAN-s / Proxy Servers from where the traffic is originating and then pointing it to the respective T-1s.
Also, if you want to you want to use the Fault-Tolerance you may do some additional config (using the PBR with Static Route Redist.) as the moment one of the T-1 would go down, the Router would purge the static route from the Routing Table and then same could be injected into the WAN-Edge switch.
Also, if you want to go ahead with Loab Balancing, Load Sharing and Fault Tolerance all in one, I guess the best bet would be to use a Raware Device for this.
Please get back if you want more details on the Load Sharing using the PBR, we have been using the same in one of our customer's side.
This scenario shows how to achieve load sharing when multiple links exist between a remote AS and a local AS. These links are terminated in one router at the local AS and on multiple routers at remote ASs in a single-homed BGP environment. The Network Diagram is an example of such a network.
Topology : Router A ---- Router B
---- Router C
This sample configuration uses the maximum-paths command. By default, BGP chooses one best path among the possible equal-cost paths that are learned from one AS. However, you can change the maximum number of parallel equal-cost paths that are allowed. In order to make this change, include the maximum-paths paths command under the BGP configuration. Use a number between 1 and 6 for the paths argument.
config A :
ip address 22.214.171.124 255.255.255.0
interface Serial 0
ip address 126.96.36.199 255.255.255.0
interface Serial 1
ip address 188.8.131.52 255.255.255.0
router bgp 11
neighbor 184.108.40.206 remote-as 10
neighbor 220.127.116.11 remote-as 10
!--- This command specifies the maximum number of paths
!--- to install in the routing table for the specific destination.
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...