Skip to main content
NetApp Knowledge Base

How do you determine the most specific network route ONTAP 9.2 and later versions will use for network traffic?

Last Updated:

Applies to

  • ONTAP 9.2 and later versions
  • IPv4


  • How ONTAP chooses a route when it needs to initiate a new request or reply to a request.
  • To determine the most specific route(s) to the destination, run the following command from the ONTAP CLI:​​​​​​
    • set advanced; network route active-entry show -vserver vserver -node node-01 
    • This will include routes that originate from the LIFs on the node specified
      • The command "route show" will only show routing configurations (not the actual routes in the routing table)
    • Alternatively, ROUTE-ACTIVE.XML can be reviewed in the AutoSupport section of  ActiveIQ 
  • From the available routes determine which route has the "narrowest" (most-specific or smallest) subnet that the destination IP will fit into.
    • For example, if the destination IP address is, looking at routing table with the following destinations:
      • "default" or matches and has a /0 (all zeroes) netmask
      • 10.1/16 matches and has a /16 ( netmask
      • 10.1.1/24 matches and has a /24 ( netmask
      • matches and has a /32 (all ones) netmask (32 is more specific than 24, 16, and 0). This is an example of a single host route, an exact match to a single IP address, making it the most specific route

(The actual routing decision takes place looking at most-specific to least-specific address, ending up a the default route when nothing else matches, including link-local addresses.

Additional Information


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.