Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Understanding Configuration Synchronization in a Junos Fusion

All configuration and management for a Junos Fusion are done from the aggregation devices. which run Junos OS software.

In a Junos Fusion with one aggregation device, all configuration—whether it’s a configuration statement that enables a feature globally or enables a feature on a specific extended port—is done from the lone aggregation device.

A Junos Fusion with multiple aggregation devices often requires that the configuration of a feature—for example, an extended port, and entities such as routing instances and VLANs that include the extended port—must match on all aggregation devices. If a configuration statement for the feature—in this case, the extended port—is specified differently on one aggregation device, the statement on that particular aggregation device might be implemented in an unpredictable manner or might not be implemented at all.

Junos Fusion supports configuration synchronization, a feature that allows users to specify configuration statements within a group on one aggregation device and then share that group with other aggregation devices.

We strongly recommend using configuration synchronization to configure software features in multiple aggregation device topologies. Configuration synchronization ensures configuration consistency by sharing the exact same configuration between aggregation devices. Configuration synchronization also simplifies administration of a Junos Fusion by allowing users to enter configuration statements once in a configuration group and apply the configuration group to all aggregation devices rather than repeating a configuration procedure manually on each aggregation device.

For more information about configuration synchronization, see Enabling Configuration Synchronization Between Aggregation Devices in a Junos Fusion, Understanding MC-LAG Configuration Synchronization, and Synchronizing and Committing MC-LAG Configurations.

See Enabling Junos Fusion Enterprise on an Enterprise Campus Network for a sample Junos Fusion Enterprise topology configured largely using configuration synchronization.