Summary

Add a built-in command to show configuration differences between nodes that participate in configuration synchronization (e.g., primary/backup peers). This enables operators to compare configs across nodes before applying or syncing changes.

Use case

Without an easy cross-node diff, operators risk pushing changes that conflict with settings on a remote peer (e.g., differing interface names, ACL/policy sets, or protocol timers). A native “compare configs across peers” function lets engineers verify intent, detect drift, and avoid outages—similar to what other vendors provide for devices in a single stack/HA pair.

Additional information

That could be something like show config-sync diff peer <peer-name> [path <config-node>] [running|candidate|saved]