Understand load-balancing - available routes to same dest not equals load balancing ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2016 06:18 PM - edited 03-08-2019 05:30 AM
Hi all,
Just a simple question, but it seems complicated to me.
Q1) if I have 2 static route with the same AD etc,
S 192.168.101.0/24 [10/0] via 192.168.100.2, FastEthernet0/1
[10/0] via 192.168.100.3, FastEthernet0/2
Will traffic be load-balance across the 2 interface ?
Q2) I have read up
http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/5212-46.html, it mentioned
If the router receives and installs multiple paths with the same administrative distance and cost to a destination, load-balancing can occur
Assuming then in my case above, how does per destination load balancing works ? It wont load balance across the interface already if it is always going to the same destination, isn't it ?
Q3) The same applies for CEF with per packet and destination load-balancing.
In short, can I say
- routes available for load-balancing to a particular destination network in the routing table (show ip route) just serve as a list available/paths for the l3switch/router to choose
- the actual load-balancing still depends if per packet or per destination is set
right ?
Q4) in that case, the available routes for load balancing to a particular destination is still done in a round-robin fashion only if
- per packet loadbalancing is set or
- packet is send to a new destination
am I right ?
Hope to hear from you gurus soon.
Thank you!
Regards,
Noob
- Labels:
-
Other Switching
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2016 09:49 AM
Anyone ? ;(
