Verify the Cisco Prime Collaboration Assurance Installation (for Advanced and Standard Mode)
If you are unable to launch Cisco Prime Collaboration Assurance, it could be because the required processes are not running on the Cisco Prime Collaboration Assurance server.
To verify the process status, login to Cisco Prime Collaboration Assurance Serviceability User Interface.
You can view the Cisco Prime Collaboration Assurance processes that are running on the server. You can start or stop the processes apart from viewing the server.
Note |
You cannot start or stop an individual process. You can either Start or Stop all processes.
|
Note |
The process status dashboard automatically refreshes every 6 seconds. |
Procedure
Step 1 |
Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, the username is admin. |
Step 2 |
Display the processes that are running. show application status cpcmThe following is sample output of the status command, for Cisco Prime Collaboration Assurance- Advanced server: S<l 11866 root Decap_main 13-01:10:20 S 11988 postgres postgres 13-01:10:18 S 12132 primea postmaster 13-01:10:07 Sl 12262 root emsam_mq 13-01:09:50 Sl 12327 root cpc_multiproclo 13-01:09:42 Sl 12362 root emsam_inventory 13-01:09:42 Sl 13141 root emsam_perfmonen 13-01:08:03 S<l 13222 root emsam_tomcat 13-01:07:53 Sl 13314 root emsam_poller 13-01:07:28 Sl 13448 root emsam_fault 13-01:07:07 Sl 13885 root emsam_troublesh 13-01:06:18 Sl 13919 root emsam_sessionmo 13-01:06:17 Sl 14733 root cpc_datapurge 13-01:04:31 Sl 14828 root cpc_segserver 13-01:04:26 Sl 15027 root cpc_qovmserver 13-01:04:15 Sl 15386 root cpc_pifserver 13-01:04:00 Sl 15539 root cpc_ipiudataser 13-01:03:47 Sl 15572 root cpc_srstserver 13-01:03:45 Sl 15974 root cpc_stserver 13-01:03:38 Sl 17685 root cpc_sshd 13-01:01:04 Sl 17724 root cpc_qovr 13-01:01:02 Sl 17746 root cpc_smdbmonitor 13-01:01:00 Sl 17792 root cpc_ipslaserver 13-01:00:57 Sl 17889 root cpc_toposerver 13-01:00:52 Sl 19542 root cpc_gpf 13-00:54:09 The following is the output of status command for Cisco Prime Collaboration Assurance- Standard server:STAT PID USER COMMAND ELAPSED =============================================== S<l 3086 root Decap_main 21:44:29 S 3204 postgres postgres 21:44:28 S 3335 primea postmaster 21:44:16 Sl 3378 root emsam_mq 21:43:59 Sl 3445 root cpc_multiproclo 21:43:51 Sl 3479 root emsam_inventory 21:43:51 Sl 4336 root emsam_perfmonen 21:42:23 S<l 4417 root emsam_tomcat 21:42:13 Sl 4592 root emsam_poller 21:41:49 Sl 4736 root emsam_fault 21:41:29 Sl 5976 root emsam_troublesh 21:40:38 [root@DragonSmokeTestStd bin]#The parameters in the COMMAND column are the processes that are running on the Cisco Prime Collaboration Assurance server (Standard/Advanced). If you do not see all of these processes running, enter the following commands to restart the Cisco Prime Collaboration Assurance services: <hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm The application start cpcm/cpcmcontrol.sh start takes 10 to 15 minutes for execution and application stop cpcm/cpcmcontrol.sh stop takes 10 minutes. |
Step 3 |
Repeat Step 2 and check whether all the processes are running. If all the required processes are still not running on the Cisco Prime Collaboration Assurance server or if you are unable to access the Cisco Prime Collaboration Assurance URL, contact TAC team. If all the processes are running, see Get Started with Cisco Prime Collaboration Assurance. |