Create a Troubleshooting Account
Procedure
From PCP |
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
From PCP |
The following procedure is applicable for Cisco Prime Collaboration Provisioning 12.3 and later releases.
Call Technical Assistance Centre (TAC), and get the troubleshooting account access.
Generate the Console Account, and then login to the CLI account.
In OS, change the configuration file sudo/etc/sysconfig/network-scripts/ifcfg-eth0 that stores network config settings specific to the new IP address.
Restart the network services using the command sudo service network restart.
To verify IP address change, issue the command sudo ifconfig and check for updated IP in the response.
Update the file /etc/resolv.conf with the DNS of the new IP address.
Update /etc/hosts file with new server IP and hostname.
Set the hostname in Cisco Prime Collaboration Provisioning server by running the command sudo hostnamectl set-hostname <HOSTNAME>.
The following procedure is applicable for Cisco Prime Collaboration Provisioning 10.0 and later releases.
Log in to the server as troubleshooting user through SSH and enter:
admin# conf t
admin(config)# interface GigabitEthernet 0
admin(config-GigabitEthernet)# ip address <ipaddress> <subnet mask>
Enter y when the following message is displayed: Changing the IP may result in undesired side effects on any installed applications. Are you sure you want to proceed? [y/n] y
Log in as troubleshooting userwith the new IP address and enter:
admin(config)# ip default-gateway <a.b.c.d>
admin(config)# ip domain-name <new_domain>
admin(config)# ip name-server <a.b.c.d>
admin(config)# hostname <new_name>
admin(config)# exit
admin# write memory
Log in as troubleshooting user with the new IP address.
Update the Nice system record in postgres:
Log in to postgres.
Goto cd /opt/postgres/pghome/bin
Enter ./psql -Upmadmin -d cupm
Enter the global admin password
Enter Select * from nicesyseng;
In the console output, check if any entries contain your old IP address (in the host column). If there are any entries, delete them by executing the following query: delete from nicesyseng where host='<old_ip_address>';
Exit the postgres by entering \q
Reboot the server.
The following procedure is applicable for Cisco Prime Collaboration Provisioning 12.6 SU1 and later releases.
Command or Action | Purpose | |
---|---|---|
Step 1 |
Modify the IP Address of the Database Server in a Distributed Setup. |
To modify the IP address of the database on the Cisco Prime Collaboration Provisioning distributed setup. |
Step 2 |
Modify the IP Address of Application Server in a Distributed Setup. |
To modify the IP address of the application server on the Cisco Prime Collaboration Provisioning distributed setup. |
Use this procedure to modify the IP address of the database server in a distributed setup.
Step 1 |
Get the troubleshooting account access from the TAC. |
Step 2 |
Generate the console account and login through the CLI account. |
Step 3 |
On the OS, change the below configuration file that stores the network configuration settings specific to the new database IP address:
|
Step 4 |
Update the file |
Step 5 |
Update the file |
Step 6 |
Run the command given below to set the hostname in Cisco Prime Collaboration Provisioning server :
|
Step 7 |
Follow the steps to add the details of the new application server IP in the file |
Step 8 |
Restart the database server. |
Step 9 |
Run the command |
Step 10 |
Execute the command given below to accept communication on port 5432 (default port for postgress) :
|
Use this procedure to modify the IP address of the application server in a distributed setup.
Step 1 |
Get the troubleshooting account access from the TAC. |
Step 2 |
Generate the console account and login through the CLI account. |
Step 3 |
On the OS, change the below configuration file that stores the network configuration settings specific to the new application IP address:
|
Step 4 |
Update the file |
Step 5 |
Update the file |
Step 6 |
Run the command given below to set the hostname in Cisco Collaboration Provisioning server :
|
Step 7 |
Update the file
|
Step 8 |
Update the file
|
Step 9 |
Restart the application server. |
Step 10 |
Run the command given below to check the readiness of the database:
|
Step 11 |
Execute the command given below in the database server, if Step10 does not give any response :
|
Step 12 |
Run the command |
Step 13 |
On the completion of the above steps, wait for a few minutes till the Cisco Prime Collaboration Provisioning Login page comes up on the application server IP. |
Note |
We can access Troubleshooting account from micro service page:https:// <PCP ip server>:28080/index. |
Go to micro service page, create a troubleshooting user. For creating a troubleshooting user, refer to Creating a Troubleshooting Account.
Login from micro service page, go to Process Management to verify the status of Prime Collaboration Provisioning services.
Note |
Console account can be created to access CLI account of Prime Collaboration Provisioning. |
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.
From console account, you can access CLI of PCP server.
Note |
|