See explanation below
Explanation/Reference:
Explanation:
For EBGP and IBGP labs you have to make corrections to the configuration in a router R1. You have only access to Router R1. R1 and RA should be neighbors through EBGP. in R1 you will find this command:
(config-router)#Neighbor 209.165.277.2 remote-as 64525
The ip address here is wrong , delete this command using:
(config-router)#No Neighbor 209.165.277.2 remote-as 64525
And replace it with new command with the correct IP of RA E0/1 interface by typing this command:
(config-router)#Neighbor 209.165.201.2 remote-as 64525
R1 and R2 and R3 are neighbors through IBGP, and R1 use the peer-group IBGP to form neighborship between R1 and R2, and between R1 and R3, but actually there is an issue with the IBGP peer-group commands in R1 You will find in R1 these following commands:
(config-router)#neighbor IBGP peer-group
(config-router)#neighbor IBGP remote-as 64550
(config-router)#neighbor IBGP next-hop-self
(config-router)#neighbor IBGP update-source loopback 0
You must correct the Remote-AS for the Peer-Group IBGP to 64520 to form the neighborship correctly. Be aware, if you delete the config with no neighbor IBGP remote-as 64550 you also will delete the following lines:
(config-router)#neighbor IBGP peer-group
(config-router)#neighbor IBGP next-hop-self
(config-router)#neighbor IBGP update-source loopback 0
So dont delete the line regarding the remote-as, just replace it with:
(config-router)#neighbor IBGP remote-as 64520
In the Scenario regarding the Lab, they tell you how the routing-table should look if you have done everything right! So if you routing-table on R1 looks like the one they posted in the scenario you have done everything right and can go on to the next topic. You have to use the command "#show ip bgp " to show bgp routing table , dont use "#show ip route"
Scenario
The company has created the test bed network shown in the layer 2 and layer 3 topology exhibits.
This network consists of four routers, two layer 3 switches and two layer 2 switches.
In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1.
DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary.
R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the ISP's network. Because the company's address space is in the private range, R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and the outside (209.65.200.0/24) network.
ASW1 and ASW2 are layer 2 switches.
NTP is enabled on all devices with 209.65.200.226 serving as the master clock source.
The client workstations receive their IP address and default gateway via R4's DHCP server. The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1 and DSW2.
In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6. DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE. The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the underlying IPv4 OSPF domain. Redistribution is enabled where necessary.
Recently the implementation group has been using the test bed to do a 'proof-of-concept' on several implementations. This involved changing the configuration on one or more of the devices. You will be presented with a series of trouble tickets related to issues introduced during these configurations.
