DocWiki - User contributions [en]

Setting up Devices for Prime Collaboration Assurance

2013-03-22T10:40:08Z

Chetrao:

This section describes how to configure devices on the network before you manage them in Cisco Prime Collaboration Assurance.

= Required Protocols for the Devices (Includes Supported Software Versions) =

You must configure the endpoints, application managers, call processors, multipoint switches, and network devices with the following protocols:

*HTTP - Access the device through HTTP to poll system status and meeting information.
*SNMP - Read Community String and SNMP Authentication Protocol (SNMP V2 or SNMP V3) - Discover and manage the device.
*CLI - Access the device through CLI to discover media path for troubleshooting.
*JTAPI - Retrieve the session status information frosm the Cisco Unified CM.
*CDP - Discover neighboring devices.

 

{| border="1" cellspacing="1" cellpadding="1" width="1000"
|-
| '''Device''' 
| '''Supported Software''' 
| '''SNMP''' 
| '''HTTP''' 
| '''CLI''' 
| '''JTAPI''' 
| '''MSI''' 
| '''CDP''' 
| '''Notes''' 
|-
| Analog Gateway 
| - 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Contact Center Enterprise 
| 7.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Contact Center Express 
| 4.6 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Multipoint Switch 
| 1.7 – 1.9 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user account must have both the Meeting Manager and Diagnostic Technician roles. 
|-
| Cisco TelePresence System 
| 1.7 – 1.9 
| Yes 
| - 
| Yes 
| -
| Yes 
| - 
|
*CLI access is required if you want to use the Troubelshooting feature in Prime Collaboration. HTTP access is not required.
*The HTTP credentials (helpdesk role) are same as the SSH credentials, which are required by Prime Collaboration to troubleshoot.

|-
| Cisco TelePresence Manager (CTS-Manager) 
| 1.7 – 1.9 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*Requires the Reporting API license and the Reporting API role for the Prime Collaboration user.
*The HTTP user needs to be an exchange mailbox user and its User Group must have Reporting API and Live Desk roles in CTS-Manager. 
*If you have installed a licensed version of Prime Collaboration, it is mandatory to configure the CTS-Manager Reporting API. If this feature is not configured on the CTS-Manager 1.7, 1.8, or 1.9, Prime Collaboration will not manage the CTS-Manager. 

|-
| Cisco Unified CM 
| 7.1 – 9.0 
| Yes 
| Yes 
| - 
| Yes 
| - 
| - 
|
*The same credentials must be created for all devices in the cluster whenever clustering is used.
*The JTAPI user needs to have these roles Standard AXL API Access, CCM Admin Users, SERVICEABILITY Administration, CTI Enabled, and CTI Allow Call Monitoring.
*The session monitoring feature is supported only on Cisco Unified CM 8.5, 8.6 and 9.0. 

|-
| Cisco Unified Communications Manager Business Edition 
| 7.1 – 9.0 
| Yes 
| Yes 
| - 
| Yes 
| - 
| - 
| 
|-
| Customer Voice Portal 
| 4.0 - 8.5 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
|
*Cisco Codec EX series
*Cisco TelePresence System Integrator C Series
*Cisco TelePresence MX Series
*Cisco TelePresence System Profile Series
*Cisco TelePresence SX20 Quick Set
*Cisco TX 9000 series 

|
*EX series: TC 4.2 - 6.0; TE 6.0 
*C, MX, and SX series: TC 4.2 - 6.0 
*TX series: TX 6.0 

| Yes 
| Yes 
| Yes 
| - 
| Yes 
| - 
|
*The HTTP user requires Admin privilege. 
*For TC 6.0 and TE 6.0, use the same HTTP credentials for MSI. 
*For TX 6.0, use the default credentials msiuser and cisco for MSI. 

|-
| Cisco IP Video Phone E20 
| TE 4.0 - 6.0 
| Yes 
| Yes 
| Yes 
| - 
| Yes 
| - 
|
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration.
*Use the same HTTP credentials for MSI. 

|-
| Emergency Responder 
| 1.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Expert Advisor 
| 7.2 - 7.6 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Finesse 
| 8.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco MCU 
| 4.1 – 4.3 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*The HTTP user requires Admin privilege. 
*This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, and MSE-8710. 

|-
| Cisco TelePresence MSE Supervisor 
| 2.1 – 2.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user requires Admin privilege. 
|-
| Mediasense 
| 8.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Meeting Place 
| 7.0 - 8.5 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Meeting Place Express 
| 2.0 - 2.1 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Personal Assistant 
| 1.3 -1.4 
| - 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence System MXP series 
| 9.1 
| Yes 
| Yes 
| Yes 
| 
| 
| 
| 
|-
| Polycom VSX series Polycom HDX series 
| 2.5 - 3.0 (for HDX series) 9.0 (for VSX series) 
| Yes 
| - 
| - 
| - 
| - 
| - 
| End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 
|-
| Cisco Presence 
| 8.0 - 9.0 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Network devices (routers and switches) 
| 
| Yes 
| - 
| Yes 
| - 
| - 
| Yes 
|
*CDP needs to be enabled for the video Troubleshooting workflow. The Telnet or SSH access is required for Cisco Medianet features, which is part if the video Troubleshooting workflow. 
*See the table ''Supported Software Versions for the Cisco Medianet'' Feature below to view the troubleshooting medianet-related data. 

|-
| Cisco TelePresence Management Suite (Cisco TMS) 
| 13.0 – 13.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*Requires Booking API license (TMS software version 13.1 or below). 
*The HTTP user for Prime Collaboration needs to be generated through the Booking API on the Cisco TMS windows server. 
*Prime Collaboration supports only the default e-mail template for the Booking Confirm e-mail in Cisco TMS. The session import feature will not work, if the default e-mail template is not used. 

|-
| Cisco Telepresence Server 
| 2.1 – 2.2 
| - 
| Yes 
| - 
| - 
| - 
| - 
|
*The HTTP user account should have the API Access privilege.
*This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, MSE-8710. 

|-
| Cisco Telepresence Conductor 
| 1.1 - 1.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity
| 7.0 - 8.6
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity Connection
| 7.0 - 9.0
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity Express
| 7.0 - 9.0
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Video Communication Server (Control and Expressway) 
| 6.0 – 7.1 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user requires Admin privilege. 
|-
| Wireless 
| - 
| Yes 
| - 
| Yes 
| - 
| - 
| - 
| 
|-
| Third party devices 
| - 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Jabber Video for Telepresence (Movi) 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco Jabber endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required).
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Cisco Cius 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco Cius endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required). You must enable web access in Cisco Unified CM for these. 
*Credentials are not required for HTTP access. 
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Cisco IP phones (89xx, 99xx) 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco IP Phones endpoints are discovered through Cisco Unified CM. You must enable web access in Cisco Unified CM for these. 
*These video phones require Cisco Unified CM application user to have the additional role ''Standard CTI Allow Control of Phones supporting Connected Xfer and conf''. 
*Credentials are not required for HTTP access. 
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Border Element, Gatekeeper, H323 Gateway, SIP Gateway MGCP Gateway, SRST Device, Voice Gateway 
| IOS 12.x or later 
| - 
| - 
| - 
| - 
| - 
| - 
| 
|}

 

= Configuring Call Controllers and Processors =

== Cisco Unified Communications Manager ==

All CTS endpoints must be added as controlled devices in Cisco Unified CM to facilitate call detection. You must configure a HTTP and JTAPI user on the call processor.

'''Note''': The procedures described below are applicable for Cisco Unified CM 8.5. If you are using any other supported versions, see the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html ''Cisco Unified CM guides''] to understand how to create groups, users and assign roles to them. 

'''Enable HTTP'''

You do not have to create a new user if you want to allow Cisco Prime Collaboration to use admin credentials to log in. Alternatively, if you want to allow Cisco Prime Collaboration Manager to use the right credentials to log in to Cisco Unified Communications Manager, you must create a new HTTP user group and a corresponding user that Cisco Prime Collaboration can use to communicate.

To create a user:

#Create a user group with sufficient privileges. Log in to the Cisco Unified Communications Manager Administration web interface using the administrator role.
#Navigate to '''User Management''' > '''User Groups''' and create a new group with a suitable name, PC_HTTP_Users in this case.
#Click '''Role'''.
#Click '''Assign Role to Group''' and select the following roles:
#*Standard AXL API Access
#*Standard CCM Admin Users
#*Standard SERVICEABILITY Administration
#Click '''Save'''.
#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration to monitor all devices.
#In the '''Permission Information''' section, click '''Add to User Group''' and select the group that was created in Step 1. (PC_HTTP_Users, for instance).
#Click '''Save'''. The page is refreshed and the right privileges are displayed.

'''Enable SNMP'''

SNMP is not enabled in Cisco Unified Communications Manager by default.

To enable SNMP:

#Log in to the '''Cisco Unified Serviceability''' view in the Cisco Unified Communications Manager web GUI.
#From the main menu in the Cisco Unified Serviceability view, navigate to SNMP > v1/v2c > community string.
#Select a Server and click '''Find'''. If the community string is already defined, the Community String Name is displayed in the Search Results.
#Click '''Add new '''to add a new string if no results are displayed.
#Specify the required SNMP information and save the configuration.

'''Enable JTAPI'''

JTAPI (Java Telephony API) is used to retrieve the session status information from the device. You must create a JTAPI user in the call processor with the required permission to receive JTAPI events on endpoints. Prime Collaboration manages multiple call processor clusters. You must ensure that the cluster IDs are unique. Create a new JTAPI user to help Cisco Prime Collaboration get the required information.

To create a new JTAPI user:

#Log in to the Cisco Unified Communications Manager administration web interface using administrator role.
#Navigate to User Management > '''User Groups''' and create a new group with a suitable name, '''PC_HTTP_Users''' in this case.
#Move all endpoint devices (for example, Cisco TelePresence codecs) to the Controlled Devices table.
#Click '''Roles'''.
#Click '''Assign Role to Group''' and select the following roles:
#*Standard CTI Allow Call Monitoring
#*Standard CTI Enabled
#*Standard CTI Allow Control of Phones supporting Connected Xfer and conf
#Click '''Save'''.
#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration to monitor all devices. '''Note''': The password must not contain a semicolon (;) or equals (=).
#In the '''Permission Information''' section, click '''Add to User Group''' and select the group that was created in step 1. (PC_HTTP_Users, for instance).
#Click '''Save'''. The page is refreshed and the right privileges are displayed.
<pre>Note:
*Ensure the following services are activated and started:
**Cisco CTIManager
**Cisco AXL Web Service
See the Cisco Unified Communications Manager guide for details about how
to configure the application user.

You can access the log files to verify whether the endpoints are assisned with the CTI-controlled roles in the Unified CM
and for the JTAPI-related issues using https://<primecollaboration-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log
</pre>
== Cisco TelePresence Video Communication Server ==

Cisco VCS serves as a call-control appliance for the Cisco TelePresence C Series, E Series, and other similar video endpoints.

'''Enable HTTP'''

You can access Cisco VCS through a web browser: http://<vcs_serveraddress>, where <vcs_serveraddress> is the IP address or hostname of your VCS appliance. The default password for administrator user '''admin''' is TANDBERG. If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the VCS. Ensure the password field is not blank as it is not recommended.

'''Enable SNMP'''

You can easily enable SNMP from the Cisco VCS web GUI: Navigate to '''System''' > '''SNMP''' and enter the SNMP information.

= Configuring Endpoints =

== Cisco TelePresence System Video Endpoints ==

'''Enable HTTP'''

You can access Cisco TelePresence system video endpoints through a web browser (preferably using Internet Explorer, if possible) by pointing the browser to:https://<serveraddress> where <serveraddress> is the IP address or hostname of the Cisco TelePresence system video endpoint.

'''Enable SNMP'''

SNMP for Cisco TelePresence system devices is configured using Cisco Unified Communications Manager phone configuration. To change the SNMP community string:

#Navigate to Cisco Unified Communications Manager Administration.
#Navigate to '''Device''' > '''Phone''' and search for Cisco TelePresence system endpoints.
#Click the '''Device Name''' link to go to the phone configuration page.
#Edit the SNMP Configuration Parameters.
#Click '''Save''' '''and''' '''Apply Config'''.

'''Enable CLI Access'''

SSH access to the Cisco TelePresence system devices is also controlled through Cisco Unified Communications Manager Phone Configuration.
<pre>Note:
If the value of SSH admin Life and SSH helpdesk Life field is zero, the password never
expires (recommended for lab testing scenarios).
However, if the value is not zero, the admin must ensure that passwords are changed
before the specified interval, for anyone or any application to be able to perform SSH
in the device including Cisco Prime Collaboration. </pre>
== Cisco TelePresence C and EX Series Video Endpoints ==

'''Enable HTTP'''

By default, HTTP is enabled for Cisco TelePresence Endpoints. Point the web browser to http://<ip_address>, where <ip_address> is the IP address or hostname of the video endpoint. The default password for the administrator user '''admin''' is " ", blank space.

'''Enable SNMP'''

To enable SNMP access for Cisco Prime Collaboration from the web interface:

Navigate to '''Configuration''' > '''Adv Configuration''' > '''Network Services''' > '''SNMP''' and click the value to edit.

'''Enable CLI Access'''

SSH must be enabled by default on TC 4.0 releases. Provide '''admin''' user access to Cisco Prime Collaboration ensure that the admin password is set and is not the default value, which is blank. Admin user access is necessary if you want to troubleshoot video sessions from Cisco TelePresence devices using Cisco Prime Collaboration. Some of the commands required to run the traceroutes are available only when you log in as root.

We recommend that you enter the real interface IP address of the gateway that runs the Hot Standby Router Protocol (HSRP), instead of the virtual IP address, while configuring the CTS. This enables Prime Collaborationto accurately discover the troubleshooting path.

Endpoint monitoring is based on the SNMP polling. You can configure traps and syslogs on the endpoints, if required.

To monitor traps and syslogs:

*Configure trap and syslog receivers for endpoints in call processors.
*Enter the Prime Collaboration IP address to configure the trap receiver: <PrimeCollaboration_ip_addr>
*Enter the Prime Collaboration IP address and port number 20514 to configure syslog receiver.: <PrimeCollaboration_ip_addr>:20514.
*Enable endpoints to send traps and syslogs.

To enable traps:

*In CISCO-TELEPRESENCE-MIB, set ctpPeripheralErrorNotifyEnable to true (1)
*In CISCO-TELEPRESENCE-CALL-MIB, set ctpcStatNotifyEnable to true (1)
*In CISCO-TELEPRESENCE-CALL-MIB, set threshold values for call stats ctpcStatMonitoredEntry

To enable syslogs: In CISCO-SYSLOG-MIB, set clogNotificationsEnabled to true (1).

= Configuring Call Management Applications =

== Cisco TelePresence Management Suite ==

HTTP and SNMP access are required to successfully monitor Cisco TMS.

'''Enable HTTP'''

