07-04-2019 03:17 AM - edited 02-21-2020 09:16 AM
I'm running an FMCv version 6.2.3, have been for a while and everything seems to work fine. However if I try and configure the database event values and click save I get an error saying "The Host that you are trying to configure (x.x.x.x) could not be reached" The bracketed IP is very similar to the FMC address, so I'm thinking there was a typo at some point during the build maybe, but I can't work out where it's getting this IP from or where it was configured, and why nothing else is broken. Anyone any ideas?
07-04-2019 03:43 AM
07-05-2019 01:38 AM
07-09-2019 05:44 AM - edited 07-09-2019 06:00 AM
I found a solution.
The error happens when the "Audit Log Host" is unreachable. Under System>Configuration>Audit Log (on the left), see what host is configured. If that host is not reachable from the FMC, any configuration save will fail.
Set the host to a reachable IP and save. If it takes the setting, you can then modify and save other settings in System Configuration successfully.
07-09-2019 06:39 AM
Hi, thanks for your response.
However as described in my post, I worked out it was because the Audit Log Host was unreachable. I actually ended up pointing it at the local FMC address so I could change some settings. However my issue is that I have to now open up the syslog server to respond to these probes, where I did not have to before, so am trying to understand what, if anything, has changed. My syslog server responds to ICMP echo requests, but does not respond to the udp echo request, dest port 7, that my FMC seems to be generating. So really just trying to work out what has changed and where.
07-12-2019 06:06 AM
For anyone who's interested, this turned out to be a bug. Fixed in 220.127.116.11 and 18.104.22.168
06-05-2020 07:24 AM - edited 06-05-2020 07:25 AM
Do you have the bug ID?
06-05-2020 08:08 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: