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:
This procedure provides a high-level summary of the steps involved in configuring a multi-node setup.
Note | Plan your multi-node setup carefully. You can only change a service node to a primary node. You cannot change any other type of node after you configure it. For example, you cannot reconfigure a primary node as a service node or an inventory database node as a monitoring database node. |
Step 1 | Deploy a
Cisco
UCS Director
VM for each node in the multi-node setup.
For more information, see the relevant installation and upgrade guide. For example, if your multi-node setup, includes a primary node, an inventory database, a monitoring database, and three service nodes, deploy six Cisco UCS Director VMs. | ||
Step 2 | In the
Cisco
UCS Director
shelladmin, configure the nodes in the following order:
| ||
Step 3 | Update the
license file in the
Cisco
UCS Director
node that will be the primary node.
You do not need to update the license file on any other node. See the "Updating the License" topic in Cisco UCS Director Installation on VMware vSphere. | ||
Step 4 | In
Cisco
UCS Director
on the primary node, configure the system tasks as follows:
For more information, see System Tasks. |
The inventory and monitoring databases must be up and running before you create the primary node.
Note | Do not run any daemons on the primary database. |
The inventory and monitoring databases must be up and running before you create the primary node.
You can enable automatic redirection from a service node to a primary node. Whenever users try to log on to the Cisco UCS Director appliance from a service node, the automatic redirection takes the user to the appliance in the primary node. To enable automatic redirection, do the following in the Cisco UCS Director appliance on the primary node. Specifically, add the primary node IP Address in the Mail Setup pane.
The System Tasks tab displays all the system tasks that are currently available in Cisco UCS Director. However, this list of system tasks is linked to the type of accounts that you have created in Cisco UCS Director. For example, if you have logged in for the first time, then only a set of general system-related tasks or VMware related tasks are visible on this page. When you add accounts, such as rack accounts or Cisco UCS Manager accounts, system tasks related to these accounts are populated on this page.
Following are the tasks that you can complete from the System Tasks page:
View the available systems tasks—You can use the Expand and Collapse options to view all the system tasks that are available on this page. The tasks are categorized according to the accounts available in Cisco UCS Director. For example: Cisco UCS Tasks or NetApp Tasks.
Disable and enable system tasks—In circumstances when there are multiple processes or tasks running on the appliance, you can choose to disable a system task. If you do so, then until such time that you manually enable it, the system task will not run. This will affect the data populated in other reports. For example, if you disable an inventory collection system task, then reports that require this data may not display accurate data. In this case, you will have to manually run an inventory collection process, or enable the system task.
For more information, see Disabling or Enabling a System Task.
In a single-node setup, where there is only one server, all system tasks will run on this server. In a multi-node setup, where there are multiple servers configured, all system tasks, by default, run on the primary server. However, you can specify system tasks to run on the secondary servers. Following are the recommended steps to perform this task:
Ensure that the secondary servers are available in Cisco UCS Director as nodes. If the servers are not available, then you must add the servers as nodes. For more information, see Creating a Service Node.
Create a node pool from the available servers. For more information, see Creating a Node Pool.
Associate a node pool with the system task policy. For more information, see Assigning a Node Pool to a System Task Policy.
Select a system task, and associate it with a system-task policy. For more information, see Assigning a System Policy to a System Task.
Step 1 | On the menu bar, choose . |
Step 2 | Choose the Service Nodes tab. |
Step 3 | Click the Service Node Pools icon. The Service Node Pool dialog box displays. |
Step 4 | Click the + (plus) icon. The Add Entry to Service Node Pools dialog box displays. |
Step 5 | In the Name field, enter the node pool name. |
Step 6 | (Optional) In the Description field, enter a description of the node pool name. |
Step 7 | Click Submit. The node pool is created. |
As an administrator, you can choose to combine a few policies and create a system task policy, in addition to the default system task policy. You can group system tasks into a system task policy to later determine which system tasks are running on which node.
Step 1 | On the menu bar, choose . |
Step 2 | Choose the System Task Policy tab. |
Step 3 | Click the Add icon. The Add dialog box displays. |
Step 4 | In the Name field, enter the name that you gave the system task policy. |
Step 5 | (Optional) In the Description field, enter a description of the system task policy. |
Step 6 | From the Node Pool drop-down list, choose the node pool to which this system task policy belongs. |
Step 7 | Click
Submit.
The selected node pool now belongs to the newly created system task policy. |
Step 1 | On the menu bar, choose . | ||
Step 2 | Choose the System Task Policy tab. | ||
Step 3 | Select an existing system task policy from the
Name column and click the
Edit icon. The
Edit dialog box displays.
| ||
Step 4 | From the Node Pool drop-down list, choose a node pool to which this System Task Policy belongs. | ||
Step 5 | Click
Submit.
The selected node pool now belongs to the system task policy. |
Step 1 | On the menu bar, choose . | ||||||||||||||||||||||
Step 2 | Choose the Service Nodes tab. | ||||||||||||||||||||||
Step 3 | Click the Add (+) | ||||||||||||||||||||||
Step 4 | In the
Service Node dialog box, complete the following fields:
| ||||||||||||||||||||||
Step 5 | Click Submit. |
Step 1 | On the menu bar, choose . | ||
Step 2 | Choose the System Task tab. | ||
Step 3 | Choose a folder that contains system tasks. Click the folder arrow to expand its tasks.
| ||
Step 4 | Choose the task and click the
Manage Task icon.
The Manage Task dialog box appears. | ||
Step 5 | From the Task Execution drop-down list, choose Enable. | ||
Step 6 | From the System Task Policy drop-down list, choose a system policy. | ||
Step 7 | Click
Submit.
The system task is assigned to the selected system policy. |
Cisco UCS Director includes a few system tasks that cannot be run remotely on a service node. Also, you can assign a system policy remotely from the local host or the primary node.
In addition, you can search and select a specific system task, and run it immediately in the system.
Step 1 | On the menu bar, choose . | ||
Step 2 | Choose the System Task tab. | ||
Step 3 | Choose a folder that contains one or more system tasks. Click the folder arrow to expand its tasks.
| ||
Step 4 | Choose the task and click the
Manage Task icon.
The Manage Task dialog box appears. | ||
Step 5 | To disable a system task, from the Task Execution drop-down list, choose Disable. | ||
Step 6 | To enable a system task, from the Task Execution drop-down list, choose Enable. | ||
Step 7 | Click Submit. |
This procedure provides a high-level summary of the steps required to back up a multi-node setup.
The backup procedure requires you to first stop the Cisco services. This must be done before you work with the Monitoring and Inventory databases. Then you back up the databases, after which you re-start the services, starting with the Primary node.
To back up the databases, you use an FTP server, for which you will need:
1. Shut down the services for both the Primary and Service nodes. Use the, Stop Services Shell potion.
2. Back up the Monitoring database. Use the Backup Database Shell option.
3. Backup the Inventory database. Use the Backup Database Shell option.
4. Start the Services (Service nodes first, followed by Primary node). Use the Start Services Shell option.
Step 1 | Shut down the services for both the Primary and Service nodes. Use the, Stop Services Shell potion. |
Step 2 | Back up the Monitoring database. Use the Backup Database Shell option. |
Step 3 | Backup the Inventory database. Use the Backup Database Shell option. |
Step 4 | Start the Services (Service nodes first, followed by Primary node). Use the Start Services Shell option. |
This procedure provides a high-level summary of the steps required to restore a multi-node setup.
The restore procedure requires you to first stop the Cisco services. This must be done before you work with the Monitoring and Inventory databases. Then you restore the databases, after which you re-start the services, starting with the Primary node.
To restore the databases, you use an FTP server, for which you will need:
1. Shut down the services for both the Primary and Service nodes. Use Shell option 3, Stop Services.
2. Restore the Monitoring database. Use the Shell Restore Database option.
3. Restore the Inventory database. Use the Shell Restore Database option.
4. Start the Services (Service nodes first, followed by Primary node). Use Shell option 4, Start Services.
Step 1 | Shut down the services for both the Primary and Service nodes. Use Shell option 3, Stop Services. |
Step 2 | Restore the Monitoring database. Use the Shell Restore Database option. |
Step 3 | Restore the Inventory database. Use the Shell Restore Database option. |
Step 4 | Start the Services (Service nodes first, followed by Primary node). Use Shell option 4, Start Services. |
This procedure provides a high-level summary of the steps required to remove a service node from a multi-node setup.
The removal procedure requires you to first stop the Cisco services. This must be done before you remove a service node from Monitoring and Inventory databases.
Step 1 | Shut down the services for both the Primary node and the Service node(s). Use Shell option 3, Stop Services. |
Step 2 | Start the services on the Service node(s) that you want to be active and operational. Use Shell option 4, Start Services. |
Step 3 | Start the services on the Primary node. Use Shell option 4, Start Services. |
Step 4 | Using the Cisco UCS Director GUI, delete the Service node that you want to remove. This removes the respective Service node from the database. |
This procedure backs up and restores only the selected database tables required for each of the inventory database and the monitoring database.
Step 1 | In the shelladmin, choose Login as Root to log in to the upgraded Cisco UCS Director. | ||
Step 2 | Back up the
database tables required for the inventory database, as follows:
| ||
Step 3 | Back up the
database tables required for the monitoring database, as follows:
| ||
Step 4 | Deploy a
Cisco
UCS Director
VM for each node in the multi-node setup.
For example, if your multi-node setup, includes a primary node, an inventory database, a monitoring database, and three service nodes, deploy six Cisco UCS Director VMs. | ||
Step 5 | In the
shelladmin, configure the nodes in the following order:
| ||
Step 6 | In the shelladmin, choose Stop services to stop the Cisco UCS Director services on the primary node and all service nodes. | ||
Step 7 | Restore the
database to the inventory database, as follows:
| ||
Step 8 | Restore the
database to the monitoring database, as follows:
| ||
Step 9 | Choose
Start services on the primary node and all
service nodes to start the
Cisco
UCS Director
services.
After you log in to the primary node, all data from the database in the Cisco UCS Director standalone appliance should be available. |