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:
The following is a high-level summary of the steps involved in configuring a multi-node setup.
Note | Plan your multi-node setup carefully. Your ability to reconfigure the nodes once they are set up is very limited. See Best Practices for a Multi-Node Setup. |
Step 1 | Deploy a
Cisco
UCS Director
VM for each node in the multi-node setup.
For more information, see the relevant installation 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 the Installation Guide for this release. | ||
Step 4 | In
Cisco
UCS Director
on the primary node, configure the system tasks as follows:
For more information, see System Tasks. |
Step 1 | Log on to the Cisco
UCS Director shelladmin on the inventory database node.
| ||
Step 2 | From the menu, choose Configure Multi-Node Setup (Advanced Deployment) and press Enter. | ||
Step 3 | From the menu, choose Current Node to configure the current node. | ||
Step 4 | When prompted, enter y to continue with the multi-node configuration. | ||
Step 5 | From the menu, choose the appropriate deployment type option: Small, Medium, or Large. See Minimum System Requirements for a Multi-Node Setup. | ||
Step 6 | From the menu, choose Configure as Inventory DB and press Enter. | ||
Step 7 | When prompted, enter y to configure the node as the Inventory Database. | ||
Step 8 | When prompted, enter y to reinitialize the database.
| ||
Step 9 | When prompted, enter and confirm the admin password for the inventory MySQL database. | ||
Step 10 | When prompted, enter and confirm the root password for the inventory MySQL database. | ||
Step 11 | When prompted, enter y to log out so that the database changes can take effect. | ||
Step 12 | After you are logged out, log back on to the Cisco
UCS Director shelladmin on the Inventory Database node.
| ||
Step 13 | To verify that the services for the Inventory Database are up and running, choose Display Services Status and press Enter.
You should see the following lines: Database IP Address State Client Connections ------------- ------------ -------- -------------- ------------ Inventory 127.0.0.1 UP 172.22.234.10 14 172.22.234.13 14 Volume Mounted on Size Used Available %Use Usage --------------------- ------------- ------- -------- --------- ------ ------------- /dev/sda3 / 97G 5.5G 86G 6% NORMAL /dev/sda1 /boot 194M 38M 147M 21% NORMAL infradb_vg-infradb_lv /infradb 99G 3.8G 95G 4% NORMAL Press return to continue ... |
Step 1 | Log on to the Cisco
UCS Director shelladmin on the monitoring database node.
| ||
Step 2 | From the menu, choose Configure Multi-Node Setup (Advanced Deployment) and press Enter. | ||
Step 3 | From the menu, choose Current Node to configure the current node. | ||
Step 4 | When prompted, enter y to continue with the multi-node configuration. | ||
Step 5 | From the menu, choose the appropriate deployment type option: Small, Medium, or Large. See Minimum System Requirements for a Multi-Node Setup. | ||
Step 6 | From the menu, choose Configure as Monitoring DB and enter Enter. | ||
Step 7 | When prompted, enter y to configure the node as the Monitoring Database. | ||
Step 8 | When prompted, enter y to reinitialize the database. | ||
Step 9 | When prompted, enter and confirm the admin password for the inventory MySQL database. | ||
Step 10 | When prompted, enter and confirm the root password for the inventory MySQL database. | ||
Step 11 | When prompted, enter y to log out so that the database changes can take effect. | ||
Step 12 | After you are logged out, log back on to the Cisco
UCS Director shelladmin on the Monitoring Database node.
| ||
Step 13 | To verify that the services for the Monitoring Database are up and running, choose Display Services Status and press Enter.
You should see the following lines: Database IP Address State Client Connections ------------- ------------ -------- -------------- ------------ Monitoring 127.0.0.1 UP 172.22.234.10 10 172.22.234.13 9 Volume Mounted on Size Used Available %Use Usage --------------------- ------------- ------- -------- --------- ------ ------------- /dev/sda3 / 97G 5.5G 86G 6% NORMAL /dev/sda1 /boot 194M 38M 147M 21% NORMAL infradb_vg-infradb_lv /infradb 99G 3.8G 95G 4% NORMAL Press return to continue ... |
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 node. |
Step 1 | Log on to the
Cisco
UCS Director
shelladmin on the primary node.
| ||
Step 2 | From the menu, choose Configure Multi-Node Setup (Advanced Deployment) and press Enter. | ||
Step 3 | From the menu, choose Current Node to configure the current node. | ||
Step 4 | When prompted, press y to continue with the configuration. | ||
Step 5 | From the menu, choose the appropriate deployment type option: Small, Medium, or Large. See Minimum System Requirements for a Multi-Node Setup. | ||
Step 6 | From the menu, choose Configure as Primary Node and press Enter. | ||
Step 7 | When prompted, enter y to configure the node as the Primary Node. | ||
Step 8 | When prompted, choose the IP version to configure, either IPv4 or IPv6, and press Enter. | ||
Step 9 | At the
Provide
Inventory DB IP prompt, enter the IP address assigned to the
Cisco
UCS Director
VM for the inventory database.
This step registers the VM as a primary node with the inventory database. | ||
Step 10 | At the
Provide
Monitoring DB IP prompt, enter the IP address assigned to the
Cisco
UCS Director
VM for the monitoring database.
This step registers the VM as a primary node with the monitoring database. | ||
Step 11 | When prompted, enter and confirm the admin password to log on to the inventory MySQL database. | ||
Step 12 | When prompted, enter and confirm the root password to log on to the inventory MySQL database.
| ||
Step 13 | When prompted, enter and confirm the admin password to log on to the monitoring MySQL database. | ||
Step 14 | When prompted, enter and confirm the root password to log on to the monitoring MySQL database.
| ||
Step 15 | When prompted, enter y to log out so that changes to the node can take effect. | ||
Step 16 | After you are logged out, log back on to the Cisco
UCS Director shelladmin on the Primary node.
| ||
Step 17 | To verify that
the services for the primary node are up and running, choose
Display Services Status and press
Enter.
You should see the following lines: Service State PID %CPU %MEM tELAPSED #Threads ------------- ------- -------- ----------------------------------- broker UP 23702 0.1 1.2 09:07:46 30 controller UP 24267 0.0 0.9 09:07:01 73 eventmgr UP 24515 0.4 5.5 09:06:15 42 idaccessmgr UP 24656 0.4 5.4 09:06:10 78 inframgr UP 24792 2.1 23.4 09:06:03 166 websock UP 24868 0.0 0.0 09:05:58 1 tomcat UP 24922 0.1 4.1 09:05:52 54 flashpolicyd UP 24952 0.0 0.0 09:05:36 1 Database IP Address State Client Connections ------------- ------------ -------- -------------- ------------ Inventory 172.22.234.14 UP 172.22.234.10 15 172.22.234.13 14 Monitoring 172.22.234.17 UP 172.22.234.10 11 172.22.234.13 9 Volume Mounted on Size Used Available %Use Usage --------------------- ------------- ------- -------- --------- ------ ------------- /dev/sda3 / 97G 5.6G 86G 7% NORMAL /dev/sda1 /boot 194M 38M 147M 21% NORMAL infradb_vg-infradb_lv /infradb 99G 3.8G 95G 4% NORMAL Press return to continue ...
|
The inventory and monitoring databases and the primary node must be up and running before you create a secondary node.
Step 1 | Log on to the
Cisco
UCS Director
shelladmin on the service node.
| ||
Step 2 | From the menu, choose Configure Multi-Node Setup (Advanced Deployment) and press Enter. | ||
Step 3 | From the menu, choose Current Node to configure the current node. | ||
Step 4 | When prompted, press y to continue with the configuration. | ||
Step 5 | From the menu, choose the appropriate deployment type option: Small, Medium, or Large. See Minimum System Requirements for a Multi-Node Setup. | ||
Step 6 | From the menu, choose Configure as Service Node and press Enter. | ||
Step 7 | When prompted, enter y to configure the node as a Secondary Node. | ||
Step 8 | When prompted, choose the IP version to configure, either IPv4 or IPv6, and press Enter. | ||
Step 9 | At the
Provide
Inventory DB IP prompt, enter the IP address assigned to the
Cisco
UCS Director
VM for the inventory database.
This step registers the VM as a service node with the inventory database. | ||
Step 10 | At the
Provide
Monitoring DB IP prompt, enter the IP address assigned to the
Cisco
UCS Director
VM for the monitoring database.
This step registers the VM as a service node with the monitoring database. | ||
Step 11 | When prompted, enter and confirm the admin password to log on to the inventory MySQL database. | ||
Step 12 | When prompted, enter and confirm the root password to log on to the inventory MySQL database.
| ||
Step 13 | When prompted, enter and confirm the admin password to log on to the monitoring MySQL database. | ||
Step 14 | When prompted, enter and confirm the root password to log on to the monitoring MySQL database.
| ||
Step 15 | When prompted, enter y to log out so that changes to the node can take effect. | ||
Step 16 | After you are logged out, log back on to the Cisco
UCS Director shelladmin on the secondary node.
| ||
Step 17 | To verify that
the services for the service node are up and running, choose
Display Services Status and press
Enter.
You should see the following lines: Service State PID %CPU %MEM tELAPSED #Threads ------------- ------- -------- ----------------------------------- broker UP 22445 0.1 1.2 09:18:59 30 controller UP 22576 0.0 0.8 09:18:14 74 eventmgr UP 22727 0.4 5.6 09:17:28 43 idaccessmgr UP 22869 0.4 5.1 09:17:23 43 inframgr UP 23005 1.7 17.6 09:17:16 64 websock UP 23081 0.0 0.0 09:17:11 1 tomcat UP 23135 0.1 4.1 09:17:05 52 flashpolicyd UP 23165 0.0 0.0 09:16:49 1 Database IP Address State Client Connections ------------- ------------ -------- -------------- ------------ Inventory 172.22.234.14 UP 172.22.234.10 14 172.22.234.13 15 Monitoring 172.22.234.17 UP 172.22.234.10 10 172.22.234.13 10 Volume Mounted on Size Used Available %Use Usage --------------------- ------------- ------- -------- --------- ------ ------------- /dev/sda3 / 97G 5.6G 86G 7% NORMAL /dev/sda1 /boot 194M 38M 147M 21% NORMAL infradb_vg-infradb_lv /infradb 99G 3.8G 95G 4% NORMAL Press return to continue ...
| ||
Step 18 | Repeat this procedure for every service 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, add the primary node IP address in the Mail Setup pane in the Cisco UCS Director appliance on the primary node. Do the following:
The System Tasks screen 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 screen:
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 run on this server. In a multi-node setup, where there are multiple servers configured, all system tasks run on the primary server by default. 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. See Creating a Service Node.
Create a node pool from the available servers. See Creating a Node Pool.
Create a system task policy, and associate it with a node policy. See Creating a System Task Policy.
Associate a node pool with the system task policy. See Assigning a Node Pool to a System Task Policy.
Select a system task, and associate it with a system-task policy. See Assigning a System Policy to a System Task.
Step 1 | Choose . |
Step 2 | On the System page, click Service Nodes. |
Step 3 | Click Service Node Pools. |
Step 4 | On the Service Node Pool screen, click Add. |
Step 5 | On the Add Entry to Service Node Pools screen enter the node pool name in the Name field. |
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 | Choose . |
Step 2 | On the System page, click System Task Policy. |
Step 3 | Click Add. |
Step 4 | On the Add screen, enter the name that you gave the system task policy in the Name field. |
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 | Choose . | ||
Step 2 | On the System page, click System Task Policy. | ||
Step 3 | Click the row with the system task policy to which you want to assign a node pool. | ||
Step 4 | Click Edit.
| ||
Step 5 | From the Node Pool drop-down list, choose a node pool that you want to assign to the system task policy. | ||
Step 6 | Click
Submit.
The selected node pool now belongs to the system task policy. |
Step 1 | Choose . | ||||||||||||||||||||||
Step 2 | On the System page, click Service Nodes. | ||||||||||||||||||||||
Step 3 | Click Add. | ||||||||||||||||||||||
Step 4 | On the Service Node screen, complete the following fields:
| ||||||||||||||||||||||
Step 5 | Click Submit. |
Step 1 | Choose . | ||
Step 2 | On the System page, click System Tasks. | ||
Step 3 | Choose a folder that contains system tasks. Click the folder arrow to expand its tasks.
| ||
Step 4 | Choose the task and click Manage Task.
The Manage Task screen 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 | Choose . | ||
Step 2 | On the System page, click System Tasks. | ||
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 Manage Task.
The Manage Task screen 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 option.
2. Back up the Monitoring database. Use the Backup Database Shell option.
3. Back up the Inventory database. Use the Backup Database Shell option.
4. Start the Services (Service nodes first, followed by the 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 option. |
Step 2 | Back up the Monitoring database. Use the Backup Database Shell option. |
Step 3 | Back up the Inventory database. Use the Backup Database Shell option. |
Step 4 | Start the Services (Service nodes first, followed by the 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 need:
1. Shut down the services for both the Primary and Service nodes. Use the Stop Services shell option.
2. Restore the Monitoring database. Use the Restore Database shell option.
3. Restore the Inventory database. Use the Restore Database shell option.
4. Start the Services (Service nodes first, followed by the 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 option. |
Step 2 | Restore the Monitoring database. Use the Restore Database shell option. |
Step 3 | Restore the Inventory database. Use the Restore Database shell option. |
Step 4 | Start the Services (Service nodes first, followed by the Primary node). Use the Start Services shell option. |
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 nodes. Use the Stop Services shell option. |
Step 2 | Start the services on the Service node(s) that you want to retain. Use the Start Services shell option. |
Step 3 | Start the services on the Primary node. Use the Start Services shell option. |
Step 4 | Using the Cisco UCS Director GUI, delete the Service node that you want to remove. This removes the 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 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 on 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.