- Preface
- New and Changed Information for this Release
- Overview
- Configuring Cisco UCS Manager Accounts
- Configuring Fabric Interconnects and Ports
- Configuring Network Connections
- Configuring Storage Connections
- Configuring Cisco UCS Server Pools and Policies
- Configuring Service Profiles
- Managing Cisco UCS Servers
- Monitoring and Reporting
- Pods
- Cisco UCS Manager Accounts
- Adding a Cisco UCS Manager Account
- Testing the Connection to a Physical Account
- Verifying the Discovery of a Cisco UCS Manager Account
- Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain
- Exporting the Configuration of a Cisco UCS Manager Account
- Importing the Configuration of a Cisco UCS Manager Account
- Selective Server Management
- Registration of a Cisco UCS Manager Account with Cisco UCS Central
- Prerequisites for Cisco UCS Central
- Registering a Cisco UCS Manager Account with Cisco UCS Central
- Unregistering a Cisco UCS Manager Account from Cisco UCS Central
- Making a Policy, Service Profile, or Service Profile Template Global
- Making a Policy, Service Profile, or Service Profile Template Local
- Organizations
- Locales
- Time Zones
- Cloning a Policy
- Deleting a Pool, Policy, or Other Object
Configuring Cisco UCS Manager Accounts
This chapter contains the following sections:
- Pods
- Cisco UCS Manager Accounts
- Selective Server Management
- Registration of a Cisco UCS Manager Account with Cisco UCS Central
- Organizations
- Locales
- Time Zones
- Cloning a Policy
- Deleting a Pool, Policy, or Other Object
Pods
A pod is a logical grouping of physical and virtual components, including one or more physical or virtual accounts, such as a Cisco UCS Manager account for computing, a network account, or a cloud account. Each pod is a module of network, compute, storage, and application components that work together to deliver services for your data center and users. The pod is a repeatable pattern, and its components maximize the modularity, scalability, and manageability of data centers.
When you create a pod, consider what you want it to represent. For example, you can create a pod to represent the following:
-
A single converged infrastructure stack, such as FlexPod, Vblock, or VSPEX
-
A grouping of resources assigned to a specific customer or tenant
-
The resources within a specific range of IP addresses
For systems that include Cisco UCS Central, we recommend that you create a pod for each Cisco UCS domain or domain group.
If needed, you can group pods into sites. However, a pod can only belong to one site.
You can view details of the pods and their components on the Converged tab in Cisco UCS Director. For information about how to create pods, see the Cisco UCS Director Administration Guide.
Adding a Pod
| 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. |
What to Do Next
Add one or more accounts to the pod.
Cisco UCS Manager Accounts
Each Cisco UCS Manager account represents a single Cisco UCS domain that you want to have managed by Cisco UCS Director.
For an environment that does not include Cisco UCS Central, you create Cisco UCS Manager accounts in a pod. You can have more than one Cisco UCS Manager account for a pod.
For an environment that includes Cisco UCS Central, you must create a Cisco UCS Central account under multi-domain managers. All Cisco UCS domains that are registered with that Cisco UCS Central, and their related Cisco UCS Manager accounts are brought into Cisco UCS Director when the Cisco UCS Central account is created. You can assign one or more of those Cisco UCS Manager accounts from the Cisco UCS Central account to a pod if needed. You can also register a Cisco UCS Manager account with a Cisco UCS Central account.
- Adding a Cisco UCS Manager Account
- Testing the Connection to a Physical Account
- Verifying the Discovery of a Cisco UCS Manager Account
- Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain
- Exporting the Configuration of a Cisco UCS Manager Account
- Importing the Configuration of a Cisco UCS Manager Account
Adding a Cisco UCS Manager Account
Add the pod to which this Cisco UCS Manager account belongs.
Cisco UCS Director tests the connection to Cisco UCS Manager. If that test is successful, it adds the Cisco UCS Manager account and discovers all infrastructure elements in Cisco UCS Manager that are associated with that account, including chassis, servers, fabric interconnects, service profiles, and pools. This discovery process and inventory collection cycle takes approximately five minutes to complete.
The polling interval configured on the tab specifies the frequency of inventory collection.
Testing the Connection to a Physical Account
You can test the connection at any time after you add an account to a pod.
What to Do Next
If the connection fails, verify the configuration of the account, including the username and password. If the username and password are correct, determine whether there is a network connectivity problem.
Verifying the Discovery of a Cisco UCS Manager Account
| Step 1 | Choose . | ||
| Step 2 | On the Compute page, choose the pod. | ||
| Step 3 | On Compute page, choose the pod that includes the Cisco UCS Manager account that you want to verify.
| ||
| Step 4 | Click Compute Accounts. | ||
| Step 5 | Choose the row of the account that you want to verify. | ||
| Step 6 | Click
View
Details.
Cisco UCS Director displays a set of tabs that contain information about the components of that account that it has discovered. |
Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain
| Step 1 | Choose . |
| Step 2 | On Compute page, choose the pod that includes the Cisco UCS Manager account for which you want to view the topology. |
| Step 3 | Click Compute Accounts. |
| Step 4 | Click the row of the account. |
| Step 5 | Click View Connectivity.
The Topology View - UCS Device Connectivity dialog box is displayed with a view of the topology and connectivity of the devices in the Cisco UCS Domain. |
| Step 6 | If desired, you can modify the following view options:
|
| Step 7 | Click Close to return to the Compute Accounts tab. |
Exporting the Configuration of a Cisco UCS Manager Account
Cisco UCS Director exports a file named Ucs-Timestamp-configuration.zip to the location configured for downloads in your browser.
| Step 1 | Choose . |
| Step 2 | On Compute page, choose the pod that includes the Cisco UCS Manager account for which you want to export the configuration. |
| Step 3 | Click Compute Accounts. |
| Step 4 | Click the row of the account. |
| Step 5 | From the More Actions drop-down menu, choose Export Configuration. |
| Step 6 | On the Export UCS Configuration screen, click Submit. |
| Step 7 | When the configuration export is complete, click Close. |
Importing the Configuration of a Cisco UCS Manager Account
You can import a configuration that has been exported from a Cisco UCS Manager account in Cisco UCS Director or from Cisco UCS Manager.
![]() Note | When you import a configuration into a Cisco UCS Manager account, you overwrite any existing configuration in that account. |
| Step 1 | Choose . | ||||||
| Step 2 | On Compute page, choose the pod that includes the Cisco UCS Manager account for which you want to export the configuration. | ||||||
| Step 3 | Click Compute Accounts. | ||||||
| Step 4 | Click the row of the account. | ||||||
| Step 5 | Click Import Configuration. | ||||||
| Step 6 | On the Upload Configuration screen, do the following: | ||||||
| Step 7 | On the Select Configuration screen, check one of the following check boxes:
| ||||||
| Step 8 | Click Submit. | ||||||
| Step 9 | When the configuration import is complete, click Close. |
Selective Server Management
When you add a Cisco UCS Manager account to a pod, you can choose how you want Cisco UCS Director to manage the servers for that account. You can choose one of the following:
- All Servers
-
All servers are managed by Cisco UCS Director. This option is the default.
- Selected Servers
-
Only selected servers are managed by Cisco UCS Director. You can add and remove servers from the managed server list as needed.
![]() Note | Server license usage includes servers in Managed, Transition, and Decommissioned states. It does not include unmanaged servers. |
- Guidelines and Limitations for Selective Server Management
- Selecting a Server for Management
- Unmanaging a Server
Guidelines and Limitations for Selective Server Management
When you configure selective server management be aware of the following guidelines and limitations.
Changes to the Server Management Option
If you change the server management setting for an existing Cisco UCS Manager account from All Servers to Selected Servers, Cisco UCS Director moves all servers to the Unmanaged state. Initially, the servers are moved to a Transition state and removed from the servers report. Unless you select one or more servers and manually move them to the Managed state, all servers remain in that Transition state for 48 hours before Cisco UCS Director completes the move to the Unmanaged state. While a server is in Transition state, it is counted in your license usage.
If you change the server management setting for an existing Cisco UCS Manager account from Selected Servers to All Servers, Cisco UCS Director moves all servers to the Managed state.
Server Pools
Cisco UCS Director displays only the managed servers in a server pool, but the size of the pool includes all servers. For example, if a server pool contains two servers and only one server is managed by Cisco UCS Director, all server pool reports and actions on that pool display only one (managed) server. However, the pool size is displayed as two.
Service Profiles
Cisco UCS Director does not display service profiles that are associated with unmanaged servers. Service profiles are displayed only when the server is managed by Cisco UCS Director.
If you use Cisco UCS Manager to associate a service profile with a server pool that has servers that are not managed by Cisco UCS Director, you cannot perform any further tasks on that service profile or server in Cisco UCS Director. To manage that server or service profile, you must add a Manage Server task to the appropriate orchestration workflows.
Selecting a Server for Management
Configure the selective server management setting for the Cisco UCS Manager account as Selected Servers to be able to choose which servers you want Cisco UCS Director to manage.
| Step 1 | Choose . |
| Step 2 | On Compute page, choose the pod that includes the Cisco UCS Manager account. |
| Step 3 | Click UCS Discovered Servers.
This screen displays all servers in the Cisco UCS domain discovered Cisco UCS Manager. |
| Step 4 | Click Manage Servers. |
| Step 5 | On the Manage Servers screen, do the following:
Cisco UCS Director moves the selected servers to the Managed state. |
Unmanaging a Server
If you have configured the server management option in a Cisco UCS Manager account for Selected Servers, you can unmanage servers that you no longer want to manage through Cisco UCS Director.
| Step 1 | Choose . |
| Step 2 | On Compute page, choose the pod that includes the Cisco UCS Manager account. |
| Step 3 | Click UCS Discovered Servers.
This screen displays all servers in the Cisco UCS domain discovered by Cisco UCS Manager. |
| Step 4 | Click Unmanage Servers. |
| Step 5 | In the
Unmanage
Servers dialog box, do the following:
Cisco UCS Director moves the selected servers to the Transition state and removes them from the servers report. The servers remain in that Transition state for 48 hours before Cisco UCS Director completes the move to the Unmanaged state. While a server is in Transition state, it is counted in your license usage. |
Registration of a Cisco UCS Manager Account with Cisco UCS Central
When you add a Cisco UCS Central account, Cisco UCS Director can use that account to manage all registered Cisco UCS domains. You can also use Cisco UCS Director to register a Cisco UCS Manager account with a Cisco UCS Central account.
You can also choose whether you want to create and manage policies, service profiles, and service profile templates through the Cisco UCS Central account or the Cisco UCS Manager account by designating them as one of the following:
- Prerequisites for Cisco UCS Central
- Registering a Cisco UCS Manager Account with Cisco UCS Central
- Unregistering a Cisco UCS Manager Account from Cisco UCS Central
- Making a Policy, Service Profile, or Service Profile Template Global
- Making a Policy, Service Profile, or Service Profile Template Local
Prerequisites for Cisco UCS Central
Before you register a Cisco UCS Manager account with a Cisco UCS Central account, do the following:
-
Configure an NTP server and the correct time zone in Cisco UCS Director, Cisco UCS Manager, and Cisco UCS Central to ensure that they are in sync. If the time and date in one or more of them are out of sync, the registration with Cisco UCS Central may fail.
-
Obtain the hostname or IP address of a Cisco UCS Central account in Cisco UCS Director.
-
Obtain the shared secret that you configured when you deployed Cisco UCS Central.
Registering a Cisco UCS Manager Account with Cisco UCS Central
Unregistering a Cisco UCS Manager Account from Cisco UCS Central
When you unregister a Cisco UCS Manager account from Cisco UCS Central, the Cisco UCS Manager account no longer receives updates to global policies.
Making a Policy, Service Profile, or Service Profile Template Global
Configure a policy, service profile, or service profile template as global through the Cisco UCS Manager account.
Register the Cisco UCS Manager account with the Cisco UCS Central account.
| Step 1 | Choose . |
| Step 2 | On Compute page, choose the pod that includes the Cisco UCS Manager account. |
| Step 3 | Navigate to where the policy is located. |
| Step 4 | Click the row for the policy, service profile, or service profile template that you want to make global. |
| Step 5 | From the More Actions drop-down menu, choose Use Global.
For some service profiles or policies, click the drop-down menu button and choose Use Global from the menu. |
| Step 6 | On the Use Global screen, click Submit. |
Making a Policy, Service Profile, or Service Profile Template Local
Configure a policy, service profile, or service profile template as local through the Cisco UCS Manager account.
| Step 1 | Choose . |
| Step 2 | On Compute page, choose the pod that includes the Cisco UCS Manager account. |
| Step 3 | Click Service profile, or Organization. |
| Step 4 | Click the row in the table for the policy, service profile, or service profile template that you want to make local. |
| Step 5 | From the More Actions drop-down menu, choose Use Local.
For some service profiles or policies, click the drop-down menu button and choose Use Local from the menu. |
| Step 6 | In the Use Local dialog box, click Submit. |
Organizations
Organizations in a Multitenancy Environment
Multi-tenancy allows you to divide the large physical infrastructure of an Cisco UCS domain into logical entities known as organizations. As a result, you can achieve a logical isolation between organizations without providing a dedicated physical infrastructure for each organization.
You can assign unique resources to each tenant through the related organization in the multi-tenant environment. These resources can include different policies, pools, and quality of service definitions. You can also implement locales to assign or restrict user privileges and roles by organization, if you do not want all users to have access to all organizations.
If you set up a multi-tenant environment, all organizations are hierarchical. The top-level organization is always root. The policies and pools that you create in root are system-wide and are available to all organizations in the system. However, any policies and pools created in other organizations are only available to organizations that are above it in the same hierarchy. For example, if a system has organizations named Finance and HR that are not in the same hierarchy, Finance cannot use any policies in the HR organization, and HR cannot access any policies in the Finance organization. However, both Finance and HR can use policies and pools in the root organization.
If you create organizations in a mult-itenant environment, you can also set up one or more of the following for each organization or for a sub-organization in the same hierarchy:
The root organization is always the top level organization.
Creating an Organization
You can create a top-level organization which is the root. The policies and pools created in this root are system-wide and are available to all organizations in the system.
Locales
Each locale defines one or more organizations to which a user is allowed access, and access would be limited to the organizations specified in the locale. One exception to this rule is a locale without any organizations, which gives unrestricted access to system resources in all organizations.
A Cisco UCS domain can contain up to 48 locales. Any locales configured after the first 48 are accepted, but will be inactive with faults raised.
You can hierarchically manage organizations. A user that is assigned at a top-level organization has automatic access to all organizations under it. For example, an Engineering organization can contain a Software Engineering organization and a Hardware Engineering organization. A locale containing only the Software Engineering organization has access to system resources only within that organization. A locale that contains the Engineering organization has access to the resources for both the Software Engineering and Hardware Engineering organizations.
Creating a Locale
Time Zones
Cisco UCS requires a domain-specific time zone setting and an NTP server to ensure the correct time displays in Cisco UCS Manager. If you do not configure time zones, the time might not display correctly.
In addition, if your environment includes Cisco UCS Central, you must configure an NTP server and the correct time zone in Cisco UCS Manager and Cisco UCS Central to ensure that they are in sync. If the time and date in the Cisco UCS domain and Cisco UCS Central are out of sync, the registration might fail.
Adding a Time Zone
Cloning a Policy
You can clone some policies and create a copy with the same settings as the original policy.
| Step 1 | Choose . |
| Step 2 | On Compute page, choose the pod that includes the Cisco UCS Manager account. |
| Step 3 | Navigate to where the policy is located.
For example, if you want to clone a boot policy, click Organizations, click the organization in which you want to clone a policy, and then click View Details. |
| Step 4 | Click the tab
for the type of policy that you want to clone.
For example, if you want to clone a boot policy, click Boot Policies. |
| Step 5 | Choose the policy that you want to clone and from More Actions drop-down menu, choose Clone. |
| Step 6 | Change the name of the policy and, if desired, the values of the other fields. |
| Step 7 | Click Submit. |
Deleting a Pool, Policy, or Other Object
The method you use to delete a pool, policy, or other object, such as a VLAN, is the same for all objects.
![]() Note | Before you delete an object, ensure that it is not used or referenced by another object in the system. For example, before you delete a network policy, ensure that a service profile does not reference that policy. |
| Step 1 | Choose . |
| Step 2 | On Compute page, choose the pod that includes the Cisco UCS Manager account. |
| Step 3 | Navigate to where the object is located.
For example, if you want to delete a VLAN, click VLANs. |
| Step 4 | Choose the object that you want to delete. |
| Step 5 | From More Actions drop-down menu, choose Delete. |
| Step 6 | Click Delete. |

Feedback