McAfee VSE-Storage 1.0.x RPC Timeout and 0×14 Errors

November 9th, 2011 by Jack Cobben Leave a reply »

Hi guys,

Just got word from McAfee about the following:

“NetApp ONTAP 7.3.6 and 8.0.2 introduced an option to handle idle RPC sessions and in particular idle RPC sessions by file ID. Generally, this new strategy behaves when a particular FID associated with an RPC connection does not have any activity for more than 20 minutes (by default), Data ONTAP disconnects the connection, considering it idle. This change was added to address a memory leak that was experienced by applications that were opening (many) RPC connections and never closing them out. This lack of closing out of connections creates the NetApp memory leak.

Because McAfee VSES uses the same infrastructure for keep-alive probes the disconnect/idle setting may cause performance issues when reading/writing large files to the filer(s).

IMPORTANT:
If you are experiencing VSE for Storage RPC Timeout disconnects with filers running 7.3.6 or 8.0.2 then current workaround steps are:

  1. Modify the following filer option cifs.rpcfd_timeout to a value of 0.
    To change the value run the following: options cifs.rpcfd_timeout 0 [ENTER].
  2. Confirm the option took by typing: options cifs.rpcfd_timeout [ENTER].
    The value returned for the option should be 0.
  3. Do one of the following to ensure the malfunctioning AV servers disconnect and reconnect:
    • Cycle the McAfee AV services on the server itself
    • Disable / Re-enable AV on the filer.

Monitor for the behavior to re-appear.
McAfee also recommends installing the latest hotfixes:

  • VSE for Storage 1.0.0 Patch 1 plus HF539302 and HF685485
  • VSE for Storage 1.0.2 plus HF672928 and HF692368

To access the above VSE for Storage hotfixes, contact McAfee Customer Support.

If you encounter VSE for Storage RPC Timeout disconnects with filers running 7.3.6 or 8.0.2, see “ONTAP RPC connections” when querying NetApp Knowledge Base Database or when opening a case with NetApp.”

 

Advertisement

Leave a Reply

In an effort to prevent automatic filling, you should perform a task displayed below.