The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Cisco UCS Director supports the NetApp storage infrastructure. Cisco UCS Director provides auto-discovery, monitoring, and complete visibility for all NetApp filer components, such as nodes, SVMs, IPspaces, aggregates, and SnapMirrors.
Note | You can view the model of a managed NetApp storage system, such as whether the system is FAS or AFF. The Model and Storage Array Type information is available on several NetApp reports, including the Cluster Summary report, the Nodes report, and the Nodes Summary report. |
The reports in Cisco UCS Director enable you to view and identify all NetApp storage systems; for example, a report for a NetApp storage system lists information about the name, type, server IP address, version, model, and storage array type of that managed system.
To manage a NetApp storage system, you need to add a pod and create a NetApp account within that pod.
A pod is a logical grouping of physical and virtual components, including one or more physical or virtual accounts, such as an HP account for computing or a NetApp ONTAP account for storage. Typically, a pod represents a single converged infrastructure stack, such as a FlexPod, Vblock, or VSPEX.
Step 1 | Choose . | ||||||||||||||
Step 2 | On the Physical Accounts page, click Pods. | ||||||||||||||
Step 3 | Click Add. | ||||||||||||||
Step 4 | On the Add POD screen, complete the following fields:
| ||||||||||||||
Step 5 | Click Add. |
Add one or more accounts to the pod.
Cisco UCS Director uses the Transport Layer Security (TLS) protocol to discover a NetApp device. In NetApp devices, set the TLS option to ON by entering the command: options tls.enable on. This setting enables Cisco UCS Director to discover NetApp accounts.
If you do not want to use the Default Pod, create a pod for this NetApp account.
Manually configure an aggregate on the ONTAP filer before you can use the filer management of Cisco UCS Director.
Cisco UCS Director tests the connection to the NetApp storage system. If that test is successful, it adds the NetApp account and discovers all infrastructure elements in the storage system that are associated with that account, including the server's information, slots, processors, memory, and NICs. This discovery process and inventory collection cycle takes a few minutes to complete.
The polling interval configured in System Tasks on specifies the frequency of inventory collection. For more information about configuring the polling interval, see the Cisco UCS Director Network Devices Management Guide.
You can test the connection after you add an account to a pod.
If the connection fails, verify the configuration of the account, including the username and password. If those items are correct, determine whether there is a network connectivity problem.
After you add a NetApp account to Cisco UCS Director, you can verify that the account is properly added and its relevant data has been collected. It can take few minutes to complete auto-discovery and populate the data.
Step 1 | Choose . | ||
Step 2 | On the Storage page, choose the pod that includes the NetApp account that you want to verify.
| ||
Step 3 | Click Storage Accounts. | ||
Step 4 | Click the row with the account that you want to verify and click View Details.
Cisco UCS Director displays the components of the NetApp server at the filer level for both ONTAP and OnCommand account types. To view the components of the filer, choose the filer and click View Details. |
After provisioning a SVM, you can directly add the SVM to Cisco UCS Director. Before you add a SVM, consider the following requirements:
User Account: Use the default vsadmin account or any other user account created on the SVM. To use the default vsadmin account, unlock the vsadmin account and provide a password.
Access: Enable access to the ontapi application for the selected user account. Also provide vsadmin role to the user account so that Cisco UCS Director performs the necessary read and write actions on the SVM.
The following example shows the role and access levels necessary to add a SVM.
a05-cluster::> security login show -SVM Goldfinger -username vsuser SVM: Goldfinger UserName Application Authentication Method Role Name Acct Locked ------- ------------ --------------------- --------- ----------- mynewuser ontapi password vsadmin no
Management LIF: Associate a management LIF with the SVM. Set the LIF type to data and the data protocol to none.
Step 1 | Choose . | ||||||||||||||||||||||||||||
Step 2 | On the Physical Accounts page, click Physical Accounts. | ||||||||||||||||||||||||||||
Step 3 | Click Add. | ||||||||||||||||||||||||||||
Step 4 | On the Add Account screen, complete the following fields:
| ||||||||||||||||||||||||||||
Step 5 | Click Submit. | ||||||||||||||||||||||||||||
Step 6 | On the second Add Account screen, complete the following fields:
| ||||||||||||||||||||||||||||
Step 7 | Click Add. |