Context
When configuring an activation policy, you can configure a file activation time and a file activation mode.
- Configuring a file activation time involves two values:
Specific time to activate files
Clients will activate files at a specified time.
Delay time before activating files
Clients activate downloaded files after a certain delay. The maximum delay can be 24 hours.
- Configuring a file activation mode involves choosing between two modes:
- Non-reset mode
By default, a client activates downloaded files without resetting. However, if a system software package (*.cc) is downloaded, the client resets to activate downloaded files regardless of whether the reset mode is configured. If no system software package is downloaded, the client activates the downloaded files as follows:
- The patch file is automatically activated.
- The configuration file is reversely compiled, and commands are saved in the client one by one. The client will use the configuration for next startup. If any command configuration fails during configuration recovery, the client resets to activate the configuration file.
- The web page file must be activated manually.
- Reset mode
A client will use the downloaded system software package, patch file, and configuration file for the next startup. The web page file must be activated manually after the client resets.
If a hot patch needs to be downloaded, you can use the default file activation mode (non-reset). If a cold patch needs to be downloaded, set the file activation mode to reset.
If the client uses the non-reset mode to activate a configuration file but some commands in the configuration file cannot be restored, the client automatically uses the reset mode to activate the configuration file.
If some clients have downstream clients attached in cascading networking, it is recommended that you configure the global file activation delay time on the Commander. If an upstream client restarts or updates the configuration immediately after downloading required files, the downstream clients connected to this client are disconnected from the Commander or file server. As a result, the EasyDeploy process fails on the downstream clients. The file activation delay time avoids this problem.
Set an appropriate delay time based on the size of files to be downloaded, to ensure that all the downstream clients download the files within this delay time.
Clients select an appropriate activation policy based on the downloaded file information.
- If you configure a group for clients when configuring the file information, the file activation mode and time configured in the group take effect for the matching clients. If no file activation mode or time is configured in the group, the global file activation mode and time configured on the Commander take effect. If no global file activation mode or time is configured on the Commander, the default file activation mode and time are used.
- If you specify a specific client when configuring the file information or retain the default file information, the global file activation mode and time configured on the Commander take effect. If no global file activation mode or time is configured on the Commander, the default file activation mode and time are used.
Procedure
Configure a file activation policy in the group view.
Run system-view
The system view is displayed.
Run easy-operation
The Easy-Operation view is displayed.
Run group build-in device-type
The built-in group view is displayed.
Or run group custom { mac-address | esn | ip-address | model | device-type } group-name
The customized group view is displayed.
Run activate-file { reload | { in time | delay delay-time } } *
An activation policy is configured for the group.
Configure a global file activation policy.
Run system-view
The system view is displayed.
Run easy-operation
The Easy-Operation view is displayed.
Run activate-file { reload | { in time | delay delay-time } }*
A global activation policy is configured.