Open topic with navigation

Using the no Form of a Command

Most commands that create objects and set parameters have a no form that you can use to delete an object or reset a parameter to its default value. The general format of the no command is:

no [keywords] {object|parameter}

The no keyword must be followed by a complete object context that specifies the object to delete or the parameter to reset:

• If the object or parameter is defined in the current context, then you do not need to specify any keywords.
• If the object or parameter is defined in a lower level context, then specify the appropriate contexts before the object or parameter name.

So, for example, type the following to delete cluster cl00:

eqcli > no cluster cl00

For objects and parameters that have lower object contexts (i.e., match rules, server instances, and subnets), you can use the no form at either the global context or in the lower object specific context:

eqcli > no cluster cl00 match ma00

eqcli > cluster cl00

eqcli cl-cl00> no match ma00

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.

Related Topics