Comware System Architecture and Device Management
Comware splits the control plane into user-plane and management-plane concepts and separates a running configuration from a startup configuration; changes take effect immediately in the running config but are lost on reboot unless saved with save. Know the file roles: the .cfg startup file, the .mdb next-startup file, and the .bin boot image selected via boot-loader. Candidates must distinguish Comware V5 from V7 CLI behavior (context-sensitive help, display vs show, role-based user lines) and understand the license and feature activation model.
Traps appear around configuration commitment and rollback. configuration replace file and archive configuration create rollback points; a question may show several archives and ask which restores a prior state - remember archives are numbered and display archive configuration lists them. Another frequent trap is the difference between display current-configuration and display saved-configuration, and where undo leaves a default value. Also watch role-based CLI access (user roles vs. user lines) and password recovery requirements (console access plus boot interruption).
Worked rule of thumb: before any risky change, run archive configuration to snapshot, then save force only after validation. If a change breaks connectivity, configuration replace file <archive> restores the snapshot in one step - far faster than undoing commands individually. Remember that a reboot without save reverts to the startup file, so never assume the running config persists.
Device management
Use display version, display device, and display boot-loader to confirm software state. Check display clock and NTP sync for log correlation.