IGRP stability features

IGRP stability features

7.3.4 This page will describe three features that are designed to enhance the stability of IGRP:

• Holddowns

• Split horizons

• Poison reverse updates

Holddowns

Holddowns are used to prevent regular update messages from reinstating a route that may not be up. When a router goes down, neighbor routers detect this from the lack of regularly scheduled update messages.

Split horizons

Split horizons are derived from the premise that it is not useful to send information about a route back in the direction from which it came. The split horizon rule helps prevent routing loops between adjacent routers.

Poison reverse updates

Poison reverse updates are used to prevent larger routing loops. Increases in routing metrics usually indicate routing loops. Poison reverse updates then are sent to remove the route and place it in holddown. With IGRP, poison reverse updates are sent only if a route metric has increased by a factor of 1.1 or greater.

IGRP also maintains many timers and variables that contain time intervals. These include an update timer, an invalid timer, a holddown timer, and a flush timer.

The update timer specifies how frequently routing update messages should be sent. The IGRP default for this variable is 90 seconds.

The invalid timer specifies how long a router should wait in the absence of routing-update messages about a route before it declares that route invalid. The IGRP default for this variable is three times the update period.

The holddown timer specifies the amount of time for which information about poorer routes is ignored. The IGRP default for this variable is three times the update timer period plus 10 seconds.

Finally, the flush timer indicates how much time should pass before a route is flushed from the routing table. The IGRP default is seven times the routing update timer.

IGRP lacks support for VLSM. Cisco has created Enhanced IGRP to correct this problem.

The next page will show students how to configure IGRP.

Comments

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.

CCNA :) Be a Good Network Administrator

Search This Blog