Dell PowerScale | EMC Isilon Prerequisites

1. For environments using CEE and RabbitMQ:  The minimum required version of OneFS for use with Peer Global File Service (PeerGFS) is v8.1.0.x.  The minimum required version of OneFS for use with PeerSync is v7.2.x.
   
   For environments using syslog:  The minimum required version of OneFS for use with Peer Global File Service (PeerGFS) is v9.5.0.x.   PeerSync cannot be used with OneFS and syslog.
   

   

   Compatibility Note - December 2021

   A new console/SSH command has been discovered to enable basic authentication in OneFS v9.2.  As such, we are now able to support OneFS v9.2 and later.  See #6 below for more information.

2. Any Windows Server that will be interfacing with a PowerScale or Isilon cluster through the Peer Agent or PeerSync must be on the same domain, same network segment, and same subnet as the cluster ("external" network, not internal).  This network must operate at speeds of at least 1 Gbit/sec.
   
   
3. The system clocks of the PowerScale or Isilon cluster as well as the Peer Agent or PeerSync server must be in sync with each other.
   
   
4. Each PowerScale or Isilon cluster that will be connected to PeerGFS or PeerSync must have a unique cluster name.
    
5. The minimum version of Windows required for PowerScale and Isilon support with the Peer Agent or PeerSync is Windows Server 2012. 
    
6. No other products based on the Common Event Enabler (CEE) framework or syslog from Peer Software or any other vendor can be run on this Windows Server.  In addition, no other Peer Software products can be run on this server (such as the Peer Management Center). 
    
7. For environments using CEE and RabbitMQ:  No other CEE-based application can be leveraging the CEE framework on the PowerScale or Isilon cluster.  This limitation does not apply to environments using syslog.
   
   For environments using syslog:  All other audit vendors using syslog with OneFS must be using TLS.
   
   

8. For OneFS v9.2 and later:  Basic Authentication must be enabled on the cluster.  To do so, run the following console/SSH command:

   CODE

   isi_gconfig -t web-config auth_basic=true

9. An API user account in OneFS is required.  If you are connecting the Peer Agent or PeerSync to an access zone other than the default System zone, this API account must have ZoneAdmin privileges within the desired access zone.  The default root and admin accounts are not automatically granted these privileges when an access zone is created.
   
   To grant ZoneAdmin privileges to a user within a specific access zone, run the following console/ssh command:

   CODE

   isi auth roles modify ZoneAdmin --zone <Zone Name>--add-user=<API User Name>

10. If you are connecting the Peer Agent or PeerSync to an access zone other than the default System zone, each node in the cluster must have an accessible IP address within the IP range tied to the desired access zone.
    
    
11. The service account for the Peer Agent or PeerSync must be a local administrator on the Windows Server that will host the Peer Agent.
     

12. The service account for the Peer Agent or PeerSync must be granted root access on all PowerScale or Isilon CIFS/SMB shares (source or target) to which the Peer Agent or PeerSync will connect.
    
    To add a new account permission with root access to a share, run the following console/SSH command:

    CODE

    isi smb shares permission create <Share Name> <User Name @ Domain Name> --run-as-root

    To change an existing account permission on a share to root access, run the following console/SSH command:

    CODE

    isi smb shares permission modify <Share Name> <User Name @ Domain Name> --run-as-root

13. The service account for the Peer Agent or PeerSync must be added as a local administrator on the PowerScale or Isilon cluster.
    
    To add an account to the local administrators group on the cluster, run the following console/SSH command:

    CODE

    isi auth groups modify --group=administrators --add-user=<User Domain>\\<User name>

14. DNS must be able to resolve the Fully Qualified Domain Name of the Windows Server that will host the Peer Agent or PeerSync.  Both forward and reverse lookups must successfully resolve.
     
15. No firewalls (software or hardware) should be enabled between the Windows Server that will host the Peer Agent or PeerSync, and the PowerScale or Isilon cluster.

Related articles