Now that the patches are in PI, verify they are there and then run them.ĬiscoPI/admin# patch install PI_1.2.1.12u_ localftp Now I used WinSCP to copy the two patch files to PI from my workstation. That was all it took to create the FTP account. Here’s how: (FTP Username – “ftpaccount”, password = My8l0gpw0rDĬiscoPI/admin# ncs password ftpuser ftpaccount password My8l0gpw0rD ![]() I logged in via SSH and created an FTP account. Research showed that I needed to create an FTP account on PI. ![]() Next I tried FTP, but now my credentials were not working. I figured I would use WinSCP, so I tried to login with the file protocol = SCP and my root credentials and was denied. I downloaded these two files from CCO: pi_1.2.1.12_ and PI_1_2_1_12u-Update.1.tar.gz ![]() I created a backup repository and configured it to do daily backups at 03:30 in the morning. ![]() I browsed here: Administration > Background Tasks > Other Background Tasks > Prime Infrastructure Server Backup Not knowing which day I was going to do the upgrade, I decided to configure PI to back itself up daily so I would always have a fresh backup and not have to wait to create one if I decided to the upgrade that day. After doing all the research, I discovered I needed to first patch our PI and make backups. I am writing this for myself and anyone else that might be upgrading your Cisco Prime Infrastructure (PI) in the future.
0 Comments
Leave a Reply. |