cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1706
Views
0
Helpful
3
Replies

Prime Infrastructure 3.10 - Repositories disappeared from running conf

0_Kiss
Level 1
Level 1

Hi all,

Has anyone else encountered the issue of disappearing repositories from the running config of Prime Infrastructure?
I can configure repos via CLI but they don't show up in the running config.
There is no repository in the running config at all not even defaultRepo.
Using "show repository xy" works fine, I can see the contents of all repos incl. external ones.

The biggest issue with this is that we are using external repos for backup but we can't chose any repositories except defaultRepo as a backup destination in the Prime GUI.

We already saw this issue with Prime 3.9 and after a upgrade to 3.10.3 the issue still persists.
We tried deleting and reconfiguring the repos but this did not help.

Has anyone also encountered this issue or any suggestions on what we could try to resolve this before we open a TAC case?

Thanks!

Best regards,
Oli

1 Accepted Solution

Accepted Solutions

0_Kiss
Level 1
Level 1

We were able to fix the issue with the help of Cisco TAC.
It seems like the repo password was too long (15 characters is max).
A reboot was still necessary, the configuration thread was stuck and would not configure any repos even when using a shorter password.
After the reboot we were able to configure the repo and it was visible again in the running config.

View solution in original post

3 Replies 3

Hello,

the first thing that comes to mind is to check if the repository has enough space (even after 'ncs cleanup')...

Hi Georg,

Thanks for the suggestion!
All the repos have enough space, there is 250 GB available on the local disk and our backups are usually about 50 GB.
The external repo is hosted on a dedicated backup server and it currently has 1 TB of free space.

0_Kiss
Level 1
Level 1

We were able to fix the issue with the help of Cisco TAC.
It seems like the repo password was too long (15 characters is max).
A reboot was still necessary, the configuration thread was stuck and would not configure any repos even when using a shorter password.
After the reboot we were able to configure the repo and it was visible again in the running config.