Configures the persistent nature of command execution for non-persistent commands.
| persistent | Configures command execution to be persistent. |
| non-persistent | Configures command execution to be not persistent. |
The default mode is non-persistent.
All ExtremeXOS commands can operate in persistent mode, and a subset of the ExtremeXOS command set can operate in non-persistent mode. Commands that are executed in persistent mode become part of the saved switch configuration that persists when the switch is rebooted. Commands that are executed in non-persistent mode configure temporary changes that are not saved in the switch configuration and do not persist when the switch is rebooted.
Most commands operate only in persistent mode. The subset of commands that operate in non-persistent mode are called non-persistent-capable commands. The Universal Port feature uses the non-persistent-capable commands to configure temporary changes that could create security issues if the switch were rebooted or reset. The use of non-persistent-capable commands in scripts and Universal Port profiles allows you to make temporary configuration changes without affecting the default configuration the next time the switch is started.
The configure cli mode command affects only the non-persistent-capable commands, which are listed in the Universal Port chapter in the Switch Engine v33.1.1 User Guide . By default, all commands operate in persistent mode with the following exceptions:
You can use the configure cli mode persistent command and the configure cli mode non-persistent command to change the mode of operation for non-persistent-capable commands multiple times within a script, profile, or configuration session.
The following example sets command execution to be persistent:
configure cli mode persistent
This command was first available in ExtremeXOS 11.6.
This command is available on all Universal switches supported in this document.