This article provides information about the syslog message: ch_set_non_stop_forwarding_cfg:Setting
ch_set_non_stop_forwarding_cfg:Setting
This message does not impact service. It is harmless and can be ignored.
The ch_set_non_stop_forwarding_cfg:Setting syslog messages are encountered as below:
ch_set_non_stop_forwarding_cfg:Setting non-stop-forwarding to Enabled, source DDL ch_set_non_stop_forwarding_cfg: non-stop-forwarding enabled but pfeman_reconnect not enabled. Enabling pfeman_reconnect ch_set_non_stop_forwarding_cfg: non-stop-forwarding enabled but re-failover not enabled. Enabling re-failover ch_set_non_stop_forwarding_cfg: non-stop-forwarding enabled but failover-on-reboot not enabled. Enabling failover-on-reboot
Enabling GRES, NSR and NSB triggers these log messages when they are commited. Example: When the following is committed, the messages could be seen from syslog.
set chassis redundancy graceful-switchover set routing-options nonstop-routing set system commit synchronize
These syslog messages are chassisd traces seen during init time of GRES configuration. They are harmless and can be ignored. They indicate settings of the non-stop-forwarding configuration, which involves enabling other configuration parameters that are required for non-stop-forwarding to work.