Intermittent connection after policy update

[AntiEarnie]

We keep having a problem with our Firebox 1000. From time to time after a policy change is pushed to the firebox we start getting an intermittent connection on all interfaces. Fun thing is that it gets progressively worse over time until the connection is so bad you can not even upload a policy/image (generally ~12 hours). Only way I have been able to fix this in the past is to factory default the firebox and manually redo the config again. Although that does not seem to always fix it on the first try.

General info:
Firebox III/1000
Driver/Daemon 7.3 B1835
Sys_B version 4.61
Routed mode with all 3 interfaces in use on different nets.

This problem has been seen with version 4.61, 7.0, 7.21.

On average I would say 1/30 policy changes will cause this.

 

[coladmin]

I had a silimar issue with my firebox and it turns out that a cooling fan stopped working and the firebox would overheat and stopp passing traffic. you may want to call support and see if this could be an issue with your firebox.

 

[pankajchawla]

Cooling fan was issue in case of X range models not in III.

In this case looks like the config is either corrupted or incorrent. I would suggest you to take the back up of running config and then create a basic config and see how that works.

 

[AntiEarnie]

pankajchawla-
Thats the fun part. When this happens simply restoring a backup flash does no good. Heck this time around doing a factory default and rebuilding the config from scratch didn't fix it. I actually had to go back to 4.61 to resolve it this time around. Why restoring a backup of the flash does not fix it when this happens has been a source of debate between myself and my co-worker. As has the mystery of why factory defaulting and repatching will sometimes not fix it.

This is just one of those devices that I would be willing to call Gremlin Infested. Just one of those fun little intermittent problems that can not be reproduced reliably but happens every six months or so.