CS计算机代考程序代写 gui IFN507 Network Systems P5: Routing Configurations

IFN507 Network Systems P5: Routing Configurations
Practical 5
Routing Configurations
Serial cable: start from DCE with clock
Configuration state on
Static Route 的目的是链接到不同的network(线与线上面那个address)
RIP 就简单多了,只需输入direct链接的东西即可

Learning Objectives
Upon completion of this practical, you will be able to:
· Create a simulated network topology using Packet Tracer (PT)
· Configure static routing
· Configure dynamic routing – RIP

Background
In the first lab activity of this practical, you will be using PT to set up a network topology that consists of routers, switches and workstations as shown in the topology diagram. After that, configure IP addresses to network interfaces, based on the given Addressing Table. Then test a connection to a device inside of the network and test a connection to a device outside of the network. With the second lab activity, you need to configure static routes to implement network communication. In the third lab activity, you need to remove static routing and then configure RIP version 1 (RIPv1), a dynamic routing protocol. With RIP, a router advertises the routes of its directly connected networks to the neighbour routers. Once these three lab activities are completed, you will work with the Lab 4 network topology configurations (saved as Lab4.1 and Lab4.2) to resolve the connectivity issue between devices that are NOT on the same network.

Scenario
· Lab Activity 1: Build a basic network and view the routing tables
· Lab Activity 2: Basic static route configurations
· Lab Activity 3: Basic RIP configurations
· Lab Activity 4: Use static routing to forward traffic between different subnets with PT (continue from Practical 4).
· Lab Activity 5: Use static routing to forward traffic between different subnets with PT (continue from Practical 4).

Lab Activity 1

Topology Diagram

Figure 1

Addressing Table 1
Device
Interface
IP Address
Subnet Mask
Default Gateway

R1
Se2/0 (DCE)
200.0.0.1
255.255.255.0
N/A

Se3/0
192.0.0.1
255.255.255.0
N/A

Fa0/0
192.0.1.1
255.255.255.0
N/A

R2
Se2/0 (DCE)
192.0.0.2
255.255.255.0
N/A

Fa0/0
192.0.2.1
255.255.255.0
N/A

Fa1/0
192.0.3.1
255.255.255.0
N/A

ISP
Se2/0
200.0.0.2
255.255.255.0
N/A

HTTP
NIC
192.0.1.5
255.255.255.0
192.0.1.1

PC1
NIC
192.0.2.11
255.255.255.0
192.0.2.1

PC2
NIC
192.0.3.22
255.255.255.0
192.0.3.1

Task 1: Build a Basic Network Topology
Build a network topology as shown in Figure 1.

Step 1: Start Cisco Packet Tracer
Click Start > All Programs > Cisco Packet Tracer > Cisco Packet Tracer

Step 2: Determine the required devices and cables
To simulate a network topology as shown in Figure 1, you need to have:
· 3 routers (ISP, R1, and R2)
· 3 switches (S1, S2, and S3)
· 1 server (HTTP Server)
· 2 workstations (PC1 and PC2)
· 2 serial cables (to connect routers)
· 6 straight-through Ethernet cables

Q1: What is the total number of networks (or subnets) as shown in the Topology Diagram (Figure 1)? (choose one)
4
5
8
9

Q2: List out all the subnets as shown in the Topology Diagram (Figure 1)?
192.0.0.0/24
192.0.1.0/24
192.0.2.0/24
192.0.3.0/24
200.0.0.0/24

Step 3: Select the devices
Place the devices in your topology area, and then label each device as shown in the diagram below:

Note: Select the “Server-PT” device from the “End Devices” area.

Step 4: Use the proper cable to connect the routers
1. Click on Serial DCE from the Connections options.

2. When the cursor appears, perform the following steps to connect routers R1 and ISP:

a. Single click on R1
b. Select Serial2/0
c. Drag the cursor to ISP
d. Single click on ISP and select Serial2/0

3. Select another Serial DCE to connect routers R2 and R1 with the following steps:

a. Single click on R2
b. Select click on Serial2/0
c. Drag the cursor to R1
d. Single click on R1 and select Serial3/0

Step 5: Select the proper cables to connect the rest of devices
Use the correct Ethernet cables to connect the rest of devices as shown in Figure 1.

