Prime Collaboration Assurance Integration

These workflow steps allow you to integrate VOSS Automate with Prime Collaboration Assurance (PCA).

Prerequisites:

  • Review role mapping for PCA to understand how your VOSS Automate roles map to PCA roles.

  • In PCA, enable SFTP (disabled by default).

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

Perform these steps:

  1. Configure PCA.

  2. Set up PCA to monitor the Unified Computing System.

  3. Add the Service Provider space and Application space under Address space information when adding Cisco Unity Connection (CUC) and Cisco IM and Presence server to VOSS Automate. PCA 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 UC applications have all required credentials. At minimum, credentials are required for Administration, platform, SNMP, JTAPI, and HTTP.

    Note

    Other credentials may be required, depending on what you’re monitoring. For more information about the required protocols, support, and credentials to set up devices for PCA monitoring, see:

    https://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/collaboration/setting_up_devices/PCA_12-1/Setting_up_Devices_for_Cisco_Prime_Collaboration_Assurance.html

  6. Synchronize your customer information with VOSS Automate. See Add a CUCM Server for more information.

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

  8. Ensure that the CPE (analog gateway, or LBO deployed at CPE) 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 PCA.

    Note

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

  10. Add PCA to VOSS Automate (default menus: Apps Management > Prime Collab > Servers). Administration and SFTP credentials are required.

  11. Onboard the customer to PCA, using the Cisco Unified Communications Manager (CUCM) admin interface.

    • CHPA pushes SNMP, Syslog, and Billing server configuration information to your VOSS Automate automatically.

    • In HCMF (Provider deployments), the CHPA pushes SNMP,Syslog, and Billing server configuration information to your VOSS Automate automatically.

    • Add Syslog and SNMP configurations manually for CUC and IM and Presence Service before onboarding.

    Note

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

    • Administration credentials for CUCM

    • Platform credentials for CUCM

    • SNMP and HTTP credentials for CUCM

    • SFTP for PCA

    This configuration is pushed to CUCM:

    • The SNMP community string

    • CDR (SFTP of the PCA server)

    • Syslog configuration

    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 CUCM with the required permission to receive JTAPI events on endpoints. The credentials must be manually configured in CUCM.

    PCA manages multiple call processor clusters and as a result you must ensure that the cluster IDs are unique.

  12. Sync Active Directory users with VOSS Automate.

    Note

    Only users at the provider hierarchy are pushed to PCA.

  13. To confirm whether the Cisco HCM-F (if installed) push and subsequent Device Discovery were successful, verify that the devices are managed in PCA.

    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 PCA 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 PCA 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 PCA dashboard.

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

  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