Applicable Models
This fault may occur on the following IPC models:
IPC2811-WD-Z20
IPC5811-WD-Z20
Symptom
Users fail to log in to the IPC. The messageThe device is busy. Try again. is displayed, and the device connection is unstable.
Possible Causes
This is a known issue in V200R001C01SPC100: The system time restores to the year of 1970 when the RTC battery runs out of power. When the system time is the year of 1970, the RTC interface fails to be set during device startup, which causes the failure to start the main program.
Solution
- Before the upgrade, disable the firewall of the PC from which you want to upgrade the IPC.
- Ensure that the network connection between the IPC and the Secure File Transfer Protocol (SFTP) server is normal. Do not disable the SSH tool, or power off or restart the IPC during the upgrade.
- The directory for storing the upgrade file cannot contain more than one .bin file; otherwise, the upgrade will fail.
- The upgrade file cannot exceed 35 MB; otherwise, the IPC may be faulty after the upgrade file is uploaded.
- Create an SFTP server, and configure the user name, password, and file path.
- Place the upgrade file in the specified directory on
the SFTP server or in a new folder in the specified directory.NOTE:
How to obtain the upgrade package, see theObtaining Upgrade Packages.
- Use SSH to log in to the IPC as the admin user.
- Run the su - root command to switch to the root user.NOTE:
For details about the default passwords of the admin and root users, see the User Guide corresponding to the faulty device.
- Run the cd /usr/app/bin/ command to go to the bin directory.
- Run the ./update sftp [IPAddr] [FilePath] [Mode] command to start the upgrade.NOTE:
- [IPAddr]: IP address of the SFTP server.
- [FilePath]: path where the upgrade file is stored on the SFTP server. Assume that the specified directory for storing the upgrade file on the SFTP server is D:\update, the path where the upgrade file is stored is D:\update\file, and the upgrade file name is updatefile. The value of this parameter is file/updatefile. If the upgrade file is directly stored in the specified directory on the SFTP server, you do not need to set this parameter.
- [Mode]: When this parameter is set to -f, the upgrade is performed forcibly. The parameter can be left blank.
For example, if you run the ./update sftp 192.168.40.254 IPC6112_V100R001C10.bin, the following information is displayed.
root@Huawei:/usr/app/bin# ./update sftp 192.168.40.254 IPC6112_V100R001C10.bin Update: Update Process Start! Update: Update Sftp Start! Update: Enter Function: UploadUpdateFile(sftp,192.168.40.254) Please Enter sftp UserName: admin Update: Start sftp IPC6112_V100R001C10.bin, Please Wait...... admin@192.168.40.254's password:
- Enter the user name and password set in 1 as prompted.NOTE:
Enter yes when the system asks you whether to continue.
The following information is displayed:Connected to 192.168.40.254. Fetching /IPC6112_V100R001C10.bin to /usr/upgrade/uImage.bin /IPC6112_V100R001C10.bin 100% 27MB 1.8MB/s 00:15 Update: sftp IPC6112_V100R001C10.bin Success! Update: Sha256Calc file length:28704768 Update: Sha256Calc break check read length :4096 Update: Sha256Calc length MAX_BUFFER_LEN:28704768 Update: Sha256Calc check read length :28700672 Update: pEncryptString:519f12426595dea0be399841175af591d442588fd581befd09889548fadb8960 Update: Start Kill Software Process.......... Start Kill Software Process killall: can't kill pid 1225: No such process killall: can't kill pid 1226: No such process killall: can't kill pid 1227: No such process killall: can't kill pid 1228: No such process killall: can't kill pid 1229: No such process killall: can't kill pid 1230: No such process killall: comm: no process killed killall: can't kill pid 1204: No such process killall: can't kill pid 1207: No such process killall: rda: no process killed killall: udhcpc: no process killed Start Update, Please Wait ...... Update: Kill Process Success! Update: Start Update.......... Erasing 128 Kibyte @ 2a00000 - 100% complete. Update: UpdateSystem() Success!
The preceding information indicates that the upgrade file is uploaded successfully and the upgrade is complete. - Check whether the fault is rectified.
- If yes, the procedure ends.
- If no, contact your service provider for assistance.