Cisco CCNP / BSCI Exam Tutorial: OSPF Router Types

When you're preparing to pass the BSCI exam on the way to the coveted Cisco CCNP certification, you can be quickly overwhelmed by the sheer amount of BGP and OSPF knowledge you must demonstrate a mastery of. One set of details that some BSCI and CCNP candidates underestimate are the differences between the OSPF router types.

An OSPF Internal router has one rule - it must have all its interfaces in a single area. It does not mean that area has to be Area 0.

An OSPF Backbone router is a router with at least a single area in the OSPF backbone area, Area 0. A router can be both an Internal and Backbone router if all its interfaces are in Area 0.

An Area Border Router has at least one interface in Area 0 and another interface in a non-backbone area. ABRs are also one of two router types that can perform OSPF route summarization. (To advertise a summary route from one OSPF area to another, use the area range command on the ABR.)

Finally, an ASBR is an OSPF router that is performing route redistribution by injecting routes from another source into the OSPF domain. This is the other OSPF router type that can perform route summarization; to summarize routes being redistributed into OSPF, use the summary-address command on the ASBR.

There are several commands you can use to determine the router types in a given OSPF area. The command "show ip ospf" will display quite a bit of information regarding the local router, and this includes whether that router is acting as an ABR or ASBR. To see the routes to the ABRs and ASBRs from the local router, run "show ip ospf border-routers".

Cisco CCNP / BSCI Exam Tutorial: Using Distribute Lists

To be successful on the BSCI exam and in earning your CCNP, you've got to master route redistribution. This isn't as easy as it sounds, because configuring route redistribution is only half the battle. Whether it's on an exam or in a real-world production network, you've got to identify possible points of trouble before you configure route redistribution - and you need to be able to control redistribution as well. You may have an OSPF domain with 100 routes, but only need to redistribute 10 of them into a neighboring RIPv2 domain. You've got to know how to do that, and one method is the use of a distribute-list.

A distribute-list is an access-list that is used to determine what routes can and cannot be redistributed. Distribute-lists let you specify what routes will be filtered from the process. You can use standard or extended ACLs, and you can filter routes that are coming into a routing process or being injected into another process.

In the following example, R1 is redistributing RIP routes into OSPF, but only wants to advertise network 150.1.1.0 /24 to other OSPF routers. An ACL will be written to match that particular network, and then the distribute-list will be written under the routing process. I'm going to show you the IOS Help output for the distribute-list command, and please note that routing updates can be controlled at the interface level or protocol level.

R1(config)#access-list 24 permit 150.1.1.0 0.0.0.255

R1(config)#router ospf 1

R1(config-router)#redistribute rip subnets

R1(config-router)#distribute-list 24 ?

in Filter incoming routing updates

out Filter outgoing routing updates

R1(config-router)#distribute-list 11 out ?

Async Async interface

BRI ISDN Basic Rate Interface

BVI Bridge-Group Virtual Interface

CTunnel CTunnel interface

Dialer Dialer interface

Ethernet IEEE 802.3

Lex Lex interface

Loopback Loopback interface

Multilink Multilink-group interface

Null Null interface

Serial Serial

Tunnel Tunnel interface

Vif PGM Multicast Host interface

Virtual-Template Virtual Template interface

Virtual-TokenRing Virtual TokenRing

bgp Border Gateway Protocol (BGP)

connected Connected

egp Exterior Gateway Protocol (EGP)

eigrp Enhanced Interior Gateway Routing Protocol (EIGRP)

igrp Interior Gateway Routing Protocol (IGRP)

ospf Open Shortest Path First (OSPF)

rip Routing Information Protocol (RIP)

static Static routes

R1(config-router)#distribute-list 11 out rip

Using distribute-lists does guard against routing loops, but they have other purposes. You may have a network segment that should be kept secret from the rest of your company; a distribute-list can filter that segment's network number from the redistribution process. In this way, distribute-lists serve as a basic form of network security. (Very basic. I wouldn't sell that firewall on ebay if I were you.)

Keeping such networks out of routing updates and routing tables throughout the network has the side effect of reducing routing update overhead as well.

Cisco CCNP / BSCI Exam Tutorial: OSPF Route Redistribution Review

OSPF route redistribution is an important topic on the BSCI exam, and it's a topic full of details and defaults that you need to know for the exam room and the job. To help you pass the BSCI exam, here's a quick review of some of the OSPF route redistribution basics.

To see if a router is an ABR or ASBR, run show ip ospf. This also displays any routes being redistributed into OSPF on this router.

R1#show ip ospf

Routing Process "ospf 1" with ID 1.1.1.1

Supports only single TOS(TOS0) routes

Supports opaque LSA

It is an area border and autonomous system boundary router

Redistributing External Routes from,

connected, includes subnets in redistribution

rip, includes subnets in redistribution

