3 Comments

  1. feelsicken
    April 15, 2018 @ 2:26 am

    Hi Todd

    Thanks for your note, we faced the same problem on a customer, resulting for the whole site to be isolated… I can confirm 100% that the configuration of syslog settings made all the traffic dropped.
    It took hours to find out that the problem was related with syslog configuration, Cisco TAC engineer was not aware of this bug and we have to find it by ourselves…

    FTD is still not ready for production environment, I am – again- very disapointed with the quality of Cisco code

    Reply

    • lammle
      April 15, 2018 @ 9:44 am

      yes, the platform issue was horrible and I had to deal with it myself, with no help or acknowledgement of the issue from Cisco. However, with all that said, the 6.2.3 code seemed to have fixed it, even though they never listed it as a problem to begin with.
      All of the problem in my blog, and there are a LOT, have been fixed (so far) with the new 6.2.3/6.3 code…
      I’ve upgraded 40 customers and had no issues on the upgrade and almost all of the problems have been fixed, with some customer running 6.3 code as well as a beta from cisco…

      Reply

  2. Moe Shea
    May 23, 2018 @ 11:43 pm

    Hi Todd

    The painful part about the FTD upgrade to 6.2.3, is that, first FMC needs to be upgraded to 6.2.3, then FXOS code on the 4100 devices to be upgraded (standby first) to 2.3, then FTD on the 4100 devices (standby first) to 6.2.3

    Then hope you don’t get any calls 🙂

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *