Why is the Programmable switch system started?

There are a lot of things worth learning about. Here we mainly introduce the Reasons and Countermeasures for "system restart" of a program-controlled switch. The "system restart" of a program-controlled switch is an automatic troubleshooting program set up to exclude some system faults mostly software faults. When a program-controlled switch is running, once it encounters internal or external interference, it may easily cause "system restart", which will directly affect the communication quality and equipment maintenance.

1. The main cause of "system restart"

First, restart due to human reasons. Maintenance personnel are mainly responsible for personnel with low technical level and unskilled operations, and artificially inputting Dangerous commands or modifying Bureau data. Inter-Bureau relay lines are interrupted due to natural disasters or human causes and transmission equipment faults, after the system is re-configured, the program becomes chaotic; if the power supply system fails, the system loses power and reloads the system.

Second, restart due to unreasonable network structure and heavy traffic load. The traffic distribution of various cabinets in the main bureau and module Bureau is unbalanced, which exceeds the processing capability of the processor. The number of forwarding and trunk lines introduced into the switch is too large and the load is too heavy; when the telephone terminal board and the remote connection board are connected by digital relay, the objects of clock extraction are different.

Third, restart is caused by problems and defects in the software and hardware of the programmable switch. There are mainly work software without backup, and automatic switch is not possible if damaged; low processing capability, difficult to withstand excessive traffic, resulting in traffic congestion; low software version, function is not complete, as a result, users, trunk lines, and internal links cannot be automatically detached in a timely manner after the end of long-distance calls or abnormal connection.

2. Main countermeasures to prevent or reduce system restart

First, strengthen technical training and improve duty maintenance capabilities. It is necessary to adopt flexible and diverse methods, strengthen technical training for on-duty maintenance personnel, and improve the service quality. When the system fails, it can be handled in a timely and correct manner, in order to prevent "restart" upgrade and prolong the fault duration, strict implementation of the human-machine command management system and careful use of dangerous man-machine commands should be made; maintenance of system software should be strengthened, and the transcription of post-aid information should be completed in a timely manner.

Second, adjust the network structure to improve the stability of devices. It is necessary to know the traffic volume distribution, adjust the network structure in time, reasonably arrange the actual users on the LIM shelf, evacuate the traffic volume of the system, and compress the total number of calls during busy hours, prevent connection interruption, channel congestion, and traffic out of control. Strengthen the Management and relay maintenance of the program-controlled switch, prevent Switch Equipment and trunk line faults, resulting in low connection rate, high congestion, and high traffic volume. Reduce the number of forwarding and long-distance trunk lines to minimize the load of the Main Board; to reasonably solve the digital network Inter-Bureau synchronization mode, we recommend that you use the "master-slave" synchronization mode for long-distance communication bureaus, local telephone terminal bureaus, and user-controlled switches connected by digital circuits.

Third, upgrade the version in time to improve the system software functions. During version upgrade, the software debugging is complicated, and the switching system has a large number of hardware, which is difficult, demanding, wide-ranging, and has long communication interruption throughout the network. Therefore, before upgrading the version, technical personnel and relevant experts must be carefully organized to carry out repeated demonstrations and formulate feasible implementation plans and emergency measures, make sure that the version is successfully upgraded once.