Symptom
Upgraded to 7.0.4 or 7.0.5 FMC and FTD they converted to light registration sfipproxy.
They need to convert light registration sfipproxy.conf.json back to legacy now to fully recover.
/var//sf/peers/*/sfipproxy.conf.json files exist on pre 7.2.0 FMC
These files don't contain prometheus service support.
/etc/sf/sfipproxy.conf does not have any FTD services defined anymore because they are moved to /var//sf/peers/*/sfipproxy.conf.json files
Conditions
Upgraded FMC and FTD's to 7.0.4 or 7.0.5 from pre 7.0.0 release
Once unexpected conversion to 7.2.0 format happens on 7.0.4(5) FMC existing legacy API will not add required new services because legacy code for that does not work for 7.2.0 configurations.
Workaround
Run attached script restore_sfipproxy_conf.pl to restore legacy configuration on FMC if /etc/sf/sfipproxy on pre-7.2.0 FMC is missing the right entries.
Further Problem Description
Recovery process - see workarounds.
