You can verify that
Cisco Prime Collaboration Provisioning has been properly installed as follows:
- In a browser, specify the IP
address of the server on which Cisco Prime Collaboration Provisioning (standard
or advanced) has been installed. The login page is displayed. Log in with
global administrator credentials.
- Log in to the Provisioning server using the SSH service and with
the CLI administrator that you created during OVA configuration. By default,
this username is troubleshooting user
With the troubleshooting UI, the user can check the services,
create the console account, and access the PCP CLI.
- Display the processes that
show application status
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
The parameters in the COMMAND column are the processes that are running on the Cisco Prime Collaboration Provisioning server (standard or advanced). If you do not see the processes running, enter the following commands to restart the Cisco 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 Cisco 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 troubleshooting 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):
If the JBoss service is running, see
Getting Started after New Installation , to get started with the Cisco Prime Collaboration Provisioning application.