Once you've got your CCNA, you're ready to move on to the next level, the Professional certifications. For years, Cisco had one Professional certification, the Cisco Certified Network Professional (CCNP) certification. Over time, Cisco has expanded this level of certifications to include the Cisco Certified Security Professional (CCSP) and Cisco Certified Voice Professional (CCVP).
With security and voice being the two most rapidly expanding areas of today's networks, some new CCNAs consider going after the CCSP or CCVP without first adding the CCNP to their resume.
While it's temping to hurry up and get a Cisco security or voice certification, the best thing you can do for your networking career is achieve your CCNP certification first, then decide on the CCVP or CCSP.
Why? Because the CCNA is just the tip of a very large iceberg when it comes to routing and switching. It's a very important accomplishment, and the CCNA is indeed the foundation of your networking career, but you need to add on to that level of understanding routing and switching before moving on to more specialized areas.
Two examples are OSPF and BGP. You learn about the theory of OSPF and some basic and intermediate configurations of that protocol in your CCNA studies, but the knowledge you acquire of OSPF in your CCNP studies is invaluable. As for BGP, there is no BGP in the CCNA curriculum, but it is a great idea to have some BGP knowledge in today's networks. It's also good for your career.
I know it is a huge temptation to go after the security and voice certifications while not paying attention to the CCNP. Do yourself a huge favor and add the tremendous amount of routing and switching knowledge needed for the CCNP to your knowledgebase, and you can then move on to the CCSP or CCVP. Even better, you'll be better prepared to climb the biggest certification mountain around - the CCIE!
Showing posts with label ospf. Show all posts
Showing posts with label ospf. Show all posts
Saturday, December 27, 2008
Friday, December 26, 2008
Cisco Routing For The CCNA And CCNP: Administrative Distance
The textbook definition of "administrative distance" is simple enough: "the measurement of a protocol's believability". It's not enough to know the definition, however you've got to know when AD comes into the picture and when it does not.
When a packet needs to be routed, the router looks in its routing table for the next-hop IP address the packet should take to get to the destination. There may be more than one matching path, in which case the router will look for the "longest match". The route that has the longest match - the route with the most bits in the mask set to "1" - will be the route that is used.
Consider the following three routes from a fictional Cisco router:
I 172.17.0.0 /24 via 172.1.1.1
O 172.17.0.0 /25 via 173.1.1.1
R 172.17.0.0 /26 via 174.1.1.1
This router has three possible next-hop IP addresses that it can send packets destined for the network 172.17.0.0. The masks are of different lengths, meaning that the route with the longest match (again, the route with the most bits set to "1") will be used. In this example, the RIP route will be used, since it has the longest match with a mask of /26. The administrative distances do not matter.
AD does matter when the masks are the same length, as shown here:
I 172.17.0.0 /24 via 172.1.1.1
O 172.17.0.0 /24 via 173.1.1.1
R 172.17.0.0 /24 via 174.1.1.1
The longest match rule always precedes the use of AD, but here there is a three-way tie regarding the masks. They're all /24 (or 255.255.255.0 in dotted decimal). AD will be used to break this tie.
As mentioned, AD is a measurement of a protocol's believability. It is important to keep in mind that the lowest AD will be preferred. And while the routing table will show you the ADs of the respective protocols, it's a very good idea to know these ADs before taking the CCNA or CCNP:
Connected route: 0
Static Route: 1
EIGRP Summary: 5
External BGP: 20
EIGRP (Internal): 90
IGRP: 100
OSPF: 110
ISIS : 115
RIP: 120
EIGRP (External) : 170
Unknown: 255 (A router will not believe a source with an AD of 255, and such routes will not be placed into the routing table.)
The three protocols we looked at in the comparison were RIP, IGRP, and OSPF. While your first instinct may be that the OSPF route would be the most believable, IGRP actually has a lower AD than the other two and would be the route installed in the routing table.
Since IGRP does not support variable-length subnet masking and OSPF does, you may never see this scenario outside of an exam question. But if you do see it in the exam room or in a production network, you'll understand how an IGRP route could be preferred over an OSPF route.
When a packet needs to be routed, the router looks in its routing table for the next-hop IP address the packet should take to get to the destination. There may be more than one matching path, in which case the router will look for the "longest match". The route that has the longest match - the route with the most bits in the mask set to "1" - will be the route that is used.
Consider the following three routes from a fictional Cisco router:
I 172.17.0.0 /24 via 172.1.1.1
O 172.17.0.0 /25 via 173.1.1.1
R 172.17.0.0 /26 via 174.1.1.1
This router has three possible next-hop IP addresses that it can send packets destined for the network 172.17.0.0. The masks are of different lengths, meaning that the route with the longest match (again, the route with the most bits set to "1") will be used. In this example, the RIP route will be used, since it has the longest match with a mask of /26. The administrative distances do not matter.
AD does matter when the masks are the same length, as shown here:
I 172.17.0.0 /24 via 172.1.1.1
O 172.17.0.0 /24 via 173.1.1.1
R 172.17.0.0 /24 via 174.1.1.1
The longest match rule always precedes the use of AD, but here there is a three-way tie regarding the masks. They're all /24 (or 255.255.255.0 in dotted decimal). AD will be used to break this tie.
As mentioned, AD is a measurement of a protocol's believability. It is important to keep in mind that the lowest AD will be preferred. And while the routing table will show you the ADs of the respective protocols, it's a very good idea to know these ADs before taking the CCNA or CCNP:
Connected route: 0
Static Route: 1
EIGRP Summary: 5
External BGP: 20
EIGRP (Internal): 90
IGRP: 100
OSPF: 110
ISIS : 115
RIP: 120
EIGRP (External) : 170
Unknown: 255 (A router will not believe a source with an AD of 255, and such routes will not be placed into the routing table.)
The three protocols we looked at in the comparison were RIP, IGRP, and OSPF. While your first instinct may be that the OSPF route would be the most believable, IGRP actually has a lower AD than the other two and would be the route installed in the routing table.
Since IGRP does not support variable-length subnet masking and OSPF does, you may never see this scenario outside of an exam question. But if you do see it in the exam room or in a production network, you'll understand how an IGRP route could be preferred over an OSPF route.
Labels:
ad,
administrative distance,
CCNA,
ccnp,
cisco,
eigrp,
exam,
nat,
ospf,
pass,
rip,
routing table,
study guide
Thursday, December 25, 2008
Cisco CCNP Certification / BSCI Exam Tutorial: Floating Static Routes
Passing the BSCI exam and earning your CCNP certification demands that you add greatly to the networking skills foundation you created when you studied for your CCNA certification. You learned quite a bit about static routing and default static routing when you passed the CCNA test, and it does seem like that should be all you need to know about static routing, right?
One thing you'll learn as you continue to earn Cisco certifications is that there's always something else to learn! You may have heard the term "floating static route", which does suggest some interesting mental pictures. "Floating"? Floating on what?
In a way, a floating static route is "floating" in your routing table. A floating static route is a route that will be used only if routes for the same destination but with a lower administrative distance are removed from the table. For example, you could be using an OSPF-discovered route as your primary route to a given destination, and the floating static route would serve as a backup route that would be used only if the OSPF route leaves the routing table.
Now, how can that happen? After all, OSPF has an administrative distance of 110 and static routes have ADs of one or zero, depending on whether it's configured with a next-hop IP address or a local exit interface. One way or the other, 1 and 0 are still less than 110!
When you want to configure a floating static route, you must assign the route an AD higher than that of the primary route. In this case, we've got to create a static route with an AD higher than 110. We do this by using the "distance" option at the end of the "ip route" command.
R1(config)#ip route 110.1.1.0 255.255.255.0 172.12.123.1 ?
<1-255> Distance metric for this route
name Specify name of the next hop
permanent permanent route
tag Set tag for this route
R1(config)#ip route 110.1.1.0 255.255.255.0 172.12.123.1 111
The number entered at the very end of the "ip route" command is the AD of that route. If there is an OSPF route for 110.1.1.0 /24, that will be the primary route, and the floating static route will not be used unless the OSPF route is taken out of the routing table.
Floating static routes aren't just a good thing to know for the BSCI exam and your CCNP certification pursuit - they're very practical in the real world as well.
One thing you'll learn as you continue to earn Cisco certifications is that there's always something else to learn! You may have heard the term "floating static route", which does suggest some interesting mental pictures. "Floating"? Floating on what?
In a way, a floating static route is "floating" in your routing table. A floating static route is a route that will be used only if routes for the same destination but with a lower administrative distance are removed from the table. For example, you could be using an OSPF-discovered route as your primary route to a given destination, and the floating static route would serve as a backup route that would be used only if the OSPF route leaves the routing table.
Now, how can that happen? After all, OSPF has an administrative distance of 110 and static routes have ADs of one or zero, depending on whether it's configured with a next-hop IP address or a local exit interface. One way or the other, 1 and 0 are still less than 110!
When you want to configure a floating static route, you must assign the route an AD higher than that of the primary route. In this case, we've got to create a static route with an AD higher than 110. We do this by using the "distance" option at the end of the "ip route" command.
R1(config)#ip route 110.1.1.0 255.255.255.0 172.12.123.1 ?
<1-255> Distance metric for this route
name Specify name of the next hop
permanent permanent route
tag Set tag for this route
R1(config)#ip route 110.1.1.0 255.255.255.0 172.12.123.1 111
The number entered at the very end of the "ip route" command is the AD of that route. If there is an OSPF route for 110.1.1.0 /24, that will be the primary route, and the floating static route will not be used unless the OSPF route is taken out of the routing table.
Floating static routes aren't just a good thing to know for the BSCI exam and your CCNP certification pursuit - they're very practical in the real world as well.
Cisco CCNP Certification / BSCI Exam Tutorial: Route Summarization Basics
As you earn your CCNA and CCNP certification, you're going to have to get comfortable with manually summarizing routes. This isn't just another reason to learn binary math (although it's a good one!), but summarizing routes is a true real-world skill that can help your network operate more efficiently. So the question isn't just how to summarize routes, it's why.
When you summarize routes in RIP, IGRP, EIGRP, or OSPF, you're replacing a series of routes with a summary route and mask. With RIP, IGRP, and EIGRP, this actually lessens the size of the routing update packet itself - multiple routes are replaced with the summary route. For instance, the routes 8.0.0.0/8, 9.0.0.0/8, 10.0.0.0/8, and 11.0.0.0/8 can be summarized as 8.0.0.0 252.0.0.0. Only the summary address will be found in the update packet, making it concise yet complete.
Summarizing routes can also make the routing table smaller, yet still allow for complete IP connectivity when done correctly. Using the above example, the four more-specific routes will be replaced by a single summary route. Since the entire routing table is parsed before the routing process is complete, keeping the routing table as small as possible does help speed the routing process as a whole.
To prepare for success on your CCNA and CCNP exam, you've got to know how to summarize routes as well as the specific commands for doing so with OSPF, EIGRP, RIP, and IGRP - but knowing why to summarize routes is just as important as knowing how! Here are some additional tips on route summarization.
With RIP version 2 and EIGRP, manual route summarization is configured on the interface that will be advertising the summary. This is done with the route summarization command "ip summary-address."
RIP version 2 and EIGRP also both perform autosummarization on routes that are advertised across classful network boundaries. This is disabled with the protocol-level command "no auto-summary".
OSPF offers two different route summarization commands. To summarize routes from one OSPF area to another, use the "area range" command; to summarize routes learned via redistribution, use the "summary-address" command on the ASBR.
With proper planning and an understanding of binary math, you'll master route summarization quickly with some practice - and you'll be ready for success on real-world networks as well as the CCNA and CCNP exams!
When you summarize routes in RIP, IGRP, EIGRP, or OSPF, you're replacing a series of routes with a summary route and mask. With RIP, IGRP, and EIGRP, this actually lessens the size of the routing update packet itself - multiple routes are replaced with the summary route. For instance, the routes 8.0.0.0/8, 9.0.0.0/8, 10.0.0.0/8, and 11.0.0.0/8 can be summarized as 8.0.0.0 252.0.0.0. Only the summary address will be found in the update packet, making it concise yet complete.
Summarizing routes can also make the routing table smaller, yet still allow for complete IP connectivity when done correctly. Using the above example, the four more-specific routes will be replaced by a single summary route. Since the entire routing table is parsed before the routing process is complete, keeping the routing table as small as possible does help speed the routing process as a whole.
To prepare for success on your CCNA and CCNP exam, you've got to know how to summarize routes as well as the specific commands for doing so with OSPF, EIGRP, RIP, and IGRP - but knowing why to summarize routes is just as important as knowing how! Here are some additional tips on route summarization.
With RIP version 2 and EIGRP, manual route summarization is configured on the interface that will be advertising the summary. This is done with the route summarization command "ip summary-address."
RIP version 2 and EIGRP also both perform autosummarization on routes that are advertised across classful network boundaries. This is disabled with the protocol-level command "no auto-summary".
OSPF offers two different route summarization commands. To summarize routes from one OSPF area to another, use the "area range" command; to summarize routes learned via redistribution, use the "summary-address" command on the ASBR.
With proper planning and an understanding of binary math, you'll master route summarization quickly with some practice - and you'll be ready for success on real-world networks as well as the CCNA and CCNP exams!
Cisco CCNP / BSCI Tutorial: The Role Of The OSPF ASBR
To pass the BSCI exam and earn your CCNP certification, you've got to master the (many) details of OSPF. You might have thought there were quite a few OSPF details in your CCNA studies, but you'll now build on that foundation on the way to earning your CCNP.
One such detail is the role of the Autonomous System Border Router (ASBR) in OSPF. The name itself raises some eyebrows, since you learned in your CCNA studies that OSPF doesn't use autonomous systems! Just as an OSPF Area Border Router borders multiple OSPF areas, the ASBR borders the entire OSPF domain and another source of routes. This can be another dynamic routing protocol, or directly connected networks that are not being advertised into OSPF by the network command.
Let's say we have a router running both OSPF and RIP version 2. By default, the RIP process will not contain any OSPF-discovered routes, and vice versa. The two separate routing processes are just that - separate. If we want the other OSPF routers to know about the RIP routes, route redistribution must be configured. When the RIP routes are redistributed into OSPF, that router is then an ASBR.
In the below example, RIP subnets have been redistributed into OSPF. A seed metric is not necessary when redistributing routes into OSPF. The command "show ip ospf" confirms that this router is now an ASBR.
R1(config)#router ospf 1
R1(config-router)#redistribute rip subnets
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 autonomous system boundary router
The ASBR can also perform route summarization on the routes being injected into OSPF with the summary-address command. (To configure OSPF inter-area summarization, use the area range command.) By mastering route summarization and route redistribution, you're well on your way to passing the BSCI exam and earning your CCNP certification!
One such detail is the role of the Autonomous System Border Router (ASBR) in OSPF. The name itself raises some eyebrows, since you learned in your CCNA studies that OSPF doesn't use autonomous systems! Just as an OSPF Area Border Router borders multiple OSPF areas, the ASBR borders the entire OSPF domain and another source of routes. This can be another dynamic routing protocol, or directly connected networks that are not being advertised into OSPF by the network command.
Let's say we have a router running both OSPF and RIP version 2. By default, the RIP process will not contain any OSPF-discovered routes, and vice versa. The two separate routing processes are just that - separate. If we want the other OSPF routers to know about the RIP routes, route redistribution must be configured. When the RIP routes are redistributed into OSPF, that router is then an ASBR.
In the below example, RIP subnets have been redistributed into OSPF. A seed metric is not necessary when redistributing routes into OSPF. The command "show ip ospf" confirms that this router is now an ASBR.
R1(config)#router ospf 1
R1(config-router)#redistribute rip subnets
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 autonomous system boundary router
The ASBR can also perform route summarization on the routes being injected into OSPF with the summary-address command. (To configure OSPF inter-area summarization, use the area range command.) By mastering route summarization and route redistribution, you're well on your way to passing the BSCI exam and earning your CCNP certification!
Cisco CCNP / BSCI Tutorial: Comparing OSPF and ISIS Hellos
While studying to pass the BSCI exam and preparing to earn your CCNP certification, you'll quickly notice that while OSPF and ISIS are both link-state protocols, there are a lot of differences between the two. One major difference is the way the two protocols handle hello packets.
Hello packets are imperative to keeping OSPF and ISIS adjacencies alive. Since they are both link-state protocols, neither of them will send updates at any specified time. Hello packets are the only method by which routers running OSPF and ISIS can see that a neighboring router is still available.
OSPF gives us some great options when it comes to keeping routing table size down via the use of stub and total stub areas, but to OSPF, a hello packet is a hello packet. ISIS routers are capable of sending two different types of hellos - Level 1 and Level 2.
ISIS routers are classified as Level 1 (L1), Level 2 (L2), and Level 1-2 (L1-L2). By default, Cisco routers are L1-L2 routers; this means that every ISIS-enabled interface will send out both L1 and L2 hellos.
If one of the interfaces is forming only an L1 or L2 adjacency, there's no reason to send out hellos for the other adjacency type. For example, if R1 is forming an L1 adjacency with R2 via its ethernet0 interface, there is no reason to allow the router to transmit L2 hellos. To hardcode a router interface to send only L1 or L2 hellos, use the isis circuit-type command.
R1(config)#interface ethernet0
R1(config-if)#isis circuit-type level-1
Note: To configure this interface to send only L2 hellos, the full command is "isis circuit-type level-2-only", not just "level-2".
This configuration would prevent L2 hellos from being transmitted out ethernet0. While this does save router resources and prevents unnecessary bandwidth usage, there is also no way an L2 adjacency can be formed - so double-check your network topology before using this command!
Hello packets are imperative to keeping OSPF and ISIS adjacencies alive. Since they are both link-state protocols, neither of them will send updates at any specified time. Hello packets are the only method by which routers running OSPF and ISIS can see that a neighboring router is still available.
OSPF gives us some great options when it comes to keeping routing table size down via the use of stub and total stub areas, but to OSPF, a hello packet is a hello packet. ISIS routers are capable of sending two different types of hellos - Level 1 and Level 2.
ISIS routers are classified as Level 1 (L1), Level 2 (L2), and Level 1-2 (L1-L2). By default, Cisco routers are L1-L2 routers; this means that every ISIS-enabled interface will send out both L1 and L2 hellos.
If one of the interfaces is forming only an L1 or L2 adjacency, there's no reason to send out hellos for the other adjacency type. For example, if R1 is forming an L1 adjacency with R2 via its ethernet0 interface, there is no reason to allow the router to transmit L2 hellos. To hardcode a router interface to send only L1 or L2 hellos, use the isis circuit-type command.
R1(config)#interface ethernet0
R1(config-if)#isis circuit-type level-1
Note: To configure this interface to send only L2 hellos, the full command is "isis circuit-type level-2-only", not just "level-2".
This configuration would prevent L2 hellos from being transmitted out ethernet0. While this does save router resources and prevents unnecessary bandwidth usage, there is also no way an L2 adjacency can be formed - so double-check your network topology before using this command!
Cisco CCNP / BSCI Exam Tutorial: Route Summarization
Preparing to pass the BSCI exam and earn your Cisco CCNP? Route summarization is just one of the many skills you'll have to master in order to earn your CCNP. Whether it's RIP version 2, OSPF, or EIGRP, the BSCI exam will demand that you can flawlessly configure route summarization.
Route summarization isn't just important for the BSCI exam. It's a valuable skill to have in the real world as well. Correctly summarizing routes can lead to smaller routing tables that are still able to route packets accurately - what I like to call "concise and complete" routing tables.
The first skill you've got to have in order to work with route summarization is binary math more specifically, you must be able to take multiple routes and come up with both a summary route and mask to advertise to downstream routers. Given the networks 100.16.0.0 /16, 100.17.0.0 /16, 100.18.0.0 /16, and 100.19.0.0 /16, could you quickly come up with both the summary address and mask? All you need to do is break the four network numbers down into binary strings. We know the last two octets will all convert to the binary string 00000000, so in this article we'll only illustrate how to convert the first and second octet from decimal to binary.
100 16 = 01100100 00010000
100 17 = 01100100 00010001
100 18 = 01100100 00010010
100 19 = 01100100 00010011
To come up with the summary route, just work from left to right and draw a line where the four networks no longer have a bit in common. For these four networks, that point comes between the 14th and 15th bits. This leaves us with this string: 01100100 000100xx. All you need to do is convert that string back to decimal, which gives us 100 for the first octet and 16 for the second. (The two x values are bits on the right side of the line, which aren't used in calculating the summary route.) Since we know that zero is the value for the last two octets, the resulting summary network number is 100.16.0.0.
But we're not done! We now have to come up with the summary mask to advertise along with the summary route. To arrive at the summary route, write out a mask in binary with a "1" for every bit to the left of the line we drew previously, and a "0" for every bit to the right. That gives us the following string:
11111111 11111100 00000000 00000000
Converting that to dotted decimal, we arrive at the summary mask 255.252.0.0. The correct summary network and mask to advertise are 100.16.0.0 252.0.0.0.
For the BSCI exam, emphasis is put on knowing how to advertise these summary routes in RIPv2, EIGRP, and OSPF. For RIP v2 and EIGRP, route summarization happens at the interface level - it's not configured under the protocol. On the interface that should advertise the summary route, use the command "ip summary-address". Here are examples of how the above summary route would be configured on ethernet0 in both RIPv2 and EIGRP.
R1(config-if)#ip summary-address rip 100.16.0.0 255.252.0.0
R1(config-if)#ip summary-address eigrp 100 100.16.0.0 255.252.0.0
The main difference between the two is that the EIGRP command must specify the AS number - that's what the "100" is in the middle of the EIGRP command. Since RIPv2 does not use AS numbers, there's no additional value needed in the configuration.
For OSPF, the commands differ. If you're configuring inter-area route summarization, use the "area range" command. The number following "area" is the area containing the routes being summarized, not the area receiving the summary.
R1(config)#router ospf 1
R1(config-router)#area 1 range 100.16.0.0 255.252.0.0
If you are summarizing routes that are being redistributed into OSPF, use the summary-address command under the OSPF routing process on the ASBR.
R1(config)#router ospf 1
R1(config-router)#summary-address 100.16.0.0 255.252.0.0
I speak from experience when I tell you that practice makes perfect on the BSCI exam, especially with binary and summarization questions. The great thing about these questions is that there are no grey areas with these questions - you either know how to do it or you don't. And with practice and an eye for detail, you can master these skills, pass the exam, and become a CCNP. Here's to your success on these tough Cisco certification exams!
Route summarization isn't just important for the BSCI exam. It's a valuable skill to have in the real world as well. Correctly summarizing routes can lead to smaller routing tables that are still able to route packets accurately - what I like to call "concise and complete" routing tables.
The first skill you've got to have in order to work with route summarization is binary math more specifically, you must be able to take multiple routes and come up with both a summary route and mask to advertise to downstream routers. Given the networks 100.16.0.0 /16, 100.17.0.0 /16, 100.18.0.0 /16, and 100.19.0.0 /16, could you quickly come up with both the summary address and mask? All you need to do is break the four network numbers down into binary strings. We know the last two octets will all convert to the binary string 00000000, so in this article we'll only illustrate how to convert the first and second octet from decimal to binary.
100 16 = 01100100 00010000
100 17 = 01100100 00010001
100 18 = 01100100 00010010
100 19 = 01100100 00010011
To come up with the summary route, just work from left to right and draw a line where the four networks no longer have a bit in common. For these four networks, that point comes between the 14th and 15th bits. This leaves us with this string: 01100100 000100xx. All you need to do is convert that string back to decimal, which gives us 100 for the first octet and 16 for the second. (The two x values are bits on the right side of the line, which aren't used in calculating the summary route.) Since we know that zero is the value for the last two octets, the resulting summary network number is 100.16.0.0.
But we're not done! We now have to come up with the summary mask to advertise along with the summary route. To arrive at the summary route, write out a mask in binary with a "1" for every bit to the left of the line we drew previously, and a "0" for every bit to the right. That gives us the following string:
11111111 11111100 00000000 00000000
Converting that to dotted decimal, we arrive at the summary mask 255.252.0.0. The correct summary network and mask to advertise are 100.16.0.0 252.0.0.0.
For the BSCI exam, emphasis is put on knowing how to advertise these summary routes in RIPv2, EIGRP, and OSPF. For RIP v2 and EIGRP, route summarization happens at the interface level - it's not configured under the protocol. On the interface that should advertise the summary route, use the command "ip summary-address". Here are examples of how the above summary route would be configured on ethernet0 in both RIPv2 and EIGRP.
R1(config-if)#ip summary-address rip 100.16.0.0 255.252.0.0
R1(config-if)#ip summary-address eigrp 100 100.16.0.0 255.252.0.0
The main difference between the two is that the EIGRP command must specify the AS number - that's what the "100" is in the middle of the EIGRP command. Since RIPv2 does not use AS numbers, there's no additional value needed in the configuration.
For OSPF, the commands differ. If you're configuring inter-area route summarization, use the "area range" command. The number following "area" is the area containing the routes being summarized, not the area receiving the summary.
R1(config)#router ospf 1
R1(config-router)#area 1 range 100.16.0.0 255.252.0.0
If you are summarizing routes that are being redistributed into OSPF, use the summary-address command under the OSPF routing process on the ASBR.
R1(config)#router ospf 1
R1(config-router)#summary-address 100.16.0.0 255.252.0.0
I speak from experience when I tell you that practice makes perfect on the BSCI exam, especially with binary and summarization questions. The great thing about these questions is that there are no grey areas with these questions - you either know how to do it or you don't. And with practice and an eye for detail, you can master these skills, pass the exam, and become a CCNP. Here's to your success on these tough Cisco certification exams!
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".
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: Configuring And Troubleshooting OSPF Virtual Links
Knowing when and how to create an OSPF virtual link is an essential skill for BSCI and CCNP exam success, not to mention how important it can be on your job! As a CCNA and CCNP candidate, you know the theory of virtual links, so let's take a look at how to configure a virtual link, as well as some real-world tips that many CCNA and CCNP study guides leave out!
In this configuration, no router with an interface in Area 4 has a physical interface in Area 0. This means a logical connection to Area 0, a virtual link, must be built.
In the following example, R1 and R3 are adjacent and both have interfaces in Area 0. R4 has an adjacency with R3 via Area 34, but R4 has no physical interface in Area 0 and is advertising its loopback 4.4.4.4 into OSPF. R1 doesn't have the route to that loopback.
R1#show ip route ospf
6.0.0.0/32 is subnetted, 1 subnets
O 6.6.6.6 [110/11] via 10.1.1.5, 01:05:45, Ethernet0
172.23.0.0/27 is subnetted, 1 subnets
O IA 172.23.23.0 [110/74] via 172.12.123.3, 00:04:14, Serial0
7.0.0.0/32 is subnetted, 1 subnets
O 7.7.7.7 [110/11] via 10.1.1.5, 01:05:45, Ethernet0
To resolve this, a virtual link will be built between R3 and R4 through Area 34. The area through which the virtual link is built, the transit area, cannot be a stub area of any kind.
R4(config)#router ospf 1
R4(config-router)#area 34 virtual-link 3.3.3.3
R3(config)#router ospf 1
2d07h: %OSPF-4-ERRRCV: Received invalid packet: mismatch area ID, from backbone area must be virtual-link but not found from 172.23.23.4, Ethernet0
R3(config)#router ospf 1
R3(config-router)#area 34 virtual-link 4.4.4.4
R3(config-router)#^Z
2d07h: %OSPF-5-ADJCHG: Process 1, Nbr 4.4.4.4 on OSPF_VL0 from LOADING to FULL, Loading Done
A few details worth noting... the virtual link command uses the remote device's RID, not necessarily the IP address on the interface that's in the transit area. Also, don't worry about that error message you see in the output from R3 that is normal and you'll see it until you finish building the virtual link.
Always confirm the virtual link with show ip ospf virtual-link. If you've configured it correctly, the VL should come up in a matter of seconds.
R3#show ip ospf virtual-link
Virtual Link OSPF_VL0 to router 4.4.4.4 is up
Run as demand circuit
DoNotAge LSA allowed.
Transit area 34, via interface Ethernet0, Cost of using 10
Transmit Delay is 1 sec, State POINT_TO_POINT,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:00
Adjacency State FULL (Hello suppressed)
Index 2/4, retransmission queue length 1, number of retransmission 1
First 0x2C8F8E(15)/0x0(0) Next 0x2C8F8E(15)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Link State retransmission due in 3044 msec
Virtual links are actually simple to configure, but for some reason they seem to intimidate people. It's my experience that the error message highlighted in R3's output above causes a lot of panic, but the only thing that message means is that you're not finished configuring the virtual link yet.
There are three main misconfigurations that cause 99% of virtual link configuration issues:
Using the wrong OSPF RID value
Trying to use a stub area as the transit area
Failure to configure link authentication on the virtual link when Area 0 is running authentication
That last one is the one that gets forgotten! A virtual link is really an extension of Area 0, and if Area 0 is running link authentication, the virtual link must be configured for it as well. Pay attention to the details. don't panic when you see the error message on the second router you configure with the virtual link, and you'll be ready for any virtual link situation on the job or in the CCNA / CCNP exam room!
In this configuration, no router with an interface in Area 4 has a physical interface in Area 0. This means a logical connection to Area 0, a virtual link, must be built.
In the following example, R1 and R3 are adjacent and both have interfaces in Area 0. R4 has an adjacency with R3 via Area 34, but R4 has no physical interface in Area 0 and is advertising its loopback 4.4.4.4 into OSPF. R1 doesn't have the route to that loopback.
R1#show ip route ospf
6.0.0.0/32 is subnetted, 1 subnets
O 6.6.6.6 [110/11] via 10.1.1.5, 01:05:45, Ethernet0
172.23.0.0/27 is subnetted, 1 subnets
O IA 172.23.23.0 [110/74] via 172.12.123.3, 00:04:14, Serial0
7.0.0.0/32 is subnetted, 1 subnets
O 7.7.7.7 [110/11] via 10.1.1.5, 01:05:45, Ethernet0
To resolve this, a virtual link will be built between R3 and R4 through Area 34. The area through which the virtual link is built, the transit area, cannot be a stub area of any kind.
R4(config)#router ospf 1
R4(config-router)#area 34 virtual-link 3.3.3.3
R3(config)#router ospf 1
2d07h: %OSPF-4-ERRRCV: Received invalid packet: mismatch area ID, from backbone area must be virtual-link but not found from 172.23.23.4, Ethernet0
R3(config)#router ospf 1
R3(config-router)#area 34 virtual-link 4.4.4.4
R3(config-router)#^Z
2d07h: %OSPF-5-ADJCHG: Process 1, Nbr 4.4.4.4 on OSPF_VL0 from LOADING to FULL, Loading Done
A few details worth noting... the virtual link command uses the remote device's RID, not necessarily the IP address on the interface that's in the transit area. Also, don't worry about that error message you see in the output from R3 that is normal and you'll see it until you finish building the virtual link.
Always confirm the virtual link with show ip ospf virtual-link. If you've configured it correctly, the VL should come up in a matter of seconds.
R3#show ip ospf virtual-link
Virtual Link OSPF_VL0 to router 4.4.4.4 is up
Run as demand circuit
DoNotAge LSA allowed.
Transit area 34, via interface Ethernet0, Cost of using 10
Transmit Delay is 1 sec, State POINT_TO_POINT,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:00
Adjacency State FULL (Hello suppressed)
Index 2/4, retransmission queue length 1, number of retransmission 1
First 0x2C8F8E(15)/0x0(0) Next 0x2C8F8E(15)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Link State retransmission due in 3044 msec
Virtual links are actually simple to configure, but for some reason they seem to intimidate people. It's my experience that the error message highlighted in R3's output above causes a lot of panic, but the only thing that message means is that you're not finished configuring the virtual link yet.
There are three main misconfigurations that cause 99% of virtual link configuration issues:
Using the wrong OSPF RID value
Trying to use a stub area as the transit area
Failure to configure link authentication on the virtual link when Area 0 is running authentication
That last one is the one that gets forgotten! A virtual link is really an extension of Area 0, and if Area 0 is running link authentication, the virtual link must be configured for it as well. Pay attention to the details. don't panic when you see the error message on the second router you configure with the virtual link, and you'll be ready for any virtual link situation on the job or in the CCNA / CCNP exam room!
Cisco CCNP / BSCI Exam Tutorial: Using The OSPF Command “Area Range”
Your BSCI and CCNP exam success depends on knowing the details, and one such detail is knowing the proper way to summarize routes in OSPF. Route summarization is not just a test of your binary conversion abilities, but knowing where and when to summarize routes. It will not surprise any CCNA or CCNP certification candidate that OSPF gives us the most options for route summarization, and therefore more details to know!
OSPF offers us two options for route summarization configurations. In a previous tutorial, we looked at the "summary-address" command, and today we'll look at the proper use of the "area range" command.
The "area range" command should be used on an Area Border Router (ABR) to summarize routes being advertised from one OSPF area to another. In this tutorial, R1 is acting as an ABR, with interfaces in both Area 0 and Area 1. Four loopbacks have been placed into R1's Area 1.
R1(config)#router ospf 1
R1(config-router)#network 12.0.0.0 0.255.255.255 a 1
R1(config-router)#network 13.0.0.0 0.255.255.255 a 1
R1(config-router)#network 14.0.0.0 0.255.255.255 a 1
R1(config-router)#network 15.0.0.0 0.255.255.255 a 1
The routing table of an OSPF neighbor, R2, shows all four routes.
R2#show ip route ospf
12.0.0.0/32 is subnetted, 1 subnets
O IA 12.12.12.12 [110/65] via 172.12.123.1, 00:18:52, Serial0
13.0.0.0/32 is subnetted, 1 subnets
O IA 13.13.13.13 [110/65] via 172.12.123.1, 00:18:42, Serial0
14.0.0.0/32 is subnetted, 1 subnets
O IA 14.14.14.14 [110/65] via 172.12.123.1, 00:18:32, Serial0
15.0.0.0/32 is subnetted, 1 subnets
O IA 15.15.15.15 [110/65] via 172.12.123.1, 00:18:32, Serial0
To keep the routing tables of downstream routers smaller but still have the desired IP connectivity, we can use the area range command on R1 to summarize these four routes. The key to keep in mind with the area range command is that the area number given in the command is the area containing the destinations, NOT the area that will receive the summary route.
R1(config)#router ospf 1
R1(config-router)#area 1 range 12.0.0.0 252.0.0.0
R2 now shows a single summary route that can be used to reach all four remote networks.
R2#show ip route ospf
O IA 12.0.0.0/6 [110/65] via 172.12.123.1, 00:00:21, Serial0
Interestingly enough, there's now an additional route in R1's routing table.
R1#show ip route ospf
O 12.0.0.0/6 is a summary, 00:07:53, Null0
When you configure summary routes in OSPF, a route to null0 will be installed into the OSPF routing table of the router performing the summarization. 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, and packets that do not match one of the summarized routes but do match the summary route will be dropped.
OSPF offers us two options for route summarization configurations. In a previous tutorial, we looked at the "summary-address" command, and today we'll look at the proper use of the "area range" command.
The "area range" command should be used on an Area Border Router (ABR) to summarize routes being advertised from one OSPF area to another. In this tutorial, R1 is acting as an ABR, with interfaces in both Area 0 and Area 1. Four loopbacks have been placed into R1's Area 1.
R1(config)#router ospf 1
R1(config-router)#network 12.0.0.0 0.255.255.255 a 1
R1(config-router)#network 13.0.0.0 0.255.255.255 a 1
R1(config-router)#network 14.0.0.0 0.255.255.255 a 1
R1(config-router)#network 15.0.0.0 0.255.255.255 a 1
The routing table of an OSPF neighbor, R2, shows all four routes.
R2#show ip route ospf
12.0.0.0/32 is subnetted, 1 subnets
O IA 12.12.12.12 [110/65] via 172.12.123.1, 00:18:52, Serial0
13.0.0.0/32 is subnetted, 1 subnets
O IA 13.13.13.13 [110/65] via 172.12.123.1, 00:18:42, Serial0
14.0.0.0/32 is subnetted, 1 subnets
O IA 14.14.14.14 [110/65] via 172.12.123.1, 00:18:32, Serial0
15.0.0.0/32 is subnetted, 1 subnets
O IA 15.15.15.15 [110/65] via 172.12.123.1, 00:18:32, Serial0
To keep the routing tables of downstream routers smaller but still have the desired IP connectivity, we can use the area range command on R1 to summarize these four routes. The key to keep in mind with the area range command is that the area number given in the command is the area containing the destinations, NOT the area that will receive the summary route.
R1(config)#router ospf 1
R1(config-router)#area 1 range 12.0.0.0 252.0.0.0
R2 now shows a single summary route that can be used to reach all four remote networks.
R2#show ip route ospf
O IA 12.0.0.0/6 [110/65] via 172.12.123.1, 00:00:21, Serial0
Interestingly enough, there's now an additional route in R1's routing table.
R1#show ip route ospf
O 12.0.0.0/6 is a summary, 00:07:53, Null0
When you configure summary routes in OSPF, a route to null0 will be installed into the OSPF routing table of the router performing the summarization. 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, and packets that do not match one of the summarized routes but do match the summary route will be dropped.
Cisco CCNP / BSCI Exam Tutorial: Using OSPF's "Summary-Address" Command
BSCI exam success, not to mention earning your CCNP, can come down to your OSPF route summarization skills. There are a few different commands and situations you need to be ready for, and one of these situations is the proper use of the "summary-address" command.
The summary-address command should be used on an ASBR in order to summarize routes that are being injected into the OSPF domain via redistribution. In the following example, four routes are being redisitributed into OSPF on R1, making R1 an ASBR.
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
These four routes are seen on downstream router R2 as External Type-2, the default for routes redistributed into OSPF.
R2#show ip route ospf
O E2 17.0.0.0/8 [110/20] via 172.12.123.1, 00:00:07, Serial0
O E2 16.0.0.0/8 [110/20] via 172.12.123.1, 00:00:07, Serial0
O E2 19.0.0.0/8 [110/20] via 172.12.123.1, 00:00:07, Serial0
O E2 18.0.0.0/8 [110/20] via 172.12.123.1, 00:00:07, Serial0
To summarize networks learned by redistribution, use the OSPF command summary-address. You can probably do this summarization in your head, but do so before continuing with the lab.
R1(config)#router ospf 1
R1(config-router)#summary-address 16.0.0.0 252.0.0.0
Look at the change in R2's OSPF table.
R2#show ip route ospf
O E2 16.0.0.0/6 [110/20] via 172.12.123.1, 00:00:05, Serial0
The external routes have been successfully summarized. Note that the summary route is still marked as an E2 route.
There's an interesting route installed into R1's OSPF table as well.
R1#show ip route ospf
O 16.0.0.0/6 is a summary, 00:01:51, Null0
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....
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:03:10, Null0
O 12.0.0.0/6 is a summary, 00:07:53, Null0
.. and packets that do not match one of the summarized routes but do match the summary route will be dropped.
The summary-address command should be used on an ASBR in order to summarize routes that are being injected into the OSPF domain via redistribution. In the following example, four routes are being redisitributed into OSPF on R1, making R1 an ASBR.
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
These four routes are seen on downstream router R2 as External Type-2, the default for routes redistributed into OSPF.
R2#show ip route ospf
O E2 17.0.0.0/8 [110/20] via 172.12.123.1, 00:00:07, Serial0
O E2 16.0.0.0/8 [110/20] via 172.12.123.1, 00:00:07, Serial0
O E2 19.0.0.0/8 [110/20] via 172.12.123.1, 00:00:07, Serial0
O E2 18.0.0.0/8 [110/20] via 172.12.123.1, 00:00:07, Serial0
To summarize networks learned by redistribution, use the OSPF command summary-address. You can probably do this summarization in your head, but do so before continuing with the lab.
R1(config)#router ospf 1
R1(config-router)#summary-address 16.0.0.0 252.0.0.0
Look at the change in R2's OSPF table.
R2#show ip route ospf
O E2 16.0.0.0/6 [110/20] via 172.12.123.1, 00:00:05, Serial0
The external routes have been successfully summarized. Note that the summary route is still marked as an E2 route.
There's an interesting route installed into R1's OSPF table as well.
R1#show ip route ospf
O 16.0.0.0/6 is a summary, 00:01:51, Null0
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....
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:03:10, Null0
O 12.0.0.0/6 is a summary, 00:07:53, Null0
.. and packets that do not match one of the summarized routes but do match the summary route will be dropped.
Cisco CCNP / BSCI Exam Tutorial: The Passive Interface Command And OSPF
To pass the BSCI exam and become a CCNP, you have to be aware of the proper use of passive interfaces. You learned about passive interfaces in your CCNA studies, but here we’ll review the basic concept and clear up one misconception regarding passive interfaces and OSPF.
Configuring an interface as passive will still allow the interface to receive routing updates, but the interface will no longer transmit them. While the command itself would make you think this command will be applied at the interface level, that is not the case. Below, we’ll configure ethernet0 as a RIP passive interface.
R1(config)#router rip
R1(config-router)#passive-interface ethernet0
Ethernet0 will no longer send RIP routing updates, but will accept them.
The passive interface concept is clear enough with RIP, IGRP, and EIGRP – all protocols that send routing update packets. But OSPF doesn’t send routing update packets – OSPF sends link state advertisements. It’s the inability of the passive interface command to stop LSAs that lead many to think that passive interfaces cannot be used with OSPF.
Even though OSPF does not sent "routing updates" in the form that RIP, IGRP, and EIGRP do, you can still configure an OSPF-enabled interface as passive in order to prevent OSPF traffic from exiting or entering that interface. No OSPF adjacency can be formed if one of the interfaces involved is a passive interface, and if you configure an OSPF-enabled interface as passive where an adjacency already exists, the adjacency will drop almost immediately.
Let's see that in action. R1 and R2 have an existing OSPF adjacency over their Ethernet interfaces. In an effort to reduce routing traffic, R1's e0 interface is configured as passive. The adjacency drops right away.
R1(config)#router ospf 1
R1(config-router)#passive-interface ethernet0
18:31:11: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0 from FULL to DOWN, Neighbor Down: Interface down or detached
Knowing how to use the passive interface command is a vital part of being a CCNP, and of being a master networker. Good luck to you in both of these pursuits!
Configuring an interface as passive will still allow the interface to receive routing updates, but the interface will no longer transmit them. While the command itself would make you think this command will be applied at the interface level, that is not the case. Below, we’ll configure ethernet0 as a RIP passive interface.
R1(config)#router rip
R1(config-router)#passive-interface ethernet0
Ethernet0 will no longer send RIP routing updates, but will accept them.
The passive interface concept is clear enough with RIP, IGRP, and EIGRP – all protocols that send routing update packets. But OSPF doesn’t send routing update packets – OSPF sends link state advertisements. It’s the inability of the passive interface command to stop LSAs that lead many to think that passive interfaces cannot be used with OSPF.
Even though OSPF does not sent "routing updates" in the form that RIP, IGRP, and EIGRP do, you can still configure an OSPF-enabled interface as passive in order to prevent OSPF traffic from exiting or entering that interface. No OSPF adjacency can be formed if one of the interfaces involved is a passive interface, and if you configure an OSPF-enabled interface as passive where an adjacency already exists, the adjacency will drop almost immediately.
Let's see that in action. R1 and R2 have an existing OSPF adjacency over their Ethernet interfaces. In an effort to reduce routing traffic, R1's e0 interface is configured as passive. The adjacency drops right away.
R1(config)#router ospf 1
R1(config-router)#passive-interface ethernet0
18:31:11: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0 from FULL to DOWN, Neighbor Down: Interface down or detached
Knowing how to use the passive interface command is a vital part of being a CCNP, and of being a master networker. Good luck to you in both of these pursuits!
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!
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 Exam Tutorial: EIGRP Route Summarization
Summarizing routes is a vital skill to learn to pass the BSCI exam and get one step closer to earning your CCNP. The actual binary conversions are only part of the test, though! You've got to know how to correctly apply the summary routes, and that differs from one protocol to the next. In the last few CCNP / BSCI tutorials, we've looked at using the "area range" and "summary-address" commands to perform OSPF route summarization. Today, we'll take a look at summarizing routes in EIGRP.
We'll use the following four loopback addresses in this example:
Loopback 16, 16.16.16.16 /32
Loopback 17, 17.17.17.17 /32
Loopback 18, 18.18.18.18 /32
Loopback 19. 19.19.19.19 /32
On R1, we'll place these four addresses into EIGRP AS 100.
R1(config-if)#router eigrp 100
R1(config-router)#network 16.16.16.16 0.0.0.0
R1(config-router)#network 17.17.17.17 0.0.0.0
R1(config-router)#network 18.18.18.18 0.0.0.0
R1(config-router)#network 19.19.19.19 0.0.0.0
R3 is an EIGRP neighbor of R1, and that router's EIGRP routing table now looks like this:
R3#show ip route eigrp
17.0.0.0/32 is subnetted, 1 subnets
D 17.17.17.17 [90/2297856] via 172.12.123.1, 00:00:29, Serial0
16.0.0.0/32 is subnetted, 1 subnets
D 16.16.16.16 [90/2297856] via 172.12.123.1, 00:00:36, Serial0
19.0.0.0/32 is subnetted, 1 subnets
D 19.19.19.19 [90/2297856] via 172.12.123.1, 00:00:08, Serial0
18.0.0.0/32 is subnetted, 1 subnets
D 18.18.18.18 [90/2297856] via 172.12.123.1, 00:00:22, Serial0
To perform manual route summarization, write out the network addresses in binary and then determine the point at which the addresses no longer have a bit in common. For these four addresses, it will be enough to write out the first octet in binary:
16 00010000
17 00010001
18 00010010
19 00010011
Working from left to right, the common bits are the first six bits - 000100xx. In decimal, this value is 16. The summary mask must be determined as well, and that value is derived from putting a "1" in the mask for each common bit. With the first six bits all set to one - 11111100 - the resulting mask is 252.0.0.0. The full summary address is 16.0.0.0 252.0.0.0.
In EIGRP, the summary address is actually configured on an interface, not under the routing process.
R1(config)#interface serial0
R1(config-if)#ip summary-address eigrp 100 16.0.0.0 252.0.0.0
02:39:50: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor
172.12.123.3 (Serial0) is down: summary configured
02:39:50: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor
172.12.123.2 (Serial0) is down: summary configured
02:40:16: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor
172.12.123.2 (Serial0) is up : new adjacency
02:40:17: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor
172.12.123.3 (Serial0) is up: new adjacency
There's an immediate side effect here that most books leave out. Your EIGRP adjacencies are going to come down after you configure this summary, but they should come back up quickly. The key word there is "should". If you configure EIGRP summary addresses on a production network, you may want to do this during non-peak hours. The timestamps on the above commands indicate that the adjacencies were down for about 27 seconds over the NBMA network. That's about 30 minutes in end-user time. ;)
Check R3's EIGRP routing table.
R3#show ip route eigrp
D 16.0.0.0/6 [90/2297856] via 172.12.123.1, 00:01:46, Serial0
The four summarized routes are no longer in the routing table, and they have been replaced by the summary route shown at the bottom of the routing table. Notice the mask is /5, which is prefix notation for 248.0.0.0.
Knowing how and why to summarize routes is a valuable skill, regardless of the protocol in use. But before you take the BSCI exam on your way to the CCNP, make sure you know how to perform summarization with all of the core protocols!
We'll use the following four loopback addresses in this example:
Loopback 16, 16.16.16.16 /32
Loopback 17, 17.17.17.17 /32
Loopback 18, 18.18.18.18 /32
Loopback 19. 19.19.19.19 /32
On R1, we'll place these four addresses into EIGRP AS 100.
R1(config-if)#router eigrp 100
R1(config-router)#network 16.16.16.16 0.0.0.0
R1(config-router)#network 17.17.17.17 0.0.0.0
R1(config-router)#network 18.18.18.18 0.0.0.0
R1(config-router)#network 19.19.19.19 0.0.0.0
R3 is an EIGRP neighbor of R1, and that router's EIGRP routing table now looks like this:
R3#show ip route eigrp
17.0.0.0/32 is subnetted, 1 subnets
D 17.17.17.17 [90/2297856] via 172.12.123.1, 00:00:29, Serial0
16.0.0.0/32 is subnetted, 1 subnets
D 16.16.16.16 [90/2297856] via 172.12.123.1, 00:00:36, Serial0
19.0.0.0/32 is subnetted, 1 subnets
D 19.19.19.19 [90/2297856] via 172.12.123.1, 00:00:08, Serial0
18.0.0.0/32 is subnetted, 1 subnets
D 18.18.18.18 [90/2297856] via 172.12.123.1, 00:00:22, Serial0
To perform manual route summarization, write out the network addresses in binary and then determine the point at which the addresses no longer have a bit in common. For these four addresses, it will be enough to write out the first octet in binary:
16 00010000
17 00010001
18 00010010
19 00010011
Working from left to right, the common bits are the first six bits - 000100xx. In decimal, this value is 16. The summary mask must be determined as well, and that value is derived from putting a "1" in the mask for each common bit. With the first six bits all set to one - 11111100 - the resulting mask is 252.0.0.0. The full summary address is 16.0.0.0 252.0.0.0.
In EIGRP, the summary address is actually configured on an interface, not under the routing process.
R1(config)#interface serial0
R1(config-if)#ip summary-address eigrp 100 16.0.0.0 252.0.0.0
02:39:50: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor
172.12.123.3 (Serial0) is down: summary configured
02:39:50: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor
172.12.123.2 (Serial0) is down: summary configured
02:40:16: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor
172.12.123.2 (Serial0) is up : new adjacency
02:40:17: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor
172.12.123.3 (Serial0) is up: new adjacency
There's an immediate side effect here that most books leave out. Your EIGRP adjacencies are going to come down after you configure this summary, but they should come back up quickly. The key word there is "should". If you configure EIGRP summary addresses on a production network, you may want to do this during non-peak hours. The timestamps on the above commands indicate that the adjacencies were down for about 27 seconds over the NBMA network. That's about 30 minutes in end-user time. ;)
Check R3's EIGRP routing table.
R3#show ip route eigrp
D 16.0.0.0/6 [90/2297856] via 172.12.123.1, 00:01:46, Serial0
The four summarized routes are no longer in the routing table, and they have been replaced by the summary route shown at the bottom of the routing table. Notice the mask is /5, which is prefix notation for 248.0.0.0.
Knowing how and why to summarize routes is a valuable skill, regardless of the protocol in use. But before you take the BSCI exam on your way to the CCNP, make sure you know how to perform summarization with all of the core protocols!
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!
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!
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.
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 CCNP / BSCI Certification: Introduction To ISIS Terminology
When you're studying to pass the BSCI exam and earn your CCNP certification, you're going to be introduced to ISIS. ISIS and OSPF are both link-state protocols, but ISIS works quite differently from OSPF. You must master these details in order to earn your CCNP.
One of the major differences between OSPF and ISIS will be evident to you when you first begin your BSCI exam studies, and that is the terminology. ISIS uses terms that no other protocol you've studied to date uses, and learning these new terms is the first step to BSCI and CCNP exam success.
First off, what does "IS" stand for in "ISIS"? It stands for "Intermediate System", which sounds like a group of routers. As opposed to Autonomous Systems, which are logical groups of routers, an Intermediate System is simply a single router. That's it.
You'll also become familiar with End Systems, referred to in ISIS as an "ES". The End System is simply an end host.
ISIS and OSPF both use the concept of areas, but ISIS takes a different approach to this concept. ISIS routers use three different types of routing levels, according to the area a router has been placed in. Level 2 routers are connected only to the backbone and serve as a transit device between non-backbone areas. Level 1 routers are totally internal to a non-backbone area.
ISIS uses both Level-1 and Level-2 Hellos, meaning that the two types of routers just mentioned cannot form an adjacency. Luckily for us, there is a middle ground, and that is the Level 1-2 router. These routers connect non-backbone areas to backbone areas. L1-L2 routers keep two separate routing tables, one for L1 routing and another for L2 routing. This is the default setting for a Cisco router, and L1-L2 routers can form adjacencies with both L1 and L2 routers.
Part of the challenge of learning ISIS is getting used to the differences between ISIS and OSPF. Keep studying the terminology, master one concept at a time, and soon you'll be a master of ISIS and a CCNP to boot!
One of the major differences between OSPF and ISIS will be evident to you when you first begin your BSCI exam studies, and that is the terminology. ISIS uses terms that no other protocol you've studied to date uses, and learning these new terms is the first step to BSCI and CCNP exam success.
First off, what does "IS" stand for in "ISIS"? It stands for "Intermediate System", which sounds like a group of routers. As opposed to Autonomous Systems, which are logical groups of routers, an Intermediate System is simply a single router. That's it.
You'll also become familiar with End Systems, referred to in ISIS as an "ES". The End System is simply an end host.
ISIS and OSPF both use the concept of areas, but ISIS takes a different approach to this concept. ISIS routers use three different types of routing levels, according to the area a router has been placed in. Level 2 routers are connected only to the backbone and serve as a transit device between non-backbone areas. Level 1 routers are totally internal to a non-backbone area.
ISIS uses both Level-1 and Level-2 Hellos, meaning that the two types of routers just mentioned cannot form an adjacency. Luckily for us, there is a middle ground, and that is the Level 1-2 router. These routers connect non-backbone areas to backbone areas. L1-L2 routers keep two separate routing tables, one for L1 routing and another for L2 routing. This is the default setting for a Cisco router, and L1-L2 routers can form adjacencies with both L1 and L2 routers.
Part of the challenge of learning ISIS is getting used to the differences between ISIS and OSPF. Keep studying the terminology, master one concept at a time, and soon you'll be a master of ISIS and a CCNP to boot!
Cisco CCNA Exam Tutorial: Route Summarization
Preparing to pass the CCNA exam and earn this important Cisco certification? Route summarization is just one of the many skills you'll have to master in order to earn your CCNA. Whether it's RIP version 2, OSPF, or EIGRP, the CCNA exam will demand that you can flawlessly configure route summarization.
Route summarization isn't just important for the CCNA exam. It's a valuable skill to have in the real world as well. Correctly summarizing routes can lead to smaller routing tables that are still able to route packets accurately - what I like to call "concise and complete" routing tables.
The first skill you've got to have in order to work with route summarization is binary math; more specifically, you must be able to take multiple routes and come up with both a summary route and mask to advertise to downstream routers. Given the networks 100.16.0.0 /16, 100.17.0.0 /16, 100.18.0.0 /16, and 100.19.0.0 /16, could you quickly come up with both the summary address and mask? All you need to do is break the four network numbers down into binary strings. We know the last two octets will all convert to the binary string 00000000, so in this article we'll only illustrate how to convert the first and second octet from decimal to binary.
100 16 = 01100100 00010000
100 17 = 01100100 00010001
100 18 = 01100100 00010010
100 19 = 01100100 00010011
To come up with the summary route, just work from left to right and draw a line where the four networks no longer have a bit in common. For these four networks, that point comes between the 14th and 15th bits. This leaves us with this string: 01100100 000100xx. All you need to do is convert that string back to decimal, which gives us 100 for the first octet and 16 for the second. (The two x values are bits on the right side of the line, which aren't used in calculating the summary route.) Since we know that zero is the value for the last two octets, the resulting summary network number is 100.16.0.0.
But we're not done! We now have to come up with the summary mask to advertise along with the summary route. To arrive at the summary route, write out a mask in binary with a "1" for every bit to the left of the line we drew previously, and a "0" for every bit to the right. That gives us the following string:
11111111 11111100 00000000 00000000
Converting that to dotted decimal, we arrive at the summary mask 255.252.0.0. The correct summary network and mask to advertise are 100.16.0.0 252.0.0.0.
For the CCNA exam, emphasis is put on knowing how to advertise these summary routes in RIPv2 and EIGRP. For both of these protocols, route summarization happens at the interface level - it's not configured under the protocol. On the interface that should advertise the summary route, use the command "ip summary-address". Here are examples of how the above summary route would be configured on ethernet0 in both RIPv2 and EIGRP.
R1(config-if)#ip summary-address rip 100.16.0.0 255.252.0.0
R1(config-if)#ip summary-address eigrp 100 100.16.0.0 255.252.0.0
The main difference between the two is that the EIGRP command must specify the AS number - that's what the "100" is in the middle of the EIGRP command. Since RIPv2 does not use AS numbers, there's no additional value needed in the configuration.
For OSPF, the commands differ. If you're configuring inter-area route summarization, use the "area range" command; if you are summarizing routes that are being redistributed into OSPF, use the summary-address command under the OSPF routing process on the ASBR. Neither of these are interface-level commands.
I speak from experience when I tell you that practice makes perfect on the CCNA exam, especially with binary and summarization questions. The great thing about these questions is that there are no grey areas with these questions - you either know how to do it or you don't. And with practice and an eye for detail, you can master these skills, pass the exam, and become a CCNA. Here's to your success!
Route summarization isn't just important for the CCNA exam. It's a valuable skill to have in the real world as well. Correctly summarizing routes can lead to smaller routing tables that are still able to route packets accurately - what I like to call "concise and complete" routing tables.
The first skill you've got to have in order to work with route summarization is binary math; more specifically, you must be able to take multiple routes and come up with both a summary route and mask to advertise to downstream routers. Given the networks 100.16.0.0 /16, 100.17.0.0 /16, 100.18.0.0 /16, and 100.19.0.0 /16, could you quickly come up with both the summary address and mask? All you need to do is break the four network numbers down into binary strings. We know the last two octets will all convert to the binary string 00000000, so in this article we'll only illustrate how to convert the first and second octet from decimal to binary.
100 16 = 01100100 00010000
100 17 = 01100100 00010001
100 18 = 01100100 00010010
100 19 = 01100100 00010011
To come up with the summary route, just work from left to right and draw a line where the four networks no longer have a bit in common. For these four networks, that point comes between the 14th and 15th bits. This leaves us with this string: 01100100 000100xx. All you need to do is convert that string back to decimal, which gives us 100 for the first octet and 16 for the second. (The two x values are bits on the right side of the line, which aren't used in calculating the summary route.) Since we know that zero is the value for the last two octets, the resulting summary network number is 100.16.0.0.
But we're not done! We now have to come up with the summary mask to advertise along with the summary route. To arrive at the summary route, write out a mask in binary with a "1" for every bit to the left of the line we drew previously, and a "0" for every bit to the right. That gives us the following string:
11111111 11111100 00000000 00000000
Converting that to dotted decimal, we arrive at the summary mask 255.252.0.0. The correct summary network and mask to advertise are 100.16.0.0 252.0.0.0.
For the CCNA exam, emphasis is put on knowing how to advertise these summary routes in RIPv2 and EIGRP. For both of these protocols, route summarization happens at the interface level - it's not configured under the protocol. On the interface that should advertise the summary route, use the command "ip summary-address". Here are examples of how the above summary route would be configured on ethernet0 in both RIPv2 and EIGRP.
R1(config-if)#ip summary-address rip 100.16.0.0 255.252.0.0
R1(config-if)#ip summary-address eigrp 100 100.16.0.0 255.252.0.0
The main difference between the two is that the EIGRP command must specify the AS number - that's what the "100" is in the middle of the EIGRP command. Since RIPv2 does not use AS numbers, there's no additional value needed in the configuration.
For OSPF, the commands differ. If you're configuring inter-area route summarization, use the "area range" command; if you are summarizing routes that are being redistributed into OSPF, use the summary-address command under the OSPF routing process on the ASBR. Neither of these are interface-level commands.
I speak from experience when I tell you that practice makes perfect on the CCNA exam, especially with binary and summarization questions. The great thing about these questions is that there are no grey areas with these questions - you either know how to do it or you don't. And with practice and an eye for detail, you can master these skills, pass the exam, and become a CCNA. Here's to your success!
Cisco CCNA Exam Tutorial: Five OSPF Hub-And-Spoke Details You Must Know!
CCNA exam success depends greatly on knowing the details, and if there's one protocol that has a lot of details, it's OSPF! This is true particularly of hub-and-spoke networks, so in this CCNA OSPF tutorial we'll take a look at some of the more important hub-and-spoke OSPF details. This will help you in working with real-world networks as well, since this OSPF network type is one of the more typical network topologies.
In OSPF, the hub must become the designated router (DR). The DR election's deciding value is the OSPF interface priority, and the default value is 1. It's not enough to set the hub's OSPF interface to 2, however, since the spoke routers must not become the DR or BDR. You must set the spoke interfaces to an OSPF priority of zero.
R2(config)#int s0
R2(config-if)#ip ospf priority 0
This ensures that the spokes will not become the DR or BDR if the hub goes down.
The hub does require a bit more configuration, though. The neighbor command must be used on the hub to indicate the IP address of the potential neighbors.
R1(config)#router ospf 1
R1(config-router)#neighbor 172.12.123.2
R1(config-router)#neighbor 172.12.123.3
It's common to have an ISDN link as a backup in an OSPF network, and when that ISDN link comes up the hello packets must be able to cross the link. What you don't want is to have the hellos keep the link up! By configuring the ISDN link as an OSPF demand circuit, the link will drop in the absence of interesting traffic, but the OSPF adjacency that formed across the ISDN link will be assumed by the router to still be up. (You usually see this command configured on both sides of the ISDN link, but it's only needed on one side. It doesn't hurt anything to put it on both sides, though.)
R2(config)#int bri0
R2(config-if)#ip ospf demand-circuit
A final detail of OSPF hub-and-spoke and demand circuits actually takes place at Layer 2. For the OSPF hello packets to successfully be transmitted across an ISDN link or a frame relay network, the broadcast option must be enabled in the appropriate frame and dialer map statements. Failure to enable this option can lead to a situation where pings will be successful, but OSPF adjacencies will not form.
R2(config-if)#dialer map ip 172.12.21.1 name R1 broadcast 5551111
R2(config-if)#frame map ip 172.12.123.1 221 broadcast
When you're troubleshooting OSPF in a production network or your CCNA / CCNP home lab, don't just look at Layer 3 - because everything's got to be right at the physical and data link layers in order for the network layer to function correctly!
In OSPF, the hub must become the designated router (DR). The DR election's deciding value is the OSPF interface priority, and the default value is 1. It's not enough to set the hub's OSPF interface to 2, however, since the spoke routers must not become the DR or BDR. You must set the spoke interfaces to an OSPF priority of zero.
R2(config)#int s0
R2(config-if)#ip ospf priority 0
This ensures that the spokes will not become the DR or BDR if the hub goes down.
The hub does require a bit more configuration, though. The neighbor command must be used on the hub to indicate the IP address of the potential neighbors.
R1(config)#router ospf 1
R1(config-router)#neighbor 172.12.123.2
R1(config-router)#neighbor 172.12.123.3
It's common to have an ISDN link as a backup in an OSPF network, and when that ISDN link comes up the hello packets must be able to cross the link. What you don't want is to have the hellos keep the link up! By configuring the ISDN link as an OSPF demand circuit, the link will drop in the absence of interesting traffic, but the OSPF adjacency that formed across the ISDN link will be assumed by the router to still be up. (You usually see this command configured on both sides of the ISDN link, but it's only needed on one side. It doesn't hurt anything to put it on both sides, though.)
R2(config)#int bri0
R2(config-if)#ip ospf demand-circuit
A final detail of OSPF hub-and-spoke and demand circuits actually takes place at Layer 2. For the OSPF hello packets to successfully be transmitted across an ISDN link or a frame relay network, the broadcast option must be enabled in the appropriate frame and dialer map statements. Failure to enable this option can lead to a situation where pings will be successful, but OSPF adjacencies will not form.
R2(config-if)#dialer map ip 172.12.21.1 name R1 broadcast 5551111
R2(config-if)#frame map ip 172.12.123.1 221 broadcast
When you're troubleshooting OSPF in a production network or your CCNA / CCNP home lab, don't just look at Layer 3 - because everything's got to be right at the physical and data link layers in order for the network layer to function correctly!
Subscribe to:
Posts (Atom)