Task 2: Configure IP Addresses
Use the information from Addressing Table 1 to assign IP addressing to the routers, HTTP server, and workstations.
Note: Do not forget to activate the interfaces/ports of routers.

Task 3: Verify Connectivity
Step 1: Test the connectivity between each workstation to its default gateway
To test the connectivity, you can use ping or the Add Simple PDU tool from each workstation to its default gateway.
Q3: From the HTTP Server, can you ping its default gateway? Yes / No
Q4: From PC1, can you ping its default gateway? Yes / No
Q5: From PC2, can you ping its default gateway? Yes / No
If you cannot ping successfully at any point, check the following:
1. Check the cabling. Have you used the correct Ethernet cables?
2. Check your IP address configuration. Is your IP address configuration the same as the one shown in the Topology Diagram and Addressing Table?
3. Check the router FastEthernet interfaces. Are all relevant interfaces on each router activated?

Step 2: Test connectivity between directly connected routers
Use the Add Simple PDU tool or ping command to test connectivity between the directly connected routers.
Q6: From R1, can you ping R2 successfully? Yes / No
Q7: From R1, can you ping ISP successfully? Yes / No
If your answer is No at any points, check the following:
1. Check cabling. Have you used a serial cable to connect two routers?
2. Check the IP assignment on routers interfaces. Is your IP address configuration the same as the one shown in the Topology Diagram and Addressing Table?
3. Check the router Serial interfaces. Are all relevant interfaces on each router activated?

Step 3: Test the connectivity between devices that are NOT on the same network
To test the connectivity use ping or the Add Simple PDU tool. Try to answer the following questions.
Q8: From PC2, can you ping the HTTP Server successfully? Yes / No
Q9: From PC1, can you ping the HTTP Server successfully? Yes / No
Q10: From the HTTP Server, can you ping ISP’s IP address 200.0.0.2 successfully? Yes / No
Q11: From the router R2, can you ping ISP successfully? Yes / No
Describe why you cannot use ping successfully at this point?
At this point, routers only know the routes for directly connected subnets when the interfaces first initialize.

Task 4: View the Routing Table
Step 1: View the routing table on router ISP
1. Single click on the icon from the Utilities area.

2. Select the router ISP, and then select “Routing Table”.

3. Use the following table to record routing information for router ISP.
Routing Table for ISP
Type
Network
Port
Next Hop IP
Metric

C
200.0.0.0/24
Serial2/0

0/0

Note: The type code C denotes directly connected networks.

Step 2: View the routing table on R1
Use the following table to record routing information for R1.
Routing Table for R1
Type
Network
Port
Next Hop IP
Metric

C
192.0.0.0/24
Serial3/0

0/0

C
192.0.1.0/24
FastEthernet0/0

0/0

C
200.0.0.0/24
Serial2/0

0/0

Step 3: View the routing table on R2
Use the following table to record routing information for R2.
Routing Table for R2
Type
Network
Port
Next Hop IP
Metric

C
192.0.0.0/24
Serial2/0

0/0

C
192.0.2.0/24
FastEthernet0/0

0/0

C
192.0.3.0/24
FastEthernet1/0

0/0

Step 4: Reflection
Q12: Which four networks are on the network topology (Figure 3.1), but they are not shown on the Routing Table for ISP?
192.0.0.0/24
192.0.1.0/24
192.0.2.0/24
192.0.3.0/24

Q13: Which two networks on the network topology (Figure 3.1), but they are not shown on the Routing Table for R1?
192.0.2.0/24
192.0.3.0/24

Q14: Which two networks on the network topology (Figure 3.1), but they are not shown on the Routing Table for R2?
200.0.0.0/24
192.0.1.0/24

Task 5: Save your work
Click the File menu and then Save your network topology with a file name: Lab5.1.

Lab Activity 2
This lab activity continues to be based on the same topology diagram as Figure 1 and Addressing Table 1.
You need to configure static routing on each router for complete network connectivity.

Task 1: Configure Static Routing pointed to a Next-Hop Address

Step 1: Configure a static route on router ISP
1. Click on router ISP, select on “Config” tab, and then click on “Static”.

