We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 557 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)


315 New Members signed up the last 30 days!


100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Notable Replies

  1. Rene,
    Great lesson however, I have questions if we have two ISPs and we would like to route traffic out through ISP-1. It means we need to set up a higher weight on the ISP-1 peering with us and setup a lower weight on the second ISP-2?
    How can we make sure traffic goes out ISP-1 and comes back in using ISP-2?


  2. Hi Hamood,

    That's right, you can use weight to select the path but this is only for the local router. If you want to influence your entire AS then you'll have to use local preference:


    To influence how traffic enters our AS we have a couple of methods, the first one is MED:


    This is only useful when you are multihomed to a single ISP. These two methods will help if you are multihomed to different ISPs:



    Hope this helps!


  3. Hi Rene,
    I have seen some articles regarding to how bgp attributes influence the traffic. There is a table for summary.
    For influence the traffic out of the AS we use local preference inbound, is it possible for you to summary which attribute should be inbound and which should be outbound?
    I assume the table should be like this? Correct me if I am wrong
    attribute inbound(config) influencetraffic
    local preference inbound outbound
    Med outbound inbound
    As prepend outbound inbound
    and so on

  4. Hi Jie,

    Let me give you an overview:

    • Local preference: is propagated throughout the local AS so typically used inbound when we receive eBGP prefixes.

    • MED: sent to neighbor ASes so used outbound.

    • AS Path prepend: normally sent to neighbor ASes so used outbound.


  5. Hi William,

    Weight is the first attribute that is used to determine the best path. Here's a nice way to remember the attributes, something I found on a blog a long time ago:

    “We Love Oranges AS Oranges Mean Pure Refreshment”

    W Weight (Highest)
    L LOCAL_PREF (Highest)
    O Originate (local) routes that are advertise through the "network" command or redistributed from an IGP.
    AS AS_PATH (shortest)
    O ORIGIN Code (IGP > EGP > Incomplete)
    M MED (lowest)
    P Paths (External > Internal)
    R RID (lowest)


Continue the discussion forum.networklessons.com

32 more replies