An IPC Fails to Go Online After Being Upgraded

Applicable Models

eSpace IPC2601-P

Symptom

IPCs are upgraded from Smart IPC V100R001C10 to eSpace IPC V100R001C11 in batches on the platform. When you query the status of the IPCs, the status is displayed as being upgraded. However, you cannot access the web pages of the IPCs.

Cause

The stop bit ranges of the PTZs of the two versions are different so that the IPC software fails to be started after being upgraded.

Solution

1. View the message.dbg log file of an IPC.

   Check whether the log file contains the following information.

   ERR:|ptz_business.c:2458|serial port set parameter enStopbit: 2 error 
   ERR:|ptz_business.c:614|PTZ SerialPortPara error!
   ERR:|copra.c:757|Control thread exit, Now Release Driver Lib Begin.

   • If yes, go to 2.
   • If no, contact your service provider for assistance.
2. Log in to the IPC through SSH, copy the default.xml file in /usr/app/bin to the local computer, and delete the default.xml file from /usr/app/bin.
   NOTE:

   For details about the default password of the admin admin user, see the User Guide corresponding to the faulty device.

3. Change the network parameter values in the local default.xml file to the values planned for the live network and save the file as a new default.xml file.
   1. Open the default.xml file on the local PC.
   2. Set MeshType (network port type) and DhcpEnable (whether to enable DHCP) to 0.
   3. Set IPAddress (front-end IP address), Netmask (front-end subnet mask), Gateway (front-end gateway address), and FirstDNSAddress (DNS server address).
   4. Set MeshDoubleSpeed (duplex transmission rate of the network port) to 3.
   5. Save another copy for the default.xml file and perform 4.
4. Place the new default.xml file to /usr/app/bin of the IPC.
5. Run the cd /usr/setting command, go to the /usr/setting directory.
6. Run the rm config* command, deletes all files whose file names start with config from /usr/setting.
7. Run the reboot -f command. The IPC restarts.
8. Access the web page of the IPC again and set platform connection parameters.
9. Log in to the IPC through SSH, delete the new default.xml file from /usr/app/bin, and copy the original default.xml file back to the directory.
10. Check whether the fault is rectified.
    • If yes, the procedure ends.
    • If no, contact your service provider for assistance.