If you have more than one array, the Automation Orchestrator plugin offers an automated way to authenticate all of your arrays. Once you have authenticated a Pure1 organization, there is a workflow called Register FlashArrays from Pure1 under Library > Everpure > Connection Management > Pure1.
Select the workflow named Register Arrays from Pure1 and click Run.
There are a few required inputs:
|
Pure1 Connection. Specify the Pure1 organization from which you would like to register the arrays. Click in the empty box and choose the correct organization and click Select. |
Use same credentials? If one set of credentials is valid for all targets, you can specify them here. If not, choose No and it will not require credentials. They can be added one at a time during the workflow |
Resolve IPs? Pure1 (currently) does not offer the FQDN of arrays, only the IP. The vRO workflow will attempt to do a DNS lookup of the IPs and use the identified FQDN. If the lookup fails, it will use the IP. If you would like it to skip arrays that it cannot resolve, choose No. |
|
|
|
|
There is another option that asks if you want to import certificates automatically. Select this to do so, or leave it deselected to confirm each certificate one-by-one interactively.
When ready click Run.
If you have chosen to specify credentials one at a time, or the credentials are wrong, it will prompt for credentials for arrays that the credentials are not valid for. You will see the workflow is waiting for input by the person icon next to the workflow run:
Click Answer to enter the correct credentials.
Enter the credentials and click Submit.
You can choose to skip an array by selecting the box to skip it and register it later.
Once done, all of the arrays in that organization will be authenticated and added to the Pure1 organization in the Automation Orchestrator inventory.
There are a few points to make about this workflow:
- This is only supported for FlashArray and Cloud Block Store. FlashBlades will be skipped. Inclusion of FlashBlades will come in a future release.
- Arrays that cannot be reached on the network will be skipped.
- Arrays that are already registered will be skipped.
- There is no option to choose a REST version--it will automatically choose the latest available 1.x release of REST on that target (REST 2.x is not yet supported).