Chapter 35 File Manager

“exit” or “!'” must follow sub commands if it is to make the NXC exit sub command mode.

Line 3 in the following example exits sub command mode.

interface ge1 ip address dhcp

!

Lines 1 and 3 in the following example are comments and line 4 exits sub command mode.

!

interface ge1

#this interface is a DHCP client

!

Lines 1 and 2 are comments. Line 5 exits sub command mode.

!this is from Joe

# on 2006/06/05 interface ge1 ip address dhcp

35.2.2Errors in Configuration Files or Shell Scripts

When you apply a configuration file or run a shell script, the NXC processes the file line-by- line. The NXC checks the first line and applies the line if no errors are detected. Then it continues with the next line. If the NXC finds an error, it stops applying the configuration file or shell script and generates a log.

You can change the way a configuration file or shell script is applied. Include setenv stop- on-error off in the configuration file or shell script. The NXC ignores any errors in the configuration file or shell script and applies all of the valid commands. The NXC still generates a log for any errors.

35.2.3 NXC Configuration File Details

You can store multiple configuration files on the NXC. You can also have the NXC use a different configuration file without the NXC restarting.

•When you first receive the NXC, it uses the system-default.confconfiguration file of default settings.

 

225

NXC CLI Reference Guide