2. On router ISP, configure a static route with a destination address of 192.0.1.0 and subnet mask of 255.255.255.0 pointed to next-hop address 200.0.0.1, which is R1’s Serial2/0 interface.

Network
192.0.1.0

Mask
255.255.255.0

Next Hop
200.0.0.1

Then click on “Add”.

3. View the router ISP’s routing table again. Use the following table to record updated routing information.

Routing Table for ISP (after adding a static route 192.0.1.0/24)
Type
Network
Port
Next Hop IP
Metric

C
200.0.0.0/24
Serial2/0

0/0

S
192.0.1.0/24

200.0.0.1
1/0

Note: The type code S denotes a static route, this is manually entered.

Note: With this route entry added to ISP’s routing table, the destination address of the packet that matches the 24 leftmost bits of 192.0.1.0/24 will be forwarded to the next-hop address 200.0.0.1.

4. At this point, you should be able to ping from the HTTP Server to router ISP 200.0.0.2.

5. From router ISP, issue four ping packets to the following destinations. Can ISP forward all of the four packets to the destinations?

Packet
Destination IP
Discard or Forward?

1
192.0.1.5 (HTTP Server)
Forwarded

2
192.0.0.2 (R2 Se2/0)
Discarded

3
192.0.2.11 (PC1)
Discarded

4
192.0.3.22 (PC2)
Discarded

Q1: Why some packets are discarded by router ISP?
ISP’s routing table does not have a route to the networks 192.0.0.0/24, 192.0.2.0/24, and 192.0.3.0/24. Therefore ISP simply discarded those packets because those destinations are not reachable.

Hint: You can use the “Add Complex PDU” function to test connectivity, that is, you can specify the destination IP address and other options.

1. Click on the “Add Complex PDU” option from the Utilities area.

2. From the Create Complex PDU dialog box, perform the following steps:
a. Select a source device.
b. Enter the Destination IP address, Sequence Number, Size and Time information.
c. Click on the Create PDU button.

Step 2: Configure three more static routes on router ISP
In order to enable router ISP to forward packets destined to other networks, you need to add more static routes to ISP.
1. On router ISP, add three more static routes 192.0.0.0/24, 192.0.2.0/24, and 192.0.3.0/24 pointed to the next-hop address 200.0.0.1, which is R1’s Serial2/0 interface.

2. View the router ISP’s routing table again. Use the following table to record the updated route entries for ISP.

Routing Table for ISP (after adding three more static routes)
Type
Network
Port
Next Hop IP
Metric

C
200.0.0.0/24
Serial2/0

0/0

S
192.0.0.0/24

200.0.0.1
1/0

S
192.0.1.0/24

200.0.0.1
1/0

S
192.0.2.0/24

200.0.0.1
1/0

S
192.0.3.0/24

200.0.0.1
1/0

3. From router ISP, issue the four ping packets again to the following destinations. Can ISP forward all of the four packets to the destinations?

Packet
Destination IP
Discard or Forward?

1
192.0.1.5 (HTTP Server)
Forwarded

2
192.0.0.2 (R2 Se2/0)
Discarded

3
192.0.2.11 (PC1)
Discarded

4
192.0.3.22 (PC2)
Discarded

Q2: Why some of the packets are stilled discarded by R1 and R2?
R1’s routing table does not have a route to reach 192.0.2.0/24 and 192.0.3.0/24.
R2’s routing table does not have a route to reach 200.0.0.0/24 and 192.0.1.0/24.

Step 3: Configure two static routes on router R2
In order to enable router R2 to route packets destined to networks 192.0.1.0/24 and 200.0.0.0/24, you need to add two static routes to R2.
On router R2, configure two static routes to networks
1. On R2, add two static routes 192.0.1.0/24 and 200.0.0.0/24 pointed to the next-hop address 192.0.0.1, which is R1’s Serial3/0 interface.

2. View the router R2’s routing table. Use the following table to record the updated route entries for R2.

Routing Table for R2 (after adding two static routes)
Type
Network
Port
Next Hop IP
Metric

C
192.0.0.0/24
Serial2/0

0/0

C
192.0.2.0/24
FastEthernet0/0

0/0

C
192.0.3.0/24
FastEthernet1/0

0/0

S
192.0.1.0/24

192.0.0.1
1/0

S
200.0.0.0/24

