2.5.2 - Force10 Networks

Applying a configuration script on a machine with certain previously configured features may result in an
error. This is because the syntax for entering the configuration mode that allows for editing the feature may
be different than the syntax that exists in the configuration (and was used to create the feature initially).
There are several such features.
For example, the command to create a class-map called “cm-1” is class-map match-all cm-1, while the
command to edit cm-1 later is class-map cm-1 (For more on class-map, see Using Differentiated Services
(DiffServ) on page 185.) Attempting to apply an unmodified config script containing cm-1 to a machine
that already has a class-map called cm-1 results in an error similar to the following example (see Figure 37
on page 73).
class-map match-all cm-1
This Diffserv class already exists.
Error in configuration script file at line number 33.
CLI Command :: class-map match-all cm-1.
Aborting script.
Execution of configuration script 'test.scr' could not be completed.
WARNING:
The running configuration may not be the desired configuration.
You might want to reload the saved configuration.
Figure 37 Example of a Scripting Error
Failure to apply a config script can be resolved by one of the following solutions:
• Issue the clear config command before applying the script.
Note: Do not issue the clear config command if you telnet into the system, otherwise you
will lose contact with the system. This command should be issued at the console port.
• Edit the script to use the proper syntax to edit the structure (ACL, map etc.).
• Edit the script by adding the no form of a command to delete a feature, then add a command to
reconfigure the same feature.
SFTOS Configuration Guide, Version 2.5.2.0 73