For those of you who missed Parts 1 and 2 of IP Addressing and Routing you can see the articles here:
Part 1: Invasion of IP Addresses
Part 2: Learn to Master the IP Routing Process
I suggest taking a look at the first two parts before moving on to the third one, just because there is a lot of fundamental concepts and information that you will need to get a clear understanding of what I will be talking about in this part.
For those of you who have been able to keep up with the first two parts, let’s get started. As promised, in this article we are going to talk about the different types of routing:
I’ll start with an explanation of how you can setup static and default routing on your Cisco routers. I will also illustrate how you can use Administrative Distances in your static routes.
Dynamic routing, as mentioned above, is a more advanced topic that requires a separate post — I don’t want to overload you with too much information right now.
So keep an eye out for my next post which is all about the two basic dynamic routing types: Distance vector and Link state — coming soon! Grab our RSS Feed and you’ll get the article sent to you directly!
For those of you who did have the chance to go through my previous posts you will know by now that routers in order to be able to route packets to their final destination, need to maintain a routing table in which all the necessary information will be held.
The information needed is simply a combination of networks and output interfaces on the router that can reach those networks.
Each time a router receives a packet it inspects the destination IP address and tries to find, by looking in its routing table, a possible route to that IP address. Routers do not send broadcasts looking for the remote networks; therefore if a network is not listed in a routers table, the router simply discards the packets.
Now how does a router maintain its routing table? The answer is pretty straightforward. Either manual route directions are configured on the router or dynamic protocols are used to populate routing information to routers.
Manually configuring routes on your router can be both beneficial and disadvantageous.
Static routing has the following benefits:
Disadvantages of Static routing include the following:
To manually insert a static route into the Cisco routers routing table the following command syntax needs to be followed in global configuration mode:

Let’s take a look at each part of the static route command:
Default routing is used only in stub networks. Stub are the networks that have only one output interface and everything going through these networks has to cross the single exit point.
Instead of having many static routes pointing to remote networks via the single output interface, a single default route is configured that matches all possible routes.
By default, Static routes have an administrative distance (AD) of 1. ADs are used for prioritization purposes. Different routes, in a specific destination network can be assigned different weights so that one of the routes is used in favor of the other.
Routes having the same weight load share the traffic. We will see in practice further on how we can change ADs in static routes.
Let’s use an example to illustrate the configuration process for static and/or default routes.

RouterA is directly connected to networks 195.14.25.40/30, 195.14.125.48/30 and 192.168.10.0/24. In order for RouterA to be able to route packets to all other networks the following static routes need to be configured on the router:
The configuration provided above is only one possible solution. A second solution could be defining a default route pointing to network 195.14.25.40/30 since RouterA is a stub router. Once this is configured, everything will be routed to that specific network. The command to configure this default route is:
You may have already noticed that we have two links connecting RouterA and RouterB together. If we wanted to share traffic between these two links then we could use the following set of commands:
Using the commands above, all traffic from RouterA is load shared between these two links (this is a load share per destination and not a 50-50 load sharing).
In case we wanted one of the links as a backup, so that it will be activated only when the primary link goes down, then we could assign different Administrative Distances to the links like, the following:
The route with the lower AD (in our case AD=1) would be the primary route and the other would be the backup route (in our case AD=100).
So far, I’ve shown you how static routes/default routes/priority routes can be defined on RouterA. Still, RouterB and RouterC cannot fully route all subnets to each other and to RouterA. Similar configuration needs to be performed on the other routers as well. But I will leave that for you to carry out.
Remember that routers only know about networks directly connected to them. Static routes or routes learned by dynamic protocols have to be configured in order for the routers to do their job: Routing packets of course.
Also keep in mind that default routes are chosen when there is no specific match in the routing table to a given network. They are preferably used in stub networks.
So go ahead and give this a try! Start by configuring either Static routes, or Default routes. You could even load share traffic when appropriate. And as always, feel free to leave me a comment if you run into any difficulties, or if you have any questions.
Did you like this post? Grab our RSS Feed and you’ll get all of our latest content sent directly to you! If you’re new to RSS see this post for more information and easy instructions!
Our instructor led video training covers the Cisco CCENT Certification and Cisco Networking, including the 64-822 ICND1: Interconnecting Cisco Network Devices Exam. Some of the topics in this training include:
Get your start in Cisco networking — the CCENT certification is your half-way point to your CCNA certification!
Copyright © Train Signal Inc. All Rights Reserved.
Pullin Says:
April 3rd, 2009 at 10:11 am
Good writeup and useful
vernon Says:
February 19th, 2010 at 3:48 am
Hi
I have the following staic routes:
ip route 41.215.235.0 255.255.255.0 41.215.234.110 5
ip route 41.215.235.0 255.255.255.0 41.215.234.114 10
The problem is when I shut the primary interface down the second link does not come up. I tried even unplugging this primary cable. Still does not switch over to the second link. Is there any other way to add weights?