Model Features: IGRP
The following features are implemented.
- The IGRP routing tables maintained at each node are initialized with the local gateway’s IP addresses. The cost for these routes is set to 0. The cost computation for routes learned from neighboring routers is performed using topological delay, bandwidth of the narrowest bandwidth segment, channel occupancy of the route, and the route reliability.
- Equal-cost multi-path support: In many cases it makes sense to split traffic between two or more paths. IGRP will do this whenever two or more paths are equally good.
- A modified Bellman-Ford algorithm (as documented in the reference above) is used during route computation.
- The start time at which the first regular routing update is generated is a parameter that you can control on a per-node basis.
- Triggered updates (that is, a new routing table) are sent every time a change is detected in the routing tables. Normally, new routing tables are sent to neighboring gateways on a regular basis (every 90 seconds by default; this can be adjusted using a model attribute).
- Holddown timer is implemented to avoid the problems due to potential latency in route propagation through the entire network. The holddown rule indicates that when a route is removed, no new route will be accepted for the same destination for some period of time. This holddown period ensures that triggered updates are delivered to all other gateways, so that any new routes received are indeed new, not an old route being re-inserted by a gateway that has not received the triggered update.
- Split horizon with route poisoning is implemented to avoid routing loops. Split horizon should prevent loops between adjacent gateways. Route poisoning is intended to break larger loops. The rule is that, when an update shows the metric for an existing route to have increased sufficiently, there is a loop. The route should be removed and put into holddown.
- IGRP simulation efficiency. With this technique (enabled by default), routing update messages are not sent after a certain point in time, resulting in faster simulation execution. If you know that routing information will not change after a certain point, enter that time as the IGRP Stop Time.
- Message priority. You can set the priority of IGRP messages exchanged in the entire network by specifying the DSCP marking of the messages using the corresponding global attribute. The default value is CS6.
It is intended that only nodes that are gateways (those that have more than one network interface) implement IGRP. Therefore the IGRP routing tables are only used to route packets between gateways. This is important in order to reduce unnecessary simulation events and therefore improve simulation efficiency.
The IGRP route metric computation requires particular units for the bandwidth and delay components. These values are specified for each media type in a common external file (igrp_metric_compute_support.gdf):
Figure 169: Units for Bandwidth and Delay Components
# This file contains default values used for different media types for
# computing advertised route metrics. Most of the default values have been
# chosen from “An Introduction by IGRP” by Charles R. Hendrick.
#
# You might want to add more entries if you are modeling data rates that are not
# defined in this file. If a new entry is not added, the next-lowest data
# rate will be assumed for computing metric components.
# ATM:
622000000, 30
155000000, 40
# Ethernet:
1000000000, 20
100000000, 50
10000000, 100
#PPP:
1544000 2000
#FDDI:
100000000, 50
# Token Ring:
16000000, 90
4000000, 200