cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1439
Views
6
Helpful
15
Replies

EIGRP 64bit metrics on IOS-XE not behaving with SVI

nick-rock-city
Level 1
Level 1

Can anyone get SVI's to behave when using 64bit EIGRP metrics?  I see this behavior on IOS-XE 16.9.5 and 17.9.5

What I mean by this is, if you have a L2 port-channel, with 2 x 40g members this will "lose" in EIGRP delay calculation to a single routed 10g port. 

 

Setting the minimum delay (1) , or a max bandwidth the platform supports (in my case 200 Gigs) does not lower the picosecond delay below that of a 1 g link when looking at the topology table.

 

the show interface | include DLY command, shows the DLY that would be used in a 32bit EIGRP calculation, so is not helpful.

 

When using a L3 port-channel - With an IP address on the interface, the picosecond delay is calculated correctly.

Does anyone know

(1) of a way to manually set picosecond delay ?

(2) a show command that shows the 64bit picosecond delay of interfaces (outside of figuring it out from the topology table)

 

Thanks,

Nick

15 Replies 15

Thank you for the reply - this would work fine in the IDF situation, what is not shown in my diagram for simplicities sake is the many international links, with more than one hop that route via the Atlantic in some cases, not via the 9 foot fiber in the same room.  I also do not want to confuse anyone with recursive next hops (which sometimes are still not the opposite core) - at least in EIGRP.  

 

I think the bigger issue here is Cisco gives us the tools we need to make Wide metric EIGRP behave in Nexus, but not in IOS.  The feature parity is not there.   I think development has basically stopped on EIGRP, so I will hasten my efforts to move to OSPF/BGP.  TAC is 99 percent sure there is no way to set delay less than the "one gig delay" in IOS.  The workaround of Making 10g / 40g /100g links slower than a delay of 10 microseconds seems completely wrong.  It breaks things downstream.  The easier fix for now is just adding L3 port-channels.

 

As far is Nexus is concerned when entering picosecond delays on SVI's- the table in the white paper is what we are using.

5.5.1.2 Cisco Interface Delay Compatibility
For compatibility with Cisco products, the following table shows the
times in picoseconds EIGRP uses for bandwidth and delay
    Bandwidth        Classic     Wide Metrics     Interface
    (Kbps)           Delay       Delay            Type
    ---------------------------------------------------------
    9                500000000   500000000        Tunnel
    56               20000000    20000000         56Kb/s
    64               20000000    20000000         DS0
    1544             20000000    20000000         T1
    2048             20000000    20000000         E1
    10000             1000000     1000000         Ethernet
    16000              630000      630000         TokRing16
    45045            20000000    20000000         HSSI
    100000             100000      100000         FDDI
    100000             100000      100000         FastEthernet
    155000             100000      100000         ATM 155Mb/s
    1000000             10000       10000         GigaEthernet
    2000000             10000        5000         2 Gig
    5000000             10000        2000         5 Gig
    10000000            10000        1000         10 Gig
    20000000            10000         500         20 Gig
    50000000            10000         200         50 Gig
    100000000           10000         100         100 Gig
    200000000           10000          50         200 Gig
    500000000           10000          20         500 Gig