Cisco Prime Collaboration Upgrade and Migration Guide, 10.0
Getting Started with Prime Collaboration
Downloads: This chapterpdf (PDF - 250.0KB) The complete bookPDF (PDF - 586.0KB) | Feedback

Table of Contents

Getting Started with

Logging In to Prime Collaboration

Getting Started with Assurance

Feature Support After Migration — Assurance

Changes to the Device Management Feature

Changes to the RBAC Feature

Feature Support After Upgrade—Prime Collaboration Assurance

Feature Support After Upgrade—Prime Collaboration Provisioning

Customizing Provisioning Attribute Conversion

Getting Started with Prime Collaboration

After you migrate to Prime Collaboration you will need to do certain tasks to enable you to use all the Prime Collaboration features. You must review Getting Started with Prime Collaboration Assurance for information about the tasks that you need to perform after you migrate from Prime UOM and Prime USM.

 

Logging In to Prime Collaboration

You can invoke Prime Collaboration using the client browser.

To log in to Prime Collaboration:


Step 1 Open a browser session from your machine. See Cisco Prime Collaboration 10.0 Quick Start Guide for information about supported browsers.

While logging in to a Prime Collaboration installation which is in converged mode, specify the IP address of Prime Collaboration Assurance server. For standalone mode, specify the IP address of either Prime Collaboration Assurance or Provisioning based on the UI that you want to launch.

Step 2 Enter either http:// IP address or https:// IP address , using the whichever of the following is appropriate for your Prime Collaboration installation:

    • For converged mode, specify the IP address of the Prime Collaboration Assurance server.
    • For standalone mode, specify the IP address of either Prime Collaboration Assurance or Prime Collaboration Provisioning, based on the UI that you want to launch.

Note You may use either the IP address or the hostname of the Prime Collaboration Assurance or Provisioning server. If you have configured DNS, we recommend that you use the hostname.


Because Prime Collaboration uses a self-signed certificate, one of the following windows appears:

    • For Internet Explorer browsers—Certificate Error: Navigation Blocked
    • For Mozilla Firefox browsers—Untrusted Connection.

Step 3 Remove the SSL certificate warning.

Step 4 In the Prime Collaboration log in page, you must login as globaladmin , using the same the credentials that you specified during the configuration.

The Prime Collaboration landing page appears along with the Getting Started popup, where you can optionally click links listed under System Setup and Manage Network to configure the Prime Collaboration server.


 


Note After installation, you can integrate Prime Collaboration Provisioning with Prime Collaboration Assurance using the Prime Collaboration Assurance UI.


Getting Started with Prime Collaboration Assurance

After you migrate to Prime Collaboration Assurance, you may need to perform the tasks listed in the following table to ensure that the features work as expected.

 

Table 4-1 Getting Started with Prime Collaboration Assurance

Task and Description
Navigation on the Prime Collaboration Assurance Standalone Server

1.

Go to the Job Management page.Verify that no job is in running state, and that auto-discovery is complete.

Administration > Job Management

2.

Add a license file.

Administration > License Management.

See Cisco Prime Collaboration Assurance Advanced Guide 10.0 for details. See also Licensing and Migration.

3.

Trigger rediscovery for all devices.

Operate > Device Work Center > Discover Devices

4.

Verify that all devices are in managed state. See Changes to the Device Management Feature.

.

Operate > Device Work Center

See Cisco Prime Collaboration Assurance Advanced Guide 10.0 for details about managing devices.

5.

Reconfigure the Cisco 1040 Sensor.

See Cisco Prime Collaboration Assurance Advanced Guide 10.0 for details.

6.

Review Feature Support After Migration—Prime Collaboration Assurance for details about changes in features.

After the device discovery is complete, you can start using the Prime Collaboration features. See Cisco Prime Collaboration 10.0 Assurance Advanced Guide for information about features that enable you to manage faults and monitor your network.

Feature Support After Migration—Prime Collaboration Assurance

Most of the features that you used in Prime UOM, Prime USM, and Prime CM are migrated to Prime Collaboration, and you can start using them without performing any additional configuration.

Table 4-2 details the features for which you would need to perform configuration again in Prime Collaboration. It also lists features that are not supported.

 

Table 4-2 Feature Support on Migration—Prime Collaboration Assurance

Feature
Supported on Migration?
In Prime Collaboration

Prime UOM/Prime USM Features

Cluster Device Discovery

Settings not preserved on migration if default was changed in Prime UOM

Configure at:

Administration > System Setup > Assurance Setup > Cluster Data Discovery Settings

Device Rediscovery Schedule

No

Configure at:

Operate > Device Work Center > Discover Devices

Phone XML Settings

Settings not preserved on migration if default was changed in Prime UOM

Configure at:

Administration > System Setup > Assurance Setup > IP Phone XML Inventory Collection Settings

Phone Inventory Collection Settings

Settings not preserved on migration if default was changed in Prime UOM

Configure at:

Administration > System Setup > Assurance Setup > IP Phone Inventory Collection Settings

Report Export Settings

No

Configure at:

  • Report > Interactive Reports > Activity Reports > Export Audio Phones
  • Report > Interactive Reports > Activity Reports > Export Video Phones
  • Report > Static Report > Event History
  • Interactive Reports > Call Quality Event History Reports > Export
  • Interactive Reports > Call Quality Reports > Export Most Impacted Endpoints

Event Customization

No

Configure at:

Alarm & Event Configuration > Event Customization .

Event suppression and severity can be customization. Event names cannot be customized

Event History Report

Available at:

Report > Static Reports

In the Reports pane, choose Event History .

Syslog Customization Support Settings

No

Can be created again at:

Administration > Event Customization

User Defined Groups

No

Configure at:

Operate > Device Work Center

RBAC Users

Partial

Custom roles will not be migrated. See Changes to the RBAC Feature for details.

NBI Preferences Settings

No

Not supported.

PTM Settings

Yes

NA

Saved Reports

No

You might have saved 24-Hour IP Phone Status Reports, Event History Reports, 24-Hour Video Phone Status Reports, and Service Quality History. These are not migrated. You must manually copy the saved reports.

SMTP Server

No

Configure at:

System Setup > Assurance Setup > General Settings

Changes to the Device Management Feature

Device credentials are managed in Prime Collaboration using credential profiles. See Cisco Prime Collaboration 10.0 Assurance Guide for information about creating and updating credential profiles.

For a device to be in managed state in Prime Collaboration, all mandatory credentials must be present in the Prime Collaboration database. In Prime UOM, if a device has only SNMP credentials available in the database, it goes to partially monitored state. But in Prime Collaboration, even if SNMP credentials are available, the device will be in inaccessible state. You must add all mandatory credentials in the credential profile, and rediscover the device in Prime Collaboration.

To edit the credentials of the devices you were managing using Prime UOM, you must add the Credential Profile in the Manage Credentials page ( Operate > Device Work Center > Credential Profile ), and then do a rediscovery.

To add a new device, you must add the Credential Profile from the Manage Credentials page, and then discover devices.

Changes to the RBAC Feature

The users that you created in Prime UOM are migrated, and they can continue to use the password you set up in Prime UOM. Roles and device-level access associated with the users are not migrated.

For details about Prime Collaboration system-defined roles and corresponding privileges, see Cisco Prime Collaboration 10.0 Assurance Guide .

Table 4-3 lists the roles assigned in Prime Collaboration after migration, for the users created in Prime UOM.

 

Table 4-3 Users and Roles

User in Prime UOM
Role in Prime Collaboration

Guest

Help Desk

User with full authorization

All five roles

User with custom role

Help Desk

User with device-level authorization but with no role assigned

Help Desk

User with no role assigned

Help Desk

User with globaladmin as username

Not migrated.

Feature Support After Upgrade—Prime Collaboration Assurance

If you upgraded from Prime Collaboration 9.0 or 9.5 and had set up notification criteria which have System Defined Device Groups added, then you need to edit the criteria and add the System Defined Device Groups again.

If you upgraded from Prime Collaboration 9.0, and had set up notification criteria which includes User Defined device groups that have clusters, then you need to edit the criteria and reselect the clusters. This is not applicable if you upgrade from Prime Collaboration 9.5.

See Configuring Alarm and Event Notification section in the Cisco Prime Collaboration Assurance - Advanced Guide 10.0 for information on setting up notification criteria.

Feature Support After Upgrade—Prime Collaboration Provisioning

Upon upgrade, the Prime Collaboration Provisioning will be in Standard mode. See Cisco Prime Collaboration 10.0 Provisioning Guide for information about features available in Standard and Advanced mode.

Provisioning Attributes (Domain, Service Area and User Role) from Prime Collaboration 9.x gets converted to Service Templates in Prime Collaboration 10.0.

During the upgrade, service templates gets created automatically depending on the Provisioning Attributes (PA) set at different levels (Domain, Service Area, User Role). These PAs will not be available in Prime Collaboration 10.0, as they will be replaced by Service Templates.

Customizing Provisioning Attribute Conversion

If you need only certain Provisioning Attributes set in Prime Collaboration 9.x to be converted to Service Templates in Prime Collaboration10.0, you have the option to customize this.

By default, during upgrade, Service templates will be created for all products like Line, EM_Line, EM_Access, Mobility, UserServices, RemoteDestinationProfile, RDP_Line, Voicemail, or Phone.

For example, this behavior can be customized to have the service templates generated only for Line and Extension Mobility Line products, by adding the following property in /opt/cupm/sep/ipt.properties:

dfc.ipt.migrateProductIDs = Line,EM_Line

After changing this property, you must restart the Prime CollaborationProvisioning server before you run the upgrade.

To convert Provisioning Attributes to Service Templates only for specified number of Phone models, add the following 2 properties in /opt/cupm/sep/ipt.properties:

  • dfc.ipt.migrateProductIDs=Phone
  • dfc.ipt.migrateEndPointIDs=Cisco_7911,Cisco_7960

Where Cisco_7911 is the product id corresponding to endpoint type Cisco 7911 and Cisco_7960 is the product id for endpoint Cisco 7960. You can add multiple endpoint type IDs to the property dfc.ipt.migrateEndPointIDs to convert those to Service templates.

After changing this property, you must restart the Prime CollaborationProvisioning server before you run the upgrade.

You can check the /opt/cupm/sep/logs/upgrade-10.0-application.log file to see the progress of the conversion. You must to open a separate SSH session into the Prime Collaboration Provisioning server and log in as root, to view this log file. You can look for:

“[java] UpdateIMDetails:Start migration PA's to Service templates....”

Alternatively, you can search as shown below:

grep –r “UpdateIMDetails:Start migration PA's to Service templates....” *.log

If, for any product, the conversion fails, the Provisioning Attributes for that product will be written to log files under /opt/cupm/sep/logs. For example, a log file by name CaliforniaDomain_Cisco_7965.log will be created under /opt/cupm/sep/logs if the migration for Cisco 7965 Phone type fails for the California domain.