CN101488881A - A fault processing method - Google Patents
A fault processing method Download PDFInfo
- Publication number
- CN101488881A CN101488881A CNA2008100563754A CN200810056375A CN101488881A CN 101488881 A CN101488881 A CN 101488881A CN A2008100563754 A CNA2008100563754 A CN A2008100563754A CN 200810056375 A CN200810056375 A CN 200810056375A CN 101488881 A CN101488881 A CN 101488881A
- Authority
- CN
- China
- Prior art keywords
- fault
- equipment
- approaching
- fault message
- alarm
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a fault processing method, the method comprises following steps that: a safe area which can not be covered is provided in a RAM of the apparatus in the process of the apparatus resetting in advance, and the termination fault information of the apparatus can be written into the safe area; then in the process of the apparatus resetting, the termination fault information can be read from the safe area; at last, the fault can be processed according to the termination fault information. The fault resulting in the apparatus resetting can be processed effectively according to the invention.
Description
Technical field
The present invention relates to communication technical field, particularly a kind of fault handling method.
Background technology
Significant trouble when taking place in present communication system; the error protection measure of most equipment all only is that this equipment is carried out reset operation; in the actual processing procedure; the relevant information of reflection equipment fault will be produced; and, make the relevant information of reflection equipment fault not be saved owing to the reset operation that equipment is carried out, therefore; can't carry out troubleshooting according to the relevant information of fault, can't thoroughly fix a breakdown then.That is to say, after the device reset operation is finished, cause that the fault of last device reset still exists, and the fault that still exists will very might cause this equipment to carry out reset operation once more, repeatedly.
As seen, when causing the fault of device reset, prior art can't be carried out effective troubleshooting.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of fault handling method, realizes the effective processing to the fault that causes device reset.
For achieving the above object, technical scheme of the present invention specifically is achieved in that
A kind of method of avoiding fault message to lose is arranged on the safety zone that can not be capped in the process of device reset in advance in the random access memory RAM of equipment, this method also comprises:
A, the fault message approaching one's end of equipment is write described safety zone;
B, in the process that equipment resets, from described safety zone, read fault message approaching one's end;
C, carry out troubleshooting according to described fault message approaching one's end.
Described fault approaching one's end can comprise: cause the fault that described equipment resets;
Described fault message approaching one's end can comprise: the relevant information that causes the fault that described equipment resets.
Before described steps A, may further include:
Receiving alarm, judge with the corresponding error protection measure of described alarm whether for immediately equipment being resetted, if, then with the content of described alarm as fault message approaching one's end.
Before described steps A, may further include:
In the process that equipment resets, judge whether to exist the hardware reset reason to cause described device reset, if exist, then with described hardware reset reason as fault message approaching one's end.
Preferably, the described fault message approaching one's end with equipment of steps A writes described safety zone and can comprise: with the described hardware reset reason safety zone of writing direct, or the form that the hardware reset reason is converted to alarm write the safety zone.
Described step C can comprise: described equipment carries out corresponding troubleshooting according to described fault message approaching one's end, and generates the event of failure report according to described fault message approaching one's end, reports Fault Management System; After described equipment successfully resetted, described equipment generated with described event of failure and reports corresponding fault clearance report, sends to Fault Management System.
Before described equipment carries out corresponding troubleshooting according to described fault message approaching one's end, may further include: described equipment judges whether described fault message approaching one's end is effective, if effectively, then continue to carry out the operation of carrying out corresponding troubleshooting according to described fault message approaching one's end, otherwise, report troubleshooting fault alarm approaching one's end to Fault Management System.
Described step C can comprise: the fault message approaching one's end that described equipment will read is carried in the device start request message, reports the main control device of described equipment; The main control device of described equipment carries out corresponding troubleshooting according to described fault message approaching one's end, and generates the event of failure report according to described fault message approaching one's end, reports Fault Management System;
After described equipment successfully resetted, the main control device of described equipment generated with described event of failure and reports corresponding fault clearance report, sends to Fault Management System.
Before the main control device of described equipment carries out corresponding troubleshooting according to described fault message approaching one's end, may further include: the main control device of described equipment judges whether described fault message approaching one's end is effective, if effectively, then continue to carry out the operation of carrying out corresponding troubleshooting according to described fault message approaching one's end, otherwise, report troubleshooting fault alarm approaching one's end to Fault Management System.
May further include in the described fault message approaching one's end: activity alarm list, history alarm daily record, equipment running status or equipment Proprietary Information.
As seen from the above technical solution; the present invention is by being arranged on shielded safety zone in the reseting procedure in the RAM of equipment; and the fault message approaching one's end of equipment is stored in this safety zone; can be so that in the process of device reset; carry out troubleshooting according to the fault message of being stored in the safety zone approaching one's end; because fault message approaching one's end is a kind of extremely important and Useful Information to the fault recovery of equipment; therefore, utilize described fault message approaching one's end can realize effective processing to the fault that causes device reset.
And, by the fault message of storing in the safety zone of the present invention approaching one's end, the network management personnel can obtain the relevant information about the fault that causes device reset, can under which running status, reset by understanding equipment, can obtain the information such as preceding active alarm and history alarm daily record that reset.
Description of drawings
Fig. 1 is the schematic flow sheet of fault handling method of the present invention;
Fig. 2 is the schematic flow sheet of the fault handling method in the embodiment of the invention one;
Fig. 3 is the schematic flow sheet of the fault handling method in the embodiment of the invention two.
Embodiment
For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in further detail.
Among the present invention, to cause that fault that equipment resets is called the fault approaching one's end (lasterror) of this equipment, because fault approaching one's end is the fault that causes device reset, therefore, the fault message approaching one's end of equipment all is unusual Useful Information concerning the fault recovery of this equipment or whole communication system.
Main thought of the present invention is exactly: by be arranged on the safety zone that can not be capped in the process of device reset in the random access memory (RAM) of equipment, and the fault message approaching one's end of equipment is stored in the described safety zone, so, in the process of device reset, just can from the safety zone, read the fault message approaching one's end of this equipment, thereby avoid losing of fault message.After this, can carry out troubleshooting, thereby realize effective processing the fault that causes device reset according to the fault message approaching one's end that is read.
Fig. 1 is the schematic flow sheet of fault handling method of the present invention.Referring to Fig. 1, this method comprises:
Step 101: in the RAM of equipment the safety zone is set in advance, the content of storing in the described safety zone can not be capped in the process of device reset.
Usually, when carrying out device reset, all the elements among the RAM all will be reset, that is: RAM will revert to initial condition, and like this, original content will be capped among the RAM.In order to realize safety zone of the present invention; a certain sector address corresponding memory space among the RAM can be designated shielded memory space; and write corresponding block being used for the software program that control appliance resets, the function of described block is that the content in the sector address corresponding memory space of the described setting of protection is uncovered in the process of device reset.
Step 102: the fault message approaching one's end of equipment is write described safety zone.
As previously mentioned, the fault approaching one's end of equipment is the fault that causes that equipment resets, and in actual applications, causes that the fault of device reset mainly contains following two kinds of situations:
1) be attended by the fault of alarm:
When this class fault takes place, will produce corresponding alarm usually.When receiving alarm, at first can judge with this and whether alarm corresponding error protection measure for immediately equipment being resetted, if the error protection measure is immediately equipment to be resetted, show that then this alarm belongs to great alarm, at this moment, can be with content that should alarm as fault message approaching one's end, and carry out that this step is described to write the operation of safety zone with fault message approaching one's end, this equipment then immediately resets; If the error protection measure is not immediately equipment to be resetted, then show with described alarm be a common alarm, only need handle getting final product according to corresponding alarming processing process.
2) hardware fault:
Because hardware fault usually occurs under the emergency case, for example: under the situation of the unexpected power down of system, equipment does not possess time enough and information usually and produces alarm and it is write the safety zone, and, resetting that hardware fault causes also will make the information dropout of safety zone, at this moment, can utilize hardware reset reason erasable, the middle record of programmable logic device (EPLD, Erasable Programmable Logic Device) to carry out troubleshooting.
Specifically, hardware device generally realizes comprising functions such as Power Supply Monitoring, reset processing, outer watchdog by EPLD.For example, work as device power, EPLD starts working in power up, and can monitor level changes, so note reset circuit (for example being recorded as " power on reset "), also be same reason for resetting of causing by reset key, outer watchdog etc. at the inner corresponding ram region of EPLD.So, what all were hardware-related resets, EPLD is recorded in the RAM, and EPLD is open to processor, also be the ram region that processor can be visited EPLD, so after device reset is restarted, can read the hardware reset reason from the relevant position of the ram region of EPLD, and with described hardware reset reason as fault message approaching one's end, carry out then that this step is described to write operation in the safety zone with fault message approaching one's end.
Situation at hardware fault, dual mode is arranged when writing fault message approaching one's end: a kind of is directly the hardware reset reason to be write the safety zone, another kind is the form that the hardware reset reason is converted to alarm, and the alarm that this is converted to writes the safety zone then.
Step 103: in the process of device reset, from described safety zone, read fault message approaching one's end.
As described in step 101, the safety zone among the present invention in fact corresponding a certain sector address among the RAM, therefore, this step is described to be read is exactly appropriate address section reading of data from RAM.
If in step 102, converted the form of alarming to for the hardware reset reason, then in this step, the fault message approaching one's end that is read will be the form of alarm, otherwise the fault message approaching one's end that this step is read may comprise part alarm and a part of hardware reset reason.
Step 104: carry out troubleshooting according to described fault message approaching one's end.
In actual applications, the equipment that breaks down can directly carry out troubleshooting and the fault that is taken place is reported Fault Management System; Also fault can be reported indirectly to its main control device that manages the operation of carrying out troubleshooting and reporting by this main control device to Fault Management System.Therefore, troubleshooting described in this step also is divided into following two kinds of situations:
First kind of situation: this equipment carries out corresponding troubleshooting according to fault message approaching one's end, and generates event of failure report (FER, Failure Event Report) according to fault message approaching one's end, reports Fault Management System; After equipment successfully resets, report corresponding fault clearance report by this equipment generation and event of failure, send to Fault Management System.
In this case, before equipment carries out corresponding troubleshooting according to fault message approaching one's end, can judge further whether fault message approaching one's end is effective, if effectively, then continue to carry out the operation of carrying out corresponding troubleshooting according to fault message approaching one's end, otherwise, report troubleshooting fault alarm approaching one's end to Fault Management System.
Second kind of situation: the fault message approaching one's end that equipment will read is carried in the device start request message, reports the main control device of this equipment; The main control device of this equipment carries out corresponding troubleshooting according to fault message approaching one's end, and generates the event of failure report according to fault message approaching one's end, reports Fault Management System; After this equipment successfully resetted, the main control device of this equipment generated with described event of failure and reports corresponding fault clearance report, sends to Fault Management System.
In this case, before the main control device of this equipment carries out corresponding troubleshooting according to fault message approaching one's end, can judge further whether fault message approaching one's end is effective, if effectively, then continue to carry out the operation of carrying out corresponding troubleshooting according to fault message approaching one's end, otherwise, report troubleshooting fault alarm approaching one's end to Fault Management System.
Above-mentionedly judge whether effective and efficient manner can be fault message approaching one's end: judge whether this equipment can discern the alarm of described fault message correspondence approaching one's end, if can discern, judge that then this fault message approaching one's end is effectively, otherwise, judge that this fault message approaching one's end is invalid.Therefore,, can when writing the safety zone, be converted into the form of alarm, perhaps, can before judging that fault message approaching one's end whether effectively, be converted into the form of alarm for the hardware reset reason.
So far, finish fault handling method of the present invention.
In above-mentioned steps 102, two kinds of major failures that cause device reset are illustrated, and have illustrated that the fault message approaching one's end with equipment that the present invention is directed to above-mentioned two kinds of faults proposition writes the mode and the opportunity of safety zone.What deserves to be explained is that the mode of above-mentioned two kinds of faults and corresponding record fault message approaching one's end is not mutual repulsion, the isolated existence, in actual applications, the mode of above-mentioned record fault message approaching one's end can be combined use.In subsequent embodiment, will be illustrated in detail.
In addition, by the explanation of above-mentioned steps 104 as can be known, the present invention is directed to the dual mode that fault reports and proposed corresponding troubleshooting scheme respectively.Describe below by two specific embodiments.
Embodiment one:
In the present embodiment, the equipment that breaks down directly reports fault to Fault Management System, and oneself carries out corresponding troubleshooting the equipment that breaks down.
Fig. 2 is the schematic flow sheet of the fault handling method in the embodiment of the invention one.Referring to Fig. 2, if receive alarm, then this method begins to carry out from step 201, if directly caused resetting by hardware fault, then this method begins to carry out from step 204.
Step 201: receive alarm.
Step 202: judge with this and alarm corresponding error protection measure whether for immediately equipment being resetted, if, then continue execution in step 203, otherwise, continuation execution in step 212.
Step 203: the content of alarm is write the safety zone as fault message approaching one's end.
Step 204: homing device immediately.
Step 205: in the process of homing device, judge that whether reset circuit is resetting of causing of hardware, if, then continue execution in step 206, otherwise, execution in step 207 continued.
In this step, can be by reading EPLD, and by judging whether there is the hardware reset reason, judge that whether reset circuit is resetting of causing of hardware.Particularly,, judge that then reset circuit is that hardware causes, continue execution in step 206 if there is the hardware reset reason; Otherwise, judge that reset circuit is not that hardware causes, continue execution in step 207.
Step 206: the hardware reset reason is write the safety zone.
As previously mentioned, in this step, the hardware reset reason can be converted to the form (can be referred to as virtual fault approaching one's end) of alarm, and described virtual fault approaching one's end is write the safety zone; Also can directly the hardware reset reason be write the safety zone.
Step 207: from the safety zone, read fault message approaching one's end.
If in step 206, converted the form of alarming to for the hardware reset reason, then in this step, the fault message approaching one's end that is read is the form of alarm, otherwise the fault message approaching one's end that this step is read will comprise original hardware reset reason.At described " otherwise " situation, may further include following processing: judge whether comprise original hardware reset reason in the fault message approaching one's end,, then described hardware reset reason is converted to the form of alarm if having.
Step 208: judge whether fault message approaching one's end is effective, if effectively, then continue execution in step 209, otherwise, continue execution in step 211.
Step 209: carry out corresponding troubleshooting according to fault message approaching one's end, and generate the event of failure report, report Fault Management System, the subsequent process of proceeding then to reset and restarting according to fault message approaching one's end.
Step 210: after equipment successfully resets, report corresponding fault clearance report, send to Fault Management System, process ends by this equipment generation and event of failure.
Step 211: equipment reports troubleshooting fault alarm approaching one's end to Fault Management System, and with the notice Fault Management System, troubleshooting approaching one's end has made mistakes, the subsequent process of proceeding then to reset and restarting, process ends.
The described troubleshooting fault alarm approaching one's end of this step can define according to existing related protocol.
Step 212: the alarm that will receive reports to Fault Management System, and carries out and this alarm corresponding protection measure process ends.
Embodiment two:
In the present embodiment, the equipment that breaks down reports fault by the main control device of this equipment to Fault Management System, and, carry out troubleshooting by the main control device of this equipment.
Fig. 3 is the schematic flow sheet of the fault handling method in the embodiment of the invention two.Referring to Fig. 3, if receive alarm, then this method begins to carry out from step 301, if directly caused resetting by hardware fault, then this method begins to carry out from step 304.
Step 301: receive alarm.
Step 302: judge with this and alarm corresponding error protection measure whether for immediately equipment being resetted, if, then continue execution in step 303, otherwise, continuation execution in step 312.
Step 303: the content of alarm is write the safety zone as fault message approaching one's end.
Step 304: device reset.
Step 305: in the process of homing device, judge that whether reset circuit is resetting of causing of hardware, if, then continue execution in step 306, otherwise, execution in step 307 continued.
Step 306: the hardware reset reason is write the safety zone.
Identical with step 206, also exist two kinds the hardware reset reason write the mode of safety zone in this step, do not repeat them here.
Step 307: from the safety zone, read fault message approaching one's end, and report the main control device of this equipment by the device start request message.
Step 308: the main control device of this equipment judges whether the fault message of receiving approaching one's end is effective, if effectively, then continue execution in step 309, otherwise, continue execution in step 311.
If in step 306, converted the form of alarming to for the hardware reset reason, then in this step, the received fault message approaching one's end of the main control device of this equipment is the form of alarm, otherwise the fault message approaching one's end that this step receives will comprise original hardware reset reason.At described " otherwise " situation, may further include following processing: judge whether comprise original hardware reset reason in the fault message approaching one's end, if have, then described hardware reset reason is converted to the form of alarm, and then carries out the whether effectively operation of fault message approaching one's end that described judgement receives.
Step 309: the main control device of this equipment carries out corresponding troubleshooting according to fault message approaching one's end, and generates the event of failure report according to fault message approaching one's end, reports Fault Management System, the subsequent process that the equipment that breaks down is proceeded to reset and restarted.
Step 310: after equipment successfully resets, report corresponding fault clearance report, send to Fault Management System, process ends by the main control device generation and the event of failure of this equipment.
Step 311: the main control device of this equipment reports troubleshooting fault alarm approaching one's end to Fault Management System, and, the subsequent process that this equipment is proceeded to reset and restarted, process ends.
Step 312: the alarm that will receive reports to the main control device of this equipment, after this, will carry out corresponding troubleshooting by the main control device of this equipment, carry out and this alarm corresponding protection measure, and process ends.
Because in actual applications, many communication equipments are embedded devices, consideration for aspects such as volume, weight, costs, these equipment do not have external memory device, for example: hard disk, therefore, safety zone of the present invention is except being used to store the fault message approaching one's end, other important informations that can also be used for memory device, for example:
A) activity alarm list (Active alarm list): if preserved the current active alarm tabulation of equipment in the safety zone, just can equipment be reset restart after, when being necessary to carry out alarm synchronization, trigger one time alarm synchronization, the current alarm that is in state of activation is reported once again, to avoid the alarm report information drop-out in the device reset process.
B) history alarm daily record (History alarm log): equipment operator often needs slave unit to obtain the history alarm daily record, the history alarm daily record is stored in the safety zone can guarantees not lose after the equipment warm reset.
C) equipment running status (Equipment running phase), for example: equipment operation still operates in the stage that service is provided at test phase.If the equipment running status of preserving in the safety zone, so, equipment can select to restart the default running status before that enters in back.
D) equipment Proprietary Information comprises: the IP address of file transfer protocol (FTP) (FTP) server, the variable-value that some are important etc.For example, TD SDMA inserts in (TD-SCDMA) system, baseband pool unit (BBU, Base Band Unit) with remote radio unit (RRU) (RRU, Remote RF Unit) under the situation of networking, RRU is stored in the safety zone with the IP address of connection BBU, BBU for its IP address allocated and for the information such as IP address of the FTP Server of its service, then these information can not lost after the RRU warm reset, RRU can select direct use, and needn't obtain from BBU by the application IP addresses process again.
As seen from the above-described embodiment; the present invention is by being arranged on shielded safety zone in the reseting procedure in the RAM of equipment; and the fault message approaching one's end of equipment is stored in this safety zone; can be so that in the process of device reset; the fault message approaching one's end of equipment can not lost, thereby makes and can carry out troubleshooting according to the fault message of being stored in the safety zone approaching one's end.Because fault message approaching one's end is a kind of extremely important and Useful Information to the fault recovery of equipment, therefore, utilize described fault message approaching one's end can realize effective processing to the fault that causes device reset.
And, by the fault message of storing in the safety zone of the present invention approaching one's end, the network management personnel can obtain the relevant information about the fault that causes device reset, can under which running status, reset by understanding equipment, can obtain the information such as preceding active alarm and history alarm daily record that reset.
Below in conjunction with two concrete application scenarioss, the present invention is described in detail:
Application scenarios one:
In the TD-SCDMA system under BBU and RRU group-network construction, RRU links to each other with BBU by a port, after the startup, BBU and RRU all will by heartbeat detection machine-processed monitor with the other side between be connected whether normal.
When the module monitors that is used to carry out heartbeat detection among the RRU when coming from the heartbeat signal of BBU, this module will produce a significant alarm, with the corresponding error protection measure of this significant alarm for resetting.Fault management module among the RRU is received after this significant alarm, will write the safety zone to this significant alarm as fault message approaching one's end, resets immediately then.RRU reset restart after, RRU will read fault message approaching one's end from the safety zone, and described fault message approaching one's end is sent to BBU by the device start request message.After BBU receives the fault message approaching one's end that comes from RRU, will carry out corresponding troubleshooting, and generate FER, described FER will be reported Operational Management System (OMC) according to fault message approaching one's end.After receiving the FER that comes from BBU, the network management personnel who is in OMC end will analyze the fault message approaching one's end that this causes that RRU resets, and take appropriate measures and avoid resetting once more because of same reason causes RRU.
Application scenarios two:
In the TD-SCDMA system that constitutes by base station (NodeB), after a radio-frequency module (RFmodule) outage powers on again, this radio-frequency module can obtain the hardware reset reason, and produces a mistake according to described hardware reset reason, writes the safety zone as fault message approaching one's end.In the process that this radio-frequency module starts, this hardware reset reason can be carried in the device start request message and send to master control borad, when master control borad is received the device start request message, can therefrom get access to the hardware reset reason, and report corresponding FER, carry out follow-up accident analysis for the network management personnel.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.All any modifications of being done within the spirit and principles in the present invention, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1, a kind of fault handling method, it is characterized in that, be arranged on the safety zone that can not be capped in the process of device reset in advance in the random access memory RAM of equipment, the content of storing in the described safety zone can not be capped in the process of device reset, and this method also comprises:
A, the fault message approaching one's end of equipment is write described safety zone;
B, in the process that equipment resets, from described safety zone, read fault message approaching one's end;
C, carry out troubleshooting according to described fault message approaching one's end.
2, method according to claim 1 is characterized in that, described fault approaching one's end comprises: cause the fault that described equipment resets;
Described fault message approaching one's end comprises: the relevant information that causes the fault that described equipment resets.
3, method according to claim 2 is characterized in that, further comprises before described steps A:
Receiving alarm, judge with the corresponding error protection measure of described alarm whether for immediately equipment being resetted, if, then with the content of described alarm as fault message approaching one's end.
4, method according to claim 2 is characterized in that, further comprises before described steps A:
In the process that equipment resets, judge whether to exist the hardware reset reason to cause described device reset, if exist, then with described hardware reset reason as fault message approaching one's end.
5, method according to claim 4 is characterized in that, the described fault message approaching one's end with equipment of steps A writes described safety zone and comprises:
With the described hardware reset reason safety zone of writing direct, or the form that the hardware reset reason is converted to alarm write the safety zone.
6, according to each described method of claim 1 to 5, it is characterized in that described step C comprises:
Described equipment carries out corresponding troubleshooting according to described fault message approaching one's end, and generates the event of failure report according to described fault message approaching one's end, reports Fault Management System;
After described equipment successfully resetted, described equipment generated with described event of failure and reports corresponding fault clearance report, sends to Fault Management System.
7, method according to claim 6 is characterized in that, before described equipment carries out corresponding troubleshooting according to described fault message approaching one's end, further comprises:
Described equipment judges whether described fault message approaching one's end is effective, if effectively, then continues to carry out the operation of carrying out corresponding troubleshooting according to described fault message approaching one's end, otherwise, report troubleshooting fault alarm approaching one's end to Fault Management System.
8, according to each described method of claim 1 to 5, it is characterized in that described step C comprises:
The fault message approaching one's end that described equipment will read is carried in the device start request message, reports the main control device of described equipment;
The main control device of described equipment carries out corresponding troubleshooting according to described fault message approaching one's end, and generates the event of failure report according to described fault message approaching one's end, reports Fault Management System;
After described equipment successfully resetted, the main control device of described equipment generated with described event of failure and reports corresponding fault clearance report, sends to Fault Management System.
9, method according to claim 8 is characterized in that, before the main control device of described equipment carries out corresponding troubleshooting according to described fault message approaching one's end, further comprises:
The main control device of described equipment judges whether described fault message approaching one's end is effective, if effectively, then continues to carry out the operation of carrying out corresponding troubleshooting according to described fault message approaching one's end, otherwise, report troubleshooting fault alarm approaching one's end to Fault Management System.
10, according to each described method of claim 2 to 5, it is characterized in that, further comprise in the described fault message approaching one's end: activity alarm list, history alarm daily record, equipment running status or equipment Proprietary Information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008100563754A CN101488881A (en) | 2008-01-17 | 2008-01-17 | A fault processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008100563754A CN101488881A (en) | 2008-01-17 | 2008-01-17 | A fault processing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101488881A true CN101488881A (en) | 2009-07-22 |
Family
ID=40891570
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2008100563754A Pending CN101488881A (en) | 2008-01-17 | 2008-01-17 | A fault processing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101488881A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101860802A (en) * | 2010-05-21 | 2010-10-13 | 中兴通讯股份有限公司 | Failure processing method and system |
| CN101951622A (en) * | 2010-09-16 | 2011-01-19 | 新邮通信设备有限公司 | Radio remote unit power-off alarm processing method and system |
| CN103139794A (en) * | 2011-11-24 | 2013-06-05 | 中兴通讯股份有限公司 | Method and system for generating out-of-service alarming information of radio frequency units |
| CN103377095A (en) * | 2012-04-24 | 2013-10-30 | 华为技术有限公司 | Running log storage method and device |
| CN105955864A (en) * | 2016-04-26 | 2016-09-21 | 浪潮(北京)电子信息产业有限公司 | Power supply fault processing method, power supply module, monitoring management module and server |
| CN107438010A (en) * | 2016-05-25 | 2017-12-05 | 中兴通讯股份有限公司 | Fault protecting method, first, second processor, network storage equipment and system |
| CN110290546A (en) * | 2019-06-21 | 2019-09-27 | 京信通信系统（中国）有限公司 | Restart localization method, device, base station equipment and storage medium in base station |
| CN114257492A (en) * | 2021-12-09 | 2022-03-29 | 北京天融信网络安全技术有限公司 | Fault processing method and device of intelligent network card, computer equipment and medium |
-
2008
- 2008-01-17 CN CNA2008100563754A patent/CN101488881A/en active Pending
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101860802A (en) * | 2010-05-21 | 2010-10-13 | 中兴通讯股份有限公司 | Failure processing method and system |
| CN101951622A (en) * | 2010-09-16 | 2011-01-19 | 新邮通信设备有限公司 | Radio remote unit power-off alarm processing method and system |
| CN103139794A (en) * | 2011-11-24 | 2013-06-05 | 中兴通讯股份有限公司 | Method and system for generating out-of-service alarming information of radio frequency units |
| CN103139794B (en) * | 2011-11-24 | 2017-08-25 | 南京中兴软件有限责任公司 | A kind of generation radio frequency unit moves back the method and system for taking warning information |
| CN103377095B (en) * | 2012-04-24 | 2016-12-07 | 华为技术有限公司 | The store method of a kind of running log and equipment |
| US9323593B2 (en) | 2012-04-24 | 2016-04-26 | Huawei Technologies Co., Ltd. | Method and device for saving running log of an operating system during a soft reset |
| CN103377095A (en) * | 2012-04-24 | 2013-10-30 | 华为技术有限公司 | Running log storage method and device |
| CN105955864A (en) * | 2016-04-26 | 2016-09-21 | 浪潮(北京)电子信息产业有限公司 | Power supply fault processing method, power supply module, monitoring management module and server |
| CN105955864B (en) * | 2016-04-26 | 2019-05-28 | 浪潮(北京)电子信息产业有限公司 | Power failure processing method, power module, monitoring management module and server |
| CN107438010A (en) * | 2016-05-25 | 2017-12-05 | 中兴通讯股份有限公司 | Fault protecting method, first, second processor, network storage equipment and system |
| CN110290546A (en) * | 2019-06-21 | 2019-09-27 | 京信通信系统（中国）有限公司 | Restart localization method, device, base station equipment and storage medium in base station |
| CN114257492A (en) * | 2021-12-09 | 2022-03-29 | 北京天融信网络安全技术有限公司 | Fault processing method and device of intelligent network card, computer equipment and medium |
| CN114257492B (en) * | 2021-12-09 | 2023-11-28 | 北京天融信网络安全技术有限公司 | Fault processing method and device for intelligent network card, computer equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101488881A (en) | A fault processing method | |
| US5875290A (en) | Method and program product for synchronizing operator initiated commands with a failover process in a distributed processing system | |
| US6012150A (en) | Apparatus for synchronizing operator initiated commands with a failover process in a distributed processing system | |
| CN107147540A (en) | Fault handling method and troubleshooting cluster in highly available system | |
| CN103812699A (en) | Monitoring management system based on cloud computing | |
| CN110851320A (en) | Server downtime supervision method, system, terminal and storage medium | |
| CN112506702B (en) | Disaster recovery method, device, equipment and storage medium for data center | |
| CN105450472A (en) | Method and device for automatically acquiring states of physical components of servers | |
| CN112181660A (en) | High-availability method based on server cluster | |
| US20020124201A1 (en) | Method and system for log repair action handling on a logically partitioned multiprocessing system | |
| US20090303884A1 (en) | Monitoring system, monitoring device, monitored device, and monitoring method | |
| CN109768884A (en) | The implementation method of communication system and its high availability, device and computer equipment | |
| CN112187807B (en) | Method, device and storage medium for monitoring branch network gateway | |
| CN101854263B (en) | Method, system and management server for analysis processing of network topology | |
| CN110990903B (en) | Cloud system and cloud system protection method | |
| CN110224872B (en) | Communication method, device and storage medium | |
| CN102006190A (en) | High-availability cluster backup system and backup method thereof | |
| CN100421381C (en) | Method and device for obtaining information of operation and failure state for network equipment | |
| CN114884803B (en) | Method, device, equipment and medium for processing multiple redundant states | |
| CN115080340A (en) | Method, system, computer device and storage medium for monitoring floppy disk array | |
| CN109614292A (en) | Host operation data automatic collection monitoring system based on shell | |
| US11237892B1 (en) | Obtaining data for fault identification | |
| CN103457792A (en) | Fault detection method and fault detection device | |
| CN109218464B (en) | Method, system, equipment and storage medium for reporting address conflict of parallel modules | |
| CN111309504A (en) | Control method for embedded module serial port redundant transmission and related components |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20090722 |