.. _concepts-onboard-voss-assurance-assets:
   
Onboard Voss Assurance Assets
------------------------------------------

.. _21.1|VOSS-842:

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: 

* :ref:`set_up_cisco_unified_communications_manager_servers`
* :ref:`set_up_cisco_unity_connection`.



.. 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-4-UC,
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.
#. 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.
   
#. Select clusters and arbitrators in **Available** transfer boxes and
   onboard by moving these to the **Selected** boxes.
#. 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:

* **Onboard Assurance Asset Cucm Server**
* **Onboard Assurance Asset Cuc Server**
* **Onboard Assurance Asset Cucm Cluster**
* **Onboard Assurance Asset Cuc Cluster**

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:

* **Credential Type**
* Cisco UCM/CUC Server or cluster
* **Arbitrator Server**

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-4-UC 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-4-UC.
3. Create probes (performance monitoring): 5 probes are created - 4 generic and 1 customer-specific.
4. Create a probe group - see :ref:`probe-names-profile-timings`.
5. Create relevant credentials on Arbitrator - using the selected credential type user credentials
   set up on VOSS-4-UC.

   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 :ref:`probe-names-profile-timings`.
7. For Unified CM, service parameters for each server are updated:
   
   a. setting up remote syslog
   b. enable CDR and related settings
   c. 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.