JP3570893B2 - Failure determination device - Google Patents

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a failure determination device that determines a failure state based on failure occurrence information reported from each part of the device.
[0002]
[Prior art]
In determining the state of a failure based on failure occurrence information reported from each monitoring point of an apparatus such as an ATM switch, various types of determination processing are required according to the type and importance of the failure. For example, for a certain device, the frequency of occurrence of an interrupt indicating the occurrence of a failure is monitored, and when the frequency of occurrence of the interrupt exceeds a predetermined threshold, if the failure continues even after a predetermined determination time has elapsed thereafter, Although it is judged as a failure state, the threshold value of the occurrence frequency and the judgment time need to be set variously according to the type and importance of the trouble, and a timer and a judgment time for measuring the occurrence frequency for each monitoring location. Requires a timer for setting.
[0003]
A close relationship, such as the relationship between a failure at the physical layer and a failure at the data link layer supported by it, that if one fails, the other always fails, but the reverse does not necessarily occur. There is a group of monitoring points with For these groups of monitoring points, it is conceivable to simplify the processing by using a common timer.
[0004]
[Problems to be solved by the invention]
A first object of the present invention is to provide a failure determination device capable of uniformly performing a determination process on a large number of monitoring locations requiring various types of determination processes with as few timers as possible. .
A second object of the present invention is to provide a failure determination device that can achieve determination processing using a common timer for a plurality of monitoring locations closely related to each other.
[0005]
[Means for Solving the Problems]
According to the present invention, means for counting the number of interrupts indicating occurrence of a failure, means for setting a first value to a timer when the number of failure occurrence interrupts is 1, Means for setting a second value to the timer when the timer has reached a predetermined value; and when the timer has expired and the number of times of failure interrupts is equal to or greater than the predetermined value and the failure has continued, a failure state Means for determining that the timer has expired, the number of times a failure interrupt has occurred is equal to or greater than the predetermined value, and when the failure has not continued, the means for determining that the failure has been restored; and Provided is a failure determination device including means for determining failure recovery when the number of occurrence interrupts does not reach the predetermined value, and means for clearing the number of failure occurrence interrupts to zero when failure recovery is determined. You.
[0006]
According to the present invention, a means for storing that a fault is being determined according to the type of a fault that has occurred when a fault has occurred, and a fault having a higher priority than a fault that has occurred when a fault has occurred. A means for setting a value to the timer when it is not stored that the determination is being made, and the highest priority among the types of failures that the timer times out and the failure determination is stored is stored. Means for determining the failure state when the failure continues, and for the highest priority type of failure stored in the timer that has expired and that the failure is being determined. And a means for setting a value to a timer when failure determination is not being performed and failure determination is being performed for another failure type.
[0007]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 1 shows a hardware configuration of a failure determination device according to the present invention. The fault determining apparatus 10 of the present invention includes a CPU 14, a ROM 16, a RAM 18, an interrupt controller 20, and a fault status register 22 interconnected by a bus 12. The CPU 14 performs a failure determination process according to a program stored in the ROM 16. The status register 22 is connected to each monitoring location of the ATM switch 24 to be subjected to the failure determination, and stores the status of the failure reported from each monitoring location. The interrupt controller 20 interrupts the CPU 14 when a failure occurs in any of the monitoring locations, and accordingly, when the failure state continues even after the CPU 14 completes the predetermined interrupt processing, or When a failure occurs again, the CPU 14 is again interrupted. The contents of the status register 22 can be read from the CPU 14.
[0008]
FIG. 2 shows a software configuration of the failure determination device according to the first embodiment of the present invention. The failure detection processing unit 30 is activated by the interruption of the failure occurrence, updates the value of the number of occurrences stored in the occurrence number storage area 32 provided for each monitoring location on the RAM 18, and the number of occurrences becomes a predetermined value. Then, a predetermined value is set in the timer area 34. The timer processing unit 36 is started by an interrupt generated every time a predetermined time elapses, counts down a timer value stored in the timer area 34, and notifies the time-up processing unit 38 of time-up when the timer value reaches zero. . The time-up processing unit 38 is activated by the time-up notification, and determines a failure state based on the number of occurrences in the occurrence count storage area 32 and the contents of the status register 22.
[0009]
FIG. 3 is a flowchart showing details of the processing in the failure detection unit 30. When activated by an interrupt indicating that a failure has occurred, the location of occurrence is first specified (step 1000), and the number of occurrences stored in the storage area 32 corresponding to the location of occurrence is incremented (step 1002). It is determined whether or not the number of occurrences has reached a predetermined value n (step 1004). If the number of occurrences has not reached n, it is next determined whether or not the number of occurrences is 1. If the number of occurrences is 1, it sets a timer value T ₁ of the for determining the occurrence frequency in the timer area 34. (Step 1008). If the number of occurrences reaches n, which means that the interrupt has occurred n times before the timer for occurrence frequency determination times out, the timer value 34 for the fixed failure determination is stored in the timer area 34. ₂ is set (step 1010). Thereafter, the interrupt is masked to prevent the occurrence count from being updated any more (step 1012).
[0010]
FIG. 4 is a flowchart showing details of the processing in the timer processing unit 36. In FIG. 4, 1 is substituted for a parameter j indicating a monitoring position during timer processing (step 1100), and it is determined whether or not the timer value of the j-th timer is zero. (Step 1102). If the timer value is not zero, it is decremented (step 1104), and if it becomes zero (step 1106), the time-up processing unit 38 is notified that the j-th timer has timed out (step 1108). Next, it is determined whether or not the processing has been completed for all the timers (step 1110). If not, the parameter j is incremented (step 1112), and the process returns to step 1102.
[0011]
FIG. 5 is a flowchart showing details of the processing in the time-up processing unit 38. In FIG. 5, first, it is determined whether the number of occurrences corresponding to the timer whose time has expired has reached n (step 1200). If occurrence frequency does not reach the n, a determination time T ₁ of the for the determination of the occurrence frequency of the time is up, since it is the interrupt occurrence count therebetween is less than n, intermittent failure or failure It is determined that the recovery has occurred (step 1206), the occurrence count is cleared to zero, and the interrupt mask is released (step 1208). If the number of occurrences in step 1200 is reached n, it means that the time is up is a time T ₂ of the order of determination holding disorders, reads the contents of the corresponding status register 22 (step 1202), it Then, it is determined whether or not the failure continues (step 1204). If it is determined that the failure continues, predetermined failure processing is performed (step 1210).
[0012]
FIG. 6 is a timing chart for explaining the operation of the failure determination device according to the first embodiment of the present invention. 6, a timer defining the determination time T ₁ is started from the first interrupt independently for fault location. In addition, the threshold value n of the number of occurrences during that time can be set to a different value for each determination point, such as n ₁ and n ₂ in FIG. For the failure points 1 and 2, when the number of occurrences reaches n ₁ and n ₂ during the determination time T ₁ , a timer for determining the determination time T ₂ starts. For determination time T ₂ can also be set to a different value for each determination point as T _21, T ₂₂ in FIG. The fault location 3, generation number determination time T ₁ before reaching the n ₃ is determined to disaster recovery because the time is up.
[0013]
In the first embodiment of the present invention, fault detection process before time-up processing unit 38 operates immediately after the timer processing unit 36 of the T ₁ timer makes a time-up notification is determined that the time is up When the number of occurrences section 30 is operated to count up from n-1 to n, the time-up processing unit 38 malfunctions as the timer T ₂ has timed. In order to avoid this, just before the timer processing unit 36 gives a time-up notification, that is, between the steps 1106 and 1108 in FIG. 4, the failure occurrence interrupt may be masked so that the number of occurrences does not increase.
[0014]
FIG. 7 shows a software configuration of the failure determination device according to the second embodiment of the present invention. In the second embodiment of the present invention, faults that are closely related to each other, such as a fault in the physical layer and a fault in the data link layer supported thereby, are collected as one fault group, and each fault group is collected. The failure state is determined using one timer each time. Further, a monitoring point of a type in which n is 1 in the first embodiment, that is, a type in which a determination of a fixed failure is made as soon as an interruption of the failure occurs is taken as the target.
[0015]
In FIG. 7, on the RAM 18 (FIG. 1), one timer area 40 is provided for each failure group, and an area 42 for storing the status (normal, under determination, or failure) of each monitoring location belonging to the failure group. Provided. The failure detection processing unit 44 is activated by the interruption of the failure occurrence, changes the state of the corresponding location during the failure determination, and all the monitoring locations belonging to the same failure group having a higher priority than the monitoring locations are normal. Only when there is a value, a value is set in the timer area 40. The timer processing unit 46 is activated by an interrupt generated every time a predetermined time elapses, counts down the timer value in the timer area 40, and notifies the time-up processing unit 48 of time-up when the timer value reaches zero. The time-up processing unit 48 is started by the time-up notification, determines the state of the failure based on the contents of the status register 22, and when it is determined that the failure has been recovered, the monitoring part having a lower priority than that is determined. If so, restart the timer.
[0016]
FIG. 8 is a flowchart showing details of the processing of the failure detection processing unit 44. When activated by the interruption of the failure occurrence, the failure group and the failure type (monitoring location) are specified (step 1300), and the status is changed from normal to failure determination with reference to the area 42 (steps 1302 and 1304). ). Next, a value is set in the timer area 40 and the timer is started only when the statuses of the monitoring points having higher priority among the monitoring points belonging to the same failure group are all set to normal (step S1). 1306, 1308). That is, when a fault with a higher priority is detected first among the monitoring points belonging to the same fault group and a fixed fault determination time starts, and a fault is detected at a monitoring point with a lower priority after the fixed fault determination time starts, a timer is set. If the value is reset, the fixed fault determination time for the high-priority monitoring point is substantially extended and the fault processing is delayed, so in order to prevent this, the high-priority monitoring point determines the fault. When it is in the middle, only the setting during the failure determination is performed, and the timer value is not set.
[0017]
FIG. 9 is a flowchart showing details of the processing of the timer processing unit 46. The operation of the timer processing unit 46 is substantially the same as the operation (FIG. 4) of the timer processing unit 36 already described, and thus the description is omitted.
FIG. 10 is a flowchart showing details of the processing of the time-up processing unit 48. In the second embodiment of the present invention, since one timer is provided for each failure group, the time-up processing unit 48 performs a failure determination process on a monitoring point belonging to the failure group corresponding to the timer whose time has expired. In step 1500, first, the state of the highest priority monitoring point belonging to the failure group corresponding to the timer whose time has expired is read from the area 42 and determined (steps 1502 and 1504). If it is neither "failure" nor "fault determination", that is, if it is "normal", the state is read for the next highest priority monitoring point (step 1506), and the process returns to step 1502. If "failure is being determined", the contents of the status register 22 corresponding thereto are read (step 1508), and it is determined whether or not the failure has continued (step 1510). The state is changed from "under failure determination" to "failure" (step 1512), and failure processing is performed (step 1514). If the fault has been recovered, the status is changed from "diagnosing fault" to "normal" (step 1516), and "monitoring fault" is set for other monitoring points belonging to the same fault group. Is determined (step 1518). If "during failure determination" is set in another monitoring location, the timer value is set again (step 1520).
[0018]
That is, in the second embodiment of the present invention, one timer is used for a plurality of monitoring points belonging to the same failure group, and if failures are detected simultaneously or consecutively, the one with the higher priority takes precedence. The fixed fault is determined in this way, and only when it is determined that the fault has been recovered, the process with the lower priority is performed.
[0019]
【The invention's effect】
As described above, according to the present invention, detection of faults having different fault types / device types and faults having priorities can be unified, and the amount of management data up to fault detection can be reduced, thereby improving the processing efficiency of fault processing. be able to.
[Brief description of the drawings]
FIG. 1 is a block diagram illustrating a hardware configuration according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating a software configuration according to the first embodiment of this invention.
FIG. 3 is a flowchart of a process performed by a failure detection processing unit 30;
FIG. 4 is a flowchart of a process of a timer processing unit 36;
FIG. 5 is a flowchart of processing of a time-up processing unit 38;
FIG. 6 is a timing chart illustrating the operation of the first exemplary embodiment of the present invention.
FIG. 7 is a block diagram illustrating a software configuration according to a second embodiment of the present invention.
FIG. 8 is a flowchart of processing of a failure detection processing unit 44;
FIG. 9 is a flowchart of a process of a timer processing unit 46;
FIG. 10 is a flowchart of a process performed by a time-up processing unit;

Claims (1)

Means for counting the number of interrupts indicating occurrence of a failure;
Means for setting a first value to a timer when the number of times of failure occurrence interrupts becomes 1,
Means for setting a second value to the timer when the number of failure occurrence interrupts reaches a predetermined value;
When the timer times out, the number of times of failure occurrence interrupt is equal to or more than the predetermined value, and when the failure occurrence continues, means for determining a failure state;
When the timer times out, the number of failure occurrence interrupts is equal to or greater than the predetermined value, and when failure occurrence is not continued, means for determining failure recovery,
Means for determining that the timer has expired, and when the number of failure interrupts does not reach the predetermined value, determines that the failure has been recovered;
Means for clearing the number of failure occurrence interrupts to zero when it is determined that the failure has been recovered.

Images