192.0.0.1
1/0

3. From router ISP, issue four ping packets to the following destinations. Can ISP forward all of the four packets to the destinations?

Packet
Destination IP
Discard or Forward?

1
192.0.1.5 (HTTP Server)
Forwarded

2
192.0.0.2 (R2 Se2/0)
Forwarded

3
192.0.2.11 (PC1)
Discarded

4
192.0.3.22 (PC2)
Discarded

Q3: Why some of the packets are still discarded by router R1?
R1’s routing table does not have a route to the networks 192.0.2.0/24 and 192.0.3.0/24.

Step 4: Configure two static routes on router R1
1. On router R1, configure two static routes 192.0.2.0/24 and 192.0.3.0/24 pointed to the next-hop address 192.0.0.2, which is R2’s Serial2/0 interface.

2. View router R1’s routing table. Use the following table to record the updated route entries for R1.

Routing Table for R1 (after adding two static routes)
Type
Network
Port
Next Hop IP
Metric

C
192.0.0.0/24
Serial3/0

0/0

C
192.0.1.0/24
FastEthernet0/0

0/0

C
200.0.0.0/24
Serial2/0

0/0

S
192.0.2.0/24

192.0.0.2
1/0

S
192.0.3.0/24

192.0.0.2
1/0

3. From router ISP, issue the four packets to the following destinations again. Can ISP forward all of the four packets to the destinations now?

Packet
Destination IP
Discard or Forward?

1
192.0.1.5 (HTTP Server)
Forwarded

2
192.0.0.2 (R2 Se2/0)
Forwarded

3
192.0.2.11 (PC1)
Forwarded

4
192.0.3.22 (PC2)
Forwarded

If you still cannot get all the packets forwarded, troubleshoot your routing configuration on each router. You may have some errors in your routing configuration. Do all the routers have a static route entry to the destination IP address?

Note: At this point, if you have followed each procedure correctly, every device should be reachable in this network topology.

Task 2: Improve Routing Configuration using a Static Default Route or/and aggregated route
The proper configuration and usage of the static route can improve the network performance. With your static routing configuration completed in Task 1 may seem working, but you can certainly improve your routing configuration by using a default route or/and aggregated route to minimise the number of static routes in the routing table. A default route is a special route.
A default route is also used when no suitable routing table entry is matched. Namely, when no matched route is found, the default route is used to forward the packet. In a routing table, the default route is expressed in the form of the route to the network address 0.0.0.0 with the network mask 0.0.0.0.
In particular, default routing is used in stub networks which have all of its non-local traffic out via a single path. In Figure 1, from the R2’s perspective, R2’s non-local traffic goes out via R1’s Serial3/0 interface. Therefore, you use a default route to replace all the other routes on R2, which is to make the routing table more concise.

Step 1: Remove the existing static routes from R2
1. Click on router R2, select on “Config” tab, and then click on “Static”.

2. Remove the two routing entries you did in Step 3 of Lab Activity 2.
You can only remove one entry at a time. Select on one entry at a time and then click on the Remove button to delete the routes.

Step 2: Configure a static default route on R2
1. Configure a default route to 0.0.0.0 with the subnet mask 0.0.0.0 pointed to the next-hop address 192.0.0.1, which is R1’s Serial3/0 interface.

Network
0.0.0.0

Mask
0.0.0.0

Next Hop
192.0.0.1

2. View the router R2’s routing table again. Use the following table to record the updated route entries.
Routing Table for R2 (updated with a default route)
Type
Network
Port
Next Hop IP
Metric

C
192.0.0.0/24
Serial2/0

0/0

C
192.0.2.0/24
FastEthernet0/0

0/0

C
192.0.3.0/24
FastEthernet1/0

0/0

S
0.0.0.0/0

192.0.0.1
1/0

Step 3: Configure a default static route on R1
In this lab activity, you do not need to remove any existing static route entries from R1. Using route aggregation concepts and techniques, you are able to configure supernetting to streamline the routing. At the moment, you only need to add a default route on R1 to forward all outbound network traffic to the Internet via ISP’s interface.

1. Configure a default route to 0.0.0.0 with the subnet mask 0.0.0.0 pointed to the next-hop address 200.0.0.2, which is ISP’s Serial2/0 interface.

