I have heard of such issues with PIX in failover pair which have FO or FO_AA license installed. If a failover unit with one of these licenses is used in standalone mode, the unit will reboot at least once every 24 hours until the unit is returned to failover duty. A unit with an FO or FO_AA license operates in standalone mode if it is booted without being connected to a failover peer with a UR license. If the unit with a UR license in a failover pair fails and is removed from the configuration, the unit with the FO or FO_AA license will not automatically reboot every 24 hours; it will operate uninterrupted unless the it is manually rebooted.
When the unit automatically reboots, the following message displays on the console:
Pls. watch what the logs show from the time of the reboot everyday.
We have seen issues where the cleaning crew just unplugged the device and plugged their vaccum cleaner in that outlet which caused a nightly reboot (believe it or not this has happened !!). So, pls. see what the logs say and we shall go from there. Since there is no crash file recorded I am thinking either it lost power or it is crashing without recording a crash file.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...