01-14-2019 09:37 AM
Ok now that 6.2.3.9 is avail as well as 6.3.0-84; is it more prudent to upgrade to either of those
or backtrack to 6.2.3.7 or lower? Currently only 6.2.3.8 is on FMC. We have experienced the bug a few times now. Also adjusted the File policies for HTTP.
Thank You All.
Solved! Go to Solution.
01-17-2019 10:14 AM - edited 01-17-2019 10:48 AM
What you saw on Tuesday (6.2.3.9 listed under the affected versions) was a glitch that was fixed after few hours.
What is shown now it is the correct info. 6.2.3.8 is affected by CSCvn82378, while 6.2.3.9 is not affected by CSCvn82378.
01-15-2019 05:16 AM
Well, I would say it depends:
01-15-2019 06:23 AM
01-15-2019 09:15 AM
Now 6.2.3.9 is buggy ? Is there a 6.2.3.10 being worked on for this or a 6.3.1 possibly?
01-15-2019 11:20 PM - edited 01-15-2019 11:21 PM
Which defect are you referring to?
01-17-2019 08:40 AM
Hey,
I thought I saw that 6.2.3.9 was included in the affected version list Tuesday afternoon; Thus my curiosity. It is now the fixed version. On Tuesday, while running 6.2.3.8 on FMC I saw traffic passing the firewall without the FMC configured rules being applied (even after redeploying). This was on one of our FW-ASAs. Others were not affected.... When I backed down to 6.2.3.7 on FMC and re-applied to sensors running 6.2.3.6. -all began working normal and has been since.
No FW-ASA configuration was changed. A bit odd; thus my questioning 6.2.3.9...
This may indeed be a separate issue, (and not related to the bug) but I need stability ASAP.
Thanks for all your help and curious if anyone else is seeing any such weirdness.
01-17-2019 10:14 AM - edited 01-17-2019 10:48 AM
What you saw on Tuesday (6.2.3.9 listed under the affected versions) was a glitch that was fixed after few hours.
What is shown now it is the correct info. 6.2.3.8 is affected by CSCvn82378, while 6.2.3.9 is not affected by CSCvn82378.
02-05-2019 08:34 AM
This bug is present in 6.3 as well. FMC 6.3.0-84 and FTD 6.3 running on a 4110 I hit it every 4 or 5 hours. Total blackhole. Luckily I had an SSH rule to hit the CLI of the FTD directly and reboot it. Only way to "fix" it. Since then I have disable file policy and added Hotfix B to the FTD. Scared to put the file policy back.
It is INSANE how unstable this platform is.
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: