Config Commands

nv config apply

Applies the current pending configuration. This command does not save the configuration; the configuration does not persist after a reboot. To save the startup configuration automatically when you run nv config apply without having to run the nv config save command, run the nv set system config auto-save enable on command, described in the System Configuration section of the Set and Unset commands.

You can specify the following options with the nv config apply command:

• --y or --assume-yes automatically replies yes to all prompts.
• --assume-no automatically replies no to all prompts.
• --confirm applies the configuration change but you must confirm the applied configuration. If you do not confirm within ten minutes, the configuration rolls back automatically. You can change the default time with the apply --confirm <time> command. For example, nv config apply --confirm 60 requires you to confirm within one hour.
• --confirm-status shows the amount of time left before the automatic rollback.

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config apply --y

nv config apply <revision>

Applies a specific configuration revision. This command does not save the configuration; the configuration does not persist after a reboot. You can specify the following options with this command:

• --y or --assume-yes automatically replies yes to all prompts.
• --assume-no automatically replies no to all prompts.
• --confirm applies the configuration change but you must confirm the applied configuration. If you do not confirm within ten minutes, the configuration rolls back automatically. You can change the default time with the apply --confirm <time> command. For example, nv config apply --confirm 60 requires you to confirm within one hour.
• --confirm-status shows the amount of time left before the automatic rollback.

Command Syntax

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config apply 5 --y

nv config save

Overwrites the startup configuration with the applied configuration by writing to the /etc/nvue.d/startup.yaml file. The configuration persists after a reboot.

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config save

nv config replace <nvue-file>

Replaces the pending configuration with the specified YAML configuration file.

Command Syntax

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config replace myconfig.yaml

nv config detach

Detaches the configuration from the current pending configuration. When you run this command, NVUE discards all configuration changes between the last nv config apply command and the nv config detach command.”

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config detach

nv config diff <revision-base> <revision-target>

Shows differences between configurations, such as the startup configuration and the applied configuration, or the applied configuration and a specific configuration revision.

Command Syntax

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config diff 1 2

nv config show

Shows the currently applied configuration in YAML format.

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config show

nv config patch <nvue-file>

Updates the pending configuration with an NVUE configuration file in YAML format.

Command Syntax

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config patch myconfig.yaml

nv config history

Shows the apply history for the current configuration revision.

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config history

nv config history <revision>

Shows the apply history for a specific configuration revision.

Command Syntax

Version History

Introduced in Cumulus Linux 5.0.0

Example

cumulus@switch:~$ nv config history 5