Cisco 500 Series, Configuration Manual

Page: 1032 / 1140

C-6
Cisco Security Appliance Command Line Configuration Guide
OL-12172-03
Appendix C Using the Command-Line Interface
Adding Comments
Adding Comments
You can precede a line with a colon ( : ) to create a comment. However, the comment only appears in the
command history buffer and not in the configuration. Therefore, you can view the comment with the
show history command or by pressing an arrow key to retrieve a previous command, but because the
comment is not in the configuration, the write terminal command does not display it.
Text Configuration Files
This section describes how to format a text configuration file that you can download to the security
appliance, and includes the following topics:
•
How Commands Correspond with Lines in the Text File, page C-6
• Command-Specific Configuration Mode Commands, page C-6
•
Automatic Text Entries, page C-7
• Line Order, page C-7
•
Commands Not Included in the Text Configuration, page C-7
• Passwords, page C-7
•
Multiple Security Context Files, page C-7
How Commands Correspond with Lines in the Text File
The text configuration file includes lines that correspond with the commands described in this guide.
In examples, commands are preceded by a CLI prompt. The prompt in the following example is
“hostname(config)#”:
hostname(config)#
context a
In the text configuration file you are not prompted to enter commands, so the prompt is omitted:
context a
Command-Specific Configuration Mode Commands
Command-specific configuration mode commands appear indented under the main command when
entered at the command line. Your text file lines do not need to be indented, as long as the commands
appear directly following the main command. For example, the following unindented text is read the
same as indented text:
interface gigabitethernet0/0
nameif inside
interface gigabitethernet0/1
nameif outside