Cisco TMS is accessed through a web browser (http://<serveraddress>/TMS), where <serveraddress> is the IP address or hostname of your server. The default password for the administrator user '''admin''' is '''TANDBERG'''.

If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully monitor Cisco TMS.

'''Enable SNMP'''

By default, '''public''' and '''Public''' are enabled as SNMP Read Only (RO) community strings for Cisco TMS. This string is used by Cisco TMS to poll other devices.

If you need to add or change these strings:

Go to the web GUI and navigate to '''Administrative''' '''Tools''' > '''Configuration''' > '''Network Settings''' and change the SNMP settings.

In addition to the Web GUI, SNMP service on the Cisco TMS server must be enabled.

To enable SNMP:

#Go to '''Start '''on the server console.
#Click '''Run '''and specify services.msc. A Service window will pop open on the server console.
#Right-click '''SNMP Service '''and select '''Properties'''.
#Click '''Security '''and select '''Add new SNMP''' string. Do not modify the default selection: Accept SNMP packets from any host unless you want only specific hosts polling SNMP from Cisco TMS.
#Optionally, click '''Traps '''to add the IP address of Cisco Prime Collaboration and a community string. This address is used in SNMP traps.
#Optionally, click '''Agent '''to specify SNMP contact and location for Cisco TMS. The Cisco Prime Collaboration uses this information to display the location of Cisco TMS in the inventory.
#Restart the '''SNMP Service '''after the necessary modifications.

== Reporting API for CTS-Manager ==

For Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager, you must have a valid Metrics Dashboard and Reporting API license in CTS-Manager. This user account should be configured in Active Directory with a mailbox and in a user group with general security. The Active Directory user group should be assigned the '''Reporting API '''role and the '''Live Desk '''role in the CTS-Manager Access Management page.
<pre>Note:
We recommend that you review the Getting Started With TelePresence Reporting API
document available at [http://developer.cisco.com/web/tra/start] for an understanding
of the Reporting API.</pre>
'''Note''': The procedures described below are applicable for CTS-Manager 1.8. If you are using any other supported versions, see the CTS-Manager Reporting API related documents. 

To enable Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager 1.8:

#In the LDAP server, create a user group. For example,create a group named pc_group.
#In the group that you created in the LDAP server, create a user. For example, create a user named pc_user. You must ensure that a valid mailbox is configured for the user created in the group in the LDAP server.
#In CTS-Manager, in the '''Access Management '''page, assign the '''Live Desk''' role and the '''Reporting API User''' role for the group you created in the LDAP server, for example, pc_group created in ''Step 1''.
#Discover the CTS-Manager in Prime Collaboration with the user that you created in the LDAP server. For example, use pc_user.

For more information about the Reporting API, see ''Cisco Telepresense Manager Reporting API Developer's Guide for Release 1.8.''

For more information about user and group configuration in LDAP server, see ''Cisco Telepresense Manager 1.8 Administration and Installation Guide''.
<pre>Note:
After creating the user account in CTS-Manager for the Prime Collaboration application, we recommend
that you log in with this account in CTS-Manager at least once before you enter the
credentials in the Prime Collaboration server.</pre>
== Cisco TMS Third Party Booking API User ==

For the Prime Collaboration server to retrieve scheduled meetings from Cisco TMS server, you must have one Application Integration License for each server that uses the API.
<pre>Note:
*We recommend that you review the Cisco TMS Third Party Booking API document available
at [http://www.tandberg.com/support/tms_documentation.jsp] for an understanding of the
Booking API.

*For Cisco TMS 13.2 and later, any HTTP user can be used to retrieve scheduled meetings
from Cisco TMS server. In addition, you do not need to install a Booking API License to
use the API.</pre>
To enable Prime Collaboration server to retrieve scheduled meetings from Cisco TMS:

#From the Cisco TMS server, go to [http://localhost/tms/external/booking/remotesetup/remotesetupservice.asmx http://localhost/tms/external/booking/remotesetup/remotesetupservice.asmx]. The RemoteSetupService page appears. You may replace localhost in the above URL with the IP address of the Cisco TMS server.
#Choose '''GenerateConferenceAPIUser'''.
#Enter the values for the following parameters:
#*userNameBase - The base portion of the user name. For example, pc_user.
#*encPassword - A base64 encoded password that is to be used for the newly created user. To encode the password to base64, we recommend that you use the web utility available at the following URL: http://www.motobit.com/util/base64-decoder-encoder.asp.
#*emailAddress - The email address of the user. Do not enter values in this field.
#*sendNotifications - To allow the user to receive scheduling notifications. You must enter False in this field since Prime Collaboration will be polling from Cisco TMS.
#Click '''Invoke'''.
#In the Cisco TMS application, verify the user name configured in Step 3is listed in the Users page.
#In the Cisco TMS application, create a user group. For example, create a group named pc_group.
#Add the user created in Step 3 to the group created in Step 6. For example, add pc_user to pc_group.
#In the '''Groups '''page, for the group created in Step 6, check the Read permission check box for List Conferences-All (under the Booking pane). For example, pc_group must have the read permission to List Conferences-All.
#Discover the Cisco TMS in Cisco Prime Collaboration with the user that you created in Step 3. For example, use pc_user.

For more information about the Cisco TMS, see the documents available at [[Www.tandberg.com/support/tms documentation.jsp|TANDBERG]] site.

For more information on creating groups and setting permission to the group, see ''Ciso Telepresence Management Suite Administrator Guide''.

= Configuring MCUs =

A Cisco TelePresence MCU MSE 8510 (MCU MSE 8510) cluster consists of a Cisco TelePresence MCU MSE 8050 Supervisor Blade (MCU MSE 8550) and a MCU MSE 8510 blade. After the basic information is configured, HTTP access is enabled by default.

'''Enable HTTP'''

The supervisor web interface can be accessed by pointing the browser to http://<MCU_Address>, where <MCU_Address> is the IP address or hostname of your server. The default password for the '''admin''' user is a blank space (no password). If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the MCU MSE Supervisor.

To log in to the web interface of the MCU MSE 8510 blade:

#Log in to the supervisor web interface.
#Go to '''Hardware''' > '''Blades''' and click the IP address of the MCU MSE 8510 blade.
#Click '''Log in''', and enter the username '''admin''' with no password.

'''Enable SNMP'''

You can edit SNMP settings by logging in to the MCU Codian Web Interface:

#Navigate to '''Network''' > '''SNMP'''.
#Edit the SNMP Read Only and Read Write strings as required.
#Click '''Update SNMP Settings''' to apply the changes.

= Configuring Cisco TelePresence Multipoint Switch =

'''Enable HTTP'''

A separate HTTP user account must be created with the Meeting Scheduler and Diagnostic Technician roles assigned to it for the Prime Collaboration application. This user can be configured in the Multipoint Switch web user interface when logged in as admin. After the dedicated HTTP user has been created, you must login to CTMS web UI using this user credential and then change the password (the same password can be entered).

An '''admin''' user is not required by Cisco Prime Collaboration to manage the Multipoint Switch.

You can access the Multipoint Switch through a web browser (preferably using Internet Explorer) by pointing the browser to: https://<ctms_serveraddress>, where <ctms_serveraddress> is the IP address or hostname of the Multipoint Switch.

'''Enable SNMP'''

SNMP is enabled by default and it monitors the Multipoint Switch system status (navigate to Troubleshoot > System Resources for system status details). You can designate a particular server where SNMP trap messages are gathered and stored. You configure all SNMP settings through the Multipoint Switch CLI commands.

The following SNMP settings are enabled by default:

*SNMPv3 username set to '''mrtg''': This name is for internal use of the system and should not be deleted.
*SNMPv2c username set to '''public''': This name is for internal use of the system and should not be deleted.
*No trap receiver is configured. Use Multipoint Switch CLI commands to configure SNMP trap receiver information.

Use SSH in the Multipoint Switch to configure SNMP using the CLI. The CLI commands to configure SNMP Read Only and Read/Write are as follows:

*set snmp user add 2c snmpro r
*set snmp user add 2c snmprw rw
<pre>Note:
Replace snmpro and snmprw with your SNMP Read and Read/Write community strings.
After creating the user account in CTMS for the Prime Collaboration application, we recommend
that you log in with this account in CTMS at least once before you enter the
credentials in the Prime Collaboration server.
</pre>
= Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices =

If you have enabled [http://www.cisco.com/web/solutions/medianet/knowledgebase/index.html#~configure Cisco Mediatrace] on your network nodes, Prime Collaboration provides Medianet Path View as part of the troubleshooting data. If you have enabled Cisco IOS IP Service Level Agreements (SLAs) on your network nodes, you can measure the network performance and health using the Proactive Troubleshooting feature.

For Cisco Mediatrace:

*Enable the initiator and/or responder roles on relevant routers and switches using the following commands: '''For Mediatrace Initiator''': 

 
<pre>mediatrace initiator source-ip ''IP Address''</pre>
 '''For Mediatrace Responder''': 

 
<pre>mediatrace responder
</pre>
 

*Configure a Telnet local login user with privilege 15 on the initiators.
*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators. See ''Web Services Management Agent (WSMA) Configuration Guide'' for details on the configuration commands. 

'''Local Auth Example''': 
<pre>username <username> priv 15 secret <username_enable_password>
ip http authentication local

</pre>
'''For WSMA (HTTP) Configuration''':
<pre>ip http server
ip http timeout-policy idle 60 life 86400 requests 10000
wsma agent exec profile wsma_listener_http
wsma agent config profile wsma_listener_http
!
wsma profile listener wsma_listener_http
transport http</pre>
'''For WSMA (HTTPS) Configuration''':

 
<pre>ip http secure-server
wsma agent exec profile wsma_listener_https
wsma agent config profile wsma_listener_https
!
wsma profile listener wsma_listener_https
transport https

</pre>
'''For WSMA SSH Configuration''': 
<pre>crypto key generate rsa
ip ssh timeout 120
ip ssh version 2
!
wsma agent exec profile wsma_listener_ssh
wsma agent config profile wsma_listener_ssh
!
wsma profile listener wsma_listener_ssh
transport ssh
</pre>
For Cisco IOS IP Service Level agreement (SLA):

*Enable the responder role using the command: 
<pre>ip sla responder

</pre>
*The initiator role is not required. 
*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.

You can verify whether these roles are enabled on the device by using Prime Collaboration Inventory (Operate > Device Work Center > Current Inventory table).

For Performance Monitoring (PM) Configuration:

Configure the Performance Monitor policy on the relevant interfaces. Prime Collaboration collects PM flow statistics through MIBs. If this is configured, Prime Collaboration does not require the CLI access to routers.

== Supported Software Versions for the Cisco Medianet Feature ==

 

{| border="1" cellspacing="1" cellpadding="1" width="800"
|-
| '''Platform''' 
| '''Minimum IOS Release''' 
| '''Minimum Package''' 
| '''Feature Support''' 
|-
| Catalyst 3560 
| 15.0(1)SE2 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 3750 
| 15.0(1)SE2 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 4500E Supervisor 7-E/7L-E 
| XE 3.3.0SG 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 4500E Supervisor 6-E/6L-E 
| 15.1(1)SG 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 6500 Supervisor 2T 
| 15.0(1)SY 
| IP Services 
| Mediatrace, Performance Monitor 
|-
| ISR 2900 and 3900 
| 15.1(3)T 
| UC and Data 
| Mediatrace, Performance Monitor 
|-
| 
| 15.2(2)T 
| UC and DSP 
| IPSLA-VO Sender 
|-
| 
| 15.2(2)T 
| IP Base 
| IPSLA-VO Responder 
|-
| ISR 1900 
| 15.1(3)T 
| UC and Data 
| Mediatrace, Performance Monitor 
|-
| 
| 15.2(2)T 
| IP Base 
| IPSLA-VO Responder 
|-
| ISR 880 and 890 
| 15.1(3)T 
| Universal 
| Mediatrace, Performance Monitor 
|-
| ASR 1000 
| XE 3.5 
| IP Base 
| Performance Monitor 
|}

 

----

 

 

 

 

 

 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Sample123

2013-03-19T13:16:57Z

Chetrao: Created page with "dgfdfggdg"

dgfdfggdg

Setting up Devices for Prime Collaboration Assurance

2013-03-17T11:13:05Z

Chetrao: /* Required Protocols for the Devices (Includes Supported Software Versions) */

This section describes how to configure devices on the network before you manage them in Cisco Prime Collaboration Assurance.

= Required Protocols for the Devices (Includes Supported Software Versions) =

You must configure the endpoints, application managers, call processors, multipoint switches, and network devices with the following protocols:

*HTTP - Access the device through HTTP to poll system status and meeting information.
*SNMP - Read Community String and SNMP Authentication Protocol (SNMP V2 or SNMP V3) - Discover and manage the device.
*CLI - Access the device through CLI to discover media path for troubleshooting.
*JTAPI - Retrieve the session status information frosm the Cisco Unified CM.
*CDP - Discover neighboring devices.

 

{| border="1" cellspacing="1" cellpadding="1" width="1000"
|-
| '''Device''' 
| '''Supported Software''' 
| '''SNMP''' 
| '''HTTP''' 
| '''CLI''' 
| '''JTAPI''' 
| '''MSI''' 
| '''CDP''' 
| '''Notes''' 
|-
| Analog Gateway 
| - 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Contact Center Enterprise 
| 7.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Contact Center Express 
| 4.6 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Multipoint Switch 
| 1.7 – 1.9 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user account must have both the Meeting Manager and Diagnostic Technician roles. 
|-
| Cisco TelePresence System 
| 1.7 – 1.9 
| Yes 
| - 
| Yes 
| -
| Yes 
| - 
|
*CLI access is required if you want to use the Troubelshooting feature in Prime Collaboration. HTTP access is not required.
*The HTTP credentials (helpdesk role) are same as the SSH credentials, which are required by Prime Collaboration to troubleshoot.

|-
| Cisco TelePresence Manager (CTS-Manager) 
| 1.7 – 1.9 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*Requires the Reporting API license and the Reporting API role for the Prime Collaboration user.
*The HTTP user needs to be an exchange mailbox user and its User Group must have Reporting API and Live Desk roles in CTS-Manager. 
*If you have installed a licensed version of Prime Collaboration, it is mandatory to configure the CTS-Manager Reporting API. If this feature is not configured on the CTS-Manager 1.7, 1.8, or 1.9, Prime Collaboration will not manage the CTS-Manager. 

|-
| Cisco Unified CM 
| 7.1 – 9.0 
| Yes 
| Yes 
| - 
| Yes 
| - 
| - 
|
*The same credentials must be created for all devices in the cluster whenever clustering is used.
*The JTAPI user needs to have these roles Standard AXL API Access, CCM Admin Users, SERVICEABILITY Administration, CTI Enabled, and CTI Allow Call Monitoring.
*The session monitoring feature is supported only on Cisco Unified CM 8.5, 8.6 and 9.0. 

|-
| Cisco Unified Communications Manager Business Edition 
| 7.1 – 9.0 
| Yes 
| Yes 
| - 
| Yes 
| - 
| - 
| 
|-
| Customer Voice Portal 
| 4.0 - 8.5 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
|
*Cisco Codec EX series
*Cisco TelePresence System Integrator C Series
*Cisco TelePresence MX Series
*Cisco TelePresence System Profile Series
*Cisco TelePresence SX20 Quick Set
*Cisco TX 9000 series 

|
*EX series: TC 4.2 - 6.0; TE 6.0 
*C, MX, and SX series: TC 4.2 - 6.0 
*TX series: TX 6.0 

| Yes 
| Yes 
| Yes 
| - 
| Yes 
| - 
|
*The HTTP user requires Admin privilege. 
*For TC 6.0 and TE 6.0, use the same HTTP credentials for MSI. 
*For TX 6.0, use the default credentials msiuser and cisco for MSI. 

|-
| Cisco IP Video Phone E20 
| TE 4.0 - 6.0 
| Yes 
| Yes 
| Yes 
| - 
| Yes 
| - 
|
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration.
*Use the same HTTP credentials for MSI. 

|-
| Emergency Responder 
| 1.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Expert Advisor 
| 7.2 - 7.6 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Finesse 
| 8.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco MCU 
| 4.1 – 4.3 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*The HTTP user requires Admin privilege. 
*This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, and MSE-8710. 

|-
| Cisco TelePresence MSE Supervisor 
| 2.1 – 2.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user requires Admin privilege. 
|-
| Mediasense 
| 8.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Meeting Place 
| 7.0 - 8.5 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Meeting Place Express 
| 2.0 - 2.1 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Personal Assistant 
| 1.3 -1.4 
| - 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence System MXP series 
| 9.1 
| Yes 
| Yes 
| Yes 
| 
| 
| 
| 
|-
| Polycom VSX series Polycom HDX series 
| 2.5 - 3.0 (for HDX series) 9.0 (for VSX series) 
| Yes 
| - 
| - 
| - 
| - 
| - 
| End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 
|-
| Cisco Presence 
| 8.0 - 9.0 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Network devices (routers and switches) 
| 
| Yes 
| - 
| Yes 
| - 
| - 
| Yes 
|
*CDP needs to be enabled for the video Troubleshooting workflow. The Telnet or SSH access is required for Cisco Medianet features, which is part if the video Troubleshooting workflow. 
*See the table ''Supported Software Versions for the Cisco Medianet'' Feature below to view the troubleshooting medianet-related data. 

|-
| Cisco TelePresence Management Suite (Cisco TMS) 
| 13.0 – 13.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*Requires Booking API license (TMS software version 13.1 or below). 
*The HTTP user for Prime Collaboration needs to be generated through the Booking API on the Cisco TMS windows server. 
*Prime Collaboration supports only the default e-mail template for the Booking Confirm e-mail in Cisco TMS. The session import feature will not work, if the default e-mail template is not used. 

|-
| Cisco Telepresence Server 
| 2.1 – 2.2 
| - 
| Yes 
| - 
| - 
| - 
| - 
|
*The HTTP user account should have the API Access privilege.
*This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, MSE-8710. 

|-
| Cisco Telepresence Conductor 
| 1.1 - 1.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity
| 7.0 - 8.6
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity Connection
| 7.0 - 9.0
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity Express
| 7.0 - 9.0
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Video Communication Server (Control and Expressway) 
| 6.0 – 7.1 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user requires Admin privilege. 
|-
| Wireless 
| - 
| Yes 
| - 
| Yes 
| - 
| - 
| - 
| 
|-
| Third party devices 
| - 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Jabber Video for Telepresence (Movi) 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco Jabber endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required).
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Cisco Cius 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco Cius endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required). You must enable web access in Cisco Unified CM for these. 
*Credentials are not required for HTTP access. 
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Cisco IP phones (89xx, 99xx) 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco IP Phones endpoints are discovered through Cisco Unified CM. You must enable web access in Cisco Unified CM for these. 
*These video phones require Cisco Unified CM application user to have the additional role ''Standard CTI Allow Control of Phones supporting Connected Xfer and conf''. 
*Credentials are not required for HTTP access. 
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Border Element, Gatekeeper, H323 Gateway, SIP Gateway MGCP Gateway, SRST Device, Voice Gateway 
| IOS 12.x or later 
| - 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Exchange
| 1.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| CUBE/SBC
| - 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|}

 

= Configuring Call Controllers and Processors =

== Cisco Unified Communications Manager ==

All CTS endpoints must be added as controlled devices in Cisco Unified CM to facilitate call detection. You must configure a HTTP and JTAPI user on the call processor.

'''Note''': The procedures described below are applicable for Cisco Unified CM 8.5. If you are using any other supported versions, see the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html ''Cisco Unified CM guides''] to understand how to create groups, users and assign roles to them. 

'''Enable HTTP'''

You do not have to create a new user if you want to allow Cisco Prime Collaboration to use admin credentials to log in. Alternatively, if you want to allow Cisco Prime Collaboration Manager to use the right credentials to log in to Cisco Unified Communications Manager, you must create a new HTTP user group and a corresponding user that Cisco Prime Collaboration can use to communicate.

To create a user:

#Create a user group with sufficient privileges. Log in to the Cisco Unified Communications Manager Administration web interface using the administrator role.
#Navigate to '''User Management''' > '''User Groups''' and create a new group with a suitable name, PC_HTTP_Users in this case.
#Click '''Role'''.
#Click '''Assign Role to Group''' and select the following roles:
#*Standard AXL API Access
#*Standard CCM Admin Users
#*Standard SERVICEABILITY Administration
#Click '''Save'''.
#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration to monitor all devices.
#In the '''Permission Information''' section, click '''Add to User Group''' and select the group that was created in Step 1. (PC_HTTP_Users, for instance).
#Click '''Save'''. The page is refreshed and the right privileges are displayed.

'''Enable SNMP'''

SNMP is not enabled in Cisco Unified Communications Manager by default.

To enable SNMP:

#Log in to the '''Cisco Unified Serviceability''' view in the Cisco Unified Communications Manager web GUI.
#From the main menu in the Cisco Unified Serviceability view, navigate to SNMP > v1/v2c > community string.
#Select a Server and click '''Find'''. If the community string is already defined, the Community String Name is displayed in the Search Results.
#Click '''Add new '''to add a new string if no results are displayed.
#Specify the required SNMP information and save the configuration.

'''Enable JTAPI'''

JTAPI (Java Telephony API) is used to retrieve the session status information from the device. You must create a JTAPI user in the call processor with the required permission to receive JTAPI events on endpoints. Prime Collaboration manages multiple call processor clusters. You must ensure that the cluster IDs are unique. Create a new JTAPI user to help Cisco Prime Collaboration get the required information.

To create a new JTAPI user:

#Log in to the Cisco Unified Communications Manager administration web interface using administrator role.
#Navigate to User Management > '''User Groups''' and create a new group with a suitable name, '''PC_HTTP_Users''' in this case.
#Move all endpoint devices (for example, Cisco TelePresence codecs) to the Controlled Devices table.
#Click '''Roles'''.
#Click '''Assign Role to Group''' and select the following roles:
#*Standard CTI Allow Call Monitoring
#*Standard CTI Enabled
#*Standard CTI Allow Control of Phones supporting Connected Xfer and conf
#Click '''Save'''.
#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration to monitor all devices. '''Note''': The password must not contain a semicolon (;) or equals (=).
#In the '''Permission Information''' section, click '''Add to User Group''' and select the group that was created in step 1. (PC_HTTP_Users, for instance).
#Click '''Save'''. The page is refreshed and the right privileges are displayed.
<pre>Note:
*Ensure the following services are activated and started:
**Cisco CTIManager
**Cisco AXL Web Service
See the Cisco Unified Communications Manager guide for details about how
to configure the application user.

You can access the log files to verify whether the endpoints are assisned with the CTI-controlled roles in the Unified CM
and for the JTAPI-related issues using https://<primecollaboration-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log
</pre>
== Cisco TelePresence Video Communication Server ==

Cisco VCS serves as a call-control appliance for the Cisco TelePresence C Series, E Series, and other similar video endpoints.

'''Enable HTTP'''

You can access Cisco VCS through a web browser: http://<vcs_serveraddress>, where <vcs_serveraddress> is the IP address or hostname of your VCS appliance. The default password for administrator user '''admin''' is TANDBERG. If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the VCS. Ensure the password field is not blank as it is not recommended.

'''Enable SNMP'''

You can easily enable SNMP from the Cisco VCS web GUI: Navigate to '''System''' > '''SNMP''' and enter the SNMP information.

= Configuring Endpoints =

== Cisco TelePresence System Video Endpoints ==

'''Enable HTTP'''

You can access Cisco TelePresence system video endpoints through a web browser (preferably using Internet Explorer, if possible) by pointing the browser to:https://<serveraddress> where <serveraddress> is the IP address or hostname of the Cisco TelePresence system video endpoint.

'''Enable SNMP'''

SNMP for Cisco TelePresence system devices is configured using Cisco Unified Communications Manager phone configuration. To change the SNMP community string:

#Navigate to Cisco Unified Communications Manager Administration.
#Navigate to '''Device''' > '''Phone''' and search for Cisco TelePresence system endpoints.
#Click the '''Device Name''' link to go to the phone configuration page.
#Edit the SNMP Configuration Parameters.
#Click '''Save''' '''and''' '''Apply Config'''.

'''Enable CLI Access'''

SSH access to the Cisco TelePresence system devices is also controlled through Cisco Unified Communications Manager Phone Configuration.
<pre>Note:
If the value of SSH admin Life and SSH helpdesk Life field is zero, the password never
expires (recommended for lab testing scenarios).
However, if the value is not zero, the admin must ensure that passwords are changed
before the specified interval, for anyone or any application to be able to perform SSH
in the device including Cisco Prime Collaboration. </pre>
== Cisco TelePresence C and EX Series Video Endpoints ==

'''Enable HTTP'''

By default, HTTP is enabled for Cisco TelePresence Endpoints. Point the web browser to http://<ip_address>, where <ip_address> is the IP address or hostname of the video endpoint. The default password for the administrator user '''admin''' is " ", blank space.

'''Enable SNMP'''

To enable SNMP access for Cisco Prime Collaboration from the web interface:

Navigate to '''Configuration''' > '''Adv Configuration''' > '''Network Services''' > '''SNMP''' and click the value to edit.

'''Enable CLI Access'''

SSH must be enabled by default on TC 4.0 releases. Provide '''admin''' user access to Cisco Prime Collaboration ensure that the admin password is set and is not the default value, which is blank. Admin user access is necessary if you want to troubleshoot video sessions from Cisco TelePresence devices using Cisco Prime Collaboration. Some of the commands required to run the traceroutes are available only when you log in as root.

We recommend that you enter the real interface IP address of the gateway that runs the Hot Standby Router Protocol (HSRP), instead of the virtual IP address, while configuring the CTS. This enables Prime Collaborationto accurately discover the troubleshooting path.

Endpoint monitoring is based on the SNMP polling. You can configure traps and syslogs on the endpoints, if required.

To monitor traps and syslogs:

*Configure trap and syslog receivers for endpoints in call processors.
*Enter the Prime Collaboration IP address to configure the trap receiver: <PrimeCollaboration_ip_addr>
*Enter the Prime Collaboration IP address and port number 20514 to configure syslog receiver.: <PrimeCollaboration_ip_addr>:20514.
*Enable endpoints to send traps and syslogs.

To enable traps:

*In CISCO-TELEPRESENCE-MIB, set ctpPeripheralErrorNotifyEnable to true (1)
*In CISCO-TELEPRESENCE-CALL-MIB, set ctpcStatNotifyEnable to true (1)
*In CISCO-TELEPRESENCE-CALL-MIB, set threshold values for call stats ctpcStatMonitoredEntry

To enable syslogs: In CISCO-SYSLOG-MIB, set clogNotificationsEnabled to true (1).

= Configuring Call Management Applications =

== Cisco TelePresence Management Suite ==

HTTP and SNMP access are required to successfully monitor Cisco TMS.

'''Enable HTTP'''

Cisco TMS is accessed through a web browser (http://<serveraddress>/TMS), where <serveraddress> is the IP address or hostname of your server. The default password for the administrator user '''admin''' is '''TANDBERG'''.

If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully monitor Cisco TMS.

'''Enable SNMP'''

By default, '''public''' and '''Public''' are enabled as SNMP Read Only (RO) community strings for Cisco TMS. This string is used by Cisco TMS to poll other devices.

If you need to add or change these strings:

Go to the web GUI and navigate to '''Administrative''' '''Tools''' > '''Configuration''' > '''Network Settings''' and change the SNMP settings.

In addition to the Web GUI, SNMP service on the Cisco TMS server must be enabled.

To enable SNMP:

#Go to '''Start '''on the server console.
#Click '''Run '''and specify services.msc. A Service window will pop open on the server console.
#Right-click '''SNMP Service '''and select '''Properties'''.
#Click '''Security '''and select '''Add new SNMP''' string. Do not modify the default selection: Accept SNMP packets from any host unless you want only specific hosts polling SNMP from Cisco TMS.
#Optionally, click '''Traps '''to add the IP address of Cisco Prime Collaboration and a community string. This address is used in SNMP traps.
#Optionally, click '''Agent '''to specify SNMP contact and location for Cisco TMS. The Cisco Prime Collaboration uses this information to display the location of Cisco TMS in the inventory.
#Restart the '''SNMP Service '''after the necessary modifications.

== Reporting API for CTS-Manager ==

For Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager, you must have a valid Metrics Dashboard and Reporting API license in CTS-Manager. This user account should be configured in Active Directory with a mailbox and in a user group with general security. The Active Directory user group should be assigned the '''Reporting API '''role and the '''Live Desk '''role in the CTS-Manager Access Management page.
<pre>Note:
We recommend that you review the Getting Started With TelePresence Reporting API
document available at [http://developer.cisco.com/web/tra/start] for an understanding
of the Reporting API.</pre>
'''Note''': The procedures described below are applicable for CTS-Manager 1.8. If you are using any other supported versions, see the CTS-Manager Reporting API related documents. 

To enable Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager 1.8:

#In the LDAP server, create a user group. For example,create a group named pc_group.
#In the group that you created in the LDAP server, create a user. For example, create a user named pc_user. You must ensure that a valid mailbox is configured for the user created in the group in the LDAP server.
#In CTS-Manager, in the '''Access Management '''page, assign the '''Live Desk''' role and the '''Reporting API User''' role for the group you created in the LDAP server, for example, pc_group created in ''Step 1''.
#Discover the CTS-Manager in Prime Collaboration with the user that you created in the LDAP server. For example, use pc_user.

For more information about the Reporting API, see ''Cisco Telepresense Manager Reporting API Developer's Guide for Release 1.8.''

For more information about user and group configuration in LDAP server, see ''Cisco Telepresense Manager 1.8 Administration and Installation Guide''.
<pre>Note:
After creating the user account in CTS-Manager for the Prime Collaboration application, we recommend
that you log in with this account in CTS-Manager at least once before you enter the
credentials in the Prime Collaboration server.</pre>
== Cisco TMS Third Party Booking API User ==

For the Prime Collaboration server to retrieve scheduled meetings from Cisco TMS server, you must have one Application Integration License for each server that uses the API.
<pre>Note:
*We recommend that you review the Cisco TMS Third Party Booking API document available
at [http://www.tandberg.com/support/tms_documentation.jsp] for an understanding of the
Booking API.

*For Cisco TMS 13.2 and later, any HTTP user can be used to retrieve scheduled meetings
from Cisco TMS server. In addition, you do not need to install a Booking API License to
use the API.</pre>
To enable Prime Collaboration server to retrieve scheduled meetings from Cisco TMS:

#From the Cisco TMS server, go to [http://localhost/tms/external/booking/remotesetup/remotesetupservice.asmx http://localhost/tms/external/booking/remotesetup/remotesetupservice.asmx]. The RemoteSetupService page appears. You may replace localhost in the above URL with the IP address of the Cisco TMS server.
#Choose '''GenerateConferenceAPIUser'''.
#Enter the values for the following parameters:
#*userNameBase - The base portion of the user name. For example, pc_user.
#*encPassword - A base64 encoded password that is to be used for the newly created user. To encode the password to base64, we recommend that you use the web utility available at the following URL: http://www.motobit.com/util/base64-decoder-encoder.asp.
#*emailAddress - The email address of the user. Do not enter values in this field.
#*sendNotifications - To allow the user to receive scheduling notifications. You must enter False in this field since Prime Collaboration will be polling from Cisco TMS.
#Click '''Invoke'''.
#In the Cisco TMS application, verify the user name configured in Step 3is listed in the Users page.
#In the Cisco TMS application, create a user group. For example, create a group named pc_group.
#Add the user created in Step 3 to the group created in Step 6. For example, add pc_user to pc_group.
#In the '''Groups '''page, for the group created in Step 6, check the Read permission check box for List Conferences-All (under the Booking pane). For example, pc_group must have the read permission to List Conferences-All.
#Discover the Cisco TMS in Cisco Prime Collaboration with the user that you created in Step 3. For example, use pc_user.

For more information about the Cisco TMS, see the documents available at [[Www.tandberg.com/support/tms documentation.jsp|TANDBERG]] site.

For more information on creating groups and setting permission to the group, see ''Ciso Telepresence Management Suite Administrator Guide''.

= Configuring MCUs =

A Cisco TelePresence MCU MSE 8510 (MCU MSE 8510) cluster consists of a Cisco TelePresence MCU MSE 8050 Supervisor Blade (MCU MSE 8550) and a MCU MSE 8510 blade. After the basic information is configured, HTTP access is enabled by default.

'''Enable HTTP'''

The supervisor web interface can be accessed by pointing the browser to http://<MCU_Address>, where <MCU_Address> is the IP address or hostname of your server. The default password for the '''admin''' user is a blank space (no password). If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the MCU MSE Supervisor.

To log in to the web interface of the MCU MSE 8510 blade:

#Log in to the supervisor web interface.
#Go to '''Hardware''' > '''Blades''' and click the IP address of the MCU MSE 8510 blade.
#Click '''Log in''', and enter the username '''admin''' with no password.

'''Enable SNMP'''

You can edit SNMP settings by logging in to the MCU Codian Web Interface:

#Navigate to '''Network''' > '''SNMP'''.
#Edit the SNMP Read Only and Read Write strings as required.
#Click '''Update SNMP Settings''' to apply the changes.

= Configuring Cisco TelePresence Multipoint Switch =

'''Enable HTTP'''

A separate HTTP user account must be created with the Meeting Scheduler and Diagnostic Technician roles assigned to it for the Prime Collaboration application. This user can be configured in the Multipoint Switch web user interface when logged in as admin. After the dedicated HTTP user has been created, you must login to CTMS web UI using this user credential and then change the password (the same password can be entered).

An '''admin''' user is not required by Cisco Prime Collaboration to manage the Multipoint Switch.

You can access the Multipoint Switch through a web browser (preferably using Internet Explorer) by pointing the browser to: https://<ctms_serveraddress>, where <ctms_serveraddress> is the IP address or hostname of the Multipoint Switch.

'''Enable SNMP'''

SNMP is enabled by default and it monitors the Multipoint Switch system status (navigate to Troubleshoot > System Resources for system status details). You can designate a particular server where SNMP trap messages are gathered and stored. You configure all SNMP settings through the Multipoint Switch CLI commands.

The following SNMP settings are enabled by default:

*SNMPv3 username set to '''mrtg''': This name is for internal use of the system and should not be deleted.
*SNMPv2c username set to '''public''': This name is for internal use of the system and should not be deleted.
*No trap receiver is configured. Use Multipoint Switch CLI commands to configure SNMP trap receiver information.

Use SSH in the Multipoint Switch to configure SNMP using the CLI. The CLI commands to configure SNMP Read Only and Read/Write are as follows:

*set snmp user add 2c snmpro r
*set snmp user add 2c snmprw rw
<pre>Note:
Replace snmpro and snmprw with your SNMP Read and Read/Write community strings.
After creating the user account in CTMS for the Prime Collaboration application, we recommend
that you log in with this account in CTMS at least once before you enter the
credentials in the Prime Collaboration server.
</pre>

= Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices =

If you have enabled [http://www.cisco.com/web/solutions/medianet/knowledgebase/index.html#~configure Cisco Mediatrace] on your network nodes, Prime Collaboration provides Medianet Path View as part of the troubleshooting data. If you have enabled Cisco IOS IP Service Level Agreements (SLAs) on your network nodes, you can measure the network performance and health using the Proactive Troubleshooting feature.

For Cisco Mediatrace:

*Enable the initiator and/or responder roles on relevant routers and switches using the following commands: '''For Mediatrace Initiator''': 

 
<pre>mediatrace initiator source-ip ''IP Address''</pre>
 '''For Mediatrace Responder''': 

 
<pre>mediatrace responder
</pre>
 

*Configure a Telnet local login user with privilege 15 on the initiators.
*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators. See ''Web Services Management Agent (WSMA) Configuration Guide'' for details on the configuration commands. 

'''Local Auth Example''': 
<pre>username <username> priv 15 secret <username_enable_password>
ip http authentication local

</pre>
'''For WSMA (HTTP) Configuration''':
<pre>ip http server
ip http timeout-policy idle 60 life 86400 requests 10000
wsma agent exec profile wsma_listener_http
wsma agent config profile wsma_listener_http
!
wsma profile listener wsma_listener_http
transport http</pre>
'''For WSMA (HTTPS) Configuration''':

 
<pre>ip http secure-server
wsma agent exec profile wsma_listener_https
wsma agent config profile wsma_listener_https
!
wsma profile listener wsma_listener_https
transport https

</pre>
'''For WSMA SSH Configuration''': 
<pre>crypto key generate rsa
ip ssh timeout 120
ip ssh version 2
!
wsma agent exec profile wsma_listener_ssh
wsma agent config profile wsma_listener_ssh
!
wsma profile listener wsma_listener_ssh
transport ssh
</pre>
For Cisco IOS IP Service Level agreement (SLA):

*Enable the responder role using the command: 
<pre>ip sla responder

</pre>
*The initiator role is not required. 
*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.

You can verify whether these roles are enabled on the device by using Prime Collaboration Inventory (Operate > Device Work Center > Current Inventory table).

For Performance Monitoring (PM) Configuration:

Configure the Performance Monitor policy on the relevant interfaces. Prime Collaboration collects PM flow statistics through MIBs. If this is configured, Prime Collaboration does not require the CLI access to routers.

== Supported Software Versions for the Cisco Medianet Feature ==

 

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
| '''Platform''' 
| '''Minimum IOS Release''' 
| '''Minimum Package''' 
| '''Feature Support''' 
|-
| Catalyst 3560 
| 15.0(1)SE2 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 3750 
| 15.0(1)SE2 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 4500E Supervisor 7-E/7L-E 
| XE 3.3.0SG 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 4500E Supervisor 6-E/6L-E 
| 15.1(1)SG 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 6500 Supervisor 2T 
| 15.0(1)SY 
| IP Services 
| Mediatrace, Performance Monitor 
|-
| ISR 2900 and 3900 
| 15.1(3)T 
| UC and Data 
| Mediatrace, Performance Monitor 
|-
| 
| 15.2(2)T 
| UC and DSP 
| IPSLA-VO Sender 
|-
| 
| 15.2(2)T 
| IP Base 
| IPSLA-VO Responder 
|-
| ISR 1900 
| 15.1(3)T 
| UC and Data 
| Mediatrace, Performance Monitor 
|-
| 
| 15.2(2)T 
| IP Base 
| IPSLA-VO Responder 
|-
| ISR 880 and 890 
| 15.1(3)T 
| Universal 
| Mediatrace, Performance Monitor 
|-
| ASR 1000 
| XE 3.5 
| IP Base 
| Performance Monitor 
|}

 

----

 

 

 

 

 

 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Setting up Devices for Prime Collaboration Assurance

2013-03-15T06:51:13Z

Chetrao:

This section describes how to configure devices on the network before you manage them in Cisco Prime Collaboration Assurance.

= Required Protocols for the Devices (Includes Supported Software Versions) =

You must configure the endpoints, application managers, call processors, multipoint switches, and network devices with the following protocols:

*HTTP - Access the device through HTTP to poll system status and meeting information.
*SNMP - Read Community String and SNMP Authentication Protocol (SNMP V2 or SNMP V3) - Discover and manage the device.
*CLI - Access the device through CLI to discover media path for troubleshooting.
*JTAPI - Retrieve the session status information frosm the Cisco Unified CM.
*CDP - Discover neighboring devices.

 

{| border="1" cellspacing="1" cellpadding="1" width="1000"
|-
| '''Device''' 
| '''Supported Software''' 
| '''SNMP''' 
| '''HTTP''' 
| '''CLI''' 
| '''JTAPI''' 
| '''MSI''' 
| '''CDP''' 
| '''Notes''' 
|-
| Analog Gateway 
| - 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Contact Center Enterprise 
| 7.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Contact Center Express 
| 4.6 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Multipoint Switch 
| 1.7 – 1.9 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user account must have both the Meeting Manager and Diagnostic Technician roles. 
|-
| Cisco TelePresence System 
| 1.7 – 1.9 
| Yes 
| - 
| Yes 
| -
| Yes 
| - 
|
*CLI access is required if you want to use the Troubelshooting feature in Prime Collaboration. HTTP access is not required.
*The HTTP credentials (helpdesk role) are same as the SSH credentials, which are required by Prime Collaboration to troubleshoot.

|-
| Cisco TelePresence Manager (CTS-Manager) 
| 1.7 – 1.9 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*Requires the Reporting API license and the Reporting API role for the Prime Collaboration user.
*The HTTP user needs to be an exchange mailbox user and its User Group must have Reporting API and Live Desk roles in CTS-Manager. 
*If you have installed a licensed version of Prime Collaboration, it is mandatory to configure the CTS-Manager Reporting API. If this feature is not configured on the CTS-Manager 1.7, 1.8, or 1.9, Prime Collaboration will not manage the CTS-Manager. 

|-
| Cisco Unified CM 
| 7.1 – 9.0 
| Yes 
| Yes 
| - 
| Yes 
| - 
| - 
|
*The same credentials must be created for all devices in the cluster whenever clustering is used.
*The JTAPI user needs to have these roles Standard AXL API Access, CCM Admin Users, SERVICEABILITY Administration, CTI Enabled, and CTI Allow Call Monitoring.
*The session monitoring feature is supported only on Cisco Unified CM 8.5, 8.6 and 9.0. 

|-
| Cisco Unified Communications Manager Business Edition 
| 7.1 – 9.0 
| Yes 
| Yes 
| - 
| Yes 
| - 
| - 
| 
|-
| Customer Voice Portal 
| 4.0 - 8.5 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
|
*Cisco Codec EX series
*Cisco TelePresence System Integrator C Series
*Cisco TelePresence MX Series
*Cisco TelePresence System Profile Series
*Cisco TelePresence SX20 Quick Set
*Cisco TX 9000 series 

|
*EX series: TC 4.2 - 6.0; TE 6.0 
*C, MX, and SX series: TC 4.2 - 6.0 
*TX series: TX 6.0 

| Yes 
| Yes 
| Yes 
| - 
| Yes 
| - 
|
*The HTTP user requires Admin privilege. 
*For TC 6.0 and TE 6.0, use the same HTTP credentials for MSI. 
*For TX 6.0, use the default credentials msiuser and cisco for MSI. 

|-
| Cisco IP Video Phone E20 
| TE 4.0 - 6.0 
| Yes 
| Yes 
| Yes 
| - 
| Yes 
| - 
|
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration.
*Use the same HTTP credentials for MSI. 

|-
| Emergency Responder 
| 1.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Expert Advisor 
| 7.2 - 7.6 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Finesse 
| 8.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco MCU 
| 4.1 – 4.3 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*The HTTP user requires Admin privilege. 
*This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, and MSE-8710. 

|-
| Cisco TelePresence MSE Supervisor 
| 2.1 – 2.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user requires Admin privilege. 
|-
| Mediasense 
| 8.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Meeting Place 
| 7.0 - 8.5 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Meeting Place Express 
| 2.0 - 2.1 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Personal Assistant 
| 1.3 -1.4 
| - 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence System MXP series 
| 9.1 
| Yes 
| Yes 
| Yes 
| 
| 
| 
| 
|-
| Polycom VSX series Polycom HDX series 
| 2.5 - 3.0 (for HDX series) 9.0 (for VSX series) 
| Yes 
| - 
| - 
| - 
| - 
| - 
| End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 
|-
| Cisco Presence 
| 8.0 - 9.0 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Network devices (routers and switches) 
| 
| Yes 
| - 
| Yes 
| - 
| - 
| Yes 
|
*CDP needs to be enabled for the video Troubleshooting workflow. The Telnet or SSH access is required for Cisco Medianet features, which is part if the video Troubleshooting workflow. 
*See the table ''Supported Software Versions for the Cisco Medianet'' Feature below to view the troubleshooting medianet-related data. 

|-
| Cisco TelePresence Management Suite (Cisco TMS) 
| 13.0 – 13.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*Requires Booking API license (TMS software version 13.1 or below). 
*The HTTP user for Prime Collaboration needs to be generated through the Booking API on the Cisco TMS windows server. 
*Prime Collaboration supports only the default e-mail template for the Booking Confirm e-mail in Cisco TMS. The session import feature will not work, if the default e-mail template is not used. 

|-
| Cisco Telepresence Server 
| 2.1 – 2.2 
| - 
| Yes 
| - 
| - 
| - 
| - 
|
*The HTTP user account should have the API Access privilege.
*This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, MSE-8710. 

|-
| Cisco Telepresence Conductor 
| 1.1 - 1.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity
| 7.0 - 8.6
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity Connection
| 7.0 - 9.0
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity Express
| 7.0 - 9.0
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Video Communication Server (Control and Expressway) 
| 6.0 – 7.1 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user requires Admin privilege. 
|-
| Wireless 
| - 
| Yes 
| - 
| Yes 
| - 
| - 
| - 
| 
|-
| Third party devices 
| - 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Jabber Video for Telepresence (Movi) 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco Jabber endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required).
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Cisco Cius 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco Cius endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required). You must enable web access in Cisco Unified CM for these. 
*Credentials are not required for HTTP access. 
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Cisco IP phones (89xx, 99xx) 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco IP Phones endpoints are discovered through Cisco Unified CM. You must enable web access in Cisco Unified CM for these. 
*These video phones require Cisco Unified CM application user to have the additional role ''Standard CTI Allow Control of Phones supporting Connected Xfer and conf''. 
*Credentials are not required for HTTP access. 
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Border Element, Gatekeeper, H323 Gateway, SIP Gateway MGCP Gateway, SRST Device, Voice Gateway, CUBE 
| IOS 12.x or later 
| - 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Exchange
| 1.2
| Yes
| Yes
| -
| -
| -
| -
|
|-
| CUBE/SBC
| -
| Yes
|
|
|
|
|
|
|}

 

= Configuring Call Controllers and Processors =

== Cisco Unified Communications Manager ==

All CTS endpoints must be added as controlled devices in Cisco Unified CM to facilitate call detection. You must configure a HTTP and JTAPI user on the call processor.

'''Note''': The procedures described below are applicable for Cisco Unified CM 8.5. If you are using any other supported versions, see the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html ''Cisco Unified CM guides''] to understand how to create groups, users and assign roles to them. 

'''Enable HTTP'''

You do not have to create a new user if you want to allow Cisco Prime Collaboration to use admin credentials to log in. Alternatively, if you want to allow Cisco Prime Collaboration Manager to use the right credentials to log in to Cisco Unified Communications Manager, you must create a new HTTP user group and a corresponding user that Cisco Prime Collaboration can use to communicate.

To create a user:

#Create a user group with sufficient privileges. Log in to the Cisco Unified Communications Manager Administration web interface using the administrator role.
#Navigate to '''User Management''' > '''User Groups''' and create a new group with a suitable name, PC_HTTP_Users in this case.
#Click '''Role'''.
#Click '''Assign Role to Group''' and select the following roles:
#*Standard AXL API Access
#*Standard CCM Admin Users
#*Standard SERVICEABILITY Administration
#Click '''Save'''.
#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration to monitor all devices.
#In the '''Permission Information''' section, click '''Add to User Group''' and select the group that was created in Step 1. (PC_HTTP_Users, for instance).
#Click '''Save'''. The page is refreshed and the right privileges are displayed.

'''Enable SNMP'''

SNMP is not enabled in Cisco Unified Communications Manager by default.

To enable SNMP:

#Log in to the '''Cisco Unified Serviceability''' view in the Cisco Unified Communications Manager web GUI.
#From the main menu in the Cisco Unified Serviceability view, navigate to SNMP > v1/v2c > community string.
#Select a Server and click '''Find'''. If the community string is already defined, the Community String Name is displayed in the Search Results.
#Click '''Add new '''to add a new string if no results are displayed.
#Specify the required SNMP information and save the configuration.

'''Enable JTAPI'''

JTAPI (Java Telephony API) is used to retrieve the session status information from the device. You must create a JTAPI user in the call processor with the required permission to receive JTAPI events on endpoints. Prime Collaboration manages multiple call processor clusters. You must ensure that the cluster IDs are unique. Create a new JTAPI user to help Cisco Prime Collaboration get the required information.

To create a new JTAPI user:

#Log in to the Cisco Unified Communications Manager administration web interface using administrator role.
#Navigate to User Management > '''User Groups''' and create a new group with a suitable name, '''PC_HTTP_Users''' in this case.
#Move all endpoint devices (for example, Cisco TelePresence codecs) to the Controlled Devices table.
#Click '''Roles'''.
#Click '''Assign Role to Group''' and select the following roles:
#*Standard CTI Allow Call Monitoring
#*Standard CTI Enabled
#*Standard CTI Allow Control of Phones supporting Connected Xfer and conf
#Click '''Save'''.
#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration to monitor all devices. '''Note''': The password must not contain a semicolon (;) or equals (=).
#In the '''Permission Information''' section, click '''Add to User Group''' and select the group that was created in step 1. (PC_HTTP_Users, for instance).
#Click '''Save'''. The page is refreshed and the right privileges are displayed.
<pre>Note:
*Ensure the following services are activated and started:
**Cisco CTIManager
**Cisco AXL Web Service
See the Cisco Unified Communications Manager guide for details about how
to configure the application user.

You can access the log files to verify whether the endpoints are assisned with the CTI-controlled roles in the Unified CM
and for the JTAPI-related issues using https://<primecollaboration-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log
</pre>
== Cisco TelePresence Video Communication Server ==

Cisco VCS serves as a call-control appliance for the Cisco TelePresence C Series, E Series, and other similar video endpoints.

'''Enable HTTP'''

You can access Cisco VCS through a web browser: http://<vcs_serveraddress>, where <vcs_serveraddress> is the IP address or hostname of your VCS appliance. The default password for administrator user '''admin''' is TANDBERG. If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the VCS. Ensure the password field is not blank as it is not recommended.

'''Enable SNMP'''

You can easily enable SNMP from the Cisco VCS web GUI: Navigate to '''System''' > '''SNMP''' and enter the SNMP information.

= Configuring Endpoints =

== Cisco TelePresence System Video Endpoints ==

'''Enable HTTP'''

You can access Cisco TelePresence system video endpoints through a web browser (preferably using Internet Explorer, if possible) by pointing the browser to:https://<serveraddress> where <serveraddress> is the IP address or hostname of the Cisco TelePresence system video endpoint.

'''Enable SNMP'''

SNMP for Cisco TelePresence system devices is configured using Cisco Unified Communications Manager phone configuration. To change the SNMP community string:

#Navigate to Cisco Unified Communications Manager Administration.
#Navigate to '''Device''' > '''Phone''' and search for Cisco TelePresence system endpoints.
#Click the '''Device Name''' link to go to the phone configuration page.
#Edit the SNMP Configuration Parameters.
#Click '''Save''' '''and''' '''Apply Config'''.

'''Enable CLI Access'''

SSH access to the Cisco TelePresence system devices is also controlled through Cisco Unified Communications Manager Phone Configuration.
<pre>Note:
If the value of SSH admin Life and SSH helpdesk Life field is zero, the password never
expires (recommended for lab testing scenarios).
However, if the value is not zero, the admin must ensure that passwords are changed
before the specified interval, for anyone or any application to be able to perform SSH
in the device including Cisco Prime Collaboration. </pre>
== Cisco TelePresence C and EX Series Video Endpoints ==

'''Enable HTTP'''

By default, HTTP is enabled for Cisco TelePresence Endpoints. Point the web browser to http://<ip_address>, where <ip_address> is the IP address or hostname of the video endpoint. The default password for the administrator user '''admin''' is " ", blank space.

'''Enable SNMP'''

To enable SNMP access for Cisco Prime Collaboration from the web interface:

Navigate to '''Configuration''' > '''Adv Configuration''' > '''Network Services''' > '''SNMP''' and click the value to edit.

'''Enable CLI Access'''

SSH must be enabled by default on TC 4.0 releases. Provide '''admin''' user access to Cisco Prime Collaboration ensure that the admin password is set and is not the default value, which is blank. Admin user access is necessary if you want to troubleshoot video sessions from Cisco TelePresence devices using Cisco Prime Collaboration. Some of the commands required to run the traceroutes are available only when you log in as root.

We recommend that you enter the real interface IP address of the gateway that runs the Hot Standby Router Protocol (HSRP), instead of the virtual IP address, while configuring the CTS. This enables Prime Collaborationto accurately discover the troubleshooting path.

Endpoint monitoring is based on the SNMP polling. You can configure traps and syslogs on the endpoints, if required.

To monitor traps and syslogs:

*Configure trap and syslog receivers for endpoints in call processors.
*Enter the Prime Collaboration IP address to configure the trap receiver: <PrimeCollaboration_ip_addr>
*Enter the Prime Collaboration IP address and port number 20514 to configure syslog receiver.: <PrimeCollaboration_ip_addr>:20514.
*Enable endpoints to send traps and syslogs.

To enable traps:

*In CISCO-TELEPRESENCE-MIB, set ctpPeripheralErrorNotifyEnable to true (1)
*In CISCO-TELEPRESENCE-CALL-MIB, set ctpcStatNotifyEnable to true (1)
*In CISCO-TELEPRESENCE-CALL-MIB, set threshold values for call stats ctpcStatMonitoredEntry

To enable syslogs: In CISCO-SYSLOG-MIB, set clogNotificationsEnabled to true (1).

= Configuring Call Management Applications =

== Cisco TelePresence Management Suite ==

HTTP and SNMP access are required to successfully monitor Cisco TMS.

'''Enable HTTP'''

Cisco TMS is accessed through a web browser (http://<serveraddress>/TMS), where <serveraddress> is the IP address or hostname of your server. The default password for the administrator user '''admin''' is '''TANDBERG'''.

If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully monitor Cisco TMS.

'''Enable SNMP'''

By default, '''public''' and '''Public''' are enabled as SNMP Read Only (RO) community strings for Cisco TMS. This string is used by Cisco TMS to poll other devices.

If you need to add or change these strings:

Go to the web GUI and navigate to '''Administrative''' '''Tools''' > '''Configuration''' > '''Network Settings''' and change the SNMP settings.

In addition to the Web GUI, SNMP service on the Cisco TMS server must be enabled.

To enable SNMP:

#Go to '''Start '''on the server console.
#Click '''Run '''and specify services.msc. A Service window will pop open on the server console.
#Right-click '''SNMP Service '''and select '''Properties'''.
#Click '''Security '''and select '''Add new SNMP''' string. Do not modify the default selection: Accept SNMP packets from any host unless you want only specific hosts polling SNMP from Cisco TMS.
#Optionally, click '''Traps '''to add the IP address of Cisco Prime Collaboration and a community string. This address is used in SNMP traps.
#Optionally, click '''Agent '''to specify SNMP contact and location for Cisco TMS. The Cisco Prime Collaboration uses this information to display the location of Cisco TMS in the inventory.
#Restart the '''SNMP Service '''after the necessary modifications.

== Reporting API for CTS-Manager ==

For Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager, you must have a valid Metrics Dashboard and Reporting API license in CTS-Manager. This user account should be configured in Active Directory with a mailbox and in a user group with general security. The Active Directory user group should be assigned the '''Reporting API '''role and the '''Live Desk '''role in the CTS-Manager Access Management page.
<pre>Note:
We recommend that you review the Getting Started With TelePresence Reporting API
document available at [http://developer.cisco.com/web/tra/start] for an understanding
of the Reporting API.</pre>
'''Note''': The procedures described below are applicable for CTS-Manager 1.8. If you are using any other supported versions, see the CTS-Manager Reporting API related documents. 

To enable Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager 1.8:

#In the LDAP server, create a user group. For example,create a group named pc_group.
#In the group that you created in the LDAP server, create a user. For example, create a user named pc_user. You must ensure that a valid mailbox is configured for the user created in the group in the LDAP server.
#In CTS-Manager, in the '''Access Management '''page, assign the '''Live Desk''' role and the '''Reporting API User''' role for the group you created in the LDAP server, for example, pc_group created in ''Step 1''.
#Discover the CTS-Manager in Prime Collaboration with the user that you created in the LDAP server. For example, use pc_user.

For more information about the Reporting API, see ''Cisco Telepresense Manager Reporting API Developer's Guide for Release 1.8.''

For more information about user and group configuration in LDAP server, see ''Cisco Telepresense Manager 1.8 Administration and Installation Guide''.
<pre>Note:
After creating the user account in CTS-Manager for the Prime Collaboration application, we recommend
that you log in with this account in CTS-Manager at least once before you enter the
credentials in the Prime Collaboration server.</pre>
== Cisco TMS Third Party Booking API User ==

For the Prime Collaboration server to retrieve scheduled meetings from Cisco TMS server, you must have one Application Integration License for each server that uses the API.
<pre>Note:
*We recommend that you review the Cisco TMS Third Party Booking API document available
at [http://www.tandberg.com/support/tms_documentation.jsp] for an understanding of the
Booking API.

*For Cisco TMS 13.2 and later, any HTTP user can be used to retrieve scheduled meetings
from Cisco TMS server. In addition, you do not need to install a Booking API License to
use the API.</pre>
To enable Prime Collaboration server to retrieve scheduled meetings from Cisco TMS:

#From the Cisco TMS server, go to [http://localhost/tms/external/booking/remotesetup/remotesetupservice.asmx http://localhost/tms/external/booking/remotesetup/remotesetupservice.asmx]. The RemoteSetupService page appears. You may replace localhost in the above URL with the IP address of the Cisco TMS server.
#Choose '''GenerateConferenceAPIUser'''.
#Enter the values for the following parameters:
#*userNameBase - The base portion of the user name. For example, pc_user.
#*encPassword - A base64 encoded password that is to be used for the newly created user. To encode the password to base64, we recommend that you use the web utility available at the following URL: http://www.motobit.com/util/base64-decoder-encoder.asp.
#*emailAddress - The email address of the user. Do not enter values in this field.
#*sendNotifications - To allow the user to receive scheduling notifications. You must enter False in this field since Prime Collaboration will be polling from Cisco TMS.
#Click '''Invoke'''.
#In the Cisco TMS application, verify the user name configured in Step 3is listed in the Users page.
#In the Cisco TMS application, create a user group. For example, create a group named pc_group.
#Add the user created in Step 3 to the group created in Step 6. For example, add pc_user to pc_group.
#In the '''Groups '''page, for the group created in Step 6, check the Read permission check box for List Conferences-All (under the Booking pane). For example, pc_group must have the read permission to List Conferences-All.
#Discover the Cisco TMS in Cisco Prime Collaboration with the user that you created in Step 3. For example, use pc_user.

For more information about the Cisco TMS, see the documents available at [[Www.tandberg.com/support/tms documentation.jsp|TANDBERG]] site.

For more information on creating groups and setting permission to the group, see ''Ciso Telepresence Management Suite Administrator Guide''.

= Configuring MCUs =

A Cisco TelePresence MCU MSE 8510 (MCU MSE 8510) cluster consists of a Cisco TelePresence MCU MSE 8050 Supervisor Blade (MCU MSE 8550) and a MCU MSE 8510 blade. After the basic information is configured, HTTP access is enabled by default.

'''Enable HTTP'''

The supervisor web interface can be accessed by pointing the browser to http://<MCU_Address>, where <MCU_Address> is the IP address or hostname of your server. The default password for the '''admin''' user is a blank space (no password). If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the MCU MSE Supervisor.

To log in to the web interface of the MCU MSE 8510 blade:

#Log in to the supervisor web interface.
#Go to '''Hardware''' > '''Blades''' and click the IP address of the MCU MSE 8510 blade.
#Click '''Log in''', and enter the username '''admin''' with no password.

'''Enable SNMP'''

You can edit SNMP settings by logging in to the MCU Codian Web Interface:

#Navigate to '''Network''' > '''SNMP'''.
#Edit the SNMP Read Only and Read Write strings as required.
#Click '''Update SNMP Settings''' to apply the changes.

= Configuring Cisco TelePresence Multipoint Switch =

'''Enable HTTP'''

A separate HTTP user account must be created with the Meeting Scheduler and Diagnostic Technician roles assigned to it for the Prime Collaboration application. This user can be configured in the Multipoint Switch web user interface when logged in as admin. After the dedicated HTTP user has been created, you must login to CTMS web UI using this user credential and then change the password (the same password can be entered).

An '''admin''' user is not required by Cisco Prime Collaboration to manage the Multipoint Switch.

You can access the Multipoint Switch through a web browser (preferably using Internet Explorer) by pointing the browser to: https://<ctms_serveraddress>, where <ctms_serveraddress> is the IP address or hostname of the Multipoint Switch.

'''Enable SNMP'''

SNMP is enabled by default and it monitors the Multipoint Switch system status (navigate to Troubleshoot > System Resources for system status details). You can designate a particular server where SNMP trap messages are gathered and stored. You configure all SNMP settings through the Multipoint Switch CLI commands.

The following SNMP settings are enabled by default:

*SNMPv3 username set to '''mrtg''': This name is for internal use of the system and should not be deleted.
*SNMPv2c username set to '''public''': This name is for internal use of the system and should not be deleted.
*No trap receiver is configured. Use Multipoint Switch CLI commands to configure SNMP trap receiver information.

Use SSH in the Multipoint Switch to configure SNMP using the CLI. The CLI commands to configure SNMP Read Only and Read/Write are as follows:

*set snmp user add 2c snmpro r
*set snmp user add 2c snmprw rw
<pre>Note:
Replace snmpro and snmprw with your SNMP Read and Read/Write community strings.
After creating the user account in CTMS for the Prime Collaboration application, we recommend
that you log in with this account in CTMS at least once before you enter the
credentials in the Prime Collaboration server.
</pre>

= Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices =

If you have enabled [http://www.cisco.com/web/solutions/medianet/knowledgebase/index.html#~configure Cisco Mediatrace] on your network nodes, Prime Collaboration provides Medianet Path View as part of the troubleshooting data. If you have enabled Cisco IOS IP Service Level Agreements (SLAs) on your network nodes, you can measure the network performance and health using the Proactive Troubleshooting feature.

For Cisco Mediatrace:

*Enable the initiator and/or responder roles on relevant routers and switches using the following commands: '''For Mediatrace Initiator''': 

 
<pre>mediatrace initiator source-ip ''IP Address''</pre>
 '''For Mediatrace Responder''': 

 
<pre>mediatrace responder
</pre>
 

*Configure a Telnet local login user with privilege 15 on the initiators.
*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators. See ''Web Services Management Agent (WSMA) Configuration Guide'' for details on the configuration commands. 

'''Local Auth Example''': 
<pre>username <username> priv 15 secret <username_enable_password>
ip http authentication local

</pre>
'''For WSMA (HTTP) Configuration''':
<pre>ip http server
ip http timeout-policy idle 60 life 86400 requests 10000
wsma agent exec profile wsma_listener_http
wsma agent config profile wsma_listener_http
!
wsma profile listener wsma_listener_http
transport http</pre>
'''For WSMA (HTTPS) Configuration''':

 
<pre>ip http secure-server
wsma agent exec profile wsma_listener_https
wsma agent config profile wsma_listener_https
!
wsma profile listener wsma_listener_https
transport https

</pre>
'''For WSMA SSH Configuration''': 
<pre>crypto key generate rsa
ip ssh timeout 120
ip ssh version 2
!
wsma agent exec profile wsma_listener_ssh
wsma agent config profile wsma_listener_ssh
!
wsma profile listener wsma_listener_ssh
transport ssh
</pre>
For Cisco IOS IP Service Level agreement (SLA):

*Enable the responder role using the command: 
<pre>ip sla responder

</pre>
*The initiator role is not required. 
*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.

You can verify whether these roles are enabled on the device by using Prime Collaboration Inventory (Operate > Device Work Center > Current Inventory table).

For Performance Monitoring (PM) Configuration:

Configure the Performance Monitor policy on the relevant interfaces. Prime Collaboration collects PM flow statistics through MIBs. If this is configured, Prime Collaboration does not require the CLI access to routers.

== Supported Software Versions for the Cisco Medianet Feature ==

 

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
| '''Platform''' 
| '''Minimum IOS Release''' 
| '''Minimum Package''' 
| '''Feature Support''' 
|-
| Catalyst 3560 
| 15.0(1)SE2 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 3750 
| 15.0(1)SE2 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 4500E Supervisor 7-E/7L-E 
| XE 3.3.0SG 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 4500E Supervisor 6-E/6L-E 
| 15.1(1)SG 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 6500 Supervisor 2T 
| 15.0(1)SY 
| IP Services 
| Mediatrace, Performance Monitor 
|-
| ISR 2900 and 3900 
| 15.1(3)T 
| UC and Data 
| Mediatrace, Performance Monitor 
|-
| 
| 15.2(2)T 
| UC and DSP 
| IPSLA-VO Sender 
|-
| 
| 15.2(2)T 
| IP Base 
| IPSLA-VO Responder 
|-
| ISR 1900 
| 15.1(3)T 
| UC and Data 
| Mediatrace, Performance Monitor 
|-
| 
| 15.2(2)T 
| IP Base 
| IPSLA-VO Responder 
|-
| ISR 880 and 890 
| 15.1(3)T 
| Universal 
| Mediatrace, Performance Monitor 
|-
| ASR 1000 
| XE 3.5 
| IP Base 
| Performance Monitor 
|}

 

----

 

 

 

 

 

 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Setting up Devices for Prime Collaboration Assurance

2013-03-15T06:48:45Z

Chetrao: /* Required Protocols for the Devices (Includes Supported Software Versions) */

This section describes how to configure devices on the network before you manage them in Cisco Prime Collaboration Assurance.

= Required Protocols for the Devices (Includes Supported Software Versions) =

You must configure the endpoints, application managers, call processors, multipoint switches, and network devices with the following protocols:

*HTTP - Access the device through HTTP to poll system status and meeting information.
*SNMP - Read Community String and SNMP Authentication Protocol (SNMP V2 or SNMP V3) - Discover and manage the device.
*CLI - Access the device through CLI to discover media path for troubleshooting.
*JTAPI - Retrieve the session status information frosm the Cisco Unified CM.
*CDP - Discover neighboring devices.

 

{| border="1" cellspacing="1" cellpadding="1" width="1000"
|-
| '''Device''' 
| '''Supported Software''' 
| '''SNMP''' 
| '''HTTP''' 
| '''CLI''' 
| '''JTAPI''' 
| '''MSI''' 
| '''CDP''' 
| '''Notes''' 
|-
| Analog Gateway 
| - 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Contact Center Enterprise 
| 7.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Contact Center Express 
| 4.6 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Multipoint Switch 
| 1.7 – 1.9 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user account must have both the Meeting Manager and Diagnostic Technician roles. 
|-
| Cisco TelePresence System 
| 1.7 – 1.9 
| Yes 
| - 
| Yes 
| -
| Yes 
| - 
|
*CLI access is required if you want to use the Troubelshooting feature in Prime Collaboration. HTTP access is not required.
*The HTTP credentials (helpdesk role) are same as the SSH credentials, which are required by Prime Collaboration to troubleshoot.

|-
| Cisco TelePresence Manager (CTS-Manager) 
| 1.7 – 1.9 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*Requires the Reporting API license and the Reporting API role for the Prime Collaboration user.
*The HTTP user needs to be an exchange mailbox user and its User Group must have Reporting API and Live Desk roles in CTS-Manager. 
*If you have installed a licensed version of Prime Collaboration, it is mandatory to configure the CTS-Manager Reporting API. If this feature is not configured on the CTS-Manager 1.7, 1.8, or 1.9, Prime Collaboration will not manage the CTS-Manager. 

|-
| Cisco Unified CM 
| 7.1 – 9.0 
| Yes 
| Yes 
| - 
| Yes 
| - 
| - 
|
*The same credentials must be created for all devices in the cluster whenever clustering is used.
*The JTAPI user needs to have these roles Standard AXL API Access, CCM Admin Users, SERVICEABILITY Administration, CTI Enabled, and CTI Allow Call Monitoring.
*The session monitoring feature is supported only on Cisco Unified CM 8.5, 8.6 and 9.0. 

|-
| Cisco Unified Communications Manager Business Edition 
| 7.1 – 9.0 
| Yes 
| Yes 
| - 
| Yes 
| - 
| - 
| 
|-
| Customer Voice Portal 
| 4.0 - 8.5 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
|
*Cisco Codec EX series
*Cisco TelePresence System Integrator C Series
*Cisco TelePresence MX Series
*Cisco TelePresence System Profile Series
*Cisco TelePresence SX20 Quick Set
*Cisco TX 9000 series 

|
*EX series: TC 4.2 - 6.0; TE 6.0 
*C, MX, and SX series: TC 4.2 - 6.0 
*TX series: TX 6.0 

| Yes 
| Yes 
| Yes 
| - 
| Yes 
| - 
|
*The HTTP user requires Admin privilege. 
*For TC 6.0 and TE 6.0, use the same HTTP credentials for MSI. 
*For TX 6.0, use the default credentials msiuser and cisco for MSI. 

|-
| Cisco IP Video Phone E20 
| TE 4.0 - 6.0 
| Yes 
| Yes 
| Yes 
| - 
| Yes 
| - 
|
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration.
*Use the same HTTP credentials for MSI. 

|-
| Emergency Responder 
| 1.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Expert Advisor 
| 7.2 - 7.6 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Finesse 
| 8.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco MCU 
| 4.1 – 4.3 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*The HTTP user requires Admin privilege. 
*This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, and MSE-8710. 

|-
| Cisco TelePresence MSE Supervisor 
| 2.1 – 2.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user requires Admin privilege. 
|-
| Mediasense 
| 8.0 - 9.0 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Meeting Place 
| 7.0 - 8.5 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Meeting Place Express 
| 2.0 - 2.1 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Personal Assistant 
| 1.3 -1.4 
| - 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence System MXP series 
| 9.1 
| Yes 
| Yes 
| Yes 
| 
| 
| 
| 
|-
| Polycom VSX series Polycom HDX series 
| 2.5 - 3.0 (for HDX series) 9.0 (for VSX series) 
| Yes 
| - 
| - 
| - 
| - 
| - 
| End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 
|-
| Cisco Presence 
| 8.0 - 9.0 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Network devices (routers and switches) 
| 
| Yes 
| - 
| Yes 
| - 
| - 
| Yes 
|
*CDP needs to be enabled for the video Troubleshooting workflow. The Telnet or SSH access is required for Cisco Medianet features, which is part if the video Troubleshooting workflow. 
*See the table ''Supported Software Versions for the Cisco Medianet'' Feature below to view the troubleshooting medianet-related data. 

|-
| Cisco TelePresence Management Suite (Cisco TMS) 
| 13.0 – 13.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
|
*Requires Booking API license (TMS software version 13.1 or below). 
*The HTTP user for Prime Collaboration needs to be generated through the Booking API on the Cisco TMS windows server. 
*Prime Collaboration supports only the default e-mail template for the Booking Confirm e-mail in Cisco TMS. The session import feature will not work, if the default e-mail template is not used. 

|-
| Cisco Telepresence Server 
| 2.1 – 2.2 
| - 
| Yes 
| - 
| - 
| - 
| - 
|
*The HTTP user account should have the API Access privilege.
*This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, MSE-8710. 

|-
| Cisco Telepresence Conductor 
| 1.1 - 1.2 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity
| 7.0 - 8.6
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity Connection
| 7.0 - 9.0
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Unity Express
| 7.0 - 9.0
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Video Communication Server (Control and Expressway) 
| 6.0 – 7.1 
| Yes 
| Yes 
| - 
| - 
| - 
| - 
| The HTTP user requires Admin privilege. 
|-
| Wireless 
| - 
| Yes 
| - 
| Yes 
| - 
| - 
| - 
| 
|-
| Third party devices 
| - 
| Yes 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco Jabber Video for Telepresence (Movi) 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco Jabber endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required).
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Cisco Cius 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco Cius endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required). You must enable web access in Cisco Unified CM for these. 
*Credentials are not required for HTTP access. 
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Cisco IP phones (89xx, 99xx) 
| all software versions. 
| - 
| - 
| - 
| - 
| - 
| - 
|
*The Cisco IP Phones endpoints are discovered through Cisco Unified CM. You must enable web access in Cisco Unified CM for these. 
*These video phones require Cisco Unified CM application user to have the additional role ''Standard CTI Allow Control of Phones supporting Connected Xfer and conf''. 
*Credentials are not required for HTTP access. 
*End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration. 

|-
| Border Element, Gatekeeper, H323 Gateway, SIP Gateway MGCP Gateway, SRST Device, Voice Gateway 
| IOS 12.x or later 
| - 
| - 
| - 
| - 
| - 
| - 
| 
|-
| Cisco TelePresence Exchange
| 1.2
| Yes
| Yes
| -
| -
| -
| -
|
|}

 

= Configuring Call Controllers and Processors =

== Cisco Unified Communications Manager ==

All CTS endpoints must be added as controlled devices in Cisco Unified CM to facilitate call detection. You must configure a HTTP and JTAPI user on the call processor.

'''Note''': The procedures described below are applicable for Cisco Unified CM 8.5. If you are using any other supported versions, see the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html ''Cisco Unified CM guides''] to understand how to create groups, users and assign roles to them. 

'''Enable HTTP'''

You do not have to create a new user if you want to allow Cisco Prime Collaboration to use admin credentials to log in. Alternatively, if you want to allow Cisco Prime Collaboration Manager to use the right credentials to log in to Cisco Unified Communications Manager, you must create a new HTTP user group and a corresponding user that Cisco Prime Collaboration can use to communicate.

To create a user:

#Create a user group with sufficient privileges. Log in to the Cisco Unified Communications Manager Administration web interface using the administrator role.
#Navigate to '''User Management''' > '''User Groups''' and create a new group with a suitable name, PC_HTTP_Users in this case.
#Click '''Role'''.
#Click '''Assign Role to Group''' and select the following roles:
#*Standard AXL API Access
#*Standard CCM Admin Users
#*Standard SERVICEABILITY Administration
#Click '''Save'''.
#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration to monitor all devices.
#In the '''Permission Information''' section, click '''Add to User Group''' and select the group that was created in Step 1. (PC_HTTP_Users, for instance).
#Click '''Save'''. The page is refreshed and the right privileges are displayed.

'''Enable SNMP'''

SNMP is not enabled in Cisco Unified Communications Manager by default.

To enable SNMP:

#Log in to the '''Cisco Unified Serviceability''' view in the Cisco Unified Communications Manager web GUI.
#From the main menu in the Cisco Unified Serviceability view, navigate to SNMP > v1/v2c > community string.
#Select a Server and click '''Find'''. If the community string is already defined, the Community String Name is displayed in the Search Results.
#Click '''Add new '''to add a new string if no results are displayed.
#Specify the required SNMP information and save the configuration.

'''Enable JTAPI'''

JTAPI (Java Telephony API) is used to retrieve the session status information from the device. You must create a JTAPI user in the call processor with the required permission to receive JTAPI events on endpoints. Prime Collaboration manages multiple call processor clusters. You must ensure that the cluster IDs are unique. Create a new JTAPI user to help Cisco Prime Collaboration get the required information.

To create a new JTAPI user:

#Log in to the Cisco Unified Communications Manager administration web interface using administrator role.
#Navigate to User Management > '''User Groups''' and create a new group with a suitable name, '''PC_HTTP_Users''' in this case.
#Move all endpoint devices (for example, Cisco TelePresence codecs) to the Controlled Devices table.
#Click '''Roles'''.
#Click '''Assign Role to Group''' and select the following roles:
#*Standard CTI Allow Call Monitoring
#*Standard CTI Enabled
#*Standard CTI Allow Control of Phones supporting Connected Xfer and conf
#Click '''Save'''.
#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration to monitor all devices. '''Note''': The password must not contain a semicolon (;) or equals (=).
#In the '''Permission Information''' section, click '''Add to User Group''' and select the group that was created in step 1. (PC_HTTP_Users, for instance).
#Click '''Save'''. The page is refreshed and the right privileges are displayed.
<pre>Note:
*Ensure the following services are activated and started:
**Cisco CTIManager
**Cisco AXL Web Service
See the Cisco Unified Communications Manager guide for details about how
to configure the application user.

You can access the log files to verify whether the endpoints are assisned with the CTI-controlled roles in the Unified CM
and for the JTAPI-related issues using https://<primecollaboration-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log
</pre>
== Cisco TelePresence Video Communication Server ==

Cisco VCS serves as a call-control appliance for the Cisco TelePresence C Series, E Series, and other similar video endpoints.

'''Enable HTTP'''

You can access Cisco VCS through a web browser: http://<vcs_serveraddress>, where <vcs_serveraddress> is the IP address or hostname of your VCS appliance. The default password for administrator user '''admin''' is TANDBERG. If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the VCS. Ensure the password field is not blank as it is not recommended.

'''Enable SNMP'''

You can easily enable SNMP from the Cisco VCS web GUI: Navigate to '''System''' > '''SNMP''' and enter the SNMP information.

= Configuring Endpoints =

== Cisco TelePresence System Video Endpoints ==

'''Enable HTTP'''

You can access Cisco TelePresence system video endpoints through a web browser (preferably using Internet Explorer, if possible) by pointing the browser to:https://<serveraddress> where <serveraddress> is the IP address or hostname of the Cisco TelePresence system video endpoint.

'''Enable SNMP'''

SNMP for Cisco TelePresence system devices is configured using Cisco Unified Communications Manager phone configuration. To change the SNMP community string:

#Navigate to Cisco Unified Communications Manager Administration.
#Navigate to '''Device''' > '''Phone''' and search for Cisco TelePresence system endpoints.
#Click the '''Device Name''' link to go to the phone configuration page.
#Edit the SNMP Configuration Parameters.
#Click '''Save''' '''and''' '''Apply Config'''.

'''Enable CLI Access'''

SSH access to the Cisco TelePresence system devices is also controlled through Cisco Unified Communications Manager Phone Configuration.
<pre>Note:
If the value of SSH admin Life and SSH helpdesk Life field is zero, the password never
expires (recommended for lab testing scenarios).
However, if the value is not zero, the admin must ensure that passwords are changed
before the specified interval, for anyone or any application to be able to perform SSH
in the device including Cisco Prime Collaboration. </pre>
== Cisco TelePresence C and EX Series Video Endpoints ==

'''Enable HTTP'''

By default, HTTP is enabled for Cisco TelePresence Endpoints. Point the web browser to http://<ip_address>, where <ip_address> is the IP address or hostname of the video endpoint. The default password for the administrator user '''admin''' is " ", blank space.

'''Enable SNMP'''

To enable SNMP access for Cisco Prime Collaboration from the web interface:

Navigate to '''Configuration''' > '''Adv Configuration''' > '''Network Services''' > '''SNMP''' and click the value to edit.

'''Enable CLI Access'''

SSH must be enabled by default on TC 4.0 releases. Provide '''admin''' user access to Cisco Prime Collaboration ensure that the admin password is set and is not the default value, which is blank. Admin user access is necessary if you want to troubleshoot video sessions from Cisco TelePresence devices using Cisco Prime Collaboration. Some of the commands required to run the traceroutes are available only when you log in as root.

We recommend that you enter the real interface IP address of the gateway that runs the Hot Standby Router Protocol (HSRP), instead of the virtual IP address, while configuring the CTS. This enables Prime Collaborationto accurately discover the troubleshooting path.

Endpoint monitoring is based on the SNMP polling. You can configure traps and syslogs on the endpoints, if required.

To monitor traps and syslogs:

*Configure trap and syslog receivers for endpoints in call processors.
*Enter the Prime Collaboration IP address to configure the trap receiver: <PrimeCollaboration_ip_addr>
*Enter the Prime Collaboration IP address and port number 20514 to configure syslog receiver.: <PrimeCollaboration_ip_addr>:20514.
*Enable endpoints to send traps and syslogs.

To enable traps:

*In CISCO-TELEPRESENCE-MIB, set ctpPeripheralErrorNotifyEnable to true (1)
*In CISCO-TELEPRESENCE-CALL-MIB, set ctpcStatNotifyEnable to true (1)
*In CISCO-TELEPRESENCE-CALL-MIB, set threshold values for call stats ctpcStatMonitoredEntry

To enable syslogs: In CISCO-SYSLOG-MIB, set clogNotificationsEnabled to true (1).

= Configuring Call Management Applications =

== Cisco TelePresence Management Suite ==

HTTP and SNMP access are required to successfully monitor Cisco TMS.

'''Enable HTTP'''

Cisco TMS is accessed through a web browser (http://<serveraddress>/TMS), where <serveraddress> is the IP address or hostname of your server. The default password for the administrator user '''admin''' is '''TANDBERG'''.

If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully monitor Cisco TMS.

'''Enable SNMP'''

By default, '''public''' and '''Public''' are enabled as SNMP Read Only (RO) community strings for Cisco TMS. This string is used by Cisco TMS to poll other devices.

If you need to add or change these strings:

Go to the web GUI and navigate to '''Administrative''' '''Tools''' > '''Configuration''' > '''Network Settings''' and change the SNMP settings.

In addition to the Web GUI, SNMP service on the Cisco TMS server must be enabled.

To enable SNMP:

#Go to '''Start '''on the server console.
#Click '''Run '''and specify services.msc. A Service window will pop open on the server console.
#Right-click '''SNMP Service '''and select '''Properties'''.
#Click '''Security '''and select '''Add new SNMP''' string. Do not modify the default selection: Accept SNMP packets from any host unless you want only specific hosts polling SNMP from Cisco TMS.
#Optionally, click '''Traps '''to add the IP address of Cisco Prime Collaboration and a community string. This address is used in SNMP traps.
#Optionally, click '''Agent '''to specify SNMP contact and location for Cisco TMS. The Cisco Prime Collaboration uses this information to display the location of Cisco TMS in the inventory.
#Restart the '''SNMP Service '''after the necessary modifications.

== Reporting API for CTS-Manager ==

For Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager, you must have a valid Metrics Dashboard and Reporting API license in CTS-Manager. This user account should be configured in Active Directory with a mailbox and in a user group with general security. The Active Directory user group should be assigned the '''Reporting API '''role and the '''Live Desk '''role in the CTS-Manager Access Management page.
<pre>Note:
We recommend that you review the Getting Started With TelePresence Reporting API
document available at [http://developer.cisco.com/web/tra/start] for an understanding
of the Reporting API.</pre>
'''Note''': The procedures described below are applicable for CTS-Manager 1.8. If you are using any other supported versions, see the CTS-Manager Reporting API related documents. 

To enable Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager 1.8:

#In the LDAP server, create a user group. For example,create a group named pc_group.
#In the group that you created in the LDAP server, create a user. For example, create a user named pc_user. You must ensure that a valid mailbox is configured for the user created in the group in the LDAP server.
#In CTS-Manager, in the '''Access Management '''page, assign the '''Live Desk''' role and the '''Reporting API User''' role for the group you created in the LDAP server, for example, pc_group created in ''Step 1''.
#Discover the CTS-Manager in Prime Collaboration with the user that you created in the LDAP server. For example, use pc_user.

For more information about the Reporting API, see ''Cisco Telepresense Manager Reporting API Developer's Guide for Release 1.8.''

For more information about user and group configuration in LDAP server, see ''Cisco Telepresense Manager 1.8 Administration and Installation Guide''.
<pre>Note:
After creating the user account in CTS-Manager for the Prime Collaboration application, we recommend
that you log in with this account in CTS-Manager at least once before you enter the
credentials in the Prime Collaboration server.</pre>
== Cisco TMS Third Party Booking API User ==

For the Prime Collaboration server to retrieve scheduled meetings from Cisco TMS server, you must have one Application Integration License for each server that uses the API.
<pre>Note:
*We recommend that you review the Cisco TMS Third Party Booking API document available
at [http://www.tandberg.com/support/tms_documentation.jsp] for an understanding of the
Booking API.

*For Cisco TMS 13.2 and later, any HTTP user can be used to retrieve scheduled meetings
from Cisco TMS server. In addition, you do not need to install a Booking API License to
use the API.</pre>
To enable Prime Collaboration server to retrieve scheduled meetings from Cisco TMS:

#From the Cisco TMS server, go to [http://localhost/tms/external/booking/remotesetup/remotesetupservice.asmx http://localhost/tms/external/booking/remotesetup/remotesetupservice.asmx]. The RemoteSetupService page appears. You may replace localhost in the above URL with the IP address of the Cisco TMS server.
#Choose '''GenerateConferenceAPIUser'''.
#Enter the values for the following parameters:
#*userNameBase - The base portion of the user name. For example, pc_user.
#*encPassword - A base64 encoded password that is to be used for the newly created user. To encode the password to base64, we recommend that you use the web utility available at the following URL: http://www.motobit.com/util/base64-decoder-encoder.asp.
#*emailAddress - The email address of the user. Do not enter values in this field.
#*sendNotifications - To allow the user to receive scheduling notifications. You must enter False in this field since Prime Collaboration will be polling from Cisco TMS.
#Click '''Invoke'''.
#In the Cisco TMS application, verify the user name configured in Step 3is listed in the Users page.
#In the Cisco TMS application, create a user group. For example, create a group named pc_group.
#Add the user created in Step 3 to the group created in Step 6. For example, add pc_user to pc_group.
#In the '''Groups '''page, for the group created in Step 6, check the Read permission check box for List Conferences-All (under the Booking pane). For example, pc_group must have the read permission to List Conferences-All.
#Discover the Cisco TMS in Cisco Prime Collaboration with the user that you created in Step 3. For example, use pc_user.

For more information about the Cisco TMS, see the documents available at [[Www.tandberg.com/support/tms documentation.jsp|TANDBERG]] site.

For more information on creating groups and setting permission to the group, see ''Ciso Telepresence Management Suite Administrator Guide''.

= Configuring MCUs =

A Cisco TelePresence MCU MSE 8510 (MCU MSE 8510) cluster consists of a Cisco TelePresence MCU MSE 8050 Supervisor Blade (MCU MSE 8550) and a MCU MSE 8510 blade. After the basic information is configured, HTTP access is enabled by default.

'''Enable HTTP'''

The supervisor web interface can be accessed by pointing the browser to http://<MCU_Address>, where <MCU_Address> is the IP address or hostname of your server. The default password for the '''admin''' user is a blank space (no password). If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the MCU MSE Supervisor.

To log in to the web interface of the MCU MSE 8510 blade:

#Log in to the supervisor web interface.
#Go to '''Hardware''' > '''Blades''' and click the IP address of the MCU MSE 8510 blade.
#Click '''Log in''', and enter the username '''admin''' with no password.

'''Enable SNMP'''

You can edit SNMP settings by logging in to the MCU Codian Web Interface:

#Navigate to '''Network''' > '''SNMP'''.
#Edit the SNMP Read Only and Read Write strings as required.
#Click '''Update SNMP Settings''' to apply the changes.

= Configuring Cisco TelePresence Multipoint Switch =

'''Enable HTTP'''

A separate HTTP user account must be created with the Meeting Scheduler and Diagnostic Technician roles assigned to it for the Prime Collaboration application. This user can be configured in the Multipoint Switch web user interface when logged in as admin. After the dedicated HTTP user has been created, you must login to CTMS web UI using this user credential and then change the password (the same password can be entered).

An '''admin''' user is not required by Cisco Prime Collaboration to manage the Multipoint Switch.

You can access the Multipoint Switch through a web browser (preferably using Internet Explorer) by pointing the browser to: https://<ctms_serveraddress>, where <ctms_serveraddress> is the IP address or hostname of the Multipoint Switch.

'''Enable SNMP'''

SNMP is enabled by default and it monitors the Multipoint Switch system status (navigate to Troubleshoot > System Resources for system status details). You can designate a particular server where SNMP trap messages are gathered and stored. You configure all SNMP settings through the Multipoint Switch CLI commands.

The following SNMP settings are enabled by default:

*SNMPv3 username set to '''mrtg''': This name is for internal use of the system and should not be deleted.
*SNMPv2c username set to '''public''': This name is for internal use of the system and should not be deleted.
*No trap receiver is configured. Use Multipoint Switch CLI commands to configure SNMP trap receiver information.

Use SSH in the Multipoint Switch to configure SNMP using the CLI. The CLI commands to configure SNMP Read Only and Read/Write are as follows:

*set snmp user add 2c snmpro r
*set snmp user add 2c snmprw rw
<pre>Note:
Replace snmpro and snmprw with your SNMP Read and Read/Write community strings.
After creating the user account in CTMS for the Prime Collaboration application, we recommend
that you log in with this account in CTMS at least once before you enter the
credentials in the Prime Collaboration server.
</pre>

= Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices =

If you have enabled [http://www.cisco.com/web/solutions/medianet/knowledgebase/index.html#~configure Cisco Mediatrace] on your network nodes, Prime Collaboration provides Medianet Path View as part of the troubleshooting data. If you have enabled Cisco IOS IP Service Level Agreements (SLAs) on your network nodes, you can measure the network performance and health using the Proactive Troubleshooting feature.

For Cisco Mediatrace:

*Enable the initiator and/or responder roles on relevant routers and switches using the following commands: '''For Mediatrace Initiator''': 

 
<pre>mediatrace initiator source-ip ''IP Address''</pre>
 '''For Mediatrace Responder''': 

 
<pre>mediatrace responder
</pre>
 

*Configure a Telnet local login user with privilege 15 on the initiators.
*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators. See ''Web Services Management Agent (WSMA) Configuration Guide'' for details on the configuration commands. 

'''Local Auth Example''': 
<pre>username <username> priv 15 secret <username_enable_password>
ip http authentication local

</pre>
'''For WSMA (HTTP) Configuration''':
<pre>ip http server
ip http timeout-policy idle 60 life 86400 requests 10000
wsma agent exec profile wsma_listener_http
wsma agent config profile wsma_listener_http
!
wsma profile listener wsma_listener_http
transport http</pre>
'''For WSMA (HTTPS) Configuration''':

 
<pre>ip http secure-server
wsma agent exec profile wsma_listener_https
wsma agent config profile wsma_listener_https
!
wsma profile listener wsma_listener_https
transport https

</pre>
'''For WSMA SSH Configuration''': 
<pre>crypto key generate rsa
ip ssh timeout 120
ip ssh version 2
!
wsma agent exec profile wsma_listener_ssh
wsma agent config profile wsma_listener_ssh
!
wsma profile listener wsma_listener_ssh
transport ssh
</pre>
For Cisco IOS IP Service Level agreement (SLA):

*Enable the responder role using the command: 
<pre>ip sla responder

</pre>
*The initiator role is not required. 
*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.

You can verify whether these roles are enabled on the device by using Prime Collaboration Inventory (Operate > Device Work Center > Current Inventory table).

For Performance Monitoring (PM) Configuration:

Configure the Performance Monitor policy on the relevant interfaces. Prime Collaboration collects PM flow statistics through MIBs. If this is configured, Prime Collaboration does not require the CLI access to routers.

== Supported Software Versions for the Cisco Medianet Feature ==

 

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
| '''Platform''' 
| '''Minimum IOS Release''' 
| '''Minimum Package''' 
| '''Feature Support''' 
|-
| Catalyst 3560 
| 15.0(1)SE2 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 3750 
| 15.0(1)SE2 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 4500E Supervisor 7-E/7L-E 
| XE 3.3.0SG 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 4500E Supervisor 6-E/6L-E 
| 15.1(1)SG 
| IP Base 
| Mediatrace, Performance Monitor, IPSLA-VO 
|-
| Catalyst 6500 Supervisor 2T 
| 15.0(1)SY 
| IP Services 
| Mediatrace, Performance Monitor 
|-
| ISR 2900 and 3900 
| 15.1(3)T 
| UC and Data 
| Mediatrace, Performance Monitor 
|-
| 
| 15.2(2)T 
| UC and DSP 
| IPSLA-VO Sender 
|-
| 
| 15.2(2)T 
| IP Base 
| IPSLA-VO Responder 
|-
| ISR 1900 
| 15.1(3)T 
| UC and Data 
| Mediatrace, Performance Monitor 
|-
| 
| 15.2(2)T 
| IP Base 
| IPSLA-VO Responder 
|-
| ISR 880 and 890 
| 15.1(3)T 
| Universal 
| Mediatrace, Performance Monitor 
|-
| ASR 1000 
| XE 3.5 
| IP Base 
| Performance Monitor 
|}

 

----

 

 

 

 

 

 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-08T10:09:29Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You must login as root user and upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see Cisco Prime Collaboration Quick Start Guide:
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html</pre>
==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts as a root user:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance)

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers start
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

==== How to configure a second NIC for Prime Collaboration? ====

A second NIC can be added to the Prime Collaboration as follows:

*Use vSphere Client ('''Edit virtual machine settings '''option) to add a second virtual Network Adapter to the virtual machine
*Login to the Prime Collaboration admin CLI to configure the IP address for the second interface
*Configure the ip route gateways for the two interfaces (with the same CLI access)

Login as admin user and execute the following CLI commands:
<pre>admin# configure
admin (config)# interface GigabitEthernet 1 (Note that the first interface is GigabitEthernet 0)
admin (config-GigabitEthernet)# ip address <ip address> <net mask>
admin (config-GigabitEthernet)# exit</pre>
To configure the ip routes to the two different gateways:
<pre>admin (config)# ip route <network addr> <net mask> <route-specific gateway1>
admin (config)# ip route <network addr> <net mask> <route-specific gateway2>
……</pre>
Change the default route (0.0.0.0 0.0.0.0) to the appropriate gateway if needed.

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-08T10:07:15Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You must login as root user and upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see Cisco Prime Collaboration Quick Start Guide:
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html</pre>
==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts as a root user:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance)

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers start
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

'''How to configure a second NIC for Prime Collaboration?'''

A second NIC can be added to the Prime Collaboration as follows:

*Use vSphere Client ('''Edit virtual machine settings '''option) to add a second virtual Network Adapter to the virtual machine
*Login to the Prime Collaboration admin CLI to configure the IP address for the second interface
*Configure the ip route gateways for the two interfaces (with the same CLI access)

Login as admin user and execute the following CLI commands:
<pre>admin# configure
admin (config)# interface GigabitEthernet 1 (Note that the first interface is GigabitEthernet 0)
admin (config-GigabitEthernet)# ip address <ip address> <net mask>
admin (config-GigabitEthernet)# exit</pre>
To configure the ip routes to the two different gateways:
<pre>admin (config)# ip route <network addr> <net mask> <route-specific gateway1>
admin (config)# ip route <network addr> <net mask> <route-specific gateway2>
……</pre>
Change the default route (0.0.0.0 0.0.0.0) to the appropriate gateway if needed.

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-04T09:44:12Z

Chetrao: /* How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? */

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You must login as root user and upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see Cisco Prime Collaboration Quick Start Guide:
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts as a root user:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers start
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-04T09:43:01Z

Chetrao: /* How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? */

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You must login as root user and upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see Cisco Prime Collaboration Quick Start Guide:
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts as a root user:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers start
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-04T09:42:22Z

Chetrao: /* How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? */

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You must login as root user and upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see Cisco Prime Collaboration Quick Start Guide:
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts as a root user:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-04T09:41:57Z

Chetrao: /* How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? */

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You must login as root user and upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see Cisco Prime Collaboration Quick Start Guide:
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts as a root user:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-04T09:40:20Z

Chetrao: /* How to upgrade Cisco Prime Collaboration Assurance deployment model? */

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You must login as root user and upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see Cisco Prime Collaboration Quick Start Guide:
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:43:55Z

Chetrao: /* How to upgrade Cisco Prime Collaboration Assurance deployment model? */

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see Cisco Prime Collaboration Quick Start Guide:
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:42:16Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see [Cisco Prime Collaboration Quick Start Guide].</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:40:14Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html Cisco Prime Collaboration Quick Start Guide].</pre>
==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:37:35Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html].</pre>
==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:36:41Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html].</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:35:55Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html].</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:34:45Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html
]</pre>
==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:31:39Z

