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 that enables you to manage all NetApp filer components.
Cisco UCS Director enables you to monitor and manage various components of the NetApp storage system. To manage the NetApp storage system, you need to add a pod and create a NetApp account.
NetApp has two types of accounts:
OnCommand manages and monitors all NetApp appliances (filers and NetCache appliances) within a network, by accessing global and detailed status reports of current and past activities. Cisco UCS Director discovers all storage elements in the NetApp account, such as aggregates, raid groups, disks, volumes, LUNs, Qtrees, and so on. Typically, the discovery process takes about 5 minutes or within a time interval that you configured in the System Tasks tab. To access the System Tasks tab, choose .
Data ONTAP is an operating system used by the NetApp filer. Data ONTAP has two modes:
Cluster mode—Defines an architecture that is made of a group of connected NetApp storage controllers (nodes) that share a global namespace (GNS). The physical NetApp storage controllers can have attached disk shelves, network interface cards (NICs), and flash cards. These components create a physical resource pool that is virtualized as a logical cluster to provide data access. Cisco UCS Director abstracts and virtualizes the physical equipment into logical resources, which allow data operations to be moved in a nondisruptive way. Cluster administrators can administer the entire cluster and the SVMs within the cluster.
SVM — SVM (formerly known as Vserver) is a secure virtual storage server that supports multiple protocols and unified storage. Each SVM is configured for the client and host access protocols such as iSCSI. Each SVM contains at least one volume and at least one logical interface. SVMs provide data access to clients without regard to physical storage or controller, similar to any storage system.
SVM administrator can administer SVMs and its resources such as volumes, protocols, and services, depending on the capabilities assigned by the cluster administrator.
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 | On the menu bar, choose . | ||||||||||||||
Step 2 | Click the Pods tab. | ||||||||||||||
Step 3 | Click Add. | ||||||||||||||
Step 4 | In the
Add
Pod dialog box, complete the following fields:
| ||||||||||||||
Step 5 | Click Add. |
Add one or more accounts to the pod.
Starting with Release 5.4, 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.
Add the pod to which this NetApp account belongs.
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 server. If that test is successful, it adds the NetApp account and discovers all infrastructure elements in the server that are associated with that account, including the server's information, slots, processors, memory, and NICs. This discovery process and inventory collection cycle takes few minutes to complete.
The polling interval configured on the System Tasks tab on the window 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 | On the menu bar, choose Physical > Storage. | ||
Step 2 | In the left
pane, choose the pod that includes the NetApp account that you want to verify.
| ||
Step 3 | Click the Storage Accounts tab. | ||
Step 4 | In the table, click the account that you want to verify. | ||
Step 5 | Click
View
Details.
Cisco UCS Director displays the components of 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. | ||
Step 6 | Click Back to return to the Storage Accounts tab. |
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 | From the Administration menu, choose . | ||||||||||||||||||||||||||||
Step 2 | Click the Physical Accounts tab. | ||||||||||||||||||||||||||||
Step 3 | On the Physical Accounts page, click Add. | ||||||||||||||||||||||||||||
Step 4 | In the
Add
Account dialog box, complete the following fields:
| ||||||||||||||||||||||||||||
Step 5 | Click Add. |