When redistributing RIP into OSPF, the “subnets" option is needed to include subnets in redistribution. When redistributing OSPF into RIP, a seed metric must be specified. (OSPF gives redistributed routes a default metric of 20 – this can be changed, but a seed metric does not have to be set.)

R1(config)#router ospf 1

R1(config-router)#redistribute connected

% Only classful networks will be redistributed

R1(config-router)#redistribute connected subnets

R1(config-router)#redistribute rip subnets

R1(config-router)#router rip

R1(config-router)#redistribute connected metric 1

R1(config-router)#redistribute ospf 1 metric 1


By default, routes redistributed into OSPF are marked as E2 routes. The metric for these routes reflects only the cost of the path from the ASBR to the destination network and does not include the cost of the path from the local router to the ASBR. By contrast, E1 routes include the cost of the entire path from the local router to the destination network.


O E2 5.1.1.1 [110/20] via 172.34.34.3, 00:33:21, Ethernet0

6.0.0.0/32 is subnetted, 1 subnets

O E2 6.1.1.1 [110/20] via 172.34.34.3, 00:33:21, Ethernet0

172.12.0.0/16 is variably subnetted, 2 subnets, 2 masks

O E2 172.12.21.0/30 [110/20] via 172.34.34.3, 00:33:32, Ethernet0

O E2 7.1.1.1 [110/20] via 172.34.34.3, 00:33:21, Ethernet0

15.0.0.0/24 is subnetted, 1 subnets

O E2 15.1.1.0 [110/20] via 172.34.34.3, 00:33:32, Ethernet0

To redistribute routes into OSPF and mark them as E1 upon redistribution, use the metric-type option with the redistribution command.

R1(config)#router ospf 1

R1(config-router)#redistribute rip subnets metric-type ?

1 Set OSPF External Type 1 metrics

2 Set OSPF External Type 2 metrics

R1(config-router)#redistribute rip subnets metric-type 1

Look at the same two routes in R4's routing table, which are now displayed as E1 routes:

O E1 5.1.1.1 [110/94] via 172.34.34.3, 00:04:13, Ethernet0

6.0.0.0/32 is subnetted, 1 subnets

O E1 6.1.1.1 [110/94] via 172.34.34.3, 00:04:14, Ethernet0

BSCI exam success and earning your CCNP certification depends on knowing the details, and there are plenty of details involved in OSPF route redistribution! Keep studying, practice different scenarios in your CCNA / CCNP home lab or rack rental, and you'll master these details and pass the exam!

Cisco CCNP / BSCI Certification Exam: Five OSPF Details You Must Know

Preparing for your BSCI exam on your way to the Cisco CCNP certification, you can quickly get overwhelmed by the details! Here are five commonly overlooked points you should keep in mind when it comes to your OSPF studies.

The virtual link command includes the area number of the transit area, and if authentication is being used on Area 0, the virtual link command must include the authentication statement. Since the virtual link is a logical extension of Area 0, it stands to reason that it has to be configured with the authentication type and password configured on Area 0.

OSPF requires no seed metric when routes are being redistributed into an OSPF domain. The default cost for such routes is 20, but you do need to use the "subnets" option if you want to redistribute subnets into OSPF.

There are two kinds of external OSPF routes. The default, E2, reflects the cost of the path from the ASBR to the external destination. The other option, E1, has a cost reflecting the entire path from the local router to the external destination.

When configuring stub areas, each router in the area must agree that the area is stub. For a total stub area, only the ABR needs to be configured with the "no-summary" option, but all routers in the area still must agree that the area is stub.

Routers in a stub area will have a default route to use to reach external destinations; routers in total stub areas will have a default route to use in order to reach both external and inter-area networks.

The BSCI exam and CCNP certification require a great deal of dedication and hard work. Keep studying and paying attention to the details, and you will get there!

Cisco CCNP / BSCI Certification: Route Redistribution And The Seed Metric

