Veritas Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- Overview of Data Insight licensing
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About bulk assignment of custodians
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Section VI. Configuring ECM data sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Section X. Reference
- Appendix A. Backing up and restoring data
- Appendix B. Data Insight health checks
- Appendix C. Command File Reference
- Appendix D. Data Insight jobs
- Appendix E. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Preparing a non-administrator domain user on a NetApp cluster for Data Insight
To configure a NetApp cluster from the Management Console, you can use an account which is not in the administrators group on the NetApp filer, but has some specific privileges. You can use the credentials of a domain user to configure Data Insight to monitor a NetApp cluster. These credentials are required to discover shares and to enable FPolicy on the NetApp cluster.
Perform the following steps on the NetApp filer console to add a non-administrator user, for example, testuser.
To use domain user credentials to configure a NetApp cluster
- Log on using SSH to the NetApp cluster with administrator credentials. Do one of the following:
If the NetApp cluster has a data SVM with a CIFS server that is already created, you can use that data SVM as an authentication tunnel. Use the following command:
security login domain-tunnel create -vserver name of data SVM
The following security command displays the specified authentication tunnel:
login domain-tunnel show
If the cluster does not have a data Storage Virtual Machine (SVM) with a CIFS server created, you can use any data SVM in the cluster and join it to a domain by using the vserver active-directory create command. Set the --vserver parameter to the data SVM. Joining a data SVM to a domain does not create a CIFS server or require a CIFS license. However, it enables the authentication of users and groups at the SVM or cluster-level.
- Grant a user or a group access to the cluster or SVM with the -authmethod parameter set to domain.
Also, create a new role, for example testrole, using the
useradmin
utility on the filer.The following command enables <testuser> in the <DOMAIN1> domain to access the cluster through SSH:
cluster1::> security login create -vserver cluster1 <-user-or-group-name> <DOMAIN1\testuser> -application ontapi -authmethod domain - role testrole
Where, <cluster1> is the name of Admin Vserver.
Note the following:
The value of the -user and -group-name parameter must be specified in the format domainname\username, where <domain name> is the name of the CIFS domain server and user name is the name of the user or group you want to grant access to.
The user group authentication supports only SSH and ONTAPI for the -application parameter.
If the authentication tunnel is deleted, the directory service logon sessions cannot be authenticated by the cluster, and users and groups cannot access the cluster. The open sessions that were authenticated before the deletion of the authentication tunnel remain unaffected.
- You can also choose to assign specific capabilities to the role.
security login role create -role testrole -cmddirname "version"-access all
Enables you to log into the NetApp filer and run commands. With this capability, you can get latency statistics (for scan throttling), volume size information, or discover shares.
Run the following commands to create the role with specific privileges:
security login role create -role testrole -cmddirname "version"-access all
security login role create -role testrole -cmddirname "vserver cifs"-access readonly
security login role create -role testrole -cmddirname "vserver nfs" -access all
security login role create -role testrole -cmddirname "vserver"-access readonly
security login role create -role testrole -cmddirname "volume"-access readonly
security login role create -role testrole - cmddirname "vserver fpolicy policy" -access all
security login role create -role testrole - cmddirname "vserver fpolicy" -access readonly
security login role create -role testrole - cmddirname "vserver fpolicy enable" -access all
security login role create -role testrole - cmddirname "vserver fpolicy disable" -access all
security login role create -role testrole - cmddirname "statistics" -access readonly
security login role create -role testorle -cmddirname "network interface show" -access readonly
The network interface show privilege automatically assigns the following privileges to the role:
network interface create
network interface modify
network interface modify
You can optionally specify a default role such as admin/vsadmin which already has these privileges.