2. View the router R1’s routing table again. Use the following table to record the updated route entries.

Routing Table for R1 (after adding a default route)
Type
Network
Port
Next Hop IP
Metric

C
192.0.0.0/24
Serial3/0

0/0

C
192.0.1.0/24
FastEthernet0/0

0/0

C
200.0.0.0/24
Serial2/0

0/0

S
192.0.2.0/24

192.0.0.2
1/0

S
192.0.3.0/24

192.0.0.2
1/0

S
0.0.0.0/0

200.0.0.2
1/0

3. Aggregate two routes that contain two continuous networks pointing the same next hop IP address (or interface).

4. View the router R1’s routing table again. Use the following table to record the updated route entries.
Type
Network
Port
Next Hop IP
Metric

C
192.0.0.0/24
Serial3/0

0/0

C
192.0.1.0/24
FastEthernet0/0

0/0

C
200.0.0.0/24
Serial2/0

0/0

S
192.0.2.0/23

192.0.0.2
1/0

S
0.0.0.0/0

200.0.0.2
1/0

Note: You may think you can also use a default route to improve routing configuration on router ISP. In fact, an ISP normally has more than one customer; from a routing perspective, it is incorrect to configure a default route pointed to a particular customer’s network.

Task 3: Save your work
Click the File menu and then Save your network topology with a file name: Lab5.2.

Lab Activity 3
This lab activity continues to be based on the same topology diagram Figure 1 and Addressing Table 1.
You need to configure a dynamic routing protocol – RIP version 1 (RIPv1) on each router for a complete network connectivity. A dynamic routing protocol is used by routers to exchange routing information with each other. In general, all dynamic routing protocols involve three stages: initialisation, sharing and updating. Before the router processes and calculates received routing information, you need to define which routes are to be advertised on a router. The routes to be advertised are the directly connected networks to the router.

Task 1: Clear any Existing Static Route Entries on the Routers
On each router, remove all the existing static routes.

Task 2: Examine the Routing Table on the Routers
View the routing table on each router. During the initial stage, a routing table consists of directly connected networks. Use the following tables to record routes for each router.
Routing Table for ISP
Type
Network
Port
Next Hop IP
Metric

C
200.0.0.0/24
Serial2/0

0/0

Routing Table for R1
Type
Network
Port
Next Hop IP
Metric

C
192.0.0.0/24
Serial3/0

0/0

C
192.0.1.0/24
FastEthernet0/0

0/0

C
200.0.0.0/24
Serial2/0

0/0

Routing Table for R2
Type
Network
Port
Next Hop IP
Metric

C
192.0.0.0/24
Serial2/0

0/0

C
192.0.2.0/24
FastEthernet0/0

0/0

C
192.0.3.0/24
FastEthernet1/0

0/0

Task 3: Configure RIP
To enable RIP in the GUI mode of Packet Tracer, you need to enter the classful network address for each directly connected network on the router manually. Then the router that participates in the RIP routing will send out routing information every 30 seconds.

Step 1: Enable and configure RIP on router ISP
1. Click on router ISP, select on “Config” tab, and then click on “RIP”.

2. Referring to router Routing Table for ISP in Task 2, there is only one directly connected network attach to router ISP. Enter the directly connected network to the routing table and then click on “Add”.

Network
200.0.0.0

Step 2: Enable and configure RIP on router R1
Referring to Routing Table for R1 in Task 2; enter the three directly connected networks to R1.

Step 3: Enable and configure RIP on router R2
Referring to Routing Table for R2 in Task 2; enter the three directly connected networks to R2.

Task 4: Verify RIP Routing
After the RIP-enabled router has processed received routing information and calculated its routing information, the routing table consists of both directly connected routes and routes learned through RIP routing (RIP-learned routes). The RIP-learned routes are coded with an R in the routing table.
Examine the routing table on each RIP-enabled router:
· Router ISP should have 4 RIP-learned route entries
· Router R1 should have 2 RIP-learned route entries
· Router R2 should have 2 RIP-learned route entries
If the number of RIP-learned route entries does not match to yours, troubleshoot your configuration:
· Check whether the network interfaces is enabled or not.
· Check whether all the directly connected networks have been added correctly or not.

