Unsupported Configuration Statements in the Ephemeral Configuration Database
The ephemeral database is an alternate configuration database. Juniper Extension Toolkit (JET) applications and NETCONF and Junos XML protocol client applications can simultaneously load and commit configuration changes to the ephemeral database with significantly greater throughput than when committing data to the candidate configuration database. To improve commit performance, the ephemeral commit process does not perform all of the operations and validations executed by the standard commit model. As a result, you cannot configure some features through the ephemeral database. For example, the ephemeral configuration database does not support configuring interface alias names.
Use Feature Explorer to confirm platform and release support for specific features.
Review the Platform-Specific Ephemeral Database Behavior section for notes related to your platform.
The ephemeral configuration database does not support the following configuration statements. We've grouped the statements under their top-level configuration statement hierarchy. If a client attempts to configure an unsupported statement in an ephemeral instance, the server returns an error during the load operation.
[edit]
[edit apply-groups] [edit access] [edit chassis] [edit dynamic-profiles] [edit security] (SRX Series only)
[edit interfaces]
[edit interfaces interface-name unit logical-unit-number alias alias-name] [edit interfaces interface-range]
[edit logical-systems]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number alias alias-name] [edit logical-systems logical-system-name policy-options prefix-list name apply-path path] [edit logical-systems logical-system-name system processes routing]
Starting in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.4R1, you can configure MSTP, RSTP, and VSTP in the ephemeral configuration database on supported platforms.
[edit policy-options]
[edit policy-options prefix-list name apply-path path]
[edit protocols]
[edit protocols igmp] [edit protocols mld]
Starting in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.4R1, you can configure MSTP, RSTP, and VSTP in the ephemeral configuration database on supported platforms.
[edit routing-instances]
Starting in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.4R1, you can configure MSTP, RSTP, and VSTP in the ephemeral configuration database on supported platforms.
[edit security]
[edit security group-vpn member ipsec vpn] [edit security ssh-known-hosts host hostname]
[edit services]
[edit services ssl initiation profile] [edit services ssl proxy profile] [edit services ssl termination profile]
[edit system]
[edit system archival] [edit system commit delta-export] [edit system commit fast-synchronize] [edit system commit notification] [edit system commit peers] [edit system commit peers-synchronize] [edit system commit persist-groups-inheritance] [edit system commit server] [edit system compress-configuration-files] [edit system configuration-database] [edit system extensions] [edit system fips] [edit system host-name] [edit system license] [edit system login] [edit system master-password] [edit system max-configurations-on-flash] [edit system radius-options] [edit system regex-additive-logic] [edit system scripts] [edit system services extension-service notification allow-clients address] [edit system time-zone]
Platform-Specific Ephemeral Database Behavior
Use Feature Explorer to confirm platform and release support for specific features.
Use the following table to review platform-specific behaviors for your platforms.
|
Platform |
Difference |
|---|---|
|
SRX Series |
|
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.
ephemeral-db-support statement at
the [edit protocols layer2-control]
hierarchy level in the static configuration
database.ephemeral-db-support statement at
the [edit protocols layer2-control]
hierarchy level in the static configuration
database.