[Index]

Model: view/OnboardAssuranceAssets

VOSS Assurance

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

New UC app onboarding

When new Unified CM and CUC servers are added in a cluster, the Monitoring details on the publisher servers show the list of available arbitrators under the Assurance Arbitrator Server check box instances. Select all the arbitrators to monitor the server.

See:

Note

The onboarding workflow transaction log also shows the updates and import of the Unified CM and CUC server service parameters.

The feature does not currently allow for the modification of any existing monitoring on UC Apps. Once a Unified CM or Unity Connection server is created, use the Onboard/Offboard Asset tools to enable/disable monitoring.

Onboard Assets

If VOSS Assurance arbitrators are configured at a hierarchy, then for existing UC app (Unified CM and Unity Connection) clusters on VOSS Automate, the Onboard Assets menu provides for the management of the clusters and arbitrator servers in a batch.

  1. Select Onboard Assets. You will be asked to choose a customer level hierarchy.
  2. From the Credential Type drop down, keep the default ADMIN or choose a type. This determines which credential type of the UC server to use for asset configuration on the arbitrator.
  3. Select clusters and arbitrators in Available transfer boxes and onboard by moving these to the Selected boxes.
  4. Click Save.

All servers in a cluster are onboarded unless a server is already onboarded, in which case the the server is skipped. Inspect the Transaction Log to see the transactions and sub-transactions for each cluster.

Additional Tools to Onboard Single Cluster and Servers

A number of Views are available that are not exposed in the menu, but do have access profiles enabled for provider and higher level administrators, so that single assets can be onboarded. The views can be added to menus if needed:

These tools do not direct you to a particular hierarchy and the views allow you to carry out the tasks on the form by selecting:

The views offer the same functionality as transfer boxes available on the Onboard Assets and Offboard Assets menus, but:

  1. A user is not forced to a hierarchy
  2. Tasks can be carried out for a shared architecture, for example if the cluster is located at a reseller hierarchy.

Onboard workflows

When a Unified CM or Unity Connection server (asset) is associated with a VOSS Assurance arbitrator, the following updates are made by VOSS Automate on the associated arbitrator.

The transactions for these can be seen on the transaction log.

Note

In the case of multiple server onboarding, the transaction log Action: Create Cucm App User may show a Status of Fail. This can be ignored, since duplicate user creation is ignored.

  1. Create asset (the server)

  2. Create (or update if not first asset) asset group (required by arbitrator)

    One asset group is created per customer on VOSS Automate.

  3. Create probes (performance monitoring): 5 probes are created - 4 generic and 1 customer-specific.

  4. Create a probe group - see Probes, Group Names, Profiles and Timings.

  5. Create relevant credentials on Arbitrator - using the selected credential type user credentials set up on VOSS Automate.

    These credentials are used to make the request to the asset, for example AXL user for Unified CM.

  6. Create profiles in the VOSS Assurance arbitrator to tie together the items above: Probe Group > Templates/Profiles

    See Probes, Group Names, Profiles and Timings.

  7. For Unified CM, service parameters for each server are updated:

    1. setting up remote syslog
    2. enable CDR and related settings
    3. create the application user if this is a Publisher

  8. If an update is made on an existing Unified CM, it is updated to show it is monitored by the arbitrator. The Monitoring details on the publisher servers show the list of available arbitrators and read-only enabled arbitrators that monitor the server.

The created assets, groups and profiles can be inspected on the integrated arbitrator interface. For details, see the VAA documentation.

Probes, Group Names, Profiles and Timings

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.

Model Details: view/OnboardAssuranceAssets

Title Description Details
Credential Type Select the credential type of the selected cliusters to use for monitoring. Default: ADMIN
  • Field Name: credential_type
  • Type: String
  • Default: ADMIN
  • Choices: ["SNMP_V1", "SNMP_V2", "SNMP_V3", "ADMIN", "PLATFORM", "WMI", "IOS_ENABLE", "HTTP", "CLI", "OPERATOR", "SFTP", "JTAPI"]
Cisco UCM Clusters Select the Cisco UCM clusters to onboard as assets onto the selected Assurance Arbitrators.
  • Field Name: cucm_clusters.[n]
  • Type: Array
Cisco Unity Connection Clusters Select the Cisco Unity Connection clusters to onboard as assets onto the selected Assurance Arbitrators.
  • Field Name: cuc_clusters.[n]
  • Type: Array
Assurance Arbitrator Servers Select one or more Arbitrator server as target to create asset and related configuration for the cluster selected above.
  • Field Name: arbitrators.[n]
  • Type: Array