Utility Commands
447
ProSAFE M7100 Managed Switches
The commands in the sections are executed when any of the following events occur:
• [boot_phase1]: This event occurs during configurator Phase1 initialization.
• [boot_phase2]: This event occurs during configurator Phase2 initialization.
• [boot_phase3]: This event occurs during configurator Phase3 initialization.
• [wait_mgmt]: This event occurs during configurator event WAIT_MGMT.
• [execute]: This event occurs during configurator event E (Execute).
• [unconfig_phase1]: This event occurs during configurator event U_PHASE1.
• [unconfig_phase2]: This event occurs during configurator event U_PHASE2.
• [terminate]: This event occurs during configurator event T (Terminate).
• [suspend]: This event oc
curs during configurator event S (Suspend).
• [resume]: This event occurs during configurator event R (Resume).
• [post_cfg]: This event occurs after Text Based Config is applied.
• [member_leav
e]: This event occurs whenever there is any unit leaves the stack.
• [member_join]: This event oc
curs whenever there is any unit joins the stack.
The devshell and drivshell commands are supported for all of these events. However, the CLI
commands ar
e not supported for the following events because the CLI tree is uninitialized when
these events occur:
• [boot_phase1]
• [boot_phase2]
• [boot_phase3]
Note: When you enter the clear config command on a switch, a [post_cfg]
event occurs twice: once for the global configuration and once for the
interface configuration. In such a situation, all the generic commands
that are listed under the [post_cfg] event are executed twice, causing
the output to be delayed. However, during the [post_cfg] event for the
global configuration, the output for the interface-specific commands
might contain unexpected information.
The following example shows a debug_config.ini file with commands in the last four sections of
the file:
[boot_phase1]
[boot_phase2]
[boot_phase3]
[wait_mgmt]
[execute]