MA5606T从MA5600V800R005升级到MA5600V800R105 h801mcua

<?xml version="1.0" encoding="utf-8"?> <config> <deploy-version value="1"> <!--It indicates the internally reserved version--> </deploy-version> <product name="MA5611S"> <!--One deployment file can involve multiple product nodes. Each product node must have a product name. If a combined package contains multiple product names, multiple product nodes are generated. In this case, product name are different but other information is the same--> <mainboard name="H82BCVMM"> <!--The control board name is obtained from the combined package. One product may have multiple control boards or does not have any control boards (only one main board node and the control board name is empty)--> </mainboard> <mainboard name="H826BVVS"></mainboard> <load> <!--It describes information required for loading, such as, the transmission protocol, version, upgrade path, initialization scripts (public and customized configuration scripts), and initialization configuration file (customized configuration file)--> <transfer-protocol isSupport="1" protocol="ftp" username="test" password="test1234" port="" serveripaddr="192.168.1.10" smartUpgrade="1"> <!--It describes parameters for file loading, such as the protocol type (FTP, TFTP, or SFTP), port ID, user name, login password (The user name and password must be configured for SFTP. The user name or password contains 1 to 40 characters), and IP address of the server where the package file is saved. You can set isSupport to 0 so that the transmission option is not supported. In this situation, configurations of the OLT take effect by default--> </transfer-protocol> <upgrade isSupport="1"> <!--The upgrade path is used to configure version information for the product upgrade. The version information includes the source and target version information. The target version information is obtained from the combined package and must be consistent with the combined package information used for upgrade. One product may support multiple upgrade paths--> <source-version> <!--It describes source version information required for product upgrade. The source version information includes the source software and patch version. If the source version information is configured, source versions are checked during the upgrade. If the source version information is not configured (isSupport is 0), source versions are not checked during the upgrade--> <softversion isSupport="0" value="MA5611SV800R013C00"> <!--It indicates the source software version. When isSupport is 0, the source software version is not matched--> </softversion> <patchversion isSupport="0" value="SPC201"> <!--It indicates the source patch version. When isSupport is 0, the source patch version is not matched--> </patchversion> </source-version> <target-version> <!--It indicates the target version information, including the target software and patch versions, attribute of the upgrade package file, and the package file name (including the path) on the server--> <softversion isSupport="1" value="MA5611SV800R015C10"> <!--It indicates the target software version information, which must be consistent with that in the combined package (isSupport is 1 when the target version is available; isSupport is 0 when the target version is unavailable indicated by an empty value)--> </softversion> <patchversion isSupport="1" value="SPC201"> <!--It indicates the target patch version information, which must be consistent with that in the combined package (isSupport is 1 when the target patch is available; isSupport is 0 when the target patch is unavailable indicated by an empty value)--> </patchversion> <software-pathfilename type="1" value="/File/ma5611s/packetfile.bin"> <!--It describes the combined package type and file name (including the path with 1 to 128 characters) on the server used for the upgrade--> </software-pathfilename> </target-version> </upgrade> <init-load-script> <!--It describes the initialization script information, including the public and customized configuration scripts--> <common-script isSupport="1" value="ma5611s/common-config.txt"> <!--It indicates the file name (including the path with 1 to 128 characters) of the public configuration script on the loading server. Setting isSupport to 0 indicates that public configuration scripts are not supported--> </common-script> <individual-script isSupport="0"> <!--It indicates the customized script configuration. Setting isSupport to 0 indicates that customized configuration scripts are not supported--> <script ip="192.168.1.1" value="ma5611s/192.168.1.1.txt"> <!--It describes the customized script configuration of a product. IP is the IP address of the product and used for verification. Value is the file name (including the path with 1 to 128 characters) of the corresponding product on the server--> </script> <script ip="192.168.1.2" value="ma5611s/192.168.1.2.txt" /> </individual-script> </init-load-script> <init-load-cfgfile> <individual-cfgfile isSupport="0"> <!--It indicates the customized file configuration. Setting isSupport to 0 indicates that customized configuration scripts are not supported--> <cfgfile ip="192.168.1.1" value="ma5611s/192.168.1.1.txt"> <!--It describes the customized configuration file of a product. IP is the IP address of the product and used for verification. Value is the file name (including the path with 1 to 128 characters) of the customized configuration for the corresponding product on the server--> </cfgfile> <cfgfile ip="192.168.1.2" value="ma5611s/192.168.1.2.txt"></cfgfile> </individual-cfgfile> </init-load-cfgfile> </load> <auto-backup isSupport="0"> <!--It describes configurations for automatic backup, including the transmission protocol, path, and strategy of the automatic backup. Setting isSupport to 0 indicates that the automatic backup configuration is not supported--> <backup-server value="192.168.1.18"> <!-- It indicates the server address for the automatic backup--> </backup-server> <backup-path value="\ma5611s\"> <!--It indicates the path (0 to 60 characters) where the automatic backup file is saved on the server--> </backup-path> <backup-protocol value="ftp"> <!-- It indicates the transmission protocol (SFTP or FTP) used for automatic backup--> </backup-protocol> <backup-username value="test"> <!--It indicates the user name used for automatic backup--> </backup-username> <backup-password value="test1234"> <!--It indicates the password used for automatic backup--> </backup-password> <backup-port value=""> <!--It indicates the port ID used for automatic backup. The port ID is required when SFTP is used and its value is 22 by default--> </backup-port> <max-copy-num value="5"> <!--Indicates the maximum number of product backup files on the server--> </max-copy-num> <backup-policy> <!--It indicates the backup policy information, including interval, start time, and end time of the automatic backup--> <interval value="1"> <!--It indicates the automatic backup interval. The unit is day and the default value is 1. The host does not support the configuration and uses the default value. --> </interval> <time value="00:00"> <!-- It indicates the start and end time when the configuration file and database are backed up. The time