cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1419
Views
0
Helpful
4
Replies

EIGRP Wide-metric support

fsebera
Level 4
Level 4

It appears EIGRP only sends the classic-scale-metrics while operating in non-named configuration mode (E.G. router eigrp # ) AND Always sends the wide-metric format while operating in Named Configuration mode (E.G. router eigrp ROCKS) regardless of the 15.2 IOS version.

When my router is running in Named config mode, sh eigrp protocols reveals K6=0,

when I remove the Named config and use the legacy router eigrp # config mode, the same sh eigrp protocols does not list the K6=0 value (only K1 - K5).

The reason I ask is the Cisco white paper (EIGRP Wide Metrics) dated Nov 2012, states if a legacy EIGRP peer is interfacing with a new EIGRP peer, the new EIGRP peer will send both formats. - Is this doc outdated by a newer doc?

Thanks

Frank

4 Replies 4

fsebera
Level 4
Level 4

Oops, here is the Cisco White Paper I referred in my original post.

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6554/ps6599/ps6630/whitepaper_C11-720525.html

Thanks

Frank

fsebera
Level 4
Level 4

Update- The original title should be referred to as EIGRP Virtual-Instance (that does support the legacy 32-bit metric and just might also support the 64-bit wide metrics; depending on your configuration).

Viewing the show command (Show command 1) based on EXAMPLE CONFIG 1 below, it's clear the K6 value is not used; only the K1 - K5 values.

If address-family vrf was implemented, as shown in EXAMPLE 2, it's clear the new wide-metric is in effect.

The question still remains, how does an EIGRP peer configured to recognize link speeds greater than 10Gbps interact with EIGRP peers that are not operating in 64-bit mode? What do the configurations look like for each of the peers?

ANYONE know?

Thanks

Frank

EXAMPLE CONFIG 1:

router eigrp TEN-GIG

!

address-family ipv4 unicast autonomous-system 200

  !

  topology base

  exit-af-topology

  network 192.168.1.1 0.0.0.255

exit-address-family

!

service-family ipv4 autonomous-system 200

  !

  sf-interface GigabitEthernet0/1

   authentication mode md5

   authentication key-chain MD5-PASS

  exit-sf-interface

  !

  topology base

  exit-sf-topology

exit-service-family

SHOW COMMAND 1:

R40#sh eigrp protocols
EIGRP-IPv4 VR(TEN-GIG) Address-Family Protocol for AS(200)
  Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
  NSF-aware route hold timer is 240
  Router-ID: 10.74.10.5
  Topology : 0 (base)
    Active Timer: 3 min
    Distance: internal 90 external 170
    Maximum path: 4
    Maximum hopcount 100
    Maximum metric variance 1
    Total Prefix Count: 6
    Total Redist Count: 0

EIGRP-SFv4 VR(TEN-GIG) Service-Family Protocol for AS(200)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
  NSF-aware route hold timer is 240
  Router-ID: 10.74.10.5
  Topology : 0 (base)
    Active Timer: 3 min
    Distance: internal 90 external 170
    Maximum path: 1
    Maximum hopcount 100
    Maximum metric variance 1
    Total Prefix Count: 0
    Total Redist Count: 0

      

EXAMPLE 2:

R-64-bit#sh ip eigrp vrf DMZ topology 192.168.1.0 255.255.255.0

EIGRP-IPv4 VR(DMZ) Topology Entry for AS(200)/ID(10.74.10.5)

Topology(base) TID(0) VRF(DMZ)

EIGRP-IPv4(200): Topology base(0) entry for 192.168.1.0/24

  State is Passive, Query origin flag is 1, 1 Successor(s), FD is 1310720, RIB is 10240

  Descriptor Blocks:

  192.168.1.1 (GigabitEthernet0/1), from 192.168.1.2, Send flag is 0x0

      Composite metric is (1310720/65536), route is Internal

      Vector metric:

        Minimum bandwidth is 1000000 Kbit

        Total delay is 10000000 picoseconds

        Reliability is 0/255

        Load is 1/255

        Minimum MTU is 1500

        Hop count is 1

Finally figured it out!!!

R39#sh eigrp protocols

EIGRP-IPv4 VR(wide) Address-Family Protocol for AS(200)

  Metric weight K1=1, K2=0, K3=1, K4=0, K5=0 K6=0

  Metric rib-scale 128

  Metric version 64bit

  NSF-aware route hold timer is 240

  Router-ID: --snip--

  Topology : 0 (base)

    Active Timer: 3 min

    Distance: internal 90 external 170

    Maximum path: 4

    Maximum hopcount 100

    Maximum metric variance 1

    Total Prefix Count: 14

    Total Redist Count: 0

With the introduction of wide metrics, the TLV packets were updated to carry additional information.  EIGRP was modified to send both the older packet formats and the newer ones in a mixed network. Sending twice the data will impact link utilization and performance.

Review Cisco Networking products for a $25 gift card