
For parameters, the no form requires the complete command used to set the parameter, minus the argument
setting the value. So, for example, to reset the value of the resp (responder) parameter on match rule ma00 in
cluster cl00, you can type any of the following:
eqcli > no cluster cl00 match ma00 resp
eqcli > cluster cl00
eqcli cl-cl00> no match ma00 resp
eqcli > cluster cl00 match ma00
eqcli cl-cl00-ma-ma00> no resp
The operation specified by the no form of a command takes effect immediately, even in explicit commit mode. In
other words, a no command form never needs to be followed by a commit, exit, or <ctrl-d> command; it is
committed to the configuration file immediately.
In all cases, the no form of a command always returns to the current context after completion.
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 committed 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 parameters 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> command is entered. The current
command context does not change.
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
All Rights Reserved.
137
Equalizer Administration Guide
Kommentare zu diesen Handbüchern