Value Of The Option Nfs.ifc.rcv.high Is Unexpectedly Reset; Enabling New Ems Messages To Help Troubleshoot Kerberos Issues; Microsoft Windows 7 Clients Fail To Rename Files And Directories - IBM N Series Manual

Value of the option nfs.ifc.rcv.high is unexpectedly reset

The option nfs.ifc.rcv.high value might unexpectedly get reset to a
previous value if it is changed by the option nfs.tcp.recvwindowsize.
The option nfs.ifc.rcv.high controls the high-water mark after which NFS
level flow control takes effect. This option is also controlled by the option
nfs.tcp.recvwindowsize. Changing the option nfs.tcp.recvwindowsize
automatically changes the value of the option nfs.ifc.rcv.high.
However, there are some scenarios in which the option nfs.ifc.rcv.high
value gets reset to a previous value if it is changed by the option
nfs.tcp.recvwindowsize. To avoid the issue, first configure the option
nfs.tcp.recvwindowsize, then manually configure the option
nfs.ifc.rcv.high.
Note: The value for the option nfs.ifc.rcv.high should be 1.5 times the
value of the option nfs.tcp.recvwindowsize.

Enabling new EMS messages to help troubleshoot Kerberos issues

New EMS messages have been added to Data ONTAP to help troubleshoot
Kerberos authentication and connectivity issues.
Enable the new EMS messages for Kerberos by entering the following
command:
options nfs.rpcsec.trace on
After you finish troubleshooting, disable the EMS message for Kerberos by
entering the following command:
options nfs.rpcsec.trace off

Microsoft Windows 7 clients fail to rename files and directories

When a Microsoft Windows 7 client accesses an SMB share with widelinks
enabled, it can fail intermittently to rename files and directories on the
mapped share. This can lead to a situation where attempts by Microsoft Office
applications to save documents on the share fail.
This issue is caused by a bug in the Windows 7 client for which a hot fix is
available from Microsoft. The bug is described and information about how to
obtain the hot fix is provided in the Microsoft KB 2703610. This KB article also
provides information about a workaround for this issue if you do not want to
apply the hot fix.
Known problems and limitations
97