Debug configuration in mixed and model-driven mode

When debugging is configured in mixed or model-driven management mode, the following usage guidelines apply.

If the commands are available in the MD-CLI, the MD-CLI commands must be used to configure debugging.

• The classic CLI cannot be used.

• Debug configuration commands entered in the MD-CLI are only displayed in the MD-CLI info and admin show configuration debug output.

• Debug configuration entered in the MD-CLI can be saved to debug.cfg or a file URL with the admin save debug command.

• Debug configuration commands entered in the MD-CLI are not displayed in the classic CLI show debug output.

If the commands are not available in the MD-CLI, the classic CLI must be used to configure debugging.

• The MD-CLI cannot be used.

• Debug configuration commands entered in the classic CLI are only displayed in the classic CLI show debug output.

• Debug configuration entered in the classic CLI can be saved to config.dbg or a file URL with the admin debug-save command.

• Debug configuration commands entered in the classic CLI are not displayed in the MD-CLI info and admin show configuration debug output.

The user must manually remove the classic and model-driven debug configuration before changing the management interface configuration mode from model-driven to mixed mode. The system automatically removes the classic and model-driven debug configuration during all other mode switches.