Chetrao: /* How to upgrade Cisco Prime Collaboration Assurance deployment model? */

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see [http:// Cisco Prime Collaboration Quick Start Guide].
</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:27:13Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see [Cisco Prime Collaboration Quick Start Guide]:
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html].
</pre>

==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]

Troubleshooting Cisco Prime Collaboration

2013-01-03T09:25:04Z

Chetrao:

= Installation and Upgrade =

==== How to verify the Cisco Prime Collaboration Assurance installation? ====

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server. 

#Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running:

'''           show application status cpcm '''           The following is sample output of the status command

           STAT PID USER COMMAND ELAPSED            ==============================================

           S<l 10401 root Decap_main 17:45:54            Sl 12586 root emsam_fault 17:43:18            Sl 10695 root emsam_inventory 17:45:39            Sl 10602 root emsam_mq 17:45:47            Sl 12148 root emsam_poller 17:43:38            Sl 13295 root emsam_sessionmo 17:42:48            Sl 11994 root emsam_tomcat 17:44:02            Sl 13422 root emsam_troublesh 17:42:44            Ss 10497 oracle oracle 17:45:53            Ssl 10431 oracle tnslsnr 17:45:54     

          STAT PID USER COMMAND ELAPSED           ===============================================           S<l  4149 root Decap_main 5-20:27:15           SNl 5780 root emsam_fault 5-20:24:16           SNl 4414 root emsam_inventory 5-20:26:41           SNl 4343 root emsam_mq 5-20:26:50           SNl 5343 root emsam_poller 5-20:24:35           SNl 6527 root emsam_sessionmo 5-20:23:45           SNl 5258 root emsam_tomcat 5-20:24:56           SNl 6502 root emsam_troublesh 5-20:23:46           SNs 4269 oracle oracle 5-20:27:03           SNsl 4181 oracle tnslsnr 5-20:27:12 Process= ESS State = Program started - No mgt msgs received Pid = 5559 RC = 0 Signo = 0 Start = 09/14/12 19:12:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMIntegrator State = Program started - No mgt msgs received Pid = 5616 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDataServer State = Running normally Pid = 5617 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = IPIUDataServer started. Process= EssMonitor State = Running normally Pid = 5618 RC = 0 Signo = 0 Start = 09/14/12 19:12:36 Stop = Not applicable Core = Not applicable Info = ESS is fully up now ! Process= InventoryCollector State = Program started - No mgt msgs received Pid = 6029 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SSHD State = Program started - No mgt msgs received Pid = 6031 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRMonitor State = Program started - No mgt msgs received Pid = 6032 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbEngine State = Program started - No mgt msgs received Pid = 6033 RC = 0 Signo = 0 Start = 09/14/12 19:12:55 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVRDbMonitor State = Running normally Pid = 6118 RC = 0 Signo = 0 Start = 09/14/12 19:12:59 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= QOVRMultiProcLogger State = Program started - No mgt msgs received Pid = 6602 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPSLAPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task IPSLAPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= FHPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task FHPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= SEGPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = DPS Task SEGPurgeTask completed at Fri Sep 14 19:14:37 UTC 2012. For status check Job Management UI. Process= IPCDiscovery State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= SDRPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task SDRPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IVR State = Program started - No mgt msgs received Pid = 6608 RC = 0 Signo = 0 Start = 09/14/12 19:13:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= DiagPurgeTask State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:55 Core = Not applicable Info = DPS Task DiagPurgeTask completed at Fri Sep 14 19:14:54 UTC 2012. For status check Job Management UI. Process= IPIUDbEngine State = Program started - No mgt msgs received Pid = 6610 RC = 0 Signo = 0 Start = 09/14/12 19:13:20 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= IPIUDbMonitor State = Running normally Pid = 6848 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= FHDbEngine State = Program started - No mgt msgs received Pid = 6849 RC = 0 Signo = 0 Start = 09/14/12 19:13:24 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FHDbMonitor State = Running normally Pid = 6985 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= INVDbEngine State = Program started - No mgt msgs received Pid = 6987 RC = 0 Signo = 0 Start = 09/14/12 19:13:28 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMDiagServer State = Program started - No mgt msgs received Pid = 7096 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= INVDbMonitor State = Running normally Pid = 7097 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EPMDbEngine State = Program started - No mgt msgs received Pid = 7098 RC = 0 Signo = 0 Start = 09/14/12 19:13:32 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMDbMonitor State = Running normally Pid = 7174 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= SIRServer State = Program started - No mgt msgs received Pid = 7175 RC = 0 Signo = 0 Start = 09/14/12 19:13:36 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= GPF State = Running normally Pid = 7226 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = GPF process successfully started. Process= ITMLogServer State = Program started - No mgt msgs received Pid = 7227 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= ITMCTMStartup State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:14:37 Core = Not applicable Info = Application started by administrator request. Process= DfmBroker State = Running normally Pid = 7229 RC = 0 Signo = 0 Start = 09/14/12 19:13:40 Stop = Not applicable Core = Not applicable Info = DfmBroker is running normally Process= DfmServer State = Running normally Pid = 7366 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = DfmServer initialized OK. Process= CSDiscovery State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= DCRDevicePoll State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= CSRegistryServer State = Running normally Pid = 7367 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = CSRegistryServer is running Process= TomcatMonitor State = Running normally Pid = 7368 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Tomcat Server up Process= LicenseServer State = Program started - No mgt msgs received Pid = 7370 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= FDRewinder State = Never started Pid = 0 RC = 0 Signo = 0 Start = N/A Stop = Not applicable Core = Not applicable Info = Not applicable, Process= NameServer State = Program started - No mgt msgs received Pid = 7371 RC = 0 Signo = 0 Start = 09/14/12 19:13:44 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NameServiceMonitor State = Program started - No mgt msgs received Pid = 7504 RC = 0 Signo = 0 Start = 09/14/12 19:13:48 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EDS State = Running normally Pid = 7624 RC = 0 Signo = 0 Start = 09/14/12 19:13:52 Stop = Not applicable Core = Not applicable Info = Initialization complete Process= CmfDbEngine State = Program started - No mgt msgs received Pid = 7931 RC = 0 Signo = 0 Start = 09/14/12 19:14:02 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= CmfDbMonitor State = Running normally Pid = 8005 RC = 0 Signo = 0 Start = 09/14/12 19:14:06 Stop = Not applicable Core = Not applicable Info = DbMonitor Running Normally. Process= EDS-GCF State = Running normally Pid = 8055 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = GCF Initialization complete at Fri Sep 14 19:14:16 UTC 2012 Process= DCRServer State = Running normally Pid = 8056 RC = 0 Signo = 0 Start = 09/14/12 19:14:07 Stop = Not applicable Core = Not applicable Info = DCRServer is up and running Process= CMFOGSServer State = Program started - No mgt msgs received Pid = 8144 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= TISServer State = Program started - No mgt msgs received Pid = 8145 RC = 0 Signo = 0 Start = 09/14/12 19:14:11 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= EPMServer State = Running normally Pid = 8238 RC = 0 Signo = 0 Start = 09/14/12 19:14:15 Stop = Not applicable Core = Not applicable Info = EPMServer is up and running Process= STServer State = Program started - No mgt msgs received Pid = 8355 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= AdapterServer State = Program started - No mgt msgs received Pid = 8356 RC = 0 Signo = 0 Start = 09/14/12 19:14:19 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= VHMServer State = Program started - No mgt msgs received Pid = 8490 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= PIFServer State = Program started - No mgt msgs received Pid = 8491 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SRSTServer State = Running normally Pid = 8492 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = SRSTServer started. Process= FHServer State = Program started - No mgt msgs received Pid = 8493 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QoVMServer State = Program started - No mgt msgs received Pid = 8494 RC = 0 Signo = 0 Start = 09/14/12 19:14:23 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= QOVR State = Running normally Pid = 8702 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = DHMain is up and running Process= IPSLAServer State = Program started - No mgt msgs received Pid = 8703 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SEGServer State = Running normally Pid = 8704 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = SEGServer is up and running Process= ITMOGSServer State = Program started - No mgt msgs received Pid = 8705 RC = 0 Signo = 0 Start = 09/14/12 19:14:27 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= NOTSServer State = Running normally Pid = 8898 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = NOTSServer started. Process= PTMServer State = Running normally Pid = 8903 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Started Successfully Process= TopoServer State = Program started - No mgt msgs received Pid = 8904 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= SMDBMonitor State = Program started - No mgt msgs received Pid = 8905 RC = 0 Signo = 0 Start = 09/14/12 19:14:31 Stop = Not applicable Core = Not applicable Info = Application started by administrator request. Process= jrm State = Administrator has shut down this server Pid = 0 RC = 1 Signo = 0 Start = 09/14/12 19:14:31 Stop = 09/14/12 19:17:55 Core = Not applicable Info = Application started by administrator request. Process= DataPurge State = Administrator has shut down this server Pid = 0 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = 09/14/12 19:17:55 Core = Not applicable Info = DataPurge initialization complete at Fri Sep 14 19:17:55 UTC 2012. Process= diskWatcher State = Running normally Pid = 9148 RC = 0 Signo = 0 Start = 09/14/12 19:14:35 Stop = Not applicable Core = Not applicable Info = diskWatcher initialized OK. 

