3.5.3.4 Packet Tracer - Configure and Verify eBGP - ILM
3.5.3.4 Packet Tracer - Configure and Verify eBGP - ILM
3.5.3.4 Packet Tracer - Configure and Verify eBGP - ILM
Topology
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.
© 2017 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 3
Packet Tracer - Configure and Verify eBGP
Address Table
Device Interface IPv4 Address Subnet Mask Default Gateway
Se realiza desde los equipos de la red del ISP comprobando conectividad hacia el equipo ISP2:
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.
Se confirma la falta de conectivida entre redes realizando ping desde PC de la red ACME:
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.
ACME1(config)# router bgp 65001
ACME1(config-router)# neighbor 1.1.1.1 remote-as 65003
ACME1(config-router)# network 192.168.0.0 mask 255.255.255.0
Se aplica la configuración en el equipo correspondiente:
From any device inside ACME’s network, ping the Other Company internal server again. Does it work?
___ No.______________________________________________________________________
Step 2: 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.
Se aplica el comando y se observa que el Router ACME tiene la adyacencia con el equipo ISP1.
b. Use the show ip bgp summary command to verify all the routes ACME1 has learned via eBGP and
their status.
Se confirma que el Router ACME aprende las redes del lado del ISP nuevo por BGP:
Al igual se observa en el Router del ISP que aprende por BGP las redes de ACME.
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.
OtherCo1 Configuration
router bgp 65002
neighbor 1.1.1.9 remote-as 65003
network 172.16.10.0 mask 255.255.255.0