Skip to main content

Static route operation

Static route operation 
6.1.2
This page will explain how static routes operate and how they are created.
Static route operations can be divided into these three parts:
  • Network administrator configures the route
  • Router installs the route in the routing table
  • The static route is used to route packets.
An administrator must use the ip route command to manually configure a static route. The correct syntax for the ip route command is shown in Figure .
In Figures and , the network administrator of the Hoboken router needs to configure a static route to the 172.16.1.0/24 and 172.16.5.0/24 networks on the other routers. The administrator could enter either of two commands to accomplish this objective. The method in Figure specifies the outgoing interface. The method in Figure specifies the next-hop IP address of the adjacent router. Either of the commands will install a static route in the routing table of Hoboken.
The administrative distance is an optional parameter that indicates the reliability of a route. A lower value for the administrative distance indicates a more reliable route. A route with a lower administrative distance will be installed before a similar route with a higher administrative distance. The default administrative distance when using a static route is 1. In the routing table, it will show the static route with the outgoing interface option as being directly connected. This is sometimes confusing, since a true directly connected route has an administrative distance of 0. To verify the administrative distance of a particular route, use the show ip routeaddress command, where the ip address of the particular route is inserted for the address option. If an administrative distance other than the default is desired, a value between 0 and 255 is entered after the next-hop or outgoing interface as follows:
waycross(config)#ip route 172.16.3.0 255.255.255.0 172.16.4.1 130
If the router cannot reach the outgoing interface that is being used in a route, the route will not be installed in the routing table. This means if that interface is down, the route will not be placed in the routing table.
Sometimes static routes are used for backup purposes. A static route can be configured on a router that will only be used when the dynamically learned route has failed. To use a static route as a backup, set a higher administrative distance than the dynamic routing protocol.
The Lab Activities will show students how static routes are created and used to troubleshoot networks.
The next page will teach students how to configure static routes.

Comments

Popular posts from this blog

OSI layers / Peer-to-peer communications / TCP/IP model

OSI layers 2.3.4 This page discusses the seven layers of the OSI model. The OSI reference model is a framework that is used to understand how information travels throughout a network. The OSI reference model explains how packets travel through the various layers to another device on a network, even if the sender and destination have different types of network media. In the OSI reference model, there are seven numbered layers, each of which illustrates a particular network function. - Dividing the network into seven layers provides the following advantages: • It breaks network communication into smaller, more manageable parts. • It standardizes network components to allow multiple vendor development and support. • It allows different types of network hardware and software to communicate with each other. • It prevents changes in one layer from affecting other layers. • It divides network communication into smaller parts to make learning it easier to understand. In the foll...

Advantages and disadvantages of link-state routing

Advantages and disadvantages of link-state routing 2.1.5  This page lists the advantages and disadvantages of link-state routing protocols. The following are advantages of link-state routing protocols:  Link-state protocols use cost metrics to choose paths through the network. The cost metric reflects the capacity of the links on those paths. Link-state protocols use triggered updates and LSA floods to immediately report changes in the network topology to all routers in the network. This leads to fast convergence times. Each router has a complete and synchronized picture of the network. Therefore, it is very difficult for routing loops to occur. Routers use the latest information to make the best routing decisions. The link-state database sizes can be minimized with careful network design. This leads to smaller Dijkstra calculations and faster convergence. Every router, at the very least, maps the topology of it...

Ports for services

Ports for services 10.2.2  Services running on hosts must have a port number assigned to them so communication can occur. A remote host attempting to connect to a service expects that service to use specific transport layer protocols and ports. Some ports, which are defined in RFC 1700, are known as the well-known ports. These ports are reserved in both TCP and UDP.  These well-known ports define applications that run above the transport layer protocols. For example, a server that runs FTP will use ports 20 and 21 to forward TCP connections from clients to its FTP application. This allows the server to determine which service a client requests. TCP and UDP use port numbers to determine the correct service to which requests are forwarded. The next page will discuss ports in greater detail.