The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do not see all of these processes running, enter the following commands to restart the Assurance services: '''<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm '''
<pre>The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.</pre>
3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

==== How to verify the Cisco Prime Collaboration Provisioning installation? ====

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

#In a browser, specify the IP address of the server on which Provisioning has been installed. The login page is displayed. Log in with globaladmin credentials.
#Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
#Enter the following command to display the processes that are running: '''show application status cpcm''' bash: no job control in this shell httpd denotes httpd service. nice.sh denotes Nice service. startcupm.sh denotes Jboss service. postmaster/su denotes Postgres service. STAT PID USER COMMAND ELAPSED =============================================== Ss 629 root httpd 02:11:38 S 613 root nice.sh 02:11:38 S 610 root startcupm.sh 02:11:38 S 608 root su 02:11:38 The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server. If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services: '''admin#application stop cpcm admin#application start cpcm '''The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services. 

You can verify if the installation is complete and successful, by checking if the JBoss service is running. In the SSH terminal, run the following command as a root user to know if the JBoss service is running: '''ps - aef|grep startcupm '''You can also check at what time the JBoss service was started, in the following location (in the last line of the log file): '''/opt/cupm/sep/logs/jboss.log''' If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

==== How to upgrade Cisco Prime Collaboration Assurance deployment model? ====

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You can upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.

 
<pre># /opt/emms/emsam/bin/cpcmtuning.sh</pre>
From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.
<pre>Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model,
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model.
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections.

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
see Cisco Prime Collaboration Quick Start Guide:
[http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html].
</pre>
==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts listed in the procedure:

