Introduction to VOSS Insights Monitoring

Overview

Users with both VOSS Automate and VOSS Insights deployed can enable monitoring of UC applications via the VOSS Automate Admin Portal, from an Insights Arbitrator server integrated with VOSS Automate.

Note

For details around integrating VOSS Automate with the Insights Arbitrator server, see Arbitrators

Once the integration is set up, you onboard customer server clusters, comprising one or more Cisco Unified Communication Manager (CUCM) CallManager servers and/or Cisco Unity Connection (CUC) servers, to an Arbitrator server for monitoring, from within the VOSS Automate Admin Portal.

The following servers are supported:

• Cisco Unity Connection (CUC) servers

• Cisco Unified Communications Manager (CallManager, or CUCM) servers

  Provisioning is supported for these CUCM server types:

  • Voice (VOICE_VIDEO)

  • IM and Presence Service (IM_P)

Note

The image displays a customer with four CallManager servers that are part of the same cluster. The cluster is onboarded to the Arbitrator server for monitoring purposes.

This feature provides the following functionality in the Admin Portal:

• Integrate Arbitrator servers, and view existing integrations, via (default menus) Apps Management > VOSS Insights > Arbitrators. See Arbitrators

  Note

  The Arbitrator server should be at version SP23 or higher.

• View currently configured monitoring set up for server clusters, if any:

  • For CUCM servers, go to (default menus) Apps Management > CUCM > Servers, then click on a cluster to view the following:

    • On the Base tab, view the cluster name and server type (VOICE_VIDEO or IM_P), and whether the server is a Publisher server or a Subscriber server.

    • On the Publisher tab, view monitoring details, including the monitoring Arbitrator server, if any.

    

  • For CUC servers, go to (default menus) Apps Management > CUC > Servers, then click on a cluster to view monitoring details, including the monitoring Arbitrator server, if any.

• When adding new CUCM or CUC server in a cluster, you can choose an Arbitrator to monitor the servers (via the Monitoring fields for Publisher servers)

Note

At the time of writing (VOSS Automate v21.3), modifying any existing monitoring setup on UC apps is not supported. However, deleting a UC app on VOSS Automate will remove the asset and related configuration from all corresponding VOSS Insights Arbitrator servers.

Onboarding Provisioning

The onboarding process triggers a workflow that finds all the servers in the cluster, then provisions all required monitoring elements (which differ depending on whether the server is CUCM or CUC, Publisher or Subscriber, or CUCM server type VOICE_VIDEO, or IM_P).

Note

You can view all workflow provisioning steps via the transaction log in the Admin Portal.

The table describes the onboarding provisioning that occurs for the server types supported for Arbitrator monitoring:

Server in the cluster	Onboarding Provisioning
CUCM VOICE Publisher (PUB)	Provisioning on Arbitrator: Creates the asset on Arbitrator. Adds the asset into an asset group on Arbitrator (or updates the asset group if it already exists) Creates a credential for the server. Creates a server-specific probe and probe group combination. Creates five Arbitrator monitoring profiles, which define the schedule for the probe to run on the asset (for example, every 5 minutes, or once a day): A server-specific PERFMON CUCM group profile that associates the probe and probe group combination with the asset and the credential. Four profiles that associate static probes (which are always on the Arbitrator) with the asset: RIS, PING Monitor, Version, RTMT The static probes must exist on the Arbitrator for Arbitrator monitoring to work. The static probes are associated with new assets, using the profiles. Provisioning on the CallManager: Creates the application user. When onboarding multiple servers, you can ignore a fail status at this step Create Cucm App User, since duplicate user creation is ignored. Updates service parameters
CUCM VOICE Subscriber (SUB)	Provisioning on Arbitrator: Creates the asset on Arbitrator. Adds the asset into an asset group on Arbitrator (or updates the asset group if it already exists) Creates a credential for the server. Creates one Arbitrator monitoring profile (ping test only).
CUCM IM_P Publisher (PUB)	Provisioning on Arbitrator: Creates the asset on Arbitrator. Adds the asset into an asset group on Arbitrator (or updates the asset group if it already exists) Creates a credential for the server. Creates a server-specific probe and probe group combination. Creates two Arbitrator monitoring profiles, which define the schedule for the probe to run on the asset (for example, every 5 minutes, or once a day): A server-specific PERFMON CUCM group profile that associates the probe and probe group combination with the asset and the credential. A PING Monitor profile

Server in the cluster	Onboarding Provisioning
CUCM IM_P Subscriber (SUB)	Provisioning on Arbitrator: Creates the asset on Arbitrator. Adds the asset into an asset group on Arbitrator (or updates the asset group if it already exists) Creates a credential for the server. Creates one Arbitrator monitoring profile (ping test only).
CUC Publisher (PUB)	View the transaction and sub-transaction log for details.
CUC Subscriber (SUB)	View the transaction and sub-transaction log for details.

For details, see Onboard Assets

Note

All provisioned elements can be viewed on the Insights Arbitrator dashboard. For details, see the VOSS Insights documentation.

Probe Groups, Profiles, and Asset Onboarding

The table describes the probe groups and profiles that are added to the VOSS Insights Arbitrator server when assets are onboarded, and removed when assets are off-boarded.

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

Offboarding Assets

Should you wish to disable monitoring and remove data from the Arbitrator server, you can offboard these assets (and their related configuration) from the Arbitrator server. For details see Offboard Assets