This KB explains the configuration synchronization behavior between a Junos device and Mist when configuration changes are made directly from the device CLI or remote shell.

Configuration is modified directly from the device CLI or remote shell.

The Junos device accepts and commits the configuration successfully.

The configuration change is not reflected in Mist.

The local configuration may be removed or affected by a subsequent Mist configuration push, depending on the Mist configuration-management settings.

Q: If I make a configuration change directly from the device CLI, will it synchronize back to Mist?

A: No.

Changes made directly from the Junos device CLI are local device changes and are not synchronized back to Mist.

Q: Does the same apply to changes made through the remote shell?

A: Yes.

Changes made through the remote shell are also local device changes and do not synchronize back to Mist.

Q: Why does the device allow the configuration to be committed?

A: Junos can independently accept and commit local configuration changes. A successful commit confirms that the configuration was committed locally on the device; it does not mean that Mist has learned or stored the change.

Q: Can Mist remove a local CLI change?

A: Yes, when "Synchronize configuration" is clicked or when a configuration change is made on MIST, it will always override the config done on CLI/remote shell.

Q: How should persistent configuration changes be made?

A: Configure persistent changes through the appropriate Mist configuration mechanism:

• Mist UI – for configuration supported by the UI.
• Mist Template – for centrally managed configuration.
• Additional CLI – for supported Junos configuration that is not available through the Mist UI. Juniper documents Additional CLI as the mechanism for configuring settings that are not available through the template GUI.

Important Note

Changes made directly on the device through CLI or remote shell do not sync back to Mist.

If a configuration change needs to be managed and retained by Mist, configure it through the Mist UI, Template, or Additional CLI as applicable.