Purpose

For this lab, we expanded on the work of Lab 9-1 to configure BGP for the remainder of the workspace.

---

Assignments

The following table was used to configure the remainder of the workspace outside of the Foster network.

Network Name	Network Address	Default Gateway
VermontISP-PacificISP	192.168.1.0/30	192.168.1.1
BTV-VermontISP	192.168.2.0/30	192.168.2.1
PacificISP-Partner Co.	192.168.3.0/30	192.168.3.1
PacificISP-Customer Co.	192.168.4.0/30	192.168.4.1
Partner Co.	10.15.6.0/24	10.15.6.1
Customer Co.	10.200.24.0/24	10.200.24.1

---

Additional BTV Router Configuration

To start, we made some additional configurations to the BTV Router.

First, we set the default route of 0.0.0.0 0.0.0.0 to 192.168.2.1, which goes to the Vermont-ISP network.

Next, we ran the command default-information originate in the OSPF config to send the default route to the other routers in the area.

Then we ran the command redistribute ospf 1 in the BGP config to advertise all of the Foster network routes. 3033 refers to the AS number for the router.

Lastly, we configured FastEthernet0/1 to connect to the Vermont-ISP network.

---

Vermont-ISP Configuration

Next, we configured the Vermont-ISP router first starting with the hostname.

We configured FastEthernet0/1 going towards the BTV Router.

Then we configured FastEthernet0/0 going towards the Pacific-ISP router.

Lastly, we configured BGP by defining the AS for the router and establishing peers---those being the 192.168.1.2 and 192.168.2.2 addresses.

We also advertised networks within the router's AS.

---

Pacific-ISP Configuration

Then we configured the Pacific-ISP router in a similar manner to that of the Vermont-ISP router.

Here, the hostname was configured as well as the interfaces for FastEthernet0/0, 0/1, and Serial0/1/0 which correspond to the VermontISP-PacificISP, PacificISP-Partner Co., and PacificISP-Customer Co. networks, respectively.

Then we configured BGP for the router and established its peers---those being the 192.168.1.1, 192.168.3.2, and 192.168.4.2 addresses.

We also advertised networks within the router's AS.

---

Partner Co. Configuration

Next we configured the Partner Co. router.

FastEthernet0/0 corresponds to the PacificISP-Partner Co. network, while 0/1 corresponds to the Partner Co. network.

Then we configured BGP for the router and established its peer---that being the 192.168.4.1 address. We also advertised the network within the router's AS---that being the 10.15.16.0 network.

---

Customer Co. Configuration

Finally, we configured the Customer Co. router in a similar manner to that of the Partner Co. router.

Serial0/1/0 corresponds to the PacificISP-Customer Co. network, while FastEthernet0/0 corresponds to the Customer Co. network.

Then we configured BGP for the router and established its peer---that also being the 192.168.4.1 address. We also advertised the network within the router's AS---that being the 10.200.24.0 network.

---

Troubleshooting

When attempting to establish connectivity, I was not able to get successful pings between the Customer PC and Data Center Station.

The first thing I troubleshooted was the BTV router's BGP to establish its peer---that being the 192.168.2.1 address from the Vermont-ISP router.

The next thing I noticed was that the default gateway for the Partner Co. laptop was not configured. I manually configured and verified it.

I also noticed one last issue with the Partner Co. router where I misconfigured the BGP peer. Instead of 192.168.4.1 which corresponds to the PacificISP-Customer Co. network, it should have been configured for 192.168.3.1 which corresponds to the PacificISP-Partner Co. network as it should.

Note: Remember to enter the command copy run start on each of the routers to save their configurations when closing the file or resetting the environment.

---

Connectivity Testing

After performing these troubleshooting tasks, I was able to get successful pings between the Customer PC and Data Center Station.

Running the command sh ip route also allowed me to verify that the BGP configurations were properly established and added to the routing tables in the routers below.