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.
Use the following table as a guide to install .
Step | Description | For more information |
---|---|---|
Step 1 |
For a production environment, install multinode or standalone . |
Multinode Installation |
Step 2 | Create the Cisco Hosted Mediation Fulfillment device. | Create the HCM-F Device |
Step 3 | Create provider. | Create a Provider |
A WebProxy node installs only the front-end web server, with the ability to distribute load among multiple middleware nodes.
A Unified node consists of the Application and Database roles on one node. For geo-redundancy, there are two Unified nodes in the Primary Site and two Unified nodes in the Disaster Recovery (DR) Site.
If you received (Unified CDM) 10.x on DVD, extract the platform-install OVA and the CUCDM template file from the CUCDM ISO file.
If you are downloading Cisco HCM-Core from Cisco.com, download the product ISO file. Mount the product ISO and extract the platform-install OVA and the CUCDM template file.
Optionally, download or extract language pack template files to support languages other than English.
Step 1 | Install the
WebProxy instances.
For each WebProxy instance, create a new VM using the platform-install OVA. Use the instructions shown in Install Cisco Unified Communications Domain Manager 10.x Details. For role, select (3) WebProxy. Specify the appropriate data center (Primary/DR site) for each WebProxy instance. |
Step 2 | Install the
Unified instances.
For each Unified instance, create a new VM using the platform-install OVA. Use the instructions shown in Install Cisco Unified Communications Domain Manager 10.x Details. For role, select (2) Unified. Specify the appropriate data center (Primary/DR Site) for each Unified instance. The following Unified nodes are required in the cluster: |
Step 3 | Check for needed security updates by running the security check command on each node. If at least one update is required for any node, run the security update commands on the node. |
Step 4 | Install
VMware tools on each node.
|
Step 5 | Prepare each node to be added to the cluster. On each WebProxy and Unified node, except for the primary Unified node, run the cluster prepnode command. |
Step 6 | Add nodes to the cluster. |
Step 7 | Add the
network domain.
|
Step 8 | Reboot the cluster nodes with the cluster run all system reboot command. |
Step 9 | Provision the
cluster.
|
Step 10 | Initialize the database and clear all data with the cleardown command on the primary database node. |
Step 11 | Import the
template.
|
Step 12 | Install the
Macro_Update.template file on secondary nodes.
|
Step 13 | Review the output from the app template command and confirm that the message Script /opt/platform/admin/home/template_xxxxxx/install_script completed successfully appears. |
Step 14 | (Optional)
Install language templates for languages other than English.
|
If you have received Cisco Unified Communications Domain Manager 10.6(x) on DVD, extract the platform-install OVA and template files from the .
If you are downloading Cisco HCM-Core from Cisco.com, download the product ISO file. Mount the product ISO and extract the platform-install OVA and template files.
Step 1 | Create a new VM using the platform-install OVA. Use the instructions shown in Install Cisco Unified Communications Domain Manager 10.x Details. When prompted for role, select Standalone. |
Step 2 | After the system has rebooted, sign-in as the platform user. |
Step 3 | Issue the system provision command. |
Step 4 | Initialize the database and clear all data with the cleardown command. |
Step 5 | Issue the network domain <your_domain> command. |
Step 6 | Issue the security update command. |
Step 7 | Issue the system reboot command. |
Step 8 | Import the
template.
|
Step 9 | Review the output from the app template command and confirm that the message Script /opt/platform/admin/home/template_xxxxxx/install_script completed successfully appears. |
Step 10 | Issue the system reboot command. |
Step 11 | Install
VMware tools:
|
The system is made available as an OVA file that can be imported into VMware vCenter Server. One OVA file is used to deploy all the functional roles. The specific role is chosen when the installation wizard is run. The administrator should set up the hardware settings on the VMware GUI.
Step 1 | Log in to vSphere to access the ESXi Host. |
Step 2 | Choose File > Deploy OVF Template. |
Step 3 | Choose Source, browse to the location of the .ova file, and click Next. |
Step 4 | On the Name and Location page, enter a Name for this server. |
Step 5 | On the Deployment Configuration page, select the appropriate node type. |
Step 6 | Choose the Resource Pool where the VM will be located. |
Step 7 | Choose which Datastore will be used to deploy the new VM. |
Step 8 | Choose the appropriate Disk format to use when deploying the new VM. In production environments, "thick provisioning" is mandatory. Eager-zeroed thick provisioning is recommended. |
Step 9 | On the Network Mapping, choose your network on which this VM will reside. |
Step 10 | Do not select Power on after deployment. |
Step 11 | On the Ready to Complete page, click Finish to start the deployment. |
Step 12 | After the VM has been created, verify the memory, CPU, and disk settings against the requirements shown in Multinode Cluster Hardware Specifications. |
Step 13 | Power on the VM. |
Step 14 | Select the
following options in the installation wizard:
|
When the installation of the OVA is complete, a login prompt for the platform user is displayed.
What to Do Next
Return to Multinode Installation or Standalone Installation to complete the overall installation procedure.
After creating the HCM-F device, a data sync begins if there is a network connection and the NBI REST service is running on the HCM-F server.
If the initial sync is not working after following the previous steps, verify that the HCM-F REST API is working by browsing to the following: http://<hcmf_app_node_host>/sdr/rest/<hcmf_version>/entity/ServiceProvider. This command returns the JSON representation of the predefined ServiceProvider instance in the HCM-F Shared Data Repository (SDR). If you get an error, log in as administrator on the HCM-F app node CLI and verify that the REST service is running:
To display the services, run the command: utils service list.
In the output, you see Cisco HCS NBI REST SDR Web Service[STARTED].
If this service is not started, start it with the command: utils service start Cisco HCS NBI REST SDR Web Service
The provider hierarchy node in Cisco Unified Communications Domain Manager 10.6(x), the Service Provider name in SDR, and optionally a default provider administrator are created. All existing Cisco HCS System Administration-level dial plan schemas and schema groups are automatically cloned to the new provider. For more information on automatic cloning, see Cisco Hosted Collaboration Solution, Release 10.6(1) Dial Plan Management Guide for Cisco Unified Communications Domain Manager, Release 10.6(x).
Step 1 | Log in to Cisco Unified Communications Domain Manager 10.6(x) as provider admin. | ||||||||||||
Step 2 | Select . | ||||||||||||
Step 3 | Click Add. | ||||||||||||
Step 4 | Complete the following fields:
| ||||||||||||
Step 5 | Click Save. |
The reseller hierarchy node in Cisco Unified Communications Domain Manager 10.6(x), the reseller in SDR, and a default reseller admin are created.
Step 1 | Log in to Cisco Unified Communications Domain Manager 10.6(x) as provider admin or reseller admin. | ||||||||||||
Step 2 | Select . | ||||||||||||
Step 3 | Click Add. | ||||||||||||
Step 4 | Complete the following fields:
| ||||||||||||
Step 5 | Click Save. |
The customer hierarchy node in Cisco Unified Communications Domain Manager 10.6(x), the customer in SDR, and a default customer admin are created.
Step 1 | Log in to Cisco Unified Communications Domain Manager 10.6(x) as customer admin. | ||||||||
Step 2 | Select . | ||||||||
Step 3 | Click Add. | ||||||||
Step 4 | Complete the following fields:
| ||||||||
Step 5 | Select a Network Device List.
| ||||||||
Step 6 | Click Save. |
The site hierarchy node in Cisco Unified Communications Domain Manager 10.6(x), the location in Cisco Unified Communications Domain Manager 10.6(x), the customer location in SDR, and a default site admin are created.