This section explains the following:
Verify the Cisco
Prime Collaboration Provisioning Installation (for Advanced or Standard
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 as globaladmin. Go to Administration>Logging and Showtech, create a troubleshooting user, and obtain the response string by mailing challenge string to the Engineering Team, and then login as troubleshooting user to the Troubleshooting UI.
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 , to get started with the Cisco Prime Collaboration Provisioning application.
Upgrade the Cisco
Prime Collaboration Provisioning from Small to Medium Deployment Model
After you manually upgrade the system requirements (vRAM, vCPU, vDISK, and so on), you must run the following scripts as a troubleshooting user:
memorymodel.sh file under
"-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m
-XX:MaxPermSize=256m" simple all
. /cpcmdiskutil.sh /dev/sda
- Restart the server(VMware
If you want to
support endpoint count as per the upgraded deployment model in Cisco Prime
Collaboration Provisioning, you must add a scale license.
Upgrade the Cisco
Prime Collaboration Provisioning Server from the Small or Medium to Large
- Back up the database from the
Cisco Prime Collaboration Provisioning application by following the procedures
Cisco Prime Collaboration
- Deploy a large OVA, both as an application and database server
by following the procedure in the
and Configuring Cisco Prime Collaboration Provisioning. Ensure that the
globaladmin password is the same as the password that you provided during the
licenses from the old server to the new server.
If you use
the MAC address of the existing Cisco Prime Collaboration Provisioning server,
then update the MAC address using the VMware client for this VMware instance.
If you use a
new MAC address for server, then you must rehost the licenses in the
/opt/cupm/license directory to match the new server
- Stop provisioning services
in the server.
Go to the
Apache, JBoss, and NICE services are stopped.
ps -aef | grep startcupm
ps -aef | grep nice
startcupm process id
nice process id
the nice process is still holding on the postgres connection.
/opt/cupm/jvm/bin/java -server -classpath
running nice process.
Process-Id found earlier
Wait a minute
to make the resources, such as ports, to become free.
- Restore the database in the server using the backed-up database
file taken from Step 1. For details, see the section Restoring Database in the
server section in the Cisco Prime Collaboration
- Stop and then start the provisioning services in the server
seconds before starting the database services
- Copy the following files from the
original Cisco Prime Collaboration Provisioning server to the newly deployed
- Change the directory
/opt/cupm/sep and edit the
dfc.properties file using the vi editor
property dfc.memory.model=medium to
property dfc.postgres.host=localhost to
dfc.postgres.host=IP of server Database
and exit the editor
- Start application services in the
start the application services
- cd /opt/cupm
The system is
now ready to be used.
Prime Collaboration Provisioning Deployment Model
Collaboration does not support the downgrade of the deployment model; that is,
you cannot downgrade from the Cisco Prime Collaboration large deployment model
to small deployment model.
Change the IP
Address on the Provisioning Server (Single Setup)
procedure is applicable for Cisco Prime Collaboration Provisioning 12.3 and
Call the Engineering Team, and get the troubleshooting account access.
Console Account, and then login to the CLI account.
In OS, change
the configuration file
/etc/sysconfig/network-scripts/ifcfg-eth0 that stores
network config settings specific to the new IP address.
network services using the command
To verify IP
address change, issue the command
and check for updated IP in the response.
/etc/resolv.conf with the DNS of the new IP address.
/etc/hosts file with new server IP and hostname.
hostname in Cisco Prime Collaboration Provisioning server by running the
Creating a Troubleshooting
- Login to PCP
- Go to
Administration > Logging and ShowTech. In Troubleshooting
Account field, provide User ID, and Select duration from
In dropdown, and then click
On creating a Troubleshooting user, challenge string is generated, using this we can generate a response which acts as password for a Troubleshooting user. Contact the Engineering Team for generating a response string.
PCP as Troubleshooting user, then start micro service page from
Troubleshooting>Launch. Also, Sep admin can be accessed
under Troubleshooting menu.
To Access Troubleshooting
Account or Console Account if the PCP UI is inaccessible
When PCP UI is
inaccessible, you can verify the status of the server from the micro service
We can access
Troubleshooting account from micro service page:https:// <PCP ip
Go to micro
service page, create a troubleshooting user. For creating a troubleshooting
user, refer to
a Troubleshooting Account .
Login from micro
service page, go to Process Management to verify the status of PCP services.
Console account can
be created to access CLI account of PCP.
Generate Console Account
using Troubleshooting User
Follow these steps to
generate a console account using troubleshooting user
In PCP micro
service page under Console Account, we generate a console account user by
providing username and password.
account, you can access CLI of PCP server.
In PCP 12.1,
there is no access to CLI/SSH as root, so the user created through console
account can access this privilege.
troubleshooting user is created using trouble shooting UI, and the Cisco Prime
Collaboration Provisioning database is not up and running, then the user will
be available only through the troubleshooting UI and not through the Cisco
prime Collaboration Provisioning UI.
Signing Request (CSR)
|| Go to micro
service page, and then create a troubleshooting user. For creating a
troubleshooting user, refer to
a Troubleshooting Account.
|| Generate the
Console Account, and then login to the CLI account.
||Go to cd
||To generate the
./openssl req -new -key
<keyName>.key -out <csrName>.csr
appropriate details when prompted, such as:
Organizational unit name:
CSR is available in the location