Device Configuration Commits

Routing Director serves as the management and orchestration layer for the network. Whenever a user creates, modifies, or removes a network service, interface, protocol, policy, or system setting through the GUI, Routing Director translates the requested intent into device-specific Junos configuration and performs a configuration commit on the targeted device or devices. As a result, every operational change made through the GUI is reflected as one or more Junos configuration commands.

This appendix documents the Junos configuration changes generated and committed by Routing Director on managed Junos devices during device onboarding and the creation of a Network Implementation Plan. The purpose of this appendix is to provide a clear mapping between these Routing Director workflows and the corresponding Junos configuration commands that are automatically applied to the managed devices.

During the onboarding process and network implementation plan creation, Routing Director generates and commits the configuration required to integrate devices into the managed network environment and prepare them for the intended network design. As part of these workflows, Routing Director translates user-defined parameters and design inputs into device-specific Junos configuration and performs the necessary configuration commits on the target devices. As a result, each onboarding and network implementation plan-related operation is reflected as one or more Junos configuration commands on the managed devices.

The sections that follow describe the configuration transactions generated during these workflows. For each supported use case, this appendix identifies:

• The onboarding or network implementation plan creation operation performed within the GUI.
• The Junos configuration hierarchy affected by the operation.
• The corresponding Junos CLI commands committed to the device.
• Any prerequisites, dependencies, or workflow-specific considerations.
• Configuration variables that are dynamically populated based on user input, device information, and network design parameters.

Variable values are shown using placeholders to illustrate the generalized configuration model used by Routing Director. Actual committed values depend on the specific device, topology, onboarding parameters, and network implementation plan configuration defined at deployment time.

Use this content to simplify operational troubleshooting, validate intended device configuration, and correlate workflow actions with the resulting Junos commits recorded on managed devices. The content is organized according to the corresponding onboarding and network implementation plan creation use cases.