Knowledge (XXG)

Enhanced Interior Gateway Routing Protocol

Source 📝

150:
the feasible successor and the successors. Routes in the topology table are marked as "passive" or "active". Passive indicates that EIGRP has determined the path for the specific route and has finished processing. Active indicates that EIGRP is still trying to calculate the best path for the specific route. Routes in the topology table are not usable by the router until they are inserted into the routing table. The topology table is never used by the
1016:
metric is a 24-bit value while EIGRP uses a 32-bit value to express this metric. By multiplying a 24-bit value with the factor of 256 (effectively bit-shifting it 8 bits to the left), the value is extended into 32 bits, and vice versa. This way, redistributing information between EIGRP and IGRP involves simply dividing or multiplying the metric value by a factor of 256, which is done automatically.
1119:
condition. However, such neighbors do not provide the shortest path to a destination, therefore, not using them does not present any significant impairment of the network functionality. These neighbors will be re-evaluated for possible usage if the router transitions to Active state for that destination.
149:
Topology Table: The topology table stores routes that it has learned from neighbor routing tables. Unlike a routing table, the topology table does not store all routes, but only routes that have been determined by EIGRP. The topology table also records the metrics for each of the listed EIGRP routes,
1047:
The feasible successor effectively provides a backup route in the case that existing successors become unavailable. Also, when performing unequal-cost load-balancing (balancing the network traffic in inverse proportion to the cost of the routes), the feasible successors are used as next hops in the
449:
Number of routers a packet passes through when routing to a remote network, used to limit the EIGRP AS. EIGRP maintains a hop count for every route, however, the hop count is not used in metric calculation. It is only verified against a predefined maximum on an EIGRP router (by default it is set to
1004:
On Cisco routers, the interface bandwidth is a configurable static parameter expressed in kilobits per second (setting this only affects metric calculation and not actual line bandwidth). Dividing a value of 10 kbit/s (i.e. 10 Gbit/s) by the interface bandwidth statement value yields a result
1118:
It is important to realize that this condition is a sufficient, not a necessary, condition. That means that neighbors which satisfy this condition are guaranteed to be on a loop-free path to some destination, however, there may be also other neighbors on a loop-free path which do not satisfy this
1084:
when the router received replies to all queries it has sent to its neighbors. Notice that if a successor stops satisfying the feasibility condition but there is at least one feasible successor available, the router will promote a feasible successor with the lowest total distance (the distance as
1043:
A feasible successor provides a working route to the same destination, although with a higher distance. At any time, a router can send a packet to a destination marked "Passive" through any of its successors or feasible successors without alerting them in the first place, and this packet will be
1015:
uses the same basic formula for computing the overall metric, the only difference is that in IGRP, the formula does not contain the scaling factor of 256. In fact, this scaling factor was introduced as a simple means to facilitate backward compatility between EIGRP and IGRP: In IGRP, the overall
166:
and can then be used to forward traffic. If the network changes (for example, a physical link fails or is disconnected), the path will become unavailable. EIGRP is designed to detect these changes and will attempt to find a new path to the destination. The old path that is no longer available is
53:
as a proprietary protocol, available only on Cisco routers. In 2013, Cisco permitted other vendors to freely implement a limited version of EIGRP with some of its associated features such as High Availability (HA), while withholding other EIGRP features such as EIGRP stub, needed for DMVPN and
1039:
is used to denote only those routes which provide a loop-free path but which are not successors (i.e. they do not provide the least distance). From this point of view, for a reachable destination, there is always at least one successor, however, there might not be any feasible successors.
397:
Router1# show ip eigrp topology 10.0.0.1 255.255.255.255 IP-EIGRP topology entry for 10.0.0.1/32 State is Passive, Query origin flag is 1, 1 Successor(s), FD is 40640000 Routing Descriptor Blocks: 10.0.0.1 (Serial0/0/0), from 10.0.0.1, Send flag is 0x0 Composite metric is
1127:
EIGRP features load balancing on paths with different costs. A multiplier, called variance, is used to determine which paths to include into load balancing. The variance is set to 1 by default, which means load balancing on equal cost paths. The maximum variance is 128. The minimum
171:
when a change is made, but will only transmit the changes that have been made since the routing table was last updated. EIGRP does not send its routing table periodically, but will only send routing table data when an actual change has occurred. This behavior is more inline with
366:
Cisco Systems now classifies EIGRP as a distance vector routing protocol, but it is normally said to be a hybrid routing protocol. While EIGRP is an advanced routing protocol that combines many of the features of both link-state and distance-vector routing protocols, EIGRP's
1097:
The feasibility condition is a sufficient condition for loop freedom in EIGRP-routed network. It is used to select the successors and feasible successors that are guaranteed to be on a loop-free route to a destination. Its simplified formulation is strikingly simple:
1051:
By default, the total count of successors and feasible successors for a destination stored in the routing table is limited to four. This limit can be changed in the range from 1 to 6. In more recent versions of Cisco IOS (e.g. 12.4), this range is between 1 and 16.
398:(40640000/128256), Route is Internal Vector metric: Minimum bandwidth is 64 Kbit Total delay is 25000 microseconds Reliability is 255/255 Load is 197/255 Minimum MTU is 576 Hop count is 2 320:. EIGRP determines the value of the path using five metrics: bandwidth, load, delay, reliability and MTU. EIGRP uses five different messages to communicate with its neighbor routers – Hello, Update, Query, Reply, and Acknowledgement. 371:
contains many features which make it more of a distance vector routing protocol than a link-state routing protocol. Despite this, EIGRP contains many differences from most other distance-vector routing protocols, including:
1005:
that is used in the weighted formula. The interface delay is a configurable static parameter expressed in tens of microseconds. EIGRP takes this value directly without scaling into the weighted formula. However, various
1139:
protocol is unable to design the network by Unequal Path Cost Load Balancing. Regarding the Unequal Path Cost Load Balancing function on industry usage, the network design can be flexible with the traffic management.
909: 463:
By default, only total delay and minimum bandwidth are considered when EIGRP is started on a router, but an administrator can enable or disable all the K values as needed to consider the other Vector metrics.
459:
The composite routing metric calculation uses five parameters, so-called K values, K1 through K5. These act as multipliers or modifiers in the composite metric calculation. K1 is not equal to Bandwidth, etc.
793: 146:
that have a direct physical connection with this router. Routers that are connected to this router indirectly, through another router, are not recorded in this table as they are not considered neighbors.
296:
Router# configure terminal Router(config)# router eigrp 1 Router (config-router)# network 10.201.96.0 0.0.15.255 Router (config-router)# no auto-summary Router (config-router)# exit
350:(RTP) to ensure that EIGRP router updates are delivered to all neighbors completely. The Reliable Transport Protocol also contains other mechanisms to maximize efficiency and support 1456:
Albrightson, R., Garcia-Luna-Aceves, J. J., & Boyle, J. (1994, May). EIGRP a fast routing protocol based on distance vectors. In Proc. Network ID/Interop (Vol. 94, pp. 136-147).
959: 1103:
If, for a destination, a neighbor router advertises a distance that is strictly lower than our feasible distance, then this neighbor lies on a loop-free route to this destination.
1288: 1221: 1009:
commands display the interface delay in microseconds. Therefore, if given a delay value in microseconds, it must first be divided by 10 before using it in the weighted formula.
994: 1113:
If, for a destination, a neighbor router tells us that it is closer to the destination than we have ever been, then this neighbor lies on a loop-free route to this destination.
656: 346:
to identify traffic. Rather, EIGRP is designed to work on top of Layer 3 (i.e. the IP protocol). Since EIGRP does not use TCP for communication, it implements Cisco's
918:
may result. Cisco routers running EIGRP will not form an EIGRP adjacency and will complain about K-values mismatch until these values are identical on these routers.
115:
that contains rules by which traffic is forwarded in a network. If the router does not contain a valid path to the destination, the traffic is discarded. EIGRP is a
1420: 853: 826: 740: 713: 686: 1528: 1306: 450:
100 and can be changed to any value between 1 and 255). Routes having a hop count higher than the maximum will be advertised as unreachable by an EIGRP router.
154:
to forward traffic. Routes in the topology table will not be inserted into the routing table if they are active, are a feasible successor, or have a higher
183:
running EIGRP is connected to another router also running EIGRP, information is exchanged between the two routers. They form a relationship, known as an
1507: 187:. The entire routing table is exchanged between both routers at this time. After the exchange has completed, only differential changes are sent. 1529:"Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x - Configuring EIGRP [Cisco Nexus 9000 Series Switches]" 394:
EIGRP associates six different vector metrics with each route and considers only four of the vector metrics in computing the Composite metric:
1494: 1076:
and there are no feasible successors identified for that destination (i.e. no backup routes are available). The destination changes back from
1715: 1677: 1399: 858: 1085:
reported by the feasible successor plus the cost of the link to this neighbor) to a new successor and the destination will remain in the
1389: 167:
removed from the routing table. Unlike most distance vector routing protocols, EIGRP does not transmit all the data in the router's
85: 1132:
of a route is multiplied by the variance value. Each path with a metric that is smaller than the result is used in load balancing.
316:) to improve the efficiency of the protocol and to help prevent calculation errors when attempting to determine the best path to a 745: 1199: 38: 225:
Periodically checks if a route is available, and propagates routing changes to neighboring routers if any changes have occurred.
1068:. A passive state is a state when the router has identified the successor(s) for the destination. The destination changes to 89: 62:
in 2016, which did not advance to Internet Standards Track level, and allowed Cisco to retain control of the EIGRP protocol.
467:
For the purposes of comparing routes, these are combined together in a weighted formula to produce a single overall metric:
1440: 1246: 335: 327:
of 90. EIGRP routing information, that has come from an EIGRP-enabled router outside the autonomous system, has a default
1623: 1417: 74: 70: 1602: 1312: 355: 323:
EIGRP routing information, exchanged to a router from another router within the same autonomous system, has a default
173: 1643: 1362: 1335: 1160:. EIGRP was developed 20 years ago, yet it is still one of the primary Cisco routing protocols due to its purported 1152:
in an effort to assist companies whose networks operate in a multi-vendor environment. The protocol is described in
1737: 309: 203: 438: 385:
the use of diffusing computations to involve the affected part of the network into computing a new shortest path.
347: 249: 1348: 1024:
A feasible successor for a particular destination is a next hop router that is guaranteed not to be a part of a
54:
large-scale campus deployment. Information needed for implementation was published with informational status as
1732: 190:
EIGRP is often considered a hybrid protocol because it also sends link state updates when link states change.
1169: 935: 328: 324: 155: 339: 1418:
CCIE Practical Studies, Volume I | Chapter 11. Hybrid: Enhanced Interior Gateway Routing Protocol (EIGRP)
914:
Obviously, these constants must be set to the same value on all routers in an EIGRP system, or permanent
1665: 970: 120: 78: 473: 1474: 1180: 1149: 1129: 1035:
Thus, every successor is also a feasible successor. However, in most references about EIGRP the term
1261: 715:) can be set by the user to produce varying behaviors. An important and unintuitive fact is that if 317: 290: 293:
on classful boundaries, which would otherwise result in routing loops in discontiguous networks.
278: 274: 180: 151: 143: 108: 66: 1673: 1395: 1240: 313: 233: 119:
protocol by which routers automatically share route information. This eases the workload on a
96: 405:
Minimum Bandwidth (in kilobits per second) along the path from router to destination network.
222:
Sends topology changes, rather than sending the entire routing table when a route is changed.
1669: 1184: 1153: 305: 55: 42: 831: 804: 718: 691: 664: 81:, reducing the workload on the router and the amount of data that needs to be transmitted. 1444: 1424: 270: 116: 1691: 1625:
Internetworking Technology Handbook: Enhanced Interior Gateway Routing Protocol (EIGRP)
376:
the use of explicit hello packets to discover and maintain adjacencies between routers.
92: 1726: 1687: 1639: 1619: 1598: 1176: 168: 163: 131: 124: 112: 50: 1375: 1576: 1025: 915: 139: 1187:
hard to set up between different vendors' routers when the protocol is used. Even
1044:
delivered properly. Feasible successors are also recorded in the topology table.
1437: 1188: 1165: 1157: 855:
to be set to 1, and the rest to zero, effectively reducing the above formula to
421:
Delay, in 10s of microseconds, along the path from router to destination network
343: 282: 59: 277:
in this example indicates a subnetwork with a maximum of 4094 hosts—it is the
1195: 1161: 351: 245: 1495:
How Does Unequal Cost Path Load Balancing (Variance) Work in IGRP and EIGRP
1391:
Troubleshooting IP Routing Protocols (CCIE Professional Development Series)
1467:"What is 10.0.0.1 IP Address ? and How to login into 10.0.0.1 ?" 1135:
With the functionality of the Unequal Path Cost Load Balancing on EIGRP,
209:
The ability to use different authentication passwords at different times.
1148:
Cisco released details of the proprietary EIGRP routing protocol in an
229: 46: 17: 904:{\displaystyle ({\text{Bandwidth}}_{E}+{\text{Delay}}_{E})\cdot 256} 162:
Information in the topology table may be inserted into the router's
88:(IGRP) in 1993. One of the major reasons for this was the change to 1466: 216: 1136: 1012: 237: 1438:
Comparative Analysis of Link State and Hybrid Routing Protocols
1289:
Enhanced Interior Gateway Routing Protocol (EIGRP) Wide Metrics
382:
the use of a feasibility condition to select a loop-free path.
241: 212: 1262:"Why Is Cisco Bothering with "Open" EIGRP? - Packet Pushers" 1060:
A destination in the topology table can be marked either as
788:{\displaystyle {\tfrac {K_{5}}{K_{4}+{\text{Reliability}}}}} 379:
the use of a reliable protocol to transport routing updates.
1191:
for example does not support unequal cost load balancing.
49:
decisions and configuration. The protocol was designed by
1552: 1072:
state when the current successor no longer satisfies the
138:
Neighbor Table: The neighbor table keeps a record of the
269:
Example of setting up EIGRP on a Cisco IOS router for a
255:
Backwards compatibility with the IGRP routing protocols.
134:, EIGRP uses the following tables to store information: 750: 1311:, Global Knowledge Training LLC, 2013, archived from 973: 938: 861: 834: 807: 748: 721: 694: 667: 476: 429:
Number in range 1 to 255; 255 being the most reliable
354:. EIGRP uses 224.0.0.10 as its multicast address and 176:, thus EIGRP is mostly considered a hybrid protocol. 73:. Unlike other well known routing protocols, such as 1222:"Enhanced Interior Gateway Routing Protocol (EIGRP)" 69:to share routes with other routers within the same 1662:CCNA Cisco Certified Network Associate Study Guide 1198:and it seems to be generally unsupported by other 988: 953: 929:configuration values with following calculations: 903: 847: 820: 787: 734: 707: 680: 650: 1427:. InformIT (2008-06-13). Retrieved on 2014-05-30. 1301: 1299: 1297: 1048:routing table for the load-balanced destination. 637: 593: 486: 479: 1179:but they leave out several core details in the 123:who does not have to configure changes to the 413:Number in range 1 to 255; 255 being saturated 8: 1508:"Enhanced Interior Gateway Routing Protocol" 1028:. This condition is verified by testing the 441:(MTU) (never used in the metric calculation) 342:(UDP). This means that EIGRP does not use a 304:EIGRP is a distance vector & Link State 1604:Enhanced Interior Gateway Routing Protocol 1228:. Archived from the original on 2013-02-21 1073: 1029: 31:Enhanced Interior Gateway Routing Protocol 980: 975: 972: 945: 940: 937: 886: 881: 871: 866: 860: 839: 833: 812: 806: 776: 767: 756: 749: 747: 726: 720: 699: 693: 672: 666: 636: 635: 627: 618: 607: 601: 592: 591: 585: 580: 570: 555: 541: 536: 526: 519: 510: 505: 495: 485: 484: 478: 477: 475: 1144:EIGRP and compatibility to other vendors 1413: 1411: 1331: 1329: 1283: 1281: 1210: 198:EIGRP supports the following features: 1238: 1194:As of 2022 EIGRP has alpha support in 954:{\displaystyle {\text{Bandwidth}}_{E}} 368: 7: 1216: 1214: 219:authentication between two routers. 1577:"EIGRP — FRR latest documentation" 1175:Cisco has stated that EIGRP is an 989:{\displaystyle {\text{Delay}}_{E}} 390:EIGRP composite and vector metrics 25: 1338:. Cisco. Retrieved on 2014-05-30. 651:{\displaystyle {\bigg }\cdot 256} 334:EIGRP does not operate using the 86:Interior Gateway Routing Protocol 1436:Ashraf, Muhammad Irfan, et al. " 1363:What is Administrative Distance? 1123:Unequal Path Cost Load Balancing 362:Distance vector routing protocol 206:on parallel links between sites. 99:, which IGRP could not support. 39:distance-vector routing protocol 1477:from the original on 2018-03-03 1497:Cisco. Retrieved on 2017-03-24 892: 862: 1: 1696:, rfc number not yet assigned 1365:, retrieved 14 September 2013 1260:Burke, Anthony (2013-01-31). 796:is not used (i.e. taken as 1) 661:where the various constants ( 336:Transmission Control Protocol 1718:. Cisco Systems. 2005-08-10. 174:link-state routing protocols 1394:. Cisco Press. 2002-05-07. 921:EIGRP scales the interface 348:Reliable Transport Protocol 312:(DUAL) (based on work from 289:command prevents automatic 1754: 1378:. Packet Life. 2009-01-17. 1308:Cisco Training White Paper 310:diffusing update algorithm 250:protocol-dependent modules 1291:, retrieved 14 March 2014 1245:: CS1 maint: unfit URL ( 742:is set to zero, the term 439:Maximum Transmission Unit 1056:Active and passive state 158:than an equivalent path. 1716:"Introduction to EIGRP" 1693:EIGRP Information Draft 1183:definition which makes 1168:in comparison to other 329:administrative distance 325:administrative distance 156:administrative distance 1361:Cisco Systems (2013), 1349:"EIGRP Messages Types" 1287:Cisco Systems (2012), 990: 955: 905: 849: 822: 789: 736: 709: 682: 652: 340:User Datagram Protocol 1666:Indianapolis, Indiana 1660:Lammle, Todd (2007), 1645:Introduction to EIGRP 1471:10.0.0.0.1 Consortium 1336:Introduction to EIGRP 1093:Feasibility condition 1074:feasibility condition 1030:feasibility condition 991: 956: 906: 850: 848:{\displaystyle K_{3}} 823: 821:{\displaystyle K_{1}} 790: 737: 735:{\displaystyle K_{5}} 710: 708:{\displaystyle K_{5}} 683: 681:{\displaystyle K_{1}} 653: 248:, through the use of 121:network administrator 971: 961:= 10 / Value of the 936: 859: 832: 805: 746: 719: 692: 665: 474: 1648:, Document ID 13669 1607:, Document ID 16406 1108:or in other words, 801:The default is for 291:route summarization 285:255.255.240.0. The 130:In addition to the 84:EIGRP replaced the 79:incremental updates 77:, EIGRP only sends 65:EIGRP is used on a 1664:(Sixth ed.), 1581:docs.frrouting.org 1443:2013-11-09 at the 1423:2014-04-26 at the 1315:on 15 October 2013 1037:feasible successor 1020:Feasible successor 986: 951: 901: 845: 818: 785: 783: 732: 705: 678: 648: 279:bitwise complement 41:that is used on a 1738:Routing protocols 1679:978-0-470-11008-9 1401:978-0-13-303467-7 1266:packetpushers.net 1000:interface command 978: 965:interface command 943: 884: 869: 782: 779: 633: 630: 583: 561: 558: 539: 508: 314:SRI International 300:Technical details 273:. The 0.0.15.255 265:Cisco IOS example 234:Internet Protocol 97:Internet Protocol 71:autonomous system 37:) is an advanced 27:Internet protocol 16:(Redirected from 1745: 1719: 1703: 1702: 1701: 1682: 1670:Wiley Publishing 1655: 1654: 1653: 1634: 1633: 1632: 1614: 1613: 1612: 1591: 1590: 1588: 1587: 1573: 1567: 1566: 1564: 1563: 1549: 1543: 1542: 1540: 1539: 1525: 1519: 1518: 1516: 1515: 1504: 1498: 1492: 1486: 1485: 1483: 1482: 1463: 1457: 1454: 1448: 1434: 1428: 1415: 1406: 1405: 1386: 1380: 1379: 1372: 1366: 1359: 1353: 1352: 1345: 1339: 1333: 1324: 1323: 1322: 1320: 1303: 1292: 1285: 1276: 1275: 1273: 1272: 1257: 1251: 1250: 1244: 1236: 1234: 1233: 1218: 1200:routing software 1185:interoperability 995: 993: 992: 987: 985: 984: 979: 976: 960: 958: 957: 952: 950: 949: 944: 941: 910: 908: 907: 902: 891: 890: 885: 882: 876: 875: 870: 867: 854: 852: 851: 846: 844: 843: 827: 825: 824: 819: 817: 816: 794: 792: 791: 786: 784: 781: 780: 777: 772: 771: 761: 760: 751: 741: 739: 738: 733: 731: 730: 714: 712: 711: 706: 704: 703: 687: 685: 684: 679: 677: 676: 657: 655: 654: 649: 641: 640: 634: 632: 631: 628: 623: 622: 612: 611: 602: 597: 596: 590: 589: 584: 581: 575: 574: 562: 560: 559: 556: 547: 546: 545: 540: 537: 531: 530: 520: 515: 514: 509: 506: 500: 499: 490: 489: 483: 482: 306:routing protocol 43:computer network 21: 1753: 1752: 1748: 1747: 1746: 1744: 1743: 1742: 1733:Cisco protocols 1723: 1722: 1714: 1711: 1699: 1697: 1686: 1680: 1659: 1651: 1649: 1638: 1630: 1628: 1618: 1610: 1608: 1597: 1594: 1585: 1583: 1575: 1574: 1570: 1561: 1559: 1551: 1550: 1546: 1537: 1535: 1527: 1526: 1522: 1513: 1511: 1506: 1505: 1501: 1493: 1489: 1480: 1478: 1465: 1464: 1460: 1455: 1451: 1445:Wayback Machine 1435: 1431: 1425:Wayback Machine 1416: 1409: 1402: 1388: 1387: 1383: 1374: 1373: 1369: 1360: 1356: 1347: 1346: 1342: 1334: 1327: 1318: 1316: 1305: 1304: 1295: 1286: 1279: 1270: 1268: 1259: 1258: 1254: 1237: 1231: 1229: 1220: 1219: 1212: 1208: 1146: 1125: 1095: 1058: 1022: 996:= Value of the 974: 969: 968: 939: 934: 933: 880: 865: 857: 856: 835: 830: 829: 808: 803: 802: 763: 762: 752: 744: 743: 722: 717: 716: 695: 690: 689: 668: 663: 662: 614: 613: 603: 579: 566: 548: 535: 522: 521: 504: 491: 472: 471: 457: 399: 392: 364: 356:protocol number 302: 297: 287:no auto-summary 271:private network 267: 262: 196: 117:dynamic routing 105: 45:for automating 28: 23: 22: 15: 12: 11: 5: 1751: 1749: 1741: 1740: 1735: 1725: 1724: 1721: 1720: 1710: 1709:External links 1707: 1706: 1705: 1690:(2013-02-18), 1684: 1678: 1657: 1642:(2005-08-10), 1636: 1616: 1601:(2005-09-09), 1593: 1592: 1568: 1544: 1520: 1499: 1487: 1473:. 2018-03-02. 1458: 1449: 1429: 1407: 1400: 1381: 1376:"RTP in EIGRP" 1367: 1354: 1340: 1325: 1293: 1277: 1252: 1209: 1207: 1204: 1145: 1142: 1124: 1121: 1116: 1115: 1106: 1105: 1094: 1091: 1057: 1054: 1021: 1018: 1002: 1001: 983: 966: 948: 900: 897: 894: 889: 879: 874: 864: 842: 838: 815: 811: 775: 770: 766: 759: 755: 729: 725: 702: 698: 675: 671: 659: 658: 647: 644: 639: 626: 621: 617: 610: 606: 600: 595: 588: 578: 573: 569: 565: 554: 551: 544: 534: 529: 525: 518: 513: 503: 498: 494: 488: 481: 456: 455:Routing metric 453: 452: 451: 447: 443: 442: 435: 431: 430: 427: 423: 422: 419: 415: 414: 411: 407: 406: 403: 396: 391: 388: 387: 386: 383: 380: 377: 369:DUAL algorithm 363: 360: 318:remote network 308:that uses the 301: 298: 295: 266: 263: 261: 258: 257: 256: 253: 232:processes for 228:Runs separate 226: 223: 220: 210: 207: 204:load balancing 195: 192: 160: 159: 147: 104: 101: 93:IPv4 addresses 26: 24: 14: 13: 10: 9: 6: 4: 3: 2: 1750: 1739: 1736: 1734: 1731: 1730: 1728: 1717: 1713: 1712: 1708: 1695: 1694: 1689: 1688:Cisco Systems 1685: 1681: 1675: 1671: 1667: 1663: 1658: 1647: 1646: 1641: 1640:Cisco Systems 1637: 1627: 1626: 1621: 1620:Cisco Systems 1617: 1606: 1605: 1600: 1599:Cisco Systems 1596: 1595: 1582: 1578: 1572: 1569: 1558: 1557:frrouting.org 1554: 1548: 1545: 1534: 1530: 1524: 1521: 1509: 1503: 1500: 1496: 1491: 1488: 1476: 1472: 1468: 1462: 1459: 1453: 1450: 1446: 1442: 1439: 1433: 1430: 1426: 1422: 1419: 1414: 1412: 1408: 1403: 1397: 1393: 1392: 1385: 1382: 1377: 1371: 1368: 1364: 1358: 1355: 1350: 1344: 1341: 1337: 1332: 1330: 1326: 1314: 1310: 1309: 1302: 1300: 1298: 1294: 1290: 1284: 1282: 1278: 1267: 1263: 1256: 1253: 1248: 1242: 1227: 1223: 1217: 1215: 1211: 1205: 1203: 1201: 1197: 1192: 1190: 1186: 1182: 1178: 1177:open standard 1173: 1171: 1167: 1163: 1159: 1155: 1151: 1143: 1141: 1138: 1133: 1131: 1122: 1120: 1114: 1111: 1110: 1109: 1104: 1101: 1100: 1099: 1092: 1090: 1088: 1083: 1079: 1075: 1071: 1067: 1063: 1055: 1053: 1049: 1045: 1041: 1038: 1033: 1031: 1027: 1019: 1017: 1014: 1010: 1008: 999: 981: 967: 964: 946: 932: 931: 930: 928: 924: 919: 917: 916:routing loops 912: 898: 895: 887: 877: 872: 840: 836: 813: 809: 799: 797: 773: 768: 764: 757: 753: 727: 723: 700: 696: 673: 669: 645: 642: 624: 619: 615: 608: 604: 598: 586: 576: 571: 567: 563: 552: 549: 542: 532: 527: 523: 516: 511: 501: 496: 492: 470: 469: 468: 465: 461: 454: 448: 445: 444: 440: 437:Minimum path 436: 433: 432: 428: 425: 424: 420: 417: 416: 412: 409: 408: 404: 401: 400: 395: 389: 384: 381: 378: 375: 374: 373: 370: 361: 359: 357: 353: 349: 345: 341: 338:(TCP) or the 337: 332: 330: 326: 321: 319: 315: 311: 307: 299: 294: 292: 288: 284: 280: 276: 272: 264: 260:Configuration 259: 254: 251: 247: 243: 239: 235: 231: 227: 224: 221: 218: 214: 211: 208: 205: 201: 200: 199: 193: 191: 188: 186: 182: 177: 175: 170: 169:routing table 165: 164:routing table 157: 153: 148: 145: 141: 137: 136: 135: 133: 132:routing table 128: 126: 125:routing table 122: 118: 114: 113:routing table 110: 102: 100: 98: 94: 91: 87: 82: 80: 76: 72: 68: 63: 61: 57: 52: 51:Cisco Systems 48: 44: 40: 36: 32: 19: 1698:, retrieved 1692: 1661: 1650:, retrieved 1644: 1629:, retrieved 1624: 1609:, retrieved 1603: 1584:. Retrieved 1580: 1571: 1560:. Retrieved 1556: 1547: 1536:. Retrieved 1532: 1523: 1512:. Retrieved 1502: 1490: 1479:. Retrieved 1470: 1461: 1452: 1432: 1390: 1384: 1370: 1357: 1343: 1319:17 September 1317:, retrieved 1313:the original 1307: 1269:. Retrieved 1265: 1255: 1230:. Retrieved 1225: 1193: 1174: 1147: 1134: 1126: 1117: 1112: 1107: 1102: 1096: 1086: 1081: 1077: 1069: 1065: 1061: 1059: 1050: 1046: 1042: 1036: 1034: 1026:routing loop 1023: 1011: 1006: 1003: 997: 962: 926: 922: 920: 913: 800: 795: 660: 466: 462: 458: 393: 365: 352:multicasting 333: 322: 303: 286: 268: 202:Support for 197: 189: 184: 178: 161: 140:IP addresses 129: 106: 83: 64: 34: 30: 29: 1553:"FRRouting" 1189:Cisco NX-OS 1166:scalability 778:Reliability 629:Reliability 426:Reliability 418:Total Delay 344:port number 283:subnet mask 107:Almost all 1727:Categories 1700:2013-02-18 1652:2024-01-22 1631:2008-04-27 1611:2008-04-27 1586:2022-09-02 1562:2022-09-02 1538:2022-09-02 1514:2017-09-02 1481:2018-03-03 1271:2022-09-02 1232:2022-09-02 1206:References 127:manually. 111:contain a 1196:FRRouting 1170:protocols 1162:usability 963:bandwidth 942:Bandwidth 923:Bandwidth 896:⋅ 868:Bandwidth 643:⋅ 599:⋅ 577:⋅ 553:− 538:Bandwidth 533:⋅ 507:Bandwidth 502:⋅ 446:Hop Count 402:Bandwidth 246:AppleTalk 185:adjacency 90:classless 1622:(n.d.), 1475:Archived 1441:Archived 1421:Archived 1241:cite web 688:through 331:of 170. 275:wildcard 194:Features 103:Overview 1510:. CISCO 1089:state. 1087:passive 1082:passive 1062:passive 281:of the 252:(PDMs). 230:routing 179:When a 144:routers 109:routers 95:in the 47:routing 1676:  1398:  1156:  1130:metric 1078:active 1070:active 1066:active 236:(IP), 181:router 152:router 67:router 58:  1533:Cisco 1226:Cisco 998:delay 977:Delay 927:Delay 883:Delay 582:Delay 217:SHA-2 35:EIGRP 18:EIGRP 1674:ISBN 1396:ISBN 1321:2013 1247:link 1164:and 1158:7868 1137:OSPF 1013:IGRP 1007:show 925:and 828:and 557:Load 410:Load 358:88. 244:and 238:IPv6 215:and 60:7868 1181:RFC 1154:RFC 1150:RFC 1080:to 1064:or 899:256 646:256 550:256 434:MTU 242:IPX 213:MD5 142:of 75:RIP 56:RFC 1729:: 1672:, 1668:: 1579:. 1555:. 1531:. 1469:. 1410:^ 1328:^ 1296:^ 1280:^ 1264:. 1243:}} 1239:{{ 1224:. 1213:^ 1202:. 1172:. 1032:. 911:. 798:. 240:, 1704:. 1683:. 1656:. 1635:. 1615:. 1589:. 1565:. 1541:. 1517:. 1484:. 1447:" 1404:. 1351:. 1274:. 1249:) 1235:. 982:E 947:E 893:) 888:E 878:+ 873:E 863:( 841:3 837:K 814:1 810:K 774:+ 769:4 765:K 758:5 754:K 728:5 724:K 701:5 697:K 674:1 670:K 638:] 625:+ 620:4 616:K 609:5 605:K 594:) 587:E 572:3 568:K 564:+ 543:E 528:2 524:K 517:+ 512:E 497:1 493:K 487:( 480:[ 33:( 20:)

Index

EIGRP
distance-vector routing protocol
computer network
routing
Cisco Systems
RFC
7868
router
autonomous system
RIP
incremental updates
Interior Gateway Routing Protocol
classless
IPv4 addresses
Internet Protocol
routers
routing table
dynamic routing
network administrator
routing table
routing table
IP addresses
routers
router
administrative distance
routing table
routing table
link-state routing protocols
router
load balancing

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.