Implementing a Batch Upgrade Using the Commander
Context
To upgrade devices that are running properly on a network supporting EasyDeploy, classify devices using the same upgrade file into one group. The network administrator only needs to specify the upgrade file for the group to implement a batch upgrade. Generally, you need to upgrade system software or patch files of devices. You are advised to create a group based on the following rules:
- Create a built-in group if clients are the same model and use the same upgrade files.
- Create a built-in group if clients are different models, but they have the same device type and use the same upgrade files.
- Create a customized group based on client IP addresses if the clients are different models and use different upgrade files.
If no matching rule is found or a rule is matched but no file information is specified in the rule, the system uses the default file information.
Pre-configuration Tasks
Before implementing a batch upgrade using the Commander, complete the following tasks:
- Ensure that reachable routes exist between the file server, Commander and clients.
- Configure a file server, configure basic Commander functions, and configure file server information.
- Add configured devices to the management domain of the Commander.
- Ensure that clients operate properly.
- Ensure that upgrade files have been uploaded to the working directory of the file server.
To enhance security for communication between the Commander and clients and prevent a bogus Commander from controlling clients, run the easy-operation shared-key command in the system views of the Commander and clients to configure the same shared key.
Procedure
Configure information about files to be downloaded.
- Configure file information for a client group.
Run system-view
The system view is displayed.
Run easy-operation
The Easy-Operation view is displayed.
Perform either of the following steps based on the group type:
Configure a matching rule for a built-in group.
Run group build-in device-type
A built-in group is created and the group view is displayed.
Configure a matching rule for a customized group.
Run group custom { mac-address | esn | ip-address | model | device-type } group-name
A customized group is created and the group view is displayed.
Run match { mac-address mac-address [ mac-mask | mac-mask-length ] | esn esn | ip-address ip-address [ ip-mask | ip-mask-length ] | model model | device-type device-type }
A matching rule is defined for the customized group.
- A maximum of 256 groups can be created and a maximum of 256 matching rules can be defined for the groups on the Commander. For groups created based on MAC addresses, IP addresses, or ESNs, multiple matching rules can be defined. For groups created based on device types and models, only one matching rule can be defined for each group.
- If multiple types of groups are configured, the clients match the groups in the following sequence: MAC address > ESN > IP address > device model > device type in the customized group > device type in the built-in group.
- If a client matches multiple groups of the same type, the groups are selected in alphabetical order of their names.
Perform the following steps to specify the files to be downloaded:
Run system-software file-name [ version ]
The system software package name and version number are specified.
Run patch file-name
The patch file name is specified.
Run configuration-file file-name
The configuration file name is specified.
Run web-file file-name
The web page file name is specified.
Run license file-name
The license file name is specified.
Run { custom-file file-name } &<1-3>
The user-defined file name is specified. A maximum of three user-defined files can be specified.
Configure default file information.
Run system-view
The system view is displayed.
Run easy-operation
The Easy-Operation view is displayed.
Perform the following steps to specify the files to be downloaded:
Run system-software file-name [ version ]
The system software package name and version number are specified.
Run patch file-name
The patch file name is specified.
Run configuration-file file-name
The configuration file name is specified.
Run web-file file-name
The web page file name is specified.
Run license file-name
The license file name is specified.
Run { custom-file file-name } &<1-3>
The user-defined file name is specified. A maximum of three user-defined files can be specified.
- Configure file information for a client group.
Configure an activation policy for downloaded files.
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.
By default, if downloaded files include the system software or configuration file, the devices activate all files by resetting. If the downloaded files do not include the system software and configuration file, the devices do not reset.
Configure a file activation policy in the group view.
-
The system view is displayed.
-
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.
Start batch upgrade.
Run system-view
The system view is displayed.
Run easy-operation
The Easy-Operation view is displayed.
Run upgrade group [ group-name ] &<1-15>
Batch upgrade is started.