Adding a NetApp Cluster-Mode Data Collector Policy
• Before adding the policy: A Data Collector must exist in the Portal, to which you will add Data Collector Policies. See
Adding/Editing Data Collectors. For specific prerequisites and supported configurations for a specific vendor, see the
APTARE Certified Configurations Guide.
• After adding the policy: For some policies, collections can be run on-demand using the Run button on the Collector Adminstration page action bar. The Run button is only displayed if the policy vendor is supported.
On-demand collection allows you to select which probes and devices to run collection against. This action collects data the same as a scheduled run, plus logging information for troubleshooting purposes. For probe descriptions, refer to the policy and see
On-Demand Data Collection for details about
Run.
To add the policy
1. Select Admin > Data Collection > Collector Administration. Currently configured Portal Data Collectors are displayed.
3. Select a Data Collector from the list.
4. Click Add Policy, and then select the vendor-specific entry in the menu.
.
5. Enter or select the parameters. Mandatory parameters are denoted by an asterisk (*):
Field | Description | Sample Value |
Collector Domain | The domain of the collector to which the collector backup policy is being added. This is a read-only field. By default, the domain for a new policy will be the same as the domain for the collector. This field is set when you add a collector. | |
Policy Domain | The Policy Domain is the domain of the policy that is being configured for the Data Collector. The Policy Domain must be set to the same value as the Collector Domain. The domain identifies the top level of your host group hierarchy. All newly discovered hosts are added to the root host group associated with the Policy Domain. Typically, only one Policy Domain will be available in the drop-down list. If you are a Managed Services Provider, each of your customers will have a unique domain with its own host group hierarchy. To find your Domain name, click your login name and select My Profile from the menu. Your Domain name is displayed in your profile settings. | |
NetApp Address* | One or more Cluster-Mode IP addresses or host names to probe. Comma-separated addresses or IP ranges are supported, for example, 192.168.0.1-250, 192.168.1.10, myhost. If you use VMs in a management server configuration, be sure to connect to the filer node IPs and not the VM. Note that these are for ONTAP Cluster-Mode and ONTAP 7 addresses cannot be used. | 192.168.0.1-250, 192.167.1.10, myhost |
User ID* | The view-only user ID for accessing NetApp ONTAP Cluster-Mode storage. | |
Password* | The password associated with the User ID. | |
Array Capacity | Check the box to collect array capacity data from your NetApp Cluster-Mode environment. Click the clock icon to create a schedule. Every Minute, Hourly, Daily, Weekly, and Monthly schedules may be created. Advanced use of native CRON strings is also available. Examples of CRON expressions: */30 * * * * means every 30 minutes */20 9-18 * * * means every 20 minutes between the hours of 9am and 6pm */10 * * * 1-5 means every 10 minutes Mon - Fri. Note: Explicit schedules set for a Collector policy are relative to the time on the Collector server. Schedules with frequencies are relative to the time that the Data Collector was restarted. | 1 */4 * * * |
Array Performance | Check the box to collect array performance data. Note that at least one collection from this array must be performed BEFORE array performance data can be collected. Click the clock icon to create a schedule. | |
Testing the Collection
You can test the collection of data using the Run functionality available in Admin>Data Collection>Collectors. This test run performs a high-level check of the installation, including a check for the domain, host group and URL, plus Data Collector policy and database connectivity. See xxx for details.
Creating a NetApp Cluster-Mode Read-only User
Data collection of NetApp Cluster-Mode requires a specific read-only role and user in order to collect data for a cluster.
To create a new user account with the required privileges, use the following Command Line Interface (CLI) steps. This set of commands creates a role as apt_readonly and then a user named apt_user with read-only access.
1. Create a read-only role using the following two commands.
security login role create -role apt_readonly -cmddirname DEFAULT -access readonly
security login role create -role apt_readonly -cmddirname security -access readonly
2. Create the read-only user using the following command. Once you have executed the create command, you will be prompted to enter a password for this user.
security login create -username apt_user -application ontapi -authmethod password -role apt_readonly
The resulting role and user login will look something like this:
Role Command/ Access
Vserver Name Directory Query Level
---------- ------------- --------- ------------------ --------
cluster1 apt_readonly DEFAULT readonly
cluster1 apt_readonly security readonly
cluster1::security login> show
Vserver: cluster1
Authentication Acct
UserName Application Method Role Name Locked
---------------- ----------- -------------- ---------------- ------
apt_user ontapi password apt_readonly no