Queued Commands
CLI commands that specify changes to the current configuration will either be committed to the
configuration file as soon as they are entered, or queued to be committed using the
commit
,
exit
, or
<ctrl-d>
commands.
l
If a
complete
command is executed for an object in a lower context, the command is com-
mitted to the configuration immediately. The current command context is not changed after
the command is entered. A “complete” command is one that specifies all parameters
required to add or modify the object.
For example, entering the following command to create a server creates the server immediately,
and leaves eqcli in the global context:
eqcli >
server sv01 proto tcp ip 192.168.0.210 port 80
eqcli >
l
If an
incomplete
command is executed for an object in a lower context, the command is
queued to be committed to the configuration until a
commit
,
exit
, or
<ctrl-d>
command is
entered. The current command context changes to the context of the object argument of the
incomplete command. An “incomplete" command is one does not include one or more para-
meters required to add or modify the object.
For example, if the server
sv01
does not exist, entering the following
server
command in the global
context queues the command and leaves eqcli in the relevant context; an explicit
commit
is needed
to create the server:
eqcli >
server sv01 proto tcp ip 192.168.0.210 port 80
eqcli sv-sv01>
commit
eqcli sv-sv01>
l
If a command is entered that affects only the object associated with the current context, the
command is queued to be committed to the configuration until a
commit
,
exit
, or
<ctrl-d>
com-
mand is entered. The current command context does not change.
For example, if
sv01
exists and the current context is “
sv-sv01
”, then the following commands are
queued until a
commit
,
exit
, or
<ctrl-d>
command is entered:
eqcli >
server sv01
eqcli sv-sv01>
ip 192.168.0.211
eqcli sv-sv01>
port 8080
eqcli sv-sv01>
commit
Queued commands can be committed or discarded using the following commands:
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
All Rights Reserved.
153
Equalizer Administration Guide
Summary of Contents for Equalizer GX Series
Page 18: ......
Page 32: ...Overview 32 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 42: ......
Page 52: ......
Page 64: ......
Page 72: ......
Page 76: ......
Page 228: ......
Page 238: ......
Page 476: ......
Page 492: ......
Page 530: ......
Page 614: ......
Page 626: ......
Page 638: ......
Page 678: ......
Page 732: ...Using SNMP Traps 732 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 754: ......
Page 790: ......
Page 804: ......
Page 842: ......
Page 866: ......