Configuration changed on standby member-juniper-junos
Generally, making configuration changes to the standby member of a device is not recommended. indeni will trigger an issue if this happens.
Make the configuration changes to the active member of the cluster.
|||1. The chassis cluster synchronization feature automatically synchronizes the configuration from the primary node to the secondary node when the secondary joins the primary as a cluster.
|2. Review the following article on Juniper tech support site: Understanding Automatic Chassis Cluster Synchronization Between Primary and Secondary Nodes
How does this work?
This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the “show chassis cluster status” command. The output includes the status of all redundancy groups across the cluster.
Why is this important?
Tracking the state of a cluster member is important. If a cluster member which used to be the active member of the cluster no longer is, it may be the result of an issue. In some cases, it is due to maintenance work (and so was anticipated), but in others it may be due to a failure in the firewall or another component in the network.
Without Indeni how would you find this?
The administrator has to run the “show chassis cluster status” on the device to find whether the cluster member is active or not.
Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/parsers/src/juniper/junos/awk/show-chassis-cluster-status.ind
Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/parsers/src/juniper/srx/awk/show-chassis-cluster-information-configuration-synchronization.ind
Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/sync_core_rules/ConfigChangeOnStandbyMemberRule.scala