Task 5: Save your work
Click the File menu and then Save your network topology with a file name: Lab5.3.

Lab Activity 4 (continuation of Lab Activity 1 of Practical 4)

Task 1: Configure Static Routing (for the configuration file saved as Lab4.1)
In this task, you are required to configure appropriate static routing on each router to enable all devices to communicate with one another across different subnets.
Step 1: Configure static routing on routers
Use the following tables to record routing information for each router. A routing table contains the necessary forwarding information such as destination network address, network mask and next hop.
The routing table for ISP
From router ISP’s perspective, you only need to have a static route to forward IP traffic to reach ABC’s network.
Network
Mask
Next Hop

193.64.33.0
255.255.255.0
200.0.0.1

Note: An ISP normally has more than one customer; therefore, it is incorrect to configure a default route pointed to a particular customer’s network.

The routing table for BR
From router BR’s perspective, you need to configure static routes to reach the two networks that are not directly attached to router BR. You also need to add a static route to reach the rest of the Internet. That is, configure a default route pointing towards the ISP to reach the Internet.
Network
Mask
Next Hop

193.64.33.128
255.255.255.192
193.64.33.2

193.64.33.192
255.255.255.192
193.64.33.2

0.0.0.0
0.0.0.0
200.0.0.2

You should be able to aggregate two routes that contain two continuous networks pointing to the same next hop.
Network
Mask
Next Hop

193.64.33.128
255.255.255.128
193.64.33.2

0.0.0.0
0.0.0.0
200.0.0.2

The routing table for HQ
From router HQ’s perspective, you need to configure a static routes to reach the networks that are not directly connected to HQ. That is, configure one default static route to reach all remote networks.
Network
Mask
Next Hop

0.0.0.0
0.0.0.0
193.64.33.1

Step 2: Verify connectivity
All the devices should become reachable at this stage. Troubleshoot when necessary.

Lab Activity 5 (continuation of Lab Activity 2 of Practical 4)

Task 1: Configure Static Routing (for the configuration file saved as Lab4.2)
In this task, you are required to configure appropriate static routing on each router to enable all devices can communicate with one another across different subnets.
Step 1: Configure static routing on routers
Use the following tables to record routing information for each router. A routing table contains the necessary forwarding information such as destination network address, network mask and next hop.
The routing table for ISP
From router ISP’s perspective, you only need to have a static route to forward IP traffic to reach XYZ’s network.
Network
Mask
Next Hop

193.64.33.0
255.255.255.0
200.0.0.1

Note: An ISP normally has more than one customer; therefore, it is incorrect to configure a default route pointed to a particular customer’s network.

The routing table for BR
From router BR’s perspective, you need to configure static routes to reach the three networks that are not directly attached to router BR. You also need to add a static route to reach the rest of the Internet. That is, configure a default route pointing towards the ISP to reach the Internet.
Network
Mask
Next Hop

193.64.33.128
255.255.255.224
193.64.33.2

193.64.33.160
255.255.255.224
193.64.33.2

193.64.33.192
255.255.255.224
193.64.33.2

0.0.0.0
0.0.0.0
200.0.0.2

You should be able to aggregate two routes that contain two continuous networks pointing to the same next hop.
Network
Mask
Next Hop

193.64.33.128
255.255.255.192
193.64.33.2

193.64.33.192
255.255.255.224
193.64.33.2

0.0.0.0
0.0.0.0
200.0.0.2

The routing table for HQ
From router HQ’s perspective, you need to configure a static route to reach the networks that are not directly connected to HQ. That is, configure one default static route to reach all remote networks.
Network
Mask
Next Hop

0.0.0.0
0.0.0.0
193.64.33.1

Step 2: Verify connectivity
All the devices should be reachable at this stage. Troubleshoot when necessary.

End of Practical 5

Page 18 of 20

PC1 PC2

R1

Fa0/0
Fa1/0

R2

Se3/0 Se2/0

DCE

200.0.0.0/24 192.0.0.0/24

.1

.5

.1 .2

.1

.22

ISP

S1

HTTP Server

Se2/0 Se2/0

S2 S3

.2

DCE

Fa0/0 .1

.11

192.0.1.0/24

.1

192.0.2.0/24 192.0.3.0/24