The customer is facing issues when trying to upgrade an USG 6350 to V500R001C30SPC600

47

The file upload procedure ends with success, but once the file is set as the startup system file, it fails giving CRC error.
Upgrade via GUI
downloaded the file several times both via Hedex and different browsers, even from different locations
This is the error reported via GUI (which should be an "human-error-free procedure")
Solution�?After using the Software digital signature validation tool to verify the integrity of the firmware downloaded from our website we were able to upgrade the firewall since there weren’t CRC error anymore.
The Software digital signature validation tool can be find here :
http://support.huawei.com/enterprise/en/tool/software-digital-signature-validation-tool-(pgp-verify)-TL1000000054/TV1000000016
Detail see
The customer is facing issues when tryng to upgrade an USG 6350 to V500R001C30SPC600

Other related questions:
Why an ISSU upgrade fails on a CE series switch
If a card fails to start using the system software of a new version, an ISSU upgrade will fail and the system will be rolled back to the previous version.

Why ISSU upgrade check fails on a CE series switch
An ISSU upgrade feasibility check fails on a CE series switch due to the following possible causes:
  • l The switch has an unregistered card installed.
  • l No patches are installed for ISSU upgrade in the current version or the installed patch is not activated.
  • l The CPU usage and memory usage are too high.
  • l The available flash memory storage space is insufficient.
  • l The patch and system software files for the next startup are inconsistent with the currently running ones.
  • l The system software and patch files to be upgraded are invalid.
  • l The active/standby switchover status of MPUs are not Ready. You can run the display switchover state command to check the active/standby switchover status of cards.
  • l The command used to enable an ISSU upgrade is not executed in the working path of the active MPU. For example, if you run the cd slave#flash:/ command, the working path of the standby MPU is displayed.

Precautions for active/standby upgrade in hot standby deployment on the USG2000&5000
Precautions for active/standby upgrade in hot standby deployment on the USG2000&5000 are as follows: As for software version upgrade in hot standby deployment, you shall comply with a primary principle. That is, you shall upgrade the active and standby devices individually and upgrade the standby device first and then the active device. In addition, you must disable the HRP function during the upgrade. Note: For software version upgrade in hot standby deployment, the target software versions of the active and standby devices must be the same. Otherwise, the HRP function may fail to be enabled simultaneously. Hardware restrictions Currently, hot standby can be implemented only between two devices. The active and standby devices must have the same product model and version. The active and standby devices must have the same number and types of boards installed in the same arrangement. Otherwise, the information synchronized from the active device does not match the physical configuration of the standby device. As a result, faults occur after an active/standby switchover. If you want to use a Layer-2 interface as a heartbeat interface, add the Layer-2 interface to a VLAN. Then create a VLANIF interface and configure an IP address for it. Use the VLANIF interface as a heartbeat interface and specify remote to specify the IP address of the heartbeat interface on the remote device. Software restrictions The active and standby devices must use the same software version. Otherwise, configuration commands or session list structures of the different software versions may be different. In this case, errors may occur on the active and standby devices when you back up configuration commands and status. The BootROM versions on the active and standby devices must be the same. The operating mode of the active and standby devices must be the same, that is, both the active and standby devices must be in firewall mode or UTM mode. You are advised to use the initial configuration file on both devices. Otherwise, faults may occur after the active/standby switchover because of configuration conflicts. The names, quantities, and configuration sequence of virtual firewalls on the active and standby devices must be the same. The interfaces on the same slot of the active and standby devices must be added to the same security zone. For example, if the GigabitEthernet0/0/1 interface on the active device is added to the Trust zone, the GigabitEthernet0/0/1 interface on the standby device must also be added to the Trust zone. Configurations of heartbeat interfaces (HRP heartbeat link) on the active and standby devices must be consistent. Note: The USG2110-X/2100 and USG2100 BSR/HSR do not support the function of specifying the heartbeat interface IP address of the peer device. Therefore, you cannot use the VLANIF interface as the heartbeat interface. The service interfaces of the active and standby devices use fixed IP addresses. Therefore, you cannot use the dual-system hot backup function together with functions for obtaining IP address automatically, such as PPPoE dial-up, DHCP client, 3G, and XDSL.

How long does it take to register the interface card if a switch is upgraded through ISSU
When the system software of an S series switch is upgraded through in-service software upgrade (ISSU), assume that the system software of the interface card has been updated to the flash memory, and the startup file and startup path have been configured. If the BootROM and Bootload before and after the version upgrade are the same, the interface card is started in fast startup mode. That is, the interface card is started using the configured startup file and path. It takes about 2 minutes to start and register the interface card. If the BootROM and Bootload before and after the version upgrade are different, the interface card is started in normal mode. In this mode, the BootROM and Bootload of the interface card are updated and the startup file is downloaded from the MPU. The whole process takes about 6 to 7 minutes.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top