CCIE Memo

Sunday, 4 November 2012

EIGRP Interface Load (K2)

EIGRP routing updates are triggered only by a change in network topology (interface up/down event, IP addressing change or configured bandwidth/delay change) and not by change in interface load or reliability. The load/reliability numbers are thus a snapshot taken at the moment of the topology change and should be ignored.

http://blog.ioshints.info/2009/06/eigrp-load-and-reliability-metrics.html
Posted by Ali at 9:36 pm
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Labels: EIGRP, Metric, Routing

No comments:

Post a Comment

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)

Blog Archive

  • ►  2013 (23)
    • ►  October (1)
    • ►  July (1)
    • ►  June (1)
    • ►  May (2)
    • ►  March (7)
    • ►  February (10)
    • ►  January (1)
  • ▼  2012 (65)
    • ►  December (25)
    • ▼  November (15)
      • IPv6 Redistribute with include-connected
      • Differences between OSPFv3 and OSPFv2
      • IPv6 and IPv4 QoS Differences
      • Differences between EIGRP for IPv4 and IPv6
      • IPv6 Neighbour Discovery Lifetime
      • Best Practice Recommendations for the Catalyst 650...
      • Etherchannel Mode On and Spanning Tree Loop
      • When RSTP flushes CAM table?
      • BPDU Guard
      • MST Configuration
      • Difference between VTP versions
      • Loop Guard
      • EIGRP Interface Load (K2)
      • EIGRP routing over DMVPN (mGRE)
      • EIGRP traffic-share min
    • ►  October (16)
    • ►  August (5)
    • ►  July (4)

About Me

Ali
View my complete profile
Awesome Inc. theme. Powered by Blogger.