In the first part of this free CCNP / BSCI tutorial, we looked at how leaving one simple word out of our route redistribution configuration - "subnets" - resulted in an incomplete routing table when redistributing routes from RIP to OSPF. (If you missed that part of the tutorial, visit my website's "Free Tutorials" section.) Today, we'll look at redistributing OSPF routes into RIP and identify another common redistribution error.

We are using a three-router network. R5 is running RIP, R1 is serving as a hub between R5 and R3 and is running RIP and OSPF, and R3 is running OSPF.

To begin this lab, we'll add three loopbacks to R3 and advertise them to R1 via OSPF.

R3(config)#int loopback33

R3(config-if)#ip address 33.3.3.3 255.255.255.255

R3(config-if)#int loopback34

R3(config-if)#ip address 34.3.3.3 255.255.255.255

R3(config-if)#int loopback35

R3(config-if)#ip address 35.3.3.3 255.255.255.255


R3(config-if)#router ospf 1

R3(config-router)#network 33.3.3.3 0.0.0.0 area 1

R3(config-router)#network 34.3.3.3 0.0.0.0 area 1

R3(config-router)#network 35.3.3.3 0.0.0.0 area 1

R1 sees all three of these routes in its routing table.

R1#show ip route ospf

34.0.0.0/32 is subnetted, 1 subnets

O IA 34.3.3.3 [110/65] via 172.12.123.3, 00:00:55, Serial0

35.0.0.0/32 is subnetted, 1 subnets

O IA 35.3.3.3 [110/65] via 172.12.123.3, 00:00:45, Serial0

33.0.0.0/32 is subnetted, 1 subnets

O IA 33.3.3.3 [110/65] via 172.12.123.3, 00:00:55, Serial0

We'll now redistribute these routes into RIP on R1. Remember the "subnets" option we talked about in the first part of this tutorial? There is no such option when redistributing OSPF routes into RIP, as IOS Help shows us.

R1(config)#router rip

R1(config-router)#redistribute ospf 1 ?

match Redistribution of OSPF routes

metric Metric for redistributed routes

route-map Route map reference

vrf VPN Routing/Forwarding Instance



R1(config-router)#redistribute ospf 1

The routes have been redistributed into RIP with the redistribute ospf 1 command. (The "1" is the OSPF process number.) Let's look at R5 and see the results.

R5#show ip route rip

R5#

The routes aren't there, but we didn't get a warning from the router that we needed to do anything else. What is the problem?

The problem is that RIP requires a seed metric to be specified when redistributing routes into that protocol. A seed metric is a "starter metric" that gives the RIP process a metric it can work with. The OSPF metric of cost is incomprehensible to RIP, since RIP's sole metric is hop count. We've got to give RIP a metric it understands when redistributing routes into that protocol, so let's go back to R1 and do so.

R1(config)#router rip

R1(config-router)#no redistribute ospf 1

R1(config-router)#redistribute ospf 1 metric 2

R5 now sees the routes. Note that the metric contained in the brackets is the seed metric.

R5#show ip route rip

34.0.0.0/32 is subnetted, 1 subnets

R 34.3.3.3 [120/2] via 100.1.1.1, 00:00:24, Ethernet0

35.0.0.0/32 is subnetted, 1 subnets

R 35.3.3.3 [120/2] via 100.1.1.1, 00:00:24, Ethernet0

33.0.0.0/32 is subnetted, 1 subnets

R 33.3.3.3 [120/2] via 100.1.1.1, 00:00:24, Ethernet0

If you read the previous tutorial, you may have noticed that we did not specify a seed metric for OSPF. OSPF does not require a seed metric to be set during redistribution. You also noticed that the router did tell us that there might be a problem when we left the "subnets" option out of RIP>OSPF redistribution, but the router didn't tell us anything about a seed metric when we performed OSPF>RIP redistribution. This is a detail you must know by heart in order to make your route redistribution successful!

Cisco CCNP / BSCI Certification: Troubleshooting Route Redistribution, Part I

If there's one CCNP / BSCI topic that looks so easy but can lead to a real headache, it's route redistribution. I'm not even talking about the routing loops and suboptimal routing that can result when route redistribution is done without proper planning - I'm talking about the basic commands themselves. Leaving out one single command option, or forgetting what else needs to be redistributed when redistributing dynamically discovered routes, can leave you with a routing table that looks complete but does not result in full IP connectivity.

In this free CCNP / BSCI tutorial series, we'll take a look at three common errors in route redistribution configurations, and how to fix them. We'll use three routers, R1, R3, and R5. R1 and R5 are in a RIPv2 domain and R1 and R3 are in an OSPF domain. R1 will be performing two-way route redistribution.

R5 is advertising its loopback, 5.5.5.5/24, into the RIPv2 domain. R1 sees this route in its RIP routing table:

R1#show ip route rip

5.0.0.0/24 is subnetted, 1 subnets

R 5.5.5.0 [120/1] via 100.1.1.5, 00:00:01, Ethernet0

For R3 to see this route, route redistribution must be configured on R1. We'll use the redistribute rip command to do so.

R1(config)#router ospf 1

R1(config-router)#redistribute rip

% Only classful networks will be redistributed

The router immediately gives us a message that "only classful networks will be redistributed". What does this mean? Let's go to R3 and see if that router is receiving this route.

R3#show ip route ospf

< no output >

When we get no result from a show command, that means there's nothing to show. The only routes that will be successfully redistributed with the current configuration on R1 are classful networks, and 5.5.5.0/24 is a subnet.

To further illustrate the point, a classful network has been added to R5. This network is 16.0.0.0 /8, and is now being advertised by RIP. R1 sees this network as classful...

R1#show ip route rip

R 16.0.0.0/8 [120/1] via 100.1.1.5, 00:00:00, Ethernet0

5.0.0.0/24 is subnetted, 1 subnets

R 5.5.5.0 [120/1] via 100.1.1.5, 00:00:00, Ethernet0

... and R3 is receiving the route through redistribution.

R3#show ip route ospf

O E2 16.0.0.0/8 [110/20] via 172.12.123.1, 00:00:08, Serial0.31

To redistribute both classful and classless networks, the option "subnets" must be added to the redistribute command on R1.

R1(config)#router ospf 1

R1(config-router)#no redistribute rip

R1(config-router)#redistribute rip subnets

R3 will now see both the classful and classless networks being redistributed into OSPF. (100.1.1.0 is the network connecting R1 and R5.)

R3#show ip route ospf

O E2 16.0.0.0/8 [110/20] via 172.12.123.1, 00:00:20, Serial0.31

100.0.0.0/24 is subnetted, 1 subnets

O E2 100.1.1.0 [110/20] via 172.12.123.1, 00:00:20, Serial0.31

5.0.0.0/24 is subnetted, 1 subnets

O E2 5.5.5.0 [110/20] via 172.12.123.1, 00:00:20, Serial0.31

This is one of the most common errors made during route redistribution, but now you know what to look out for! In the next part of this free CCNP / BSCI tutorial, we'll take a look at another such error.

Cisco CCNA Certification: The Path To Take After Earning The CCNA

Once you earn your CCNA certification, you've got quite a few exciting choices ahead of you! The majority of CCNAs go on to pursue another Cisco certification, and this is a wise decision. The more you know, the more valuable you are in today's IT market.

A question I'm often asked by new CCNAs is "Which certification should I go after next?" Often, these new CCNAs have their eye on the Cisco Certified Security Professional (CCSP) certification. While adding a security certification to your resume is an excellent idea, I strongly recommend that new CCNAs acquire their Cisco Certified Network Professional (CCNP) certification before pursuing their security certifications. The CCNP requires you to pass three or four exams (depending on the path you choose) that will demand a further mastery of some subjects you studies to earn your CCNA as well as several important topics that you haven’t seen yet.

The CCNP builds on the foundation of networking knowledge you built when you earned your CCNA, and your CCNP study will add greatly to your skills and resume. There are some common technologies that you'll see in many networks - BGP and route redistribution among them - that you don't learn about in your CCNA studies. By pursuing your CCNP, you'll also learn much more about OSPF, switching, and refine your troubleshooting skills. These are skills that will pay off in your current job as well as any future job hunting you do.

CCNP / BSCI Exam Tutorial: Route Summarization And The OSPF Null Interface

CCNP exam success, particularly on the BSCI exam, demands you understand the details of route summarization. This skill not only requires that you have a comfort level with binary conversions, but you have to know how and where to apply route summarization with each individual protocol.

You also have to know the "side effects" of route summarization. With OSPF, there will actually be an extra interface created at the point of summarization, and this catches a lot of CCNP candidates by surprise. Let's take a look at the null0 interface and how it relates to OSPF summarization.

On R1, the following networks are redistributed into OSPF, and then summarized.

interface Loopback16

ip address 16.16.16.16 255.0.0.0


interface Loopback17

ip address 17.17.17.17 255.0.0.0


interface Loopback18

ip address 18.18.18.18 255.0.0.0

interface Loopback19

ip address 19.19.19.19 255.0.0.0

R1(config)#router ospf 1

R1(config-router)#redistribute connected subnets

R1(config-router)#summary-address 16.0.0.0 252.0.0.0

The summary address appears on R2, a downstream router.

R2#show ip route ospf


O E2 16.0.0.0/6 [110/20] via 172.12.123.1, 00:00:05, Serial0


Let's go back to R1 and look at its OSPF table.

R1#show ip route ospf


O 16.0.0.0/6 is a summary, 00:01:51, Null0

Where did the null0 interface come from, and why is it there? Packets sent to the null interface are dropped, and in this case, that's a good thing.

When you configure summary routes in OSPF, a route to null0 will be installed into the OSPF routing table. This helps to prevent routing loops. Any packets destined for the routes that have been summarized will have a longer match in the routing table, as shown below...

C 17.0.0.0/8 is directly connected, Loopback17

C 16.0.0.0/8 is directly connected, Loopback16

C 19.0.0.0/8 is directly connected, Loopback19

C 18.0.0.0/8 is directly connected, Loopback18

O 16.0.0.0/6 is a summary, 00:01:51, Null0


.. and packets that do not match one of the summarized routes but do match the summary route will be dropped.

Preventing routing loops when performing route redistribution and summarization is vital. OSPF gives us a little help in that regard in this situation, and as you study more complex redistribution scenarios on your way to the CCNP and CCIE, you'll realize that we'll take all the help we can get!