Eigrp Summary
Eigrp Summary
Eigrp Summary
EIGRP Summary
The characteristics of EIGRP follow:
Have the power to shut the Auto-summarization And make a configured manual
Summarization.
You can factor load, MTU and reliability into the metric.
Sends route updates to multicast address 224.0.0.10, and nei. Reply’s back with
Unicast Address.
Send Hello packets every 5 sec. and Hold down timer is 15 sec.
For Low speed Hello is every 60 sec. with hold down time 180 sec.
Administrative distance is 90 for EIGRP internal routes, 170 for EIGRP external
routes, and 5 for EIGRP summary routes.
Potential routing protocol for the core of a network; used in large networks.
For neighbor relation to be established, both routers must send and receive Hello
or Ack packets from each other, they must have the same AS #, and the same
Metric K values.
Eigrp doesn’t restrict that neighbors must have the same Hello & dead interval
timers, Unlike OSPF.
Has a Maximum hop count of 255, the default is 100 in the last IOS releases.
Given the default values for k1 through k5, the composite metric calculation used by
IGRP reduces to the default metric:
BWIGRP(min) = 107/BW(min)
Requests were a type of packet originally intended for use in route servers. This application was
never implemented, and request packets are noted here only because they are mentioned in some
older EIGRP documentation.
Protocol-Dependent Modules (PDM): EIGRP implements modules for IP, IPX, and AppleTalk,
which are responsible for the protocol-specific routing tasks. For example, the IPX EIGRP module is
responsible for exchanging route information about IPX networks with other IPX EIGRP processes and for
passing the information to the DUAL. Additionally, the IPX module will send and receive SAP
information.
Reliable Transport Protocol (RTP): The Reliable Transport Protocol (RTP) manages the delivery
and reception of EIGRP packets. Reliable delivery means that delivery is guaranteed and that packets will
be delivered in order. If any packet is reliably multicast and an ACK is not received from a neighbor, the
packet will be retransmitted as a unicast to that unresponding neighbor. If an ACK is not received after 16
of these unicast retransmissions, the neighbor will be declared dead. The time to wait for an ACK before
switching from multicast to unicast is specified by the multicast flow timer. The time between the
subsequent unicasts is specified by the retransmission timeout (RTO). Both the multicast flow timer and
the RTO are calculated for each neighbor from the smooth round-trip time (SRTT). The SRTT is the
average elapsed time, measured in milliseconds, between the transmission of a packet to the neighbor and
the receipt of an acknowledgment. The formulas for calculating the exact values of the SRTT, the RTO,
and the multicast flow timer are proprietary.
Neighbor Discovery/Recovery: Hellos are multicast every 5 sec., minus a small random time to
prevent synchronization. & are unicast every 60 sec. On multipoint X.25, Frame Relay, and ATM
interfaces, with access link speeds of T1 or slower also it's the default for ATM SVCs and for ISDN PRI In
all cases, the Hellos are unacknowledged.
Diffusing Update Algorithm (DUAL): Used For routing calculations, loop free & convergence.
EIGRP Configuration
conf-router)#passive-interface <interface>
The router may be configured to use more than one "key chain." & also different keys at different
times (key management).
Auth must be done in a fixed order rather than this you may have problems, The steps for setting
up EIGRP authentication follow:
The password that is accepted from other routers and the password that is used with transmitted/sent
messages are managed separately. Both the accept-lifetime and the send-lifetime cmd. must have a
specified start time and may have either a specified duration or end time or the keyword infinite. The key
numbers are examined from the lowest to the highest, and the first valid key is used.
For RIP key ID & its password isn't important to match, they will work.
BUT for EIGRP key # must match.
Show Commands
# sh ip route
# sh ip route eigrp
# sh ip route < Net ID >
# sh ip protocols
# sh ip eigrp traffic
# sh ip eigrp traffic <AS#>
# sh ip eigrp nei
# sh ip eigrp topology
#debug ip eigrp
#debug ip eigrp fsm
#debug ip eigrp nei (Shows the hello packets sent and received to the neighbors)
#debug ip eigrp route (Shows dynamic changes made on the routing table process)
#debug ip eigrp summary (Shows a summary of the EIGRP activity)
#debug ip eigrp packet (Shows the packets sent and received by the router.
The packet types to be monitored can be selected.
Up to 11 types are available)
# no debug all / u all
'I can accept failure. Everyone fails at something.,But I can't accept not trying.'
' Every class i teach , i learn something new myself '
http://twitter.com/aelhoussiny
www.linkedin.com/in/aelhoussiny