Skip to main content
NetApp Knowledge Base

CIFS shares not accessible when client is in same subnet as one of the data lif in vserver

  1. Last updated
  2. Save as PDF
Views:
515
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • CIFS
  • Asymmetric routing

Issue

  • As Ontap already have data lif with same subnet as client is, it is using the same subnet lif to respond back to client even though request landed on different lif on Ontap.
  • Because the firewall is dropping the response packet as it has different mac than the request packet, client is not getting response and CIFS share are inaccesible.

For example:

  • Consider that there are two lifs on vserver as below:

cdot_vsim_9_8::> net int show -vserver vs1
  (network interface show)
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
vs1
            lif1         up/up    10.80.70.150/24     node1
                                                                    e0c     true
            lif2         up/up  10.80.96.11/24        node1
                                                                    e0c     true
 

  • Client_A IP is "10.80.70.92/24" is in same subnet as "lif1" is as shown above.
  • Now, if client_A send request on "lif2", Ontap will response back using "lif1".
  • This is called asymmetric routing and behaviour is explained in article.
  • Because the response is dropped in the firewall, client will not see response and CIFS shares will be inaccessible.

NOTE: To check which lif Ontap is using to respond, please capture packet traces.

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.