What is the success rate of Cisco ACI
This document describes how to run a database vacuum to clean up obsolete or redundant DB entries in the Prime Collaboration Assurance (PCA) application.
Employed by Joseph Koglin, Cisco TAC Engineer.
Cisco recommends that you understand these topics and make the following recommendations:
- Basic knowledge of the PCA
- If you take any of the actions outlined in this document, you will need a maintenance window while the PCA is in production.
- You need full root access. For instructions, see Root Access at the bottom of this document if you have not configured root access.
The information in this document is based on the following software versions and applications:
PCA and PCA power supply database
The information in this document was produced by the devices in a specific laboratory environment. All devices used in this document started with an empty (standard) configuration. With your network up and running, make sure you understand the potential implications of a command.
A DB vacuum or DB cleanup can be used.
- When the space is repeatedly increased from the "/ opt" directory
- The server has been online for a long time, e.g. B. 6 months or more and can be used for routine maintenance.
- Backups keep failing
Think of this as reorganizing the database, which can take advantage
- The system performance is faster
- Data that was occasionally displayed is now displayed consistently.
- The storage space can be drastically reduced in order to free more storage space for a larger DB growth.
- Backups complete faster and have a higher success rate.
Note: Before you run the DB vacuum, please note that the DB vacuum process can usually take between 2 hours and 12 hours. Since the DB vacuum depends on the DB size, the process time can vary
Premature steps before starting the DB vacuum
Before doing this, please take a snapshot of the VM via vSphere or take a PCA backup, this is a precautionary measure just to be safe.
Although no cases of problems with the DB vacuum in the PCA have been reported, it is best to be sure.
There are two options
Take a VM snapshot:
Step 1: Right click on the VM in vSphere.
Step 2: Choose Snapshot >> Create Snapshot. Display at the bottom of the sphere to monitor completion
Create a PCA backup:
1. Navigate to Select System Administration> Backup Settings >> New and fill in the required information depending on whether you only need the Assurance or Assurance and Analysis data.
If you have a VM snapshot or a successful backup, please continue.
To ensure that the PCA-DB port is open
Follow the next steps to ensure that the ports required to operate the DB Vacuum are open for connection.
Step 1: Log in to PCA via SSH as the root user and port 26.
Step 2: input. / sbin / iptables -A INPUT -p tcp -dport 5433 -j ACCEPT
Step 3: input. /etc/init.d/iptables save
DB vacuum process
Step 1: Log in to PCA as the root user through the VM console. Using putty or securecrt on the SSH session can cause the timeout and make these commands more reliable in the VM console to execute
Step 2: Stop all processes and services./opt/emms/emsam//bin/cpcmcontrol.sh stop (this process can take 10-15 minutes until all services are completely set)
Step 3: run to make sure all services are stopped./opt/emms/emsam/bin/cpcmcontrol.sh
Step 4: Start the DB service only./opt/emms/emsam/bin/start_db.sh
Step 5: You change the directory to navigate to Postgres for the remaining commands cd /opt/postgres/9.2/ to execute.
Note: The Postgres version can be changed depending on the major version. You can run cd / opt / postgres / followed by ls -l to find the installed version if the command doesn't work with version 9.2.
Step 6: Input.see Postgre
Step 7: Input. vacuumlo -U cmuser -p 5433 -v cpcm
Note: Steps 7-10 take a few hours and each command is executed on its own. When the process is complete, go to the next step.
Step 8 input. vacuumlo -U cmuser -p 5433 -v qovr
Step 9: input. /opt/postgres/9.2/bin/psql -p 5433 —username = cmuser cpcm -c "VACUUM FULL ANALYZE;"
Step 10: input. /opt/postgres/9.2/bin/psql -p 5433 —username = qovr qovr -c "VACUUM FULL ANALYZE;"
Step 11. Entry: su root and enter the root password again
Step 12: stop DB - /opt/emms/emsam/bin/shutdown_db.sh
Step 13: start all processes - /opt/emms/emsam//bin/cpcmcontrol.sh start
It takes approx. 15 minutes until all services are available again and then log back into the GUI.
You have now completed the DB vacuum process.
This section describes how to get full root access for PCA.
Step 1: Login to PCA via SSH and use port 26 as the admin user.
Step 2: input.root_enable
Enter the desired root password.
Step 3: Input.rootand Enter the root password.
Step 4: After logging in as root input./opt/emms/emsam/bin/enableRoot.sh
Step 5: Input.passwd and enter your root password again
You should now be able to close the SSH session and log in again directly as root.
- Why is the div tag used in HTML
- What is SDR
- Why was Machiavelli considered the prince
- How do people become fascists
- How does gold develop
- Sarabjit Singh was a RAW agent
- Why is India far better than Pakistan
- What if your company is taken over
- Which states hold elections in India
- What does the Malayalam word pucchham mean
- Why is Modi successful
- Successful people are perfectionists
- Why do Indians forget their Sanskrit
- What are Southwest Airlines' best hacks
- Did Donald Trump ever bribe anyone
- Will I survive in NYC?
- Will Karl Deisseroth win a Nobel Prize
- How do I track good penny stocks
- All religion evolved from Hinduism
- Hair transplant causes cancer
- Boys need emotional support
- Why does coffee taste like alcohol?
- Can I play an online lottery from Bangalore?
- Which robo-advisors offer UTMA-UGMA accounts