09-20-2016 04:53 AM - edited 03-20-2019 09:04 PM
After upgrading our FMC from 6.0.1 to 6.1.0, we cannot access AMP > AMP Management.
We receive following message: An error occurred while fetching page data. Please reload the page and try again.
After clicking OK, we cannot add an AMP Cloud connection because the cloud name field is empty...
I already imported a backup in a freshly installed FMC 6.1.0, but the problem remains...
There is a very similar bug known: CSCvb27732 FMC: Unable to access Devices under Management page on FMC
Somebody else who experienced the same issue? Any solutions available?
In parallel, a case has been logged @cisco...
Thanks.
Ruben
09-20-2016 05:40 AM
Problem has been solved thanks to Cisco TAC.
For our case, following 2 commands did the trick (you must be root):
root@firepower:~# OmniQuery.pl -db mdb -e "select * from fireamp_cloud"
getting filenames from [/usr/local/sf/etc/db_updates/index]
getting filenames from [/usr/local/sf/etc/db_updates/base-6.1.0]
+------------------+----------+------------+------------------+------+---------- +
| uuid | name | last_event | domain_uuid | data | obj_uuid |
+------------------+----------+------------+------------------+------+---------- +
| ▒▒;A▒2^▒ | EU Cloud | 0 | ▒v▒▒▒▒▒im▒ԛb_ | | |
+------------------+----------+------------+------------------+------+---------- +
ERROR
Check Syntax.
----------------------------
OmniQuery v2.1
(c) 2016 Cisco Systems, Inc.
.:|:.:|:.
----------------------------
mdb>
root@firepower:~# OmniQuery.pl -db mdb -e "truncate fireamp_cloud"
getting filenames from [/usr/local/sf/etc/db_updates/index]
getting filenames from [/usr/local/sf/etc/db_updates/base-6.1.0]
No results.
----------------------------
OmniQuery v2.1
(c) 2016 Cisco Systems, Inc.
.:|:.:|:.
----------------------------
mdb>
11-10-2016 06:24 PM
I have a fmc with same error, and these two commands dont fix. Do you have another sugestions?
Tks
11-14-2016 10:17 AM
Thanks a lot!, it worked great for me. I just signed shelled in as admin then "sudo" the two commands and it worked. Notice that you don't run the second command from within the "mdb>" prompt but from the "admin@firepower:~#" prompt same as the first command.
Thanks again.
01-05-2017 12:06 AM
We also faced the same problem. Cisco TAC solved the problem as the way mentioned here.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide