Configuration changed on standby member-checkpoint-gaia,ipso

Configuration changed on standby member-checkpoint-gaia,ipso
0

Configuration changed on standby member-checkpoint-gaia,ipso

Vendor: checkpoint

OS: gaia,ipso

Description:
Generally, making configuration changes to the standby member of a device is not recommended. indeni will trigger an issue if this happens.

Remediation Steps:
Make the configuration changes to the active member of the cluster.

How does this work?
The clish command “show config-state” is used to retrieve the current save status.

Why is this important?
When making a change in clish, the configuration is not written to disk until the command “save config” is run. This means that if the device reboots before the configuration is properly saved, it will be lost.

Without Indeni how would you find this?
An administrator could login and manually run the command.

chkp-clish-config-unsaved

Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/parsers/src/checkpoint/clish/clish-config-unsaved.ind

cross_vendor_config_change_on_standby

Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/sync_core_rules/ConfigChangeOnStandbyMemberRule.scala