On this page

Prime Collaboration Assurance Integration

Before You Begin

  • Review Role Mapping for Prime Collaboration Assurance to understand how your VOSS Automate roles map to Prime Collaboration Assurance roles.

  • In Prime Collaboration Assurance, enable SFTP. SFTP is not enabled by default.

  • Ensure that the smuser account is available in the Prime Collaboration Assurance, and you can log in. The default SFTP credential in PCA is smuser/smuse.

Use this workflow to integrate VOSS Automate with Prime Collaboration Assurance.

Procedure

  1. Configure Prime Collaboration Assurance.

  2. Set up Prime Collaboration Assurance to monitor the Unified Computing System.

  3. Add the Service Provider space and Application space under Address space information when adding Cisco Unity Connection and Cisco IM and Presence server to VOSS Automate. Prime Collaboration Assurance uses the server’s Service provider space to monitor the applications. See Set Up IM and Presence Service Servers.

  4. Add Cisco IM and Presence Service subnode information to VOSS Automate if you have multiple instances of Cisco IM and Presence Service deployed.

  5. Ensure that your Unified Communications applications have all the needed credentials. At a minimum, you require credentials for Administration, platform, SNMP, JTAPI, and HTTP.

    Note:

    Depending on what you are monitoring, other credentials may be needed. For more information about the required protocols, support, and credentials to set up devices for Prime Collaboration Assurance monitoring, see:

    http://docwiki.cisco.com/wiki/Setting_up_Devices_for_Prime_Collaboration_Assurance.

  6. Synchronize your customer information with VOSS Automate. See Set Up CUCM Servers for more information.

  7. (Optional) Ensure that the Session Border Controller has the required credentials in Hosted Collaboration Mediation-Fulfillment.

  8. Ensure that the CPE (analog gateway or LBO) has the required credentials in VOSS Automate under Devices.

  9. Enter the SNMP commands manually on the Local Break Out (LBO) gateway or analog gateway. This task is required to manage the LBO gateway and analog gateway in Prime Collaboration Assurance.

    Note:

    IOS default command builder does not generate SNMP commands. The administrator must enter SNMP commands.

  10. Add Prime Collaboration Assurance to VOSS Automate (Device Management > Prime Collab > Servers). (Administration and SFTP credentials are required.)

  11. Onboard the customer to Prime Collaboration Assurance using the Cisco Unified Communications Manager administrative interface. CHPA pushes SNMP, Syslog, and Billing server configuration information to your VOSS Automate automatically. Add Syslog and SNMP configurations manually for Cisco Unity Connection and IM and Presence Service before onboarding.

    Note:

    Configure these credentials in Unified CM nodes to ensure a successful CHPA configuration:

    • Administration credentials for Unified CM

    • Platform credentials for Unified CM

    • SNMP and HTTP credentials for Unified CM

    • SFTP for Prime Collaboration Assurance

    Note:

    This configuration is pushed to Unified CM:

    • The SNMP community string

    • CDR (SFTP of the Prime Collaboration Assurance server)

    • Syslog configuration

    Note:

    JTAPI credentials are optional credentials used for TelePresence session monitoring. They are used to retrieve session status information from TelePresence devices. Create a JTAPI user in the Unified Communications Manager with the required permission to receive JTAPI events on endpoints. The credentials must be manually configured in Unified CM. Note also that Prime Collaboration Assurance manages multiple call processor clusters and as a result you must ensure that the cluster IDs are unique.

  12. Synchronize Active Directory users with VOSS Automate.

    Note: Only users at the provider hierarchy are pushed to PCA.

  13. To confirm if the Cisco HCM-F (if installed) push and subsequent Device Discovery were successful, verify that the devices are managed in Prime Collaboration Assurance. Review the Current Inventory table at Operate > Device Work Center (Prime Collaboration Assurance 10.5.1) or Device Inventory > Inventory Management (Prime Collaboration Assurance 11.5 or later). Devices appear in Inventory Management with the Managed status. For details on the Prime Collaboration Assurance Inventory table, see the Manage Inventory section of Cisco Prime Collaboration Assurance Guide Advanced, available at:

    http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-collaboration/products-user-guide-list.html.

    Note:

    In Cisco HCM-F (if installed), you may receive a Credential-related error message, but there can be other reasons for this error, such as a firewall issue. We recommend that you use Prime Collaboration Assurance to verify that devices are managed. If a device is not going into the managed state successfully, refer to the Troubleshooting section of the Discover Devices chapter in Cisco Prime Collaboration Assurance Guide Advanced for troubleshooting tips.

    A list of the devices supported by Prime Collaboration Assurance is available at:

    http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-collaboration/products-device-support-tables-list.html.

  14. Check the Prime Collaboration Assurance dashboard.

    See UC Performance Monitor Dashboards in the Cisco Prime Collaboration Assurance Guide Standard or Cisco Prime Collaboration Assurance Guide Advanced.

  15. Monitor components and devices with Prime Collaboration Assurance.

previous

Role Mapping for Prime Collaboration Assurance

next

LBO and Analog Gateway Configuration and Generated Events