05-23-2018 03:52 AM - edited 03-20-2019 10:10 PM
We have the same problem with Prime 3.2.0.0.258. Can anybody provide a solution or a reason of the bug?
07-26-2018 01:58 PM
We are seeing the same Alarm running 3.2.0.0.258, did you ever find a resolution?
07-29-2018 09:16 PM
Hi
No unfortunately there's no answer from cisco to this bug. I think with upgrading to prime 3.4, the error is gone.
07-30-2018 01:58 AM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
