[Top] [Prev] [Next] [Contents] [Index]

Configuring the Apply Command

The configuration language apply command:

The apply command can be used in interactive configuration through a TELNET connection and in configuration files, although in configuration files the apply command is automatic at end-of-file. When the user clicks on the Apply button in Change Setup Parameters, Change Quick Setup, or Change User Preferences, an apply command is executed.

The extent of the information applied to the current configuration, and written to NVRAM and the default file is configurable. By default, the information written consists of the user changes. User changes are the current contents of the .stp file (if any), plus any changes made during the session through a TELNET connection or Change Setup Parameters, Change Quick Setup, or Change User Preferences.

The following sections explain how to change the auto-save defaults.

Protocols for Auto-Save

If you are using TFTP for auto-save, the file must already exist before you write to it and must be world-writable. You can create such a file by using the touch(1) utility.

If you are using NFS for auto-save, the directory in which the file is saved should have world-write permission. The auto-save file itself generally is owned by nobody; that is, the terminal's default identity.

Configuring Auto-Save to NVRAM

By default, changes are written to NVRAM after an apply command. To prevent changes from being written to NVRAM when you use the apply command, set the config-auto-save-nvram parameter to "false" (Setup -> Change Setup Parameters -> Configuration [Configuration Daemon section] -> Auto Save NVRAM).

Table 6-15 config-auto-save-nvram Parameter
Possible Values
Results
default true
true Changes made to parameters that are saved in NVRAM are written to NVRAM after an apply command.
false Changes made to parameters that are saved in NVRAM are not written to NVRAM after an apply command.

The Remote Configuration Parameter Quick Reference shows which parameters can be saved to NVRAM.

Configuring Auto-Save to a File

The following subsections explain how to disable auto-save to a file, change the name of the auto-save file, and change the extent of the data saved to the file.

Disabling Auto-Save

By default, changes are written to the .stp file or another specified file after an apply command. To prevent changes from being written to a file when you use the apply command, set the config-auto-save-file parameter to "false" (Setup -> Change Setup Parameters -> Configuration [Configuration Daemon Section] -> Auto Save File).

Table 6-16 config-auto-save-file Parameter
Possible Values
Result
default true
true Any changes made to the terminal's configuration are saved automatically to a file after an apply command.
false No changes made to the terminal's configuration are saved automatically to a file after an apply command.

Changing the Name of the Auto-Save File

The config-auto-save-file-name parameter controls the file to which changes are written. You can specify a different filename from the default (the name of the configuration file loaded plus the .stp extension).

The file is written to the default directory for configuration files. To change the default directory, follow the directions in "Specifying a Different Configuration File Directory".

The file must be accessible through the file service table.

To change the name of the auto-save file, specify the filename in the config-auto-save-file-name parameter (Setup -> Change Setup Parameters -> Configuration [Configuration Daemon Section] -> Auto Save File Name).

Table 6-17 config-auto-save-file-name Parameter
Possible Values
Result
default The file named for the initial configuration file downloaded by the terminal plus the .stp filename extension.
filename Filename or pathname to which configuration data should be written.

Specifying the Data to Save

The config-auto-saved-info parameter controls the extent of the information to save (Setup -> Change Setup Parameters -> Configuration [Configuration Daemon Section] -> Auto Saved Info).

Table 6-18 config-auto-saved-info Parameter
Possible Values
Result
default user-changes
user-changes Changes made to the terminal's default configuration by using Change Setup Parameters, Change Quick Setup, Change User Preferences or a TELNET connection (including the current contents of the auto-save file, if any) are written to the auto-save file.
all-changes All changes made to the terminal's default configuration (including the current contents of the auto-save file and the initial configuration file downloaded by the terminal) are written to the auto-save file.
all-info All read/write configuration parameters are written to the auto-save file.



[Top] [Prev] [Next] [Contents] [Index]

Send comments, suggestions, or questions about this document to the NCD Technical Publications Department by Internet e-mail. Write to us at techpubs@ncd.com.
Copyright © 1997, NCD Inc. All rights reserved.