The parameters in the COMMAND column are the processes that are running on the Assurance server. If you do notsee all of these processes running, enter the following commands to restart the Assurance services:<hostname>/admin#application stop cpcm<hostname>/admin#application start cpcm

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 cpcmadmin#application start cpcmThe 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 startcupmYou 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.logIf 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.

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.

# /opt/emms/emsam/bin/cpcmtuning.sh

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.

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 ].

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:

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 troubleshooting status shows No CLI Access and does not allow to troubleshoot.

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.