debug ip igrp transactions
debug ip igrp transactions [ip-address]no debug ip igrp transactions [ip-address]
ip-address (Optional) The IP address of an IGRP neighbor.
To display transaction information on Interior Gateway Routing Protocol (IGRP) routing transactions,
use the debug ip igrp transactions privileged EXEC command. The no form of this command disables
If the IP address of an IGRP neighbor is specified, the resulting debug ip igrp transactions output
includes messages describing updates from that neighbor and updates that the router broadcasts toward
When many networks are in your routing table, the debug ip igrp transactions command can flood the
console and make the router unusable. In this case, use the debug ip igrp events command instead to
display summary routing information.
The following is sample output from the debug ip igrp transactions command:
Router# debug ip igrp transactions
IGRP: received update from 126.96.36.199 on Ethernet
subnet 188.8.131.52, metric 1300 (neighbor 1200)
subnet 184.108.40.206, metric 8676 (neighbor 8576)
subnet 220.127.116.11, metric 1200 (neighbor 1100)
subnet 18.104.22.168, metric 1300 (neighbor 1200)
subnet 22.214.171.124, metric 8676 (neighbor 8576)
network 126.96.36.199, metric 158550 (neighbor 158450)
network 188.8.131.52, metric 1115511 (neighbor 1115411)
network 184.108.40.206, metric 16777215 (inaccessible)
exterior network 220.127.116.11, metric 9676 (neighbor 9576)
exterior network 18.104.22.168, metric 9676 (neighbor 9576)
IGRP: received update from 22.214.171.124 on Ethernet
subnet 126.96.36.199, metric 180671 (neighbor 180571)
subnet 188.8.131.52, metric 1200 (neighbor 1100)
subnet 184.108.40.206, metric 16777215 (inaccessible)
IGRP: sending update to 255.255.255.255 via Ethernet0 (220.127.116.11)
subnet 18.104.22.168, metric=847
IGRP: sending update to 255.255.255.255 via Serial1 (22.214.171.124)
subnet 126.96.36.199, metric=16777215
subnet 188.8.131.52, metric=1100
The output shows that the router being debugged has received updates from two other routers on the
network. The router at source address 184.108.40.206 sent information about ten destinations in the
update; the router at source address 220.127.116.11 sent information about three destinations in its update.
The router being debugged also sent updates�in both cases to the broadcast address 255.255.255.255
as the destination address.
On the second line the first field refers to the type of destination information: "subnet" (interior),
"network" (system), or "exterior" (exterior). The second field is the Internet address of the destination
network. The third field is the metric stored in the routing table and the metric advertised by the neighbor
sending the information. "Metric... inaccessible" usually means that the neighbor router has put the
destination in a hold down state.
The entries show that the router is sending updates that are similar, except that the numbers in
parentheses are the source addresses used in the IP header. A metric of 16777215 is inaccessible.
Other examples of output that the debug ip igrp transactions command can produce follow.
The following entry indicates that the routing table was updated and shows the new edition number (97
in this case) to be used in the next IGRP update:
IGRP: edition is now 97
Entries such as the following occur on startup or when some event occurs such as an interface making a
transition or a user manually clearing the routing table:
IGRP: broadcasting request on Ethernet0
IGRP: broadcasting request on Ethernet1
The following type of entry can result when routing updates become corrupted between sending and
IGRP: bad checksum from 18.104.22.168
An entry such as the following should never appear. If it does, the receiving router has a bug in the
software or a problem with the hardware. In either case, contact your technical support representative.
IGRP: system 45 from 22.214.171.124, should be system 109
� Cisco Systems, Inc. 2001, 2002, 2003
World Wide Education
|Converted from CHM to HTML with chm2web Pro 2.85 (unicode)|