#Execute the memorymodel.sh file under /opt/cupm: ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
#Execute cpcmdiskutil.sh under /opt/cupm: . cpcmdiskutil.sh /dev/sda
#Restart the server(vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps:

#Stop jboss and nice services in the application server.
#Go to /opt/cupm/sep/build/bin and execute vi nice.sh
#Modify the following line- JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
#Save nice.sh file.
#Execute vi run.conf
#Modify the following line: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" as  JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
#Save run.conf file.
#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart Provisioning services: /etc/init.d/pmservers start
#Restart the server (vmware instance) 

==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====

#Stop the database service: /etc/init.d/pmservers stop
#Copy the configuration file: cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
#Rename the file as postgresql.conf: mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
#Update the file - /opt/postgres/9.0/data/postgresql.conf: In the above file, search for the word "@PORT@" and change it as - 5432
#Restart Provisioning services: /etc/init.d/pmservers stop
#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume): . cpcmdiskutil.sh /dev/sda
#Restart the server (vmware instance) 

= User Interface =

==== How to remove the SSL certificate warning? ====

*Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
*Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

#Choose '''Continue to this website (not recommended)'''.
#Choose '''Tools '''> '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Security '''tab, choose '''Trusted sites''', and then click '''Sites'''.
#Confirm that the URL that appears in the field and matches the application URL, and then click '''Add'''.
#Close all dialog boxes and refresh the browser.
#Choose '''Certificate Error '''to the right of the address bar, and then click '''View certificates'''.
#In the '''Certificate''' dialog box, click '''Install Certificate'''.
#In the '''Certificate Import Wizard '''dialog box, click Next.
#Click the '''Place all certificates in the following store '''radio button, and then click '''Browse'''.
#In the '''Select Certificate Store '''dialog box, choose '''Trusted Root Certification Authorities''', and then click '''OK'''.
#Click '''Next '''> '''Finish'''.
#In the '''Security Warning '''message box, click '''Yes'''.
#In the '''Certificate Import Wizard '''message box, click '''OK'''.
#In the '''Certificate '''dialog box, click '''OK'''.
#Repeat Step 2 and Step 3.
#Select the URL in the '''Websites '''section, and then click '''Remove'''.
#Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of [http://www.cisco.com/en/US/products/ps12363/tsd_products_support_series_home.html Prime Collaboration 9.0 Administration Guide ]for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

#Choose '''Tools''' > '''Internet Options'''.
#In the '''Internet Options '''dialog box, click the '''Advanced''' tab.
#In the '''Security '''section, uncheck the '''Warn about certificate address mismatch''' check box.

In Mozilla Firefox, to remove the SSL certificate warning:

#Click'''I Understand the Risks '''>'''Add Exception'''.
#In the the '''Add Security Exception '''dialog box, click '''Confirm Security Exception'''.

= Video Troubleshooting =

==== While performing the troubleshooting workflow between endpoints, I am seeing these issues: ====

*'''Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.''' 
*

'''Some network nodes are missing in the path topology''' 

If you are seeing any one of the above issues, you can check whether: 

*"utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000). 
*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system. traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20. In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20. 

*"systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table). 

==== The troubleshooting status shows No CLI Access and does not allow to troubleshoot. ====

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

==== Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page? ====

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully. 

 

[[Category:Cisco_Prime_Collaboration_9_0]]