This topic provides information and instructions for changing the default configuration settings of the Cisco HCS Provider. You must ensure that the configurations are set up for the Cisco HCS Provider to function correctly.
Before you begin
Ensure that you have completed the following tasks:
To change Cisco HCS configurations
- Log on to the BMC Remedy IT Service Management Console, and click Cisco Hosted Collaboration Solution > Configuration, as shown in the following figure:
- In the Configuration window, click Search, as shown in the following figure:
The configuration details of the Cisco HCS Provider are displayed, as shown in the following figure:

Change the configuration details of the Cisco HCS Provider according to the information in the following tables:
Click here to edit the General settings
| | | | |
---|
| | | | Specifies whether the sync functionality is enabled. If enabled, the sync functionality runs at the same time as any operation related to the specified Application Node Type. |
| | | | Specifies whether the sync functionality is enabled for all the hosts |
| | | <Application Type:Application node type> For example: CUCM:PUB You can specify multiple combination values separated by comma (,). For example: CUCM:PUB, CUCXN:CUCXN | Specifies the node types for which a core needs to be reserved while provisioning the application in the ESXi host. Note: It needs to match with the application type and application node type character lengths, specified in the host name configuration. |
| | | | Specifies the number of cores reserved for the selected node type |
| Datastore Storage Reservation (in GB) | | | Specifies the storage capacity (in GB) that must be kept unallocated while provisioning a VM in a datastore |
| | | | Specifies the hardware architecture supported for the applications. Recommended value is Unknown since infrastructure might be a mix of different hardware architecture. |
| Auto on-board Template Prefix | | Any alphanumeric value up to 255 characters (including - and _, but no other special characters permitted) | It is the prefix of the Cisco HCS Golden templates in vCenter. |
Click here to edit the Global Properties settings
Note
The global properties apply to every infrastructure resource available for provisioning Cisco HCS applications.
| | | |
---|
Allow chassis rule violation | | | Specifies whether the chassis anti-affinity rule violation is enabled |
Allow cluster rule violation | | | Specifies whether the cluster level anti-affinity rule violation is enabled. |
Allow host rule violation | | | Specifies whether the host-level anti-affinity rule violation is enabled |
Allow raid group rule violation | | | Specifies whether the raid group-level storage anti-affinity rule violation is enabled |
| | | Specifies whether the SAN-level storage anti-affinity rule violation is enabled |
Allow datastore rule violation | | | Specifies whether the datastore-level storage anti-affinity rule violation is enabled |
1 TRUE = Anti-affinity rules will not be considered while provisioning applications.
Click here to edit the Host name settings
Note
The host name settings apply to creation of custom host names.
| | | |
---|
| | | Specifies the prefix for the application cluster |
| | | Number of characters to be used from site ID for generating the host name |
| | | Number of characters to be used from enterprise ID for generating the host name |
| | | Number of characters to be used from application type tag in service blueprint |
| | | Number of digits to be appended to the cluster instance prefix |
| | | Number of characters to be used from application node type tag in service blueprint |
| | | |
| | | Maximum number of characters in the host name |
Click here to edit the Adapters settings
Note
If any adapter is preconfigured, use the same name in the configuration.
| | |
---|
| | Name of the VMware adapter as specified in the BMC Atrium Orchestrator Grid Manager |
| | Name of the Command Line adapter as specified in the BMC Atrium Orchestrator Grid Manager |
| | Name of the Web Service adapter as specified in the BMC Atrium Orchestrator Grid Manager |
| | Name of the HTTP adapter as specified in the BMC Atrium Orchestrator Grid Manager |
Click here to edit the Platform settings
Note
These values are populated by default, based on the BMC Cloud Lifecycle Management Platform Manager details. Change these values only if you have made any changes manually.
| | |
---|
| | User name to log on to the BMC Cloud Lifecycle Management Platform Manager |
| | Super user password to authenticate the superuser ID |
| | API URL to access the BMC Cloud Lifecycle Management Platform Manager server |
| | Polling count of a task in the BMC Cloud Lifecycle Management Platform Manager server |
Click here to edit the BNA Parameters settings
| | |
---|
| | URL to access BMC Network Automation Note: This value is populated by default, based on the BMC Network Automation environment details. Change it only if you have made a change manually. |
| | Password to authenticate BMC Network Automation Note: This value is populated by default, based on the BMC Network Automation environment details. Change it only if you have made a change manually. |
| | User name for logging on to BMC Network Automation Note: This value is populated by default, based on the BMC Network Automation environment details. Change it only if you have made a change manually. |
| | Name by which the Cube SP job is configured Note: Modify this name based on the BMC Network Automation settings. |
Unconfigure CUBE Job Name | | Name by which the Cube SP job is unconfigured Note: Modify this name based on the BMC Network Automation settings. |
Allow Unsigned Certificates | FALSE or TRUE Default value: FALSE | Specifies whether to install unsigned certificates automatically |
| FALSE or TRUE Default value: TRUE | Specifies whether to install certificates automatically |
Is Cube Configuration Enabled | FALSE or TRUE Default value: TRUE | Specifies whether the Cube SP configuration is enabled |
- Click Save to save the changed configuration settings.