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 549 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

299 New Members signed up the last 30 days!

 
satisfaction-guaranteed

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

Tags:


Notable Replies

  1. HI Rene,

    you mentioned two methods to solve the two same AS issue.

    Use Allow-AS in to overrule the loop prevention mechanism of external BGP.
    Use AS override to change the AS number on the PE routers.

    my question is that among both method which method should I use for which situation?

    thanks,
    Nyi Nyi.

  2. Hi Nyi Nyi,

    Both will get the job done, the main difference is that allow AS in is configured on the customer routers and AS override is done on the SP routers. In the real world you probably don't have access to both the customer and SP routers so it's possible that only one of the two options is available to you.

    Rene



  3. Hi Rene,
    everything was clear about this lesson but am confused why did you configure AS 12 on Router CE1? It should have been AS1. If we configure different AS then we dont have to use Allowas-in command, right?

    hostname CE1
    !
    interface Loopback0
    ip address 1.1.1.1 255.255.255.255
    !
    interface GigabitEthernet0/1
    ip address 192.168.12.1 255.255.255.0
    duplex auto
    speed auto
    media-type rj45
    !
    router bgp 12
    bgp log-neighbor-changes
    network 1.1.1.1 mask 255.255.255.255
    neighbor 192.168.12.2 remote-as 234
    neighbor 192.168.12.2 allowas-in
    !
    end

  4. Excellent lab Rene! keep it up!

  5. Hi Eleever,

    You mean this part?

     address-family ipv4
      no neighbor 4.4.4.4 activate
     exit-address-family
     !
     address-family vpnv4
      neighbor 4.4.4.4 activate
      neighbor 4.4.4.4 send-community extended
     exit-address-family

    What is does is that we don't exchange IPv4 unicast routes but only VPNv4 routes with our neighbor.

    Rene

Continue the discussion forum.networklessons.com

7 more replies

Participants