To add the policy

1. Select Admin > Data Collection > Collector Administration. Currently configured Portal Data Collectors are displayed.
2. Search for a Collector if required.
3. Select a Data Collector from the list.
4. Click Add Policy, and then select the vendor-specific entry in the menu.
5. Add or select the parameters. Mandatory parameters are denoted by an asterisk (*):

   Field	Description
   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 Collector Domain is the domain that was supplied during the Data Collector installation process. 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.
   HP 3PAR Storage System Address(es)*	Enter a comma-separated list of IP addresses or host names of the HP 3PAR Storage Systems from which you want to collect data.
   Collection Method	The Command Line Interface (CLI) is the only available method for HP 3PAR data collection. This method logs in to the HP 3PAR Storage System via SSH and uses the command line for data collection. Data collection supports two authentication types: password based authentication and SSH key based authentication. Select the required type in the Authentication Type field.
   User ID*	Specify the User ID for the HP 3PAR Storage Systems. The User ID and Password must be the same for all systems identified in the Host Address field. The HP 3PAR user account should have been created with Browse rights. The same User ID is used for both password based and SSH key based authentication.
   Password*	Enter the password associated with the User ID. This field is required when Authentication Type is set to Password. When Authentication Type is set to SSH Key, enter the private key passphrase in this field, or leave it empty if the key pair was generated without a passphrase. Note: The password is encrypted prior to saving in the database and is never visible in any part of the application.
   SSH Private Key Passphrase	Applicable only when Authentication Type is set to SSH Key. Enter the passphrase that protects the private key file. Leave this field empty if the key pair was generated without a passphrase. Enter the passphrase in the Password field. When Authentication Type is set to SSH Key, the value in the Password field is treated as the private key passphrase. The passphrase is encrypted before it is saved in the database and is never visible in any part of the application.
   SSH Private Key File Path	Applicable only when Authentication Type is set to SSH Key. Enter the absolute path of the private key file as it is stored on the Data Collector server. The private key file must be readable by the operating system account that runs the Data Collector service, and its permissions must be restricted to that account. Upload the matching public key to the HP 3PAR or HPE Alletra user account before the first collection. See Pre-Installation setup for HP 3PAR.
   Authentication Type	Select the method that the Data Collector uses to authenticate to the HP 3PAR Storage Systems over SSH. Password: the Data Collector authenticates with the User ID and Password. SSH Key: the Data Collector authenticates with the User ID and an SSH private key. Password is the default. Use SSH Key for arrays on which SSH password authentication is disabled. On the HPE Alletra Storage MP B10000 series running ArcusOS 10.6.0 and later, the array default for PasswordAuthentication is no, so SSH key-based authentication must be used. SSH keys are also supported on earlier HPE 3PAR and HPE Alletra firmware, so the same policy configuration works before and after an array upgrade.
   Array Details	Select the check box to activate the array details collection. Click the clock icon to create a schedule frequency. You schedule the collection frequency by minute, hour, day, week and month. Advanced use of native CRON strings is also available. 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.
   Health Check	This probe collects physical disk, event log, space and replication information. Note that to perform the collection of the array health check data, at least one Array Details collection from this array must be complete. Default scheduled: Every 4 hours.
   Volume Performance	This probe collects performance metrics for Virtual Volumes and VLUNs. Note that at least one Array Details collection from this array must be performed before this data can be collected.
   Controller Performance	The probe collects performance metrics for Controllers, Nodes, and Ports. Note that at least one Array Details collection from this array must be performed before this data can be collected.
   Notes	Enter or edit notes for your data collector policy. The maximum number of characters is 1024. Policy notes are retained along with the policy information for the specific vendor and displayed on the Collector Administration page as a column making them searchable as well.

6. Click OK to save the Policy and return to the Collection Administration window where the Policy will be listed under the Data Collector. From here you can add an additional Policy record (for example, if the data collector needs to communicate with other servers), or make changes to the Policy you just created.