Edit Pristine Config

Modifying pristine config is a local operation, and does not lead to a change to the running device configuration. Changes are applied on the next full config push. If you want to apply persistent changes to a configuration, use configlets.

CAUTION:

Manual modifications to the Pristine Config are not validated. Mistakes can lead to full erasure of the device, potentially causing a service-impacting outage. Never modify the pristine config directly unless there is no alternative. For assistance, contact Juniper Support.
  1. From the left navigation menu, navigate to Devices > Managed Devices and click the Management IP of the device to Update.
    HPE Apstra interface showing the Managed Devices section under Devices menu, listing device details including Management IP, Device Key, Device Profile, Hostname, OS version, State, Communication status, Acknowledged status, Blueprint, Type, and Agent Profile. Options for creating Onbox or Offbox agents and advanced settings are visible along with navigation to sections like Blueprints, System Agents, ZTP Status, and Device Profiles.
    The Device details page for the selection appears.
  2. Click the Pristine Config tab (top), then click the Edit pristine config button (under committed_configuration on the left).
    Configuration interface with tabs Device, Agent, Pristine Config, and Telemetry; Pristine Config is selected. Panel shows pre-Apstra config message. Code block includes version 21.4R3.15 and root authentication details. Buttons Revert to Pristine and Update From Device are visible.
  3. Make your changes to the configuration. (For information about what should and should not be included in pristine configurations, see Create Onbox Agent and Create Offbox Agent, as applicable.)
    Update Config interface with warning about manual changes, info on device update delay, config code for version 21.4R3.15, and action buttons.
  4. If the device is deployed, and you absolutely need to change pristine config, you can force the update without undeploying first. Never use this option unless you are otherwise directed by the Juniper support team. This update has the power to impact your entire network. To proceed, check the Force Update check box.
    Configuration update interface with warnings about using Force Update under supervision and risks of manual modifications. Includes committed_configuration section with version info and encrypted passwords. Features Force Update checkbox and Update button.
  5. Click Update to apply the changes.