When originally implemented the ftp auto update feature had several problems when using other ftp servers.
The implementation has changed over the past few years, and become more generalized.
So the listed FTP Servers are the ones "officially" tested and supported.
However, it should work with most other FTP servers as well.
I would recommend trying it with whatever FTP server you already have running. If it works then great; you are probably fine to keep using it.
If it doesn't work with your FTP server, then you can contact the TAC. If it turns out to be an incompatability between the sensor and your FTP server, then the issue would have to be entered as an enhancement request to get your FTP server supported rather than an actual bug.
We used to hear alot of incompatability problems with other FTP servers a few years ago.
But I haven't heard of any in the past 2 years.
If it is not working, then it is usually not a problem with the actual FTP server, but rather in how it was configured.
Here are a few examples of issues that are sometimes seen, and can be avoided with configuration of the FTP server.
Additional login messages can sometimes confuse the sensor (like warnings about who can access the box).
The FTP server has to be configured to use unix style directory listings instead of windows style.
Permissions on the files themselves can be a problem.
Renaming of the files after being pulled from cisco.com can cause problems, so keep the filenames exactly as seen on the cisco.com pages.
Keep directory names to letters and numbers to avoid parsing problems with the directory name.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...