Re: internal tag value are missing for some EIGRP entires under Nexus9000 C9336C topology table

eric.guo · ‎08-16-2018

hi All,

we just provisoned one pair of Nexus9000-C9336C devices into the production as Data Center service vlan L3 gateway routers, we setup EIGRP neighbourship with our 2 Core Cisco ASR1006X routers parallelly . The routing protocol are running good between them and outside EIGRP routes are recevied into these Nexus9000 EIGRP topology table wihtout problem. But most of entires are showing up with their internal tag value, but some entires with tag 2000/3000 aren't showing up with their internal tag value in these Nexus9000 device . We already checked there is not any route-map/filter in the between, and these entires with 2000/3000 tag can be received into other core peering routers perporly

so did someone havesame issue? or could someone provide any comment on it ?

These Nexus9000 code are running on latest version -7.0(3)I7(4).

For example: normal one:

DC-CORE-N9K-3-4-33# sh ip eigrp topology 10.129.16.0/20

IP-EIGRP (AS 350): Topology entry for 10.129.16.0/20
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 3598
Routing Descriptor Blocks:
172.22.130.2 (Vlan130), from 172.22.130.2, Send flag is 0x0
      Composite metric is (3598/3342), Route is Internal
      Vector metric:
        Minimum bandwidth is 1000000 Kbit
        Total delay is 40 microseconds
        Reliability is 255/255
        Load is 18/255
        Minimum MTU is 1500
        Hop count is 2
        Internal tag is 233
172.22.251.1 (port-channel30), from 172.22.251.1, Send flag is 0x0
      Composite metric is (259098/3098), Route is Internal
      Vector metric:
        Minimum bandwidth is 1000000 Kbit
        Total delay is 10021 microseconds
        Reliability is 255/255
        Load is 25/255
        Minimum MTU is 1500
        Hop count is 3
        Internal tag is 222

====================

abnormal one:

====================

DC-CORE-N9K-3-4-33# sh ip eigrp topology 10.195.0.0/20

IP-EIGRP (AS 350): Topology entry for 10.195.0.0/20
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 3598
Routing Descriptor Blocks:
172.22.130.2 (Vlan130), from 172.22.130.2, Send flag is 0x0
      Composite metric is (3598/3342), Route is Internal
      Vector metric:
        Minimum bandwidth is 1000000 Kbit
        Total delay is 40 microseconds
        Reliability is 255/255
        Load is 9/255
        Minimum MTU is 1500
        Hop count is 2
        Internal tag is 0----supposed to be 2000
172.22.251.1 (port-channel30), from 172.22.251.1, Send flag is 0x0
      Composite metric is (259098/3098), Route is Internal
      Vector metric:
        Minimum bandwidth is 1000000 Kbit
        Total delay is 10021 microseconds
        Reliability is 255/255
        Load is 23/255
        Minimum MTU is 1500
        Hop count is 3
        Internal tag is 0------------ supposed to be 3000

thanks

Eric

Georg Pauwen · ‎08-16-2018

Hello,

this could be related to eigrp wide metrics, do you have that configured ? If so, try and remove it from your config...

eric.guo · ‎08-16-2018

hi Georg,

Thanks for your quick response !

could you please indicate me how to check this eigrp wide metrics under these N9K devices? and how to remove it if possible?

thanks,

Eric

Georg Pauwen · ‎08-16-2018

Hello,

if you don't see 'eigrp wide metric' under the EIGRP process, it is not configured. You might want to check if it might be configured by accident on any of the neighboring routers...