- New and Changed Information
- Preface
- A Commands
- Advanced Services Modules Commands
- B Commands
- C Commands
- Caching Services Module Commands
- D Commands
- Debug Commands
- E Commands
- F Commands
- G Commands
- H Commands
- I Commands
- CLI Overview
- J Commands
- K Commands
- L Commands
- M Commands
- N Commands
- O Commands
- P Commands
- Q Commands
- R Commands
- S Commands
- Show Commands
- T Commands
- U Commands
- V Commands
- W Commands
- Z Commands
Cisco MDS 9000 Family Command Reference, Release 5.2(8)
- Updated:
- January 31, 2018
Chapter: E Commands
- egress-sa
- email-contact
- enable
- enable (Call Home configuration submode)
- enable user-server-group
- enable secret
- enable cert-DN-match
- encryption
- end
- enrollment terminal
- errdisable detect cause link-down
- errdisable detect cause bit-errors
- errdisable detect cause credit-loss
- errdisable detect cause link-reset
- errdisable detect cause signal-loss
- errdisable detect cause sync-loss
- errdisable detect cause trustsec-violation
- event cli
- event counter
- event fanabsent
- event fanbad
- event memory
- event module-failure
- event oir
- event policy-default
- event poweroverbudget
- event snmp
- event syslog
- event temperature
- event manager applet
- event manager policy
- event manager environment
- exit
E Commands
The commands in this chapter apply to the Cisco MDS 9000 Family of multilayer directors and fabric switches. All commands are shown here in alphabetical order regardless of command mode. See “About the CLI Command Modes” section to determine the appropriate mode for each command.
egress-sa
To configure the Security Association (SA) to the egress hardware, use the engress-sa command. To delete the SA from the egress hardware, use the no form of the command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to configure the SA to the egress hardware:
Related Commands
|
|
|
|---|---|
Displays FC-SP-related information for a specific interface. |
email-contact
To configure an e-mail contact with the Call Home function, use the email-addr command in Call Home configuration submode. To disable this feature, use the no form of the command.
Syntax Description
Configures an e-mail address. Uses a standard e-mail address that does not have any text size restrictions. |
Defaults
Command Modes
Call Home configuration submode.
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to configure e-mail contact in the Call Home configuration:
Related Commands
|
|
|
|---|---|
Sends a dummy test message to the configured destination(s). |
|
enable
To turn on the privileged commands, use the enable command. To disable this feature, use the disable command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to turn on the privileged commands:
Related Commands
|
|
|
|---|---|
enable (Call Home configuration submode)
To enable the Call Home function, use the enable command in Call Home configuration submode. To disable this feature, use the disable command.
Syntax Description
Defaults
Command Modes
Call Home configuration submode.
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to enable the Call Home function.
Related Commands
|
|
|
|---|---|
Sends a dummy test message to the configured destination(s). |
|
enable user-server-group
To enable or disable group validation, use the enable user-server-group command. To disable this feature, use the no form of the command.
Syntax Description-
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
Related Commands
|
|
|
|---|---|
enable secret
To create secret for privilege escalation, use the enable secret command. To disable this feature, use the no form of the command.
enable secret {0 | 5} [password priv-lvl privilege-level]
no enable secret {0 | 5} [password priv-lvl privilege-level]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to specifiy the secret that follows should be in clear text:
The following example shows how to specify the secret that follows should be encrypted:
Related Commands
|
|
|
|---|---|
enable cert-DN-match
To enable or disable cert DN matching, use the enable cert-DN-match command. To disable this feature, use the no form of the command.
Syntax Description-
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If Cert-DN match is configured, user will be allowed to login only if the user profile lists the subject-DN of the usercertificate as authorized for logging in.
Examples
Related Commands
|
|
|
|---|---|
encryption
To configure an encryption algorithm for an IKE protocol policy, use the encryption command. To revert to the default, use the no form of the command.
encryption { 3des | aes | des }
Syntax Description
Defaults
Command Modes
IKE policy configuration submode.
Command History
|
|
|
Usage Guidelines
To use this command, the IKE protocol must be enabled using the crypto ike enable command.
Examples
The following example shows how to configure the encryption algorithm for the IKE protocol:
Related Commands
|
|
|
|---|---|
end
To exit any of the configuration modes and return to EXEC mode, use the end command in configuration mode.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Examples
The following example shows how to exit from configure mode:
The following example changes the name to george. Entering the end command causes the system to exit configuration mode and return to EXEC mode.
Related Commands
|
|
|
|---|---|
Exits configuration mode, or any of the configuration modes. |
enrollment terminal
To enable manual cut-and-paste certificate enrollment through the switch console, use the enrollment terminal command in trust point configuration submode. To revert to the default certificate enrollment process, use the no form of the command.
Syntax Description
Defaults
The default enrollment method is manual cut-and-paste, which is the only enrollment method that the MDS switch currently supports.
Command Modes
Trust point configuration submode.
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to configure trust point enrollment through the switch console:
The following example shows how to discard a trust point enrollment through the switch console:
Related Commands
|
|
|
|---|---|
errdisable detect cause link-down
To error-disable and bring down a port on a link failure, use the errdisable detect cause link-down command. To disable this feature, use the no form of the command.
errdisable detect cause link-down num-times {flaps number} duration{sec}
no errdisable detect cause link-down num-times {flaps number} duration{sec}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The port guard feature is used in the environments where the system and application does not adapt quickly and efficiently to a port going down and back up or to a port rapidly cycling up and down which can happen in some failure modes. For example, if the port is going up and down once a second, and the system takes five seconds to stabilize after the port goes down, this situation might cause a more severe failure in the fabric.
The port guard feature gives the SAN administrator the ability to prevent this issue from occuring in environments that are vulnerable to these problems. The port can be configured to stay down after the first failure, or after a specified number of failures in a specified time period. This allows the SAN administartaion to intervene and control the recovery and avoiding any problems caused by the cycling.
Examples
The following example shows how to configure the port as down when the link flaps once:
The following example shows how to configure the port as down when the link flaps 5 times in 30 seconds:
The following example shows how to remove the port guard feature on the interface:
Related Commands
|
|
|
|---|---|
errdisable detect cause bit-errors
To enable error-disable detection on bit errors, use the errdisable detect cause bit-errors command. To disable this feature, use the no form of the command.
errdisable detect cause bit-errors num-times {flaps number} duration {sec}
no errdisable detect cause bit-errors num-times {flaps number} duration {sec}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The port guard feature is used in the environments where the system and application does not adapt quickly and efficiently to a port going down and back up or to a port rapidly cycling up and down which can happen in some failure modes. For example, if the port is going up and down once a second, and the system takes five seconds to stabilize after the port goes down, this situation might cause a more severe failure in the fabric.
The port guard feature gives the SAN administrator the ability to prevent this issue from occuring in environments that are vulnerable to these problems. The port can be configured to stay down after the first failure, or after a specified number of failures in a specified time period. This allows the SAN administartaion to intervene and control the recovery and avoiding any problems caused by the cycling.
Examples
The following example shows how to enable error-disable detection on bit errors:
Related Commands
|
|
|
|---|---|
errdisable detect cause credit-loss
To enable error-disable detection on a credit loss, use the errdisable detect cause credit-loss command. To disable this feature, use the no form of the command.
errdisable detect cause credit-loss num-times {flaps number} duration {sec}
no errdisable detect cause credit-loss num-times {flaps number} duration {sec}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The port guard feature is used in the environments where the system and application does not adapt quickly and efficiently to a port going down and back up or to a port rapidly cycling up and down which can happen in some failure modes. For example, if the port is going up and down once a second, and the system takes five seconds to stabilize after the port goes down, this situation might cause a more severe failure in the fabric.
The port guard feature gives the SAN administrator the ability to prevent this issue from occuring in environments that are vulnerable to these problems. The port can be configured to stay down after the first failure, or after a specified number of failures in a specified time period. This allows the SAN administartaion to intervene and control the recovery and avoiding any problems caused by the cycling.
Examples
The following example shows how to enable error-disable detection on a credit loss:
Related Commands
|
|
|
|---|---|
errdisable detect cause link-reset
To enable error-disable detection on a link reset, use the errdisable detect cause link-reset command. To disable this feature, use the no form of the command.
errdisable detect cause link-reset num-times {number} duration {sec}
no errdisable detect cause link-reset num-times {number} duration {sec}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The port guard feature is used in the environments where the system and application does not adapt quickly and efficiently to a port going down and back up or to a port rapidly cycling up and down which can happen in some failure modes. For example, if the port is going up and down once a second, and the system takes five seconds to stabilize after the port goes down, this situation might cause a more severe failure in the fabric.
The port guard feature gives the SAN administrator the ability to prevent this issue from occuring in environments that are vulnerable to these problems. The port can be configured to stay down after the first failure, or after a specified number of failures in a specified time period. This allows the SAN administartaion to intervene and control the recovery and avoiding any problems caused by the cycling.
Examples
The following example shows how to enable error-disable detection on a link reset:
Related Commands
|
|
|
|---|---|
errdisable detect cause signal-loss
To enable error-disable detection on a signal loss, use the errdiable detect cause signal-loss command. To disable this feature, use the no form of the command.
errdisable detect cause signal-loss num-times {number} duration {sec}]
no errdisable detect cause signal-loss num-times {number} duration {sec}]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The port guard feature is used in the environments where the system and application does not adapt quickly and efficiently to a port going down and back up or to a port rapidly cycling up and down which can happen in some failure modes. For example, if the port is going up and down once a second, and the system takes five seconds to stabilize after the port goes down, this situation might cause a more severe failure in the fabric.
The port guard feature gives the SAN administrator the ability to prevent this issue from occuring in environments that are vulnerable to these problems. The port can be configured to stay down after the first failure, or after a specified number of failures in a specified time period. This allows the SAN administartaion to intervene and control the recovery and avoiding any problems caused by the cycling.
Examples
The following example shows how to enable error-disable on a signal loss:
Related Commands
|
|
|
|---|---|
errdisable detect cause sync-loss
To enable error-disable detection on a sync loss, use the errdisable detect cause sync-loss command. To disable this feature, use the no form of the command.
errdisable detect cause sync-loss num-times {number} duration {sec}
no errdisable detect cause sync-loss num-times {number} duration {sec}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The port guard feature is used in the environments where the system and application does not adapt quickly and efficiently to a port going down and back up or to a port rapidly cycling up and down which can happen in some failure modes. For example, if the port is going up and down once a second, and the system takes five seconds to stabilize after the port goes down, this situation might cause a more severe failure in the fabric.
The port guard feature gives the SAN administrator the ability to prevent this issue from occuring in environments that are vulnerable to these problems. The port can be configured to stay down after the first failure, or after a specified number of failures in a specified time period. This allows the SAN administartaion to intervene and control the recovery and avoiding any problems caused by the cycling.
Examples
The following example shows how to enable error-disable detection on a syncronised loss:
Related Commands
|
|
|
|---|---|
errdisable detect cause trustsec-violation
To enable error-disable detection on a trustsec violation, use the errdisable detect cause trustsec-violation command. To disable this feature, use the no form of the command.
errdisable detect cause trustsec-violation num-times {number} duration {sec}
no errdisable detect cause trustsec-violation num-times {number} duration {sec}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The port guard feature is used in the environments where the system and application does not adapt quickly and efficiently to a port going down and back up or to a port rapidly cycling up and down which can happen in some failure modes. For example, if the port is going up and down once a second, and the system takes five seconds to stabilize after the port goes down, this situation might cause a more severe failure in the fabric.
The port guard feature gives the SAN administrator the ability to prevent this issue from occuring in environments that are vulnerable to these problems. The port can be configured to stay down after the first failure, or after a specified number of failures in a specified time period. This allows the SAN administartaion to intervene and control the recovery and avoiding any problems caused by the cycling.
Examples
The following example shows how to enable error-disable detection on a trustsec violation:
Related Commands
|
|
|
|---|---|
event cli
To configure a CLI command as an EEM applet trigger, use the event cli command. To delete the applet trigger, use the no form of the command.
event cli match expression [ count countnum [ time seconds ]]
no event cli match expression [ count countnum [ time seconds ]]
Syntax Description
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
A cli event trigger allows control over CLI commands. By default, the triggering command is not executed. This allows an applet to take action before or after a command runs, or even prevent it from running. To run the triggering command, configure an event-default action at the stage in the applet where the command should run.
Examples
The following example shows how to match the shutdown command as an applet trigger:
The following example shows how to use spaces and regular expressions. Action 10 logs a syslog message and action 20 allows the matching command to complete normally.
Related Commands
|
|
|
|---|---|
event counter
To configure a counter as an EEM applet trigger, use the event counter command. To delete the applet trigger, use the no form of the command.
event counter name name entry-val value entry-op operator [ exit-val value exit-op operator ]
no event counter name name entry-val value entry-op operator [ exit-val value exit-op operator ]
Syntax Description
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to trigger an EEM applet when a counter named 'test' has a value of 0:
Related Commands
|
|
|
|---|---|
event fanabsent
To configure a fan absence as an EEM applet trigger, use the event fanabsent command. To delete the applet trigger, use the no form of the command.
fanabsent [ fan fannumber ] time seconds
no fanabsent [ fan fannumber ] time seconds
Syntax Description
(Optional) Configures a chassis fan. |
|
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
This event specification monitors if a fan is removed from the chassis for a particular period of time. Embedded Event Manager takes an action based on the actions configured on the applet.
Examples
This example shows how to configure a an EEM applet to trigger after a fan absence of 300 seconds (5 minutes):
Related Commands
|
|
|
|---|---|
event fanbad
To configure fanbad event specification, use the event fanbad command. To remove the fanbad event, use the no form of the command.
event fanbad [ fan fannumber ] time seconds
no event fanbad [ fan fannumber ] time seconds
Syntax Description
(Optional) Configures a chassis fan. |
|
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
This event specification monitors for the failure of any chassis cooling fan and Embedded Event Manager takes an action based on the actions configured on the applet.
Examples
This example shows how to configure an EEM applet to trigger after a fan failure of 10 seconds:
Related Commands
|
|
|
|---|---|
event memory
To configure memory thresholds event specification, use the event memory command. To remove the memory threshold event, use the no form of the command.
event memory { minor | severe | critical }
no event memory { minor | severe | critical }
Syntax Description
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
The event specification monitors the memory threshold specified in the applet and Embedded Event Manager takes an action based on the actions configured on the applet.
Examples
This example shows how to configure memory threshold event specification:
Related Commands
|
|
|
|---|---|
event module-failure
To create a module failure event specification, use the event module-failure command. To remove the module failure event, use the no form of the command.
event module-failure type failure-type module { all | slot } count count [ time seconds ]
no event module-failure type failure-type module { all | slot } count count [ time seconds ]
Syntax Description
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to configure a module failure event specification:
Related Commands
|
|
|
|---|---|
event oir
To configure an Online Insertion Removal event specification, use the event oir command. To remove the Online Insertion Removal event, use the no form of the command.
event oir { fan | module | powersupply } { insert | remove | anyoir } [ number ]
no event oir { fan | module | powersupply } { insert | remove | anyoir } [ number ]
Syntax Description
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
This event specification monitors whenever there is insertion or removal of the following components: fan, module, and power supply. Embedded Event Manager takes an action based on the actions configured on the applet.
Examples
This example shows how to configure the Online Insertion Removal event specification:
Related Commands
|
|
|
|---|---|
event policy-default
To configure the event specification when the system policy is overridden, use the event policy-default command. To remove the configuration, use the no form of the command.
event policy-default count count [ time seconds ]
no event policy-default count count [ time seconds ]
Syntax Description
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
ExamplesNone.
This example shows how to configure an event configuration when the system policy is overridden:
Related Commands
|
|
|
|---|---|
event poweroverbudget
The power over-budget policy gets triggered when the available power capacity drops below zero and the device is no longer able to keep the previously powered-up modules in the powered-up state. The default action is to print a syslog to notify the user of the occurrence of power over budget. To change the power over budget behavior, use the event poweroverbudget command. You must override the default system policy __pfm_power_over_budget with a new policy to do this. To remove the power over-budget event specification, use the no form of the command.
Syntax Description
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to shut down modules starting from module 1 when the available power drops below zero:
Related Commands
|
|
|
|---|---|
event snmp
To configure an SNMP event, use the event snmp command. To remove the SNMP event, use the no form of the command.
event snmp oid oid get-type { exact | next } entry-op { gt | ge | eq | ne | lt | le } entry-val value [{ exit-comb { or | and } exit-op { gt | ge | eq | ne | lt | le } exit-val value exit-time time } | { exit-op { gt | ge | eq | ne | lt | le } exit-val value }] poll-interval time
no event snmp oid oid get-type { exact | next } entry-op { gt | ge | eq | ne | lt | le } entry-val value [{ exit-comb { or | and } exit-op { gt | ge | eq | ne | lt | le } exit-val value exit-time time } | { exit-op { gt | ge | eq | ne | lt | le } exit-val value }] poll-interval time
Syntax Description
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
An Embedded Event Manager event is triggered when one of the fields specified by an SNMP object ID crosses a defined threshold. If multiple conditions exist, the SNMP event is triggered when all the conditions are met.
Exit criteria are optional. If exit criteria are not specified, event monitoring will be re-enabled immediately. If exit criteria are specified on the basis of values or time periods, the event monitoring is not re-enabled until the criteria are met.
When the entry-op keyword is used and there is a match, an event is triggered and event monitoring is disabled until the exit criteria are met.
When the exit-op keyword is used and there is a match, an event is triggered and event monitoring is re-enabled.
The entry-type keyword triggers one of the following actions:
- If the value keyword is specified, the entry-value is an actual value and an SNMP event is raised whenever the absolute value occurs.
- If the increment keyword is specified, the entry-value is an increment and an SNMP event is raised whenever the incremental value is reached.
- If the rate keyword is specified, the entry-value is a rate of change and an SNMP event is raised whenever the rate of change value is reached.
When the optional exit-type keyword is used, the following conditions occur:
- If the value keyword is specified, the exit value is an actual value and the event monitoring is re-enabled whenever the absolute value occurs. This is the default.
- If the increment keyword is specified, the exit value is an increment and the event monitoring is re-enabled whenever the incremental value is reached.
- If the rate keyword is specified, the exit value is a rate of change and the event monitoring is re-enabled whenever the rate of change value is reached.
Examples
The following example shows how to monitor the CPU free memory OID and log a corresponding syslog:
Related Commands
|
|
|
|---|---|
event syslog
To specify event criteria for an Embeded Event Manager applet that is run by matching syslog messages, use the event syslog command in the applet configuration mode. To remove the syslog message event criteria, use the no form of the command.
event syslog [ occurs count ] [ period interval ] [ priority [ 0-7 | alerts | critical | debugging | emergencies | errors | informational | notifications | warnings ]] pattern expression
no event syslog [ occurs count ] [ period interval ] [ priority [ 0-7 | alerts | critical | debugging | emergencies | errors | informational | notifications | warnings ]] pattern expression
Syntax Description
Defaults
If the occurs parameter is not specified, the default value of 1 is used.
If the period parameter is not specified, the default value of 0 is used.
If the priority parameter is not specified, the default value of informational is used.
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
The syslog and Embedded Event Manager client processes run on each supervisor module in a system. Therefore, in dual supervisor systems, an event syslog command will be matched on both the active and standby supervisors. Both Embedded Event Manager clients will notify the Embedded Event Manager master process on the active supervisor causing the applet to be triggered twice. Be sure to take this potential double triggering in to account in the applet.
Examples
This example shows how to configure an applet to trigger after 10 "authentication failed" syslog events:
This example shows how to configure an applet to tag module power up and standby online syslog events:
Related Commands
|
|
|
|---|---|
Configures a syslog message to generate when an EEM applet is triggered. |
|
event temperature
To specify an event criteria for an Embedded Event Manager (EEM) applet that is run on the basis of a temperature event, use the event temperature command in the applet configuration mode. To remove the temperature event criteria, use the no form of the command.
event temperature [ module slot ] [ sensor number ] threshold { major | minor | any }
no event temperature [ module slot ] [ sensor number ] threshold { major | minor | any }
Syntax Description
Defaults
Command Modes
EEM applet configuration (config-applet).
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows the default system major temperature EEM policy and only performs the default action for a major temperature alert for sensor #8 only.
Related Commands
|
|
|
|---|---|
event manager applet
To register an applet with the Embedded Event Manager (EEM) and to enter applet configuration mode, use the event manager applet command.
event manager applet applet-name
Syntax Description
The applet name can be any case-sensitive alphanumeric string up to 29 characters. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to register an applet with EEM and to enter applet configuration mode:
Related Commands
|
|
|
|---|---|
event manager policy
To register and activate an Embeded Event Manager policy (EEM) script policy, use the event manager policy command.
event manager policy policy-script
no event manager policy policy-script
Syntax Description
Specifies the EEM policy script. This name becomes the name of the EEM policy. The maximum size is 29 characters. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The EEM schedules and runs policies on the basis of an event specification that is contained within the policy itself. When the event manager policy command is invoked, the EEM examines the policy and registers it to be run when the specified event occurs.
Examples
The following example shows how to register a policy:
Related Commands
|
|
|
|---|---|
event manager environment
To configure an EEM environment variable, use the event manager environment command. To disable an EEM environment variable, use the no form of the command.
event manager environment variable-name variable-value
no event manager environment variable-name variable-value
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to set an EEM environment variable:
Related Commands
|
|
|
|---|---|
exit
To exit any configuration mode or close an active terminal session and terminate the EXEC, use the exit command at the system prompt.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Use the exit command at the EXEC levels to exit the EXEC mode. Use the exit command at the configuration level to return to privileged EXEC mode. Use the exit command in interface configuration mode to return to configuration mode. You also can press Ctrl-Z, or use the end command, from any configuration mode to return to EXEC mode.
Note
The exit command is associated with privilege level 0. If you configure AAA authorization for a privilege level greater than 0, this command will not be included in the command set for that privilege level.
Examples
The following example displays an exit from the submode:
The following example displays an exit from the interface configuration mode for VRRP to return to the interface configuration mode:
The following example displays an exit from the interface configuration mode to return to the configuration mode:
The following example shows how to exit an active session (log-out):
Related Commands
|
|
|
|---|---|
Feedback