Scribd Logo
Upload

Welcome to Scribd!

  • 129 views

    3.5.3.4 Packet Tracer - Configure and Verify EBGP - Pka

    Uploaded by

    Henry Vizcaino
    The document describes configuring and verifying eBGP between two autonomous systems, AS 65001 for ACME Inc. and AS 65002 for Other Company Inc. The ISP acts as the transit AS 65003. The summary configures ACME1 and OtherCo1 routers to establish eBGP peering with ISP1 and ISP2 routers respectively. Route exchange is verified by checking the routing tables and confirming connectivity between internal networks.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    3.5.3.4 Packet Tracer - Configure and Verify EBGP - Pka

    Uploaded by

    Henry Vizcaino
    129 views5 pages
    The document describes configuring and verifying eBGP between two autonomous systems, AS 65001 for ACME Inc. and AS 65002 for Other Company Inc. The ISP acts as the transit AS 65003. The summary configures ACME1 and OtherCo1 routers to establish eBGP peering with ISP1 and ISP2 routers respectively. Route exchange is verified by checking the routing tables and confirming connectivity between internal networks.

    Original Description:

    3.5.3.4 Packet Tracer - Configure and Verify EBGP.pka

    Original Title

    3.5.3.4 Packet Tracer - Configure and Verify EBGP.pka

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes configuring and verifying eBGP between two autonomous systems, AS 65001 for ACME Inc. and AS 65002 for Other Company Inc. The ISP acts as the transit AS 65003. The summary configures ACME1 and OtherCo1 routers to establish eBGP peering with ISP1 and ISP2 routers respectively. Route exchange is verified by checking the routing tables and confirming connectivity between internal networks.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    129 views5 pages

    3.5.3.4 Packet Tracer - Configure and Verify EBGP - Pka

    Uploaded by

    Henry Vizcaino
    The document describes configuring and verifying eBGP between two autonomous systems, AS 65001 for ACME Inc. and AS 65002 for Other Company Inc. The ISP acts as the transit AS 65003. The summary configures ACME1 and OtherCo1 routers to establish eBGP peering with ISP1 and ISP2 routers respectively. Route exchange is verified by checking the routing tables and confirming connectivity between internal networks.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 5

    Packet Tracer - Configure and Verify eBGP

    Objectives
    Configure and verify eBGP between two autonomous systems.

    Background / Scenario
    In this activity, you will configure and verify the operation of eBGP between autonomous
    systems 65001 and 65002. ACME Inc. is a company that has a partnership with Other
    Company and must exchange routes. Both companies have their own autonomous systems
    and will use ISP as the transit AS to reach each other.
    Note: Only companies with very large networks can afford their own autonomous system.

    Address Table
    Device Interface IPv4 Address Subnet Mask Default Gateway

    G0/0 192.168.0.1 255.255.255.0 N/A


    ACME1
    S0/0/0 1.1.1.2 255.255.255.252 N/A
    G/0/0 172.16.10.1 255.255.255.0 N/A
    OtherCo1
    S0/0/0 1.1.1.10 255.255.255.252 N/A
    S0/0/0 1.1.1.1 255.255.255.252
    ISP1
    S0/0/1 1.1.1.5 255.255.255.252
    S0/0/0 1.1.1.9 255.255.255.252
    ISP2
    S0/0/1 1.1.1.6 255.255.255.252
    PC0 NIC DHCP 192.168.0.1
    Laptop0 NIC DHCP 192.168.0.1
    Laptop1 NIC DHCP 192.168.0.1
    Server NIC 172.16.10.2 255.255.255.0 172.16.10.1

    Step 1: Configure eBGP in ACME Inc.


    ACME Inc. hired an ISP to connect to a partner company called Other Company. The ISP has
    established network reachability within its network and to Other Company. You must connect
    ACME to the ISP so that ACME and Other Company can communicate. Because ISP is using
    BGP as the routing protocol, you must configure ACME1, ACME’s border router, to establish a
    BGP neighbor connection with ISP1, the ISP border router that faces ACME.
    a. Verify that the ISP has provided IP reachability through its network by pinging 1.1.1.9, the
    IP address assigned to ISP2’s Serial 0/0/0.
    b. From any device inside ACME’s network, ping the Other Company’s server 172.16.10.2.
    The pings should fail as no BGP routing is configured at this time.

    c. Configure ACME1 to become an eBGP peer with ISP1. ACME’s AS number is 65001, while
    the ISP is using AS number 65003. Use the 1.1.1.1 as the neighbor IP address and make
    sure to add ACME’s internal network 192.168.0.0/24 to BGP.
    From any device inside ACME’s network, ping the Other Company internal server again.
    Does it work? NO

    Configure eBGP in Other Company Inc.


    The network administrator at Other Company is not familiar with BGP and could not configure
    their side of the link. You must also configure their end of the connection.
    Configure OtherCo1 to form an eBGP adjacency with ISP2, the ISP border router facing
    OtherCo1. Other Company is under AS 65002 while ISP is under AS 65003. Use the 1.1.1.9 as
    the neighbor IP address of ISP2 and make sure to add Other Company’s internal network
    172.16.10.0/24 to BGP.

    Step 2: eBGP Verification


    a. Verify that ACME1 has properly formed an eBGP adjacency with ISP1. The show ip bgp
    summarycommand is very useful here.
    b. Use the show ip bgp summary command to verify all the routes ACME1 has learned via
    eBGP and their status.

    c. Look at the routing tables on ACME1 and OtherCo1. ACME1 should have routes learned
    about Other Company’s route 172.16.10.0/24. Similarly, OtherCo1 should now know about
    ACME’s route 192.168.0.0/24.
    d. Open a web browser in any ACME Inc. end devices and navigate to Other Company’s
    server by entering its IP address 172.16.10.2
    e. From any ACME Inc. device, ping the Other Company’s server at 172.16.10.2.

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy