Scribd
Upload
66 views

Multi Area Ospf Routing Configuration

Uploaded by

api-334296831
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
66 views

Multi Area Ospf Routing Configuration

Uploaded by

api-334296831
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Multi-Area OSPF Routing Configuration

In this lab, we will create an IPv4 addressing scheme and implement multi-area OSPF routing.
The topology is shown in the figure below. You can download the base topology from Canvas to
start your configuration.

The VPCS in
the topology
are to represent
multiple
hosts. We will
only

implement one; however, the subnetting for that network must support the specified number
of hosts.

The actual configuration of multi-area OSPF isn’t significantly different than a single area OSPF.
However, unlike single area OSPF we have to give more thought to the addressing scheme we
use to make the summarization as efficient as possible. We want to minimize the type 3 LSA’s
that have to be exchanged between the area border routers (ABR’s).

1. Design an IPv4 addressing scheme of the lab topology that minimizes the number of
type 3 LSA’s exchanged between the ABR’s. To do this effectively, we want the subnets
in Area 1 to be contiguous (one right after the other) as well as in Area 51.
a. Draw the addressing from the 10.X.X.X/8 IPv4 address range for the subnets in
Area 1 and Area 51.
b. Use the subnet 192.168.1.0/30 for the serial link between R1 and R2.
c. Design each network to support the hosts specified below by completing the
table.
Hosts Host bits Network 1st Host Last Host Broadcast CIDR
VPCS # Area Required required Address Address Address Address (/ XX)
1 1 228
2 1 899
3 1 135
4 1 646
5 1 152
6 1 118
7 1 510
8 51 564
9 51 601
10 51 293
11 51 665
12 51 185
13 51 155
14 51 204

This table is available for download on Canvas as an Excel file.

A technique to make the design easier starts with the largest subnets first and
work to the smaller subnets. Also, if any require less than 24 bits, allocate 24 bits
to that subnet. One final thought on the design if you are close to a bit boundary
in your subnets in one area. For example, if you have 10.0.0.0 through
10.0.13.255 allocated to subnets in one area, you might want to over-allocate to
one of your bigger subnets to make the ranges in the area 10.0.0.0 through
10.0.15.255 because now it can be summarized as 10.0.0.0/20. Compare this to
not over-allocating, and we end up with Type 3 LSA’s of 10.0.0.0/21, 10.0.8.0/22,
and 10.0.12.0/23.

Q1: Are there any instances in your network design that would benefit from over-allocation
to a subnet to reduce the number of summarization messages (type 3 LSA’s) sent?
No, each area can be summarized very well from how I have it designed. The areas can be easily
summarized with their own address, 10.1.0.0/20 for area 1 and 10.51.0.0/19 for area 51. These
subnets count for each host connected to that area.

2. Implement your network design in the topology. Allocate the 1st host address of the
subnet to the router interface and the last host address of the subnet to the VPCS. Don’t
forget when setting the IP address on the VPCS to also set the gateway, which should be
the IP address of the router. The format of the command for the VPCS is
ip address subnet gateway
3. Verify your network configuration with some pings between the router interfaces that
are directly connected.
4. Implement OSPF multi-area routing.
a. Implement OSPF in area 1 and get it working – Only between the hosts in area 1.
b. Implement OSPF in area 51 and get it working – Only be the hosts in area 51
c. Implement OSPF on area border routers with area 0. Area 0 is the backbone
area.
5. Verify that routing is working across the areas.
Q2: Which routers are the area border routers?
The area border routers are R1 and R2.

Q3: On a router in area 1 and a router in area 51 do the command show ip ospf
route Are the routes summarized to the other area? Why or why not?
No, the table shows a route for each individual subnet. In order to simplify it and to group
the subnets into a summarization it needs to be configured.

Q4: To enable summarization, we need to be on the area border routers and issue the
following commands.
router ospf X
area 1 range network_address subnet_mask
area 51 range network_address subnet_mask
What commands did you issue on each of the area, routers?
R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#router ospf 1
R1(config-router)#area 1 range 10.1.0.0 255.255.240.0
R1(config-router)#area 51 range 10.51.0.0 255.255.224.0
R1(config-router)#end

R2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R2(config)#router ospf 1
R2(config-router)#area 1 range 10.1.0.0 255.255.240.0
R2(config-router)#area 51 range 10.51.0.0 255.255.224.0
R2(config-router)#end

Q5: On a router in area 1 and a router in area 51 do the command show ip ospf
route Are the routes now summarized to the other area? Why or why not?
Yes, the routes are now summarized because the area border routers have been configured
to summarize the areas to minimize the number of routes in the table.

Q6: On R1 and R2 do a show ip ospf database and paste a screenshot of the


command in the document for the answer to this question. Are all the networks in the
topology present in that ospf database?
Not all of the subnets are listed but the summary for the areas are provided along with the
connected routes.
Export your working topology to a GNS3 portable project and upload your file to along with the
answers to these questions.

You might also like