[Index]
If VOSS Insights Arbitrator servers are configured at a hierarchy, you can manage the clusters and Arbitrator servers in a batch, for existing UC app clusters (CUCM and CUC) in VOSS Automate.
Note
At the time of writing (VOSS Automate 21.3), modification of any existing monitoring on UC Apps is not supported. However, once a CUCM or CUC server is created, use the Onboard/Offboard Asset tools to enable/disable monitoring.
In the VOSS Admin Portal, go to Apps Management > VOSS Insights > Onboard Assets.
Choose a Customer hierarchy.
From the Credential Type drop down, keep the default, ADMIN, or choose a different credential type.
Note
This field defines the credential type of the UC server to use for asset configuration on the Arbitrator.
View available CUCM and CUC clusters and Arbitrators, then select options in the Available fields and move these to the Selected fields in the relevant transfer boxes.
Click Save.
Related Topics
Additional Onboarding Tools for Single Clusters and Servers
VOSS Automate provides a number of additional views that are not, by default, exposed in the default menus, but which have access profiles enabled for Provider and higher-level administrators. These views allow you to onboard single assets.
You can add these views to the menus, if required:
These tools do not direct you to a particular hierarchy and the views allow you to carry out the tasks on the page by selecting the following:
The views offer the same functionality as the transfer boxes available via the Onboard Assets and Offboard Assets menus. However:
When assets are onboarded, the probe groups and profiles as shown in the tables below are added to the VOSS Assurance and Analytics arbitrator.
Note
For Unified CM and Unity Connection servers, only the ping monitor profile is added.
When assets are offboarded, these are similarly removed from the arbitrator.
PERFMON CUCM Group Profile | |
---|---|
Probe name | axlGetPerfmonCounters_CUCM_INTF (<CUCM Cluster name>) |
Probe Group Name | <customer_name>-CUCM Perfmon AXL (<CUCM Cluster name>) |
Frequency | 600 sec (10 min) |
For Publisher Server | Yes |
For Subscriber Server | No |
PERFMON CUC Group Profile | |
---|---|
Probe name | axlgetperfmon (<CUCxn Cluster name>) |
Probe Group Name | <customer_name>-Cisco Unity AXL (<CUCxn Cluster name>) |
Frequency | 300 sec (5 min) |
For Publisher Server | Yes |
For Subscriber Server | No |
RIS Group Profile | |
---|---|
Probe Group Name | 1-Cisco CUCM RIS CmDevice_creds |
Frequency | 300 sec (5 min) |
For Publisher Server | Yes |
For Subscriber Server | No |
PINGMON Group Profile | |
---|---|
Probe Group Name | 1b-PING Monitor |
Frequency | 300 sec (5 min) |
For Publisher Server | Yes |
For Subscriber Server | Yes |
VERSION Group Profile | |
---|---|
Probe Group Name | 4-Cisco CUCM Version |
Frequency | 86400 sec (24 hr) |
For Publisher Server | Yes |
For Subscriber Server | No |
RTMT Group Profile | |
---|---|
Probe Group Name | 5-Cisco RTMT |
Frequency | 1800 sec (30 min) |
For Publisher Server | Yes |
For Subscriber Server | No |
This tool onboards multiple Cisco UCM and Unity Cnnection cluster as assets onto multiple Assurance arbitrator servers.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Credential Type | Select the credential type of the selected cliusters to use for monitoring. Default: ADMIN |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Cisco UCM Clusters | Select the Cisco UCM clusters to onboard as assets onto the selected Assurance Arbitrators. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Cisco Unity Connection Clusters | Select the Cisco Unity Connection clusters to onboard as assets onto the selected Assurance Arbitrators. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Assurance Arbitrator Servers | Select one or more Arbitrator server as target to create asset and related configuration for the cluster selected above. |
|