ONTAP Discussions

8.3.1 using wrong lif for traceroutes


Seems like the 'net traceroute' command is broken in three ways:


1. Doesn't use the lif specified on the command line (i.e. -lif <lifname>)

2. Doesn't use the routing table to select the correct route - simply uses the default route in all cases.

3. Doesn't hit the destination I specified!!


Can anyone replicate this behavior?


fcnascl02::> net route show -vserver fcnascl02                                                               
  (network route show)
Vserver             Destination     Gateway         Metric
------------------- --------------- --------------- ------
             10  <--- Should be using this route because it is most specific

fcnascl02::> net int show -role intercluster -vserver fcnascl02
  (network interface show)
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
                         up/up   fcnas04n0     a0a-757 true  <--- lif specified in the command below
                         up/up   fcnas04n1     a0a-757 true

fcnascl02::> net traceroute -lif fcnas04n0_snapmirror-n0-757 -vserver fcnascl02 -destination  <-- same subnet
  (network traceroute)
traceroute to ( from, 64 hops max, 44 byte packets
 1  fcnas05n0-e0m (  0.300 ms  0.234 ms  0.177 ms  <--- WRONG destination lif shown - is it even using my destination?



fcnascl02::> net traceroute -node fcnas04n0 -vserver fcnascl02 -destination  <--- no lif selected, should use routing table
  (network traceroute)
traceroute to (, 64 hops max, 44 byte packets
 1  fcnas05n0-e0m (  0.371 ms  0.264 ms  0.232 ms  <--- WRONG destination lif shown again




This issue is impacting my ability to troubleshoot a cluster peer issue.



Your desired path seems to have the same metric as that of the default route. Try decreasing that value using the "network route create -metric " commandline. System prefers the route which has the lowest metric. In case if there is a conflict, it may choose the route that comes first in the routing table.

Another possibility is the IP fastpath option. You can see whether it is enabled by using the following command.


For Data ONTAP 8.3.1 and later, run the following command:
::>options ip.fastpath.enable


IP fastpath is a feature that bypasses the routing table lookups thereby improving network performance. But it can cause issues in complex networks sometimes. One should be aware of the consequences of enabling or disabling this feature. If this is causing the issue, please log a case and get NetApp tech support involved. 


If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.