<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NDU 7mode 812P4 to 824P4 on system running heavily used CIFS vfilers in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/NDU-7mode-812P4-to-824P4-on-system-running-heavily-used-CIFS-vfilers/m-p/122967#M26364</link>
    <description>&lt;P&gt;When doing a NDU you should terminate cifs on physical as well as all vfilers (cifs terminate -t 0).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In huge environments with plenty of open shares, files, locks etc. you might need to run a lock break -p cifs to get rid of oplocks, then you can use cifs terminate -t 0 and command wont get stuck.&lt;/P&gt;</description>
    <pubDate>Tue, 06 Sep 2016 19:35:13 GMT</pubDate>
    <dc:creator>thomas_glodde</dc:creator>
    <dc:date>2016-09-06T19:35:13Z</dc:date>
    <item>
      <title>NDU 7mode 812P4 to 824P4 on system running heavily used CIFS vfilers</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/NDU-7mode-812P4-to-824P4-on-system-running-heavily-used-CIFS-vfilers/m-p/122953#M26363</link>
      <description>&lt;P&gt;Have been &amp;nbsp;doing a series of NDU upgrades &amp;gt; 824P4 7-mode, culminating soon on a heavily used CIFS vfilers with thousands of shares.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;System is a FAS 3240 HA pair 8.1.2P4&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CIFS is not configured on physcial filers....so whilst the UA procedure discusses running "cifs terminate" this is not appropriate as cifs only&amp;nbsp;&lt;/P&gt;&lt;P&gt;configured on vfilers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the specific Upgrade Advisor (UA) doesn't advocate running a cifs terminate on each of &amp;nbsp;the cifs vfilers .....and ....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Moreover, something &amp;nbsp;like "vfiler run * cifs terminate" has caused one of my colleagues problems in past where the command hung up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So should i expect cf takeover and cf giveback to deal with all &amp;nbsp;of these CIFS sessions &amp;nbsp;?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So please what is advise of operation experience on doing NDU ONTAP upgrades where lots of CIFS usage...please noteam familiar with the general Upgrade Advisor procedure , which works &amp;nbsp;well, &amp;nbsp;its just this system has vfilers with loads of shares that am concerned with ...... any thoughts appreciated ... john&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 19:13:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/NDU-7mode-812P4-to-824P4-on-system-running-heavily-used-CIFS-vfilers/m-p/122953#M26363</guid>
      <dc:creator>HYPERHYPO</dc:creator>
      <dc:date>2025-06-04T19:13:08Z</dc:date>
    </item>
    <item>
      <title>Re: NDU 7mode 812P4 to 824P4 on system running heavily used CIFS vfilers</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/NDU-7mode-812P4-to-824P4-on-system-running-heavily-used-CIFS-vfilers/m-p/122967#M26364</link>
      <description>&lt;P&gt;When doing a NDU you should terminate cifs on physical as well as all vfilers (cifs terminate -t 0).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In huge environments with plenty of open shares, files, locks etc. you might need to run a lock break -p cifs to get rid of oplocks, then you can use cifs terminate -t 0 and command wont get stuck.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Sep 2016 19:35:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/NDU-7mode-812P4-to-824P4-on-system-running-heavily-used-CIFS-vfilers/m-p/122967#M26364</guid>
      <dc:creator>thomas_glodde</dc:creator>
      <dc:date>2016-09-06T19:35:13Z</dc:date>
    </item>
  </channel>
</rss>

