These log messages refer to the HA (High Availability events) category.
2.26.1. peer_gone (ID: 01200001)
- Default Severity
- NOTICE
- Log Message
- Peer firewall disappeared. Going active
- Explanation
- The peer firewall (which was active) is not available anymore. This firewall will now go active instead.
- Firewall Action
- activate
- Recommended Action
- None
- Revision
- 2
2.26.2. peer_gone (ID: 01200002)
- Default Severity
- NOTICE
- Log Message
- Peer firewall disappeared.
- Explanation
- The peer firewall (which was inactive) is not available anymore. This firewall will continue to stay active.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
2.26.3. conflict_both_peers_active (ID: 01200003)
- Default Severity
- NOTICE
- Log Message
- Conflict: Both peers are active! Resolving...
- Explanation
- A conflict occured as both peers are active at the same time. The conflict will automatically be resolved.
- Firewall Action
- resolving
- Recommended Action
- None
- Revision
- 1
2.26.4. peer_has_higher_local_load (ID: 01200004)
- Default Severity
- NOTICE
- Log Message
- Both active, peer has higher local load; staying active
- Explanation
- Both memebrs are active, but the peer has higher local load. This firewall will stay active.
- Firewall Action
- stay_active
- Recommended Action
- None
- Revision
- 2
2.26.5. peer_has_lower_local_load (ID: 01200005)
- Default Severity
- NOTICE
- Log Message
- Both active, peer has lower local load; deactivating
- Explanation
- Both members are active, but the peer has lower local load. This firewall will de-activate.
- Firewall Action
- deactivate
- Recommended Action
- None
- Revision
- 2
2.26.6. peer_has_more_connections (ID: 01200006)
- Default Severity
- NOTICE
- Log Message
- Both active, peer has more connections; deactivating
- Explanation
- Both members are active, but the peer has more connections. This firewall will de-activate.
- Firewall Action
- deactivate
- Recommended Action
- None
- Revision
- 2
2.26.7. peer_has_fewer_connections (ID: 01200007)
- Default Severity
- NOTICE
- Log Message
- Both active, peer has fewer connections; staying active
- Explanation
- Both members are active, but the peer has fewer connections. This firewall will stay active.
- Firewall Action
- stay_active
- Recommended Action
- None
- Revision
- 2
2.26.8. conflict_both_peers_inactive (ID: 01200008)
- Default Severity
- NOTICE
- Log Message
- Conflict: Both peers are inactive! Resolving...
- Explanation
- A conflict occured as both peers are inactive at the same time. The conflict will automatically be resolved.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 1
2.26.9. peer_has_more_connections (ID: 01200009)
- Default Severity
- NOTICE
- Log Message
- Both inactive, peer has more connections; staying inactive...
- Explanation
- Both members are inactive, but the peer has more connections. This firewall will stay inactive.
- Firewall Action
- stay_deactivated
- Recommended Action
- None
- Revision
- 2
2.26.10. peer_has_fewer_connections (ID: 01200010)
- Default Severity
- NOTICE
- Log Message
- Both inactive, peer has fewer connections; going active...
- Explanation
- Both members are inactive, but the peer has fewer connections. This firewall will go active.
- Firewall Action
- activate
- Recommended Action
- None
- Revision
- 2
2.26.11. peer_alive (ID: 01200011)
- Default Severity
- NOTICE
- Log Message
- Peer firewall is alive
- Explanation
- The peer firewall is alive.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
2.26.12. heartbeat_from_unknown (ID: 01200043)
- Default Severity
- WARNING
- Log Message
- Received HA heartbeat from unknown IP. Dropping
- Explanation
- The received HA heartbeat packet was originating from an unknown IP. The packet will be dropped.
- Firewall Action
- drop
- Recommended Action
- None
- Revision
- 1
- Context Parameters
- Rule Name
Packet Buffer
2.26.13. should_have_arrived_on_sync_iface (ID: 01200044)
- Default Severity
- WARNING
- Log Message
- This packet should have arrived on the sync iface. Dropping
- Explanation
- The HA packet did not arrive on the sync interface. The packet will be dropped.
- Firewall Action
- drop
- Recommended Action
- None
- Revision
- 1
- Context Parameters
- Rule Name
Packet Buffer
2.26.14. activate_failed (ID: 01200050)
- Default Severity
- WARNING
- Log Message
- Failed to activate the configuration merged from HA partner
- Explanation
- The firewall failed to activate the merged configuration that was received from the peer.
- Firewall Action
- ha_activate_conf
- Recommended Action
- None
- Revision
- 2
2.26.15. merge_failed (ID: 01200051)
- Default Severity
- WARNING
- Log Message
- Failed to merge configuration from HA partner
- Explanation
- The firewall failed to merge the configuration that was received from the peer.
- Firewall Action
- ha_merge_conf
- Recommended Action
- None
- Revision
- 2
2.26.16. ha_commit_error (ID: 01200052)
- Default Severity
- WARNING
- Log Message
- The merged HA configuration contains errors
- Explanation
- The merged HA configuration contains errors and can not be commited.
- Firewall Action
- ha_commitchanges
- Recommended Action
- Resolve the errors and commit the changes again.
- Revision
- 1
2.26.17. ha_write_failed (ID: 01200053)
- Default Severity
- WARNING
- Log Message
- Could not write HA configuration to disk
- Explanation
- The HA configuration could not be written to the storate media.
- Firewall Action
- ha_commitchanges
- Recommended Action
- Verify that the storage media is not write protected or damaged.
- Revision
- 1
2.26.18. ha_commit_unknown_error (ID: 01200054)
- Default Severity
- WARNING
- Log Message
- An unknown error occured while saving the HA configuration
- Explanation
- An unknown error occured when the HA configuration was to be saved. It has not been commited.
- Firewall Action
- ha_commitchanges
- Recommended Action
- None
- Revision
- 1
2.26.19. linkmon_triggered_failover (ID: 01200055)
- Default Severity
- NOTICE
- Log Message
- HA node going inactive. <reason>
- Explanation
- Linkmon requested the node to go inactive.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 1
- Parameters
- reason
2.26.20. resync_conns_to_peer (ID: 01200100)
- Default Severity
- WARNING
- Log Message
- Initiating complete resynchronization of <numconns> connections to peer firewall
- Explanation
- All current connections will be re-synchronized to peer, as the peer has been restarted. Initializing re-synchronization process.
- Firewall Action
- resync_conns_init
- Recommended Action
- None
- Revision
- 1
- Parameters
- reason
numconns
2.26.21. hasync_connection_established (ID: 01200200)
- Default Severity
- NOTICE
- Log Message
- HASync connection to peer firewall established
- Explanation
- HA synchronization connection to peer has been establihsed. Supported events will now be synchronized between the members
of the HA cluster.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 2
2.26.22. hasync_connection_disconnected_lifetime_expired (ID: 01200201)
- Default Severity
- NOTICE
- Log Message
- HASync connection lifetime expired. Reconnecting...
- Explanation
- The HA synchronization connection lifetime has expired. A new connection will be establised by reconnecting to the peer.
- Firewall Action
- reconnect
- Recommended Action
- None
- Revision
- 2
2.26.23. hasync_connection_failed_timeout (ID: 01200202)
- Default Severity
- NOTICE
- Log Message
- HASync connection to peer firewall failed. Reconnecting...
- Explanation
- The HA synchronization connection attempt failed. Reconnecting to peer.
- Firewall Action
- reconnect
- Recommended Action
- None
- Revision
- 2
2.26.24. resync_conns_to_peer_complete (ID: 01200300)
- Default Severity
- NOTICE
- Log Message
- Connection resynchronization to peer complete
- Explanation
- The connection resynchronization process to peer is complete. All connections has been synchronized.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 1
2.26.25. disallowed_on_sync_iface (ID: 01200400)
- Default Severity
- WARNING
- Log Message
- Received non-HA traffic on sync iface. Dropping
- Explanation
- A packet which is not a HA-related packet was received on the sync interface. This should not happend and the packet will
be dropped.
- Firewall Action
- drop
- Recommended Action
- None
- Revision
- 1
- Context Parameters
- Rule Name
Packet Buffer
2.26.26. sync_packet_on_nonsync_iface (ID: 01200410)
- Default Severity
- WARNING
- Log Message
- Received state sync packet on non-sync iface. Dropping
- Explanation
- A HA state sync packet was recieved on a non-sync interface. This should never happend and the packet will be dropped.
- Firewall Action
- drop
- Recommended Action
- None
- Revision
- 1
- Context Parameters
- Rule Name
Packet Buffer
2.26.27. ttl_too_low (ID: 01200411)
- Default Severity
- WARNING
- Log Message
- Received HA heartbeat with too low TTL. Dropping
- Explanation
- The received HA heartbeat packet had a TTL (Time-To-Live) field which is too low. The packet will be dropped.
- Firewall Action
- drop
- Recommended Action
- None
- Revision
- 1
- Context Parameters
- Rule Name
Packet Buffer
2.26.28. heartbeat_from_myself (ID: 01200412)
- Default Severity
- WARNING
- Log Message
- Received HA heartbeat from the firewall itself. Dropping
- Explanation
- The received HA heartbeat packet was originating from the firewall itself. The packet will be dropped.
- Firewall Action
- drop
- Recommended Action
- None
- Revision
- 2
- Context Parameters
- Rule Name
Packet Buffer
2.26.29. config_sync_failure (ID: 01200500)
- Default Severity
- CRITICAL
- Log Message
- Tried to synchronize configuration to peer 3 times without success. Giving up.
- Explanation
- The firewall tried to synchronize the configuration to peer three times, but failed. It will now give up trying to do so.
- Firewall Action
- give_up_synching
- Recommended Action
- None
- Revision
- 2
- Parameters
- numretries
2.26.30. both_active (ID: 01200616)
- Default Severity
- NOTICE
- Log Message
- Both active, deactivation in progress.
- Explanation
- Both active, deactivation in progress.
- Firewall Action
- deactivate
- Recommended Action
- None
- Revision
- 2
2.26.31. both_inactive (ID: 01200617)
- Default Severity
- NOTICE
- Log Message
- Both not active, activation in progress.
- Explanation
- Both not active, activation in progress.
- Firewall Action
- activate
- Recommended Action
- None
- Revision
- 2
2.26.32. going_online (ID: 01200618)
- Default Severity
- NOTICE
- Log Message
- Ha unit going online.
- Explanation
- Ha unit going online.
- Firewall Action
- going_online
- Recommended Action
- None
- Revision
- 3
- Parameters
- previous_event=
2.26.33. fast_inactive (ID: 01200619)
- Default Severity
- NOTICE
- Log Message
- Fast inactive, deactivation in progress.
- Explanation
- Fast inactive, deactivation in progress.
- Firewall Action
- deactivate
- Recommended Action
- None
- Revision
- 2
2.26.34. diff_firmware_versions (ID: 01200620)
- Default Severity
- NOTICE
- Log Message
- HA peer is running a different firmware version. Local_version:<local_version> Peer_version:<peer_version>
- Explanation
- HA peer running a different firmware version which may cause interop issues.
- Firewall Action
- None
- Recommended Action
- None
- Revision
- 1
- Parameters
- local_version
peer_version
cOS Core 15.00.02 Log Reference Guide
