NetApp Data ONTAP 7-Mode Prerequisites
Last Updated | 17 December 2020 |
The minimum required version of ONTAP (operating in 7-Mode) for use with Peer Global File Service or PeerSync is v7.3.5. Older versions of ONTAP will not work properly.
Any Windows Server that will be interfacing with the NetApp device through the Peer Agent or PeerSync must be on the same domain, same network segment, and same subnet as the NetApp device. This network must operate at speeds of at least 1 Gbit/sec.
The minimum version of Windows required for FPolicy support with the Peer Agent or PeerSync is Windows Server 2012.
If you are using Windows Server 2019 for the Peer Agent or PeerSync, SMB1 must be enabled (it is disabled by default). The following PowerShell commands can be used to check and enable SMB1:
No other FPolicy or VSCAN products from Peer Software or any other vendor can be run on this FPolicy Server. In addition, no other Peer Software products can be run on this server (such as the Peer Management Center).
The service account for the Peer Agent or PeerSync must be a member of the Local Admin Group on the NetApp device. You can add a domain user <Domain User Name> (in the format "DOMAIN\USERNAME") to the Local Admin Group of the device with the following ONTAP command from the filer or vFiler context:
CODEuseradmin domainuser add <Domain User Name> -g administrators
Any Windows server that will be interfacing with the NetApp device through the Peer Agent or PeerSync must have the following Local Security Policy settings:
Security Policy
Setting
Network access: Named Pipes that can be accessed anonymously
Add ntapfprq and ntapfpcp
Network access: Let Everyone permissions apply to anonymous users
Enabled
Microsoft network server: Digitally sign communications (always)
Disabled
Microsoft network server: Digitally sign communications (if client agrees)
Disabled
Note: You must restart the server after changing the Local Security Policy settings.
Optional Local Security Policy settings:
blank line
DNS must be able to resolve the Fully Qualified Domain Name of any server that will be interacting with the NetApp device through the Peer Agent or PeerSync. Both forward and reverse lookups must successfully resolve.
The NetBIOS name of the controller or vFiler must match its ONTAP system name.
No firewalls (software or hardware) should be enabled between the FPolicy Server and the NetApp device.
Related articles
- Achieving high availability for the PMC through active-passive configuration
- Achieving high availability for the PMC through active-passive configuration (v4.7.0 - v5.1.1)
- Achieving high availability for the PMC through active-passive configuration (v5.2 and later)
- Amazon FSx for NetApp ONTAP Prerequisites
- Dell EMC Celerra | VNX | VNX 2 Prerequisites