Configuring IGRP in a Network

IGRP is similar to RIP in its general operation. One of the principal differences is that IGRP can maintain multiple routes for each destination and can do load balancing between the routes based on dynamic metrics.

Attributes for configuring IGRP are grouped together under the IGRP Parameters compound attribute. All of the attributes described in the rest of this section are sub-attributes of IGRP Parameters. Most IGRP attributes can be left in their default values; however, you may wish to perform some of the following steps to configure IGRP for your network model:

  1. Ensure that IGRP is one of the routing protocols specified for all appropriate interfaces in your routers’ IP > IP Routing Parameters > Interface Information > Routing Protocols attribute. See the Chapter 14 “IP” on page 1 for instructions on how to do this.
  2. Configure the timers associated with IGRP using the “Timers” compound attribute. The “Timers” table consists of an Update Interval timer to control the frequency (secs) of IGRP updates sent by the router. If desired, you may change the standard timer settings that control route aging. In IGRP, both routes and destinations can become stale and then removed from the routing table. Routes are aged out and removed from the routing table when the “Timeout Value” timer expires. When a destination has no more routes, the “Flush Value” timer is set. After this timer expires, the destination’s entry in the routing table goes into a “hold down” mode for a duration equal to the value of the “Holddown Value” timer. During this period, new updates are ignored to prevent old information from undoing the destination removal. After this period, the destination is removed.
  3. Configure the IGRP activity period. For the purposes of simulation, you may or may not want IGRP to be active throughout the period you are studying. If IGRP traffic overhead and/or IGRP behavior is of interest, you should allow IGRP to remain active. However, if these issues are not key to your simulation project, you can save simulation time by shutting down IGRP activity once stable routes have been established. IGRP activity should not start too early in the network simulation because other critical network functions must be established to transport IGRP packets. Namely, layer 2 functionality of the Spanning Tree Bridge protocol must converge on a stable logical topology before IGRP packets are sent. Otherwise, IGRP will not successfully transmit its initial routing updates and routing will not be possible until at least one “Update Interval” later (typically 30 seconds). Use the Start Time and Stop Time attributes to control the duration of this period. However, it is not recommended to have the Start Time set to less than the default of 5 seconds.
  4. Configure IGRP’s multipath capability. IGRP can store multiple routes for each destination. To control how many routes are stored, a certain “variance” in route cost is tolerated. This is controlled via the “Variance” attribute of each router. Normally, this value is set to 1.0, meaning that only paths of equal cost are considered. In other words, the best path and any paths of equal cost to it are maintained and second-best paths are deleted. This is the recommended setting, providing “equal-cost multipath” capability; however, if you want to change it, consult your commercial IGRP documentation for a complete discussion of its behavior.