Can't Replace Previously Installed Policy After (reinstalling) a - busy - firewall1 (between 8-10Mbps over the external interface), a problem which we were trying to get rid of reappeared -- customer insists on "Account" logging for traffic to its DMZ - (motivation is commercial/financial)
Problem is that, when "Account" logging is activated, the firewall panics when reloading the policy. My principal problem now is that after reboot, the firewall automatically loads the policy with the "account" logging activated. Our guess is that, since the latest policy - without account logging - did not successfully load, the firewall somehow finds and loads the previous version. Weird thing is that the GUI and the real loaded policy no longer match !
Answer This is because FireWall-1 stores the last installed policy in $FWDIR/state. If you haven't been able to install the policy since this problem started occurring, then you've got the old policy there. You can clear $FWDIR/state on both your management console and firewall module. This should prevent FireWall-1 from loading a policy on startup. Then you can load the proper policy from your management console.
--
RobertGraham - 16 Mar 2004
FAQForm FAQs.Class:
LoggingAndAlertingFAQs,
TroubleshootingFAQs FAQs.OS: FAQs.Version:
Can't Replace Previously Installed Policy 
2005-08-12 
Can't Replace Previously Installed Policy 
Linear Mode
