The system supports two configuration validation modes: immediate validation and two-phase validation. By default, the two-phase validation mode takes effect. The system also supports offline configuration, which means that you can change interface configurations after a board is removed.
The two configuration validation modes are described as follows:
The immediate validation mode is a traditional configuration validation mode.
In this mode, the system-view immediately command is used to enter the system view. After you enter a command and press Enter, the system performs a syntax check. If the check is successful, the configuration immediately takes effect.
Configuration rollback is not supported in immediate validation mode.
In two-phase validation mode, the system configuration process is divided into two phases:
In this mode, the system-view command is used to enter the system view. In the first phase, after you enter a configuration command, the system performs syntax and semantics checks on the candidate database. If an incorrect clause is found, the system displays a message on the command line terminal, indicating the fault and cause. After entering a series of commands to complete a configuration, you can run the commit command to commit the configuration. The system then enters the second phase, that is, configuration commitment phase. In the second phase, the system delivers the configuration in the candidate database to the corresponding service module. If the configuration takes effect, the system adds it to the running database. If the same configuration is added, the system displays a message.
The following table describes the advantages and disadvantages of the immediate and two-phase validation modes.
|Immediate validation mode||The configuration impact on services can be detected immediately.||Incorrect configurations immediately affect services. You must delete incorrect configurations one by one because deleting services as a whole is not allowed.|
|Two-phase validation mode||
||The commit command must be run to validate configurations.
In two-phase validation mode, if a configuration has not been committed, the symbol "*" is displayed in the corresponding view (except the user view). If all configurations have been configured, the symbol "~" is displayed in the corresponding view (except the user view).
The system supports offline configuration. Specifically, after you configure interfaces on a board and then remove the board, the configurations are not affected and you can continue to configure the interfaces.
If you install another board in the slot, the impacts on the previous configurations are as follows:
The new board has the same type as the previous board.
The system automatically restores the configurations of all interfaces on the new board. Then, you can view interface configurations and configure the interfaces on the new board.
The new board has interfaces of a different type than the previous board.
The system deletes the configurations of all interfaces on the previous board. The deleted configurations cannot be restored.
The new board has a different number of interfaces of the same type as those on the previous board.
If the new board has more interfaces than the previous board does, the system performs the following operations:
If the new board has fewer interfaces than the previous board, the system performs the following operations: