JP5068774B2 - Network monitoring device - Google Patents

Description

  The present invention relates to a network monitoring apparatus for monitoring devices and networks (communication networks).

  In a device constituting a network, when a device failure and a device operation are stopped, the network is affected, and a line stop may occur for a plurality of users. For this reason, network operators have constructed a network monitoring system for constantly monitoring the network and devices so that a rapid response can be made when a failure occurs.

  FIG. 1 is a diagram showing a configuration example of a general network monitoring system used conventionally.

  In FIG. 1, a monitoring target 1 is a network composed of devices such as an exchange, a transmission device, an IP (Internet Protocol) device, etc., and a collection device 2 that collects failure information (failure information) from the monitoring target 1 and a collection A network monitoring device 3 that performs main cause determination and influence deployment based on failure information collected by the device 2, a monitoring terminal 4 that displays failure information to an administrator, and a network configuration management device that manages network configuration information 5 is provided. Here, the physical connections and logical connections that make up the network are called “trails”, and the main cause determination is the trail that is positioned at the top of the alarms that indicate a failure. It is to identify the cause of the failure. Further, the influence deployment is to analyze the influence on the lower trail when a failure occurs in the upper trail.

  The network monitoring device 3 includes a facility management database DB1, a name database DB2, a status change logging database DB3, an ongoing database DB4, a determination result database DB5, and a network configuration database DB6 as parts for storing information necessary for processing. . Among these, the equipment management database DB1, the name database DB2, and the network configuration database DB6 have a master database in the network configuration management device 5, and a necessary range is automatically downloaded to the network monitoring device 3.

  The network monitoring device 3 includes an information collecting unit 31, an ongoing management unit 32, a main cause determination unit 33, and an influence deployment unit 34 as functional units mainly realized by a computer program.

  An example of the monitoring target 1 is shown in the lower part of FIG. 1, and the L2 links 101 to 104, the VLANs 105 and 106, and the data service 107 are all trails constituting the network.

  Hereinafter, an operation when the L2 link 101 is determined to be a main cause failure will be described.

  The information collection unit 31 receives failure information generated from the device 11 to be monitored 1 from the collection device 2 (step S1), and hands it over to the ongoing management unit 32 (step S2).

  The facility management database DB1 has only the device information key, and its Japanese name is stored in the name database DB2. The ongoing management unit 32 searches the name database DB2 from the failure information, and the operator can easily understand the Japanese language. The name is converted into a name (step S3).

  Next, the ongoing management unit 32 stores the logging information of the failure information in the state change logging database DB3 (step S4).

  Next, the in-progress management unit 32 manages the occurrence of failure information, and stores the occurrence of failure information in the occurrence database DB4 (step S5).

  Next, the ongoing management unit 32 displays the occurrence of the failure information logging of the device 11 on the monitoring terminal 4 (step S6). At this time, if there is a trail name, it is also displayed.

  Next, the in-progress management unit 32 displays that the failure of the device 11 is occurring on the monitoring terminal 4 (step S7). At this time, if there is a trail name, it is also displayed.

  Next, the main cause determination unit 33 identifies the hierarchy (the highest level) that is the main cause from the failure information (alarm) that is aggregated in units of a predetermined period (for example, 30 seconds) (step S8).

  Next, the main cause determination unit 33 stores trail information (L2 link 101) and device failure information (device 11) as a result of the main cause determination in the determination result database DB5 (step S9).

  Next, the main cause determination unit 33 displays the result of the main cause determination on the monitoring terminal 4 (step S10).

  Next, the influence deployment unit 34 performs the influence deployment of the paths, lines, and services accommodated under the main cause determination result (only when there is a trail name) (step S11). At this time, the network configuration database DB6 is referred to in order to carry out the influence development (step S12).

  Next, the influence development unit 34 displays the result of the influence development on the monitoring terminal 4 (step S13). In the case of this example, the trails determined and displayed as the influence development result are the VLAN 105 and the data service 107.

  The applicant has not been able to find published prior art documents related to the present invention by the time of filing. Therefore, prior art document information is not disclosed.

  In the past, influence deployment was performed as described above. However, in recent years, with the introduction of IP devices, it is possible to switch between a plurality of single routes, and there is a need to consider a redundant configuration method. It was. A single route is one in which devices are provided at both ends, and is different from a multiple route in which a plurality of routes are provided by a set of devices. By bundling multiple single routes, it is possible to achieve a redundant configuration equivalent to multiple routes, but it is not possible to obtain comprehensive information about each route from a single device as in the case of multiple routes. Is difficult.

  Also, with the spread of FTTH (Fiber To The Home), a large number of general users have been accommodated, and it is necessary to know the degree of impact strictly. Considering network quality degradation and switching / switchback time in redundant configurations The need to do it came out.

  Currently, it is not possible to determine the impact time when there is an impact from the result of impact deployment, so the operator (monitor) must determine whether there is a manual impact from the redundant configuration and contact the affected user. Judgment of whether or not. Therefore, a new influence deployment function is required.

  Hereinafter, the problem will be described in more detail.

  In the conventional network monitoring system described with reference to FIG. 1, it is possible to display the affected trails. However, since the stop time of the L2 link 101 and the switching time to the L2 link 102 are not considered, the data service 107 is affected. It was difficult to determine the influence time if there was an influence on the data service 107 or if there was an influence.

  In addition, in the conventional method, models that can be affected are limited, and there is a problem that the network model of IP devices in recent years cannot be supported.

  FIG. 2 is a diagram illustrating an example of a model in which stop determination and influence development can be performed by the conventional method.

  FIG. 2A shows the case of a single route configuration. When section # 1 is stopped, path # 1 and line # 1 are determined to be stopped and displayed as an effect development result.

  FIG. 2B shows a case of a redundant configuration with multiple routes. When both the sections R1 and R2 are stopped, the path # 1 and the line # 1 are determined to be stopped and displayed as an effect deployment result. Further, when the one-system stop of the sections R1 and R2 is performed, it is determined that the path # 1 and the line # 1 are non-stopped (normal) and displayed as an influence development result.

  FIG. 3 is a diagram showing an example of a case where a stop occurs due to switching / switching back by a redundant configuration in the same configuration as FIG. 2B, (a) shows the network configuration, and (b) is before the occurrence of an abnormality. The time chart from the completion of switching to after completion of switching is shown.

  That is, conventionally, the switching time from the section R1 to the section R2 and the switching protection time are not taken into consideration, and it is determined that the trouble time when the stoppage occurs due to switching / switchback in the redundant configuration is normal. The line will not be affected. The switching time is the time from the start of switching to the completion of switching, and the switching protection time is the time when switching is not performed if the failure is resolved within that time.

  If the switching time and the switching protection time are taken into consideration, this example is divided into four patterns. Pattern # 1 is a case where section R1 has a continuous failure. In this case, the failure time of line # 1 is from the start of switching to the completion of switching. Pattern # 2 is when the failure of section R1 is shorter than the switching protection time. In this case, the failure time of line # 1 is from the start of switching to the failure recovery of section R1. Pattern # 3 is a case where the failure of section R1 is longer than the switching protection time and shorter than the switching time. In this case, the trouble time of the line # 1 is from the start of switching to the completion of switching. The pattern # 4 is a case where the failure time of the section R1 is longer than the switching time and the trouble time can be determined. In this case, the trouble time of the line # 1 is from the start of switching to the completion of switching.

  FIG. 4 is a diagram illustrating an example of a model in which stop determination and influence development cannot be performed in the conventional method.

  FIG. 4A shows a redundant configuration with multiple routes. In this case, no determination can be made for the rest, except when all the sections R1 to R4 are normal and when all the sections R1 to R4 are stopped. That is, it is impossible to determine the quality stop of the path # 1 and the line # 1 by stopping 2 to 3 sections R1 to R4. The quality stop is a stop due to the stop of a predetermined number of all the redundant configurations. Further, it is not possible to determine whether the path # 1 and the line # 1 are stopped by stopping one of the sections R1 to R4.

  FIG. 4B shows the case of a redundant configuration with a single route. In this case, since there is a device for each route in the single route, stop determination cannot be made in all cases. That is, it is not possible to determine the quality stop of VLAN # 1 and service # 1 by stopping 2 to 3 links # 1 to # 4. In addition, it is impossible to determine whether VLAN # 1 and service # 1 are stopped because all links # 1 to # 4 are stopped. Further, when one of the links # 1 to # 4 is stopped, the stop determination of the VLAN # 1 and the service # 1 cannot be performed.

  In view of the above-described conventional problems, an object is to provide a network monitoring apparatus that can accurately determine the degree of influence on an end-to-end user line.

  In one embodiment of this network monitoring device, a network monitoring device that receives a failure alarm from a network and devices constituting the network, determines a main cause of the failure, and develops an influence on a lower level, the network configuration information Based on the above, means for searching for alarm information from the trail determined to be the main cause toward the lower trail, and making a stop determination, and the trail in the middle of the lower stop determination is virtually lower in the redundant configuration by a single route If it is a set trail group, the alarm information is searched for higher trails based on the network configuration information and stopped based on the switching time, switching protection time and stop condition set for the trail group. Means for making a determination.

  Preferably, as the stop condition, “AND” that treats the trail that is accommodated as a stop when all of the trails that are configured as a stop is stopped, and when any of the trails that are configured as a stop is stopped, "OR" that treats a trail that has been stopped as a stop, and when n or more of m trails that are composed of multiple stops, the trail that is accommodated is treated as a stop, and m trails that are configured When the stop is 1 or more and less than n, it is defined as “mCn” to be treated as quality degradation.

  Preferably, the stop time of the subordinate trail is determined according to the combination pattern of the redundancy switching time and the switching protection time.

  In the disclosed network monitoring apparatus, it is possible to accurately determine the degree of influence on the end-to-end user line.

  Hereinafter, preferred embodiments of the present invention will be described.

<Overview>
The network monitoring system of the present embodiment grasps the state of the device and the network, and after determining the part or trail of the device that is the main cause from the result of the main cause determination, the influence of the line accommodated under the device is determined. It is to grasp. At that time, a new concept of virtual trail has been established to realize a new impact deployment method based on failure conditions patterns of stop conditions, switching time, switching protection time, and redundant configuration (including multi-stage redundant configuration) .

More specifically, it has the following functions.
(1) A function for determining whether or not it has been stopped due to quality degradation (quality stop) (2) Judging whether or not it has been stopped by switching / switching back by a redundant configuration (switching / switching time and protection time can be set) (3) Function for performing determination (3) When there are a plurality of routes in a redundant configuration, a function for determining whether all have stopped or how many stops have been performed (4) According to (1) to (3) above Function to determine whether the line was affected (stopped) or not (normal) (5) If the line was affected, the trouble time (affected time) was determined and the continuous stop Or, if time can be determined, the function to display the time. With these functions, it is possible to understand the impact on the end-to-end user's line due to equipment failure, equipment work, trail trouble, and trail work. be able to.

<Configuration>
FIG. 5 is a diagram showing a configuration example of a network monitoring apparatus according to an embodiment of the present invention.

  In FIG. 5, only the processing related to the processing of the influence deployment unit 34 in the network monitoring device 3 is shown, and the other configuration and basic operation are the same as those shown in FIG.

  In FIG. 5, the influence expansion unit 34 is an influence expansion pre-processing method 341, an influence expansion result acquisition method 342, an influence information setting method 343, an influence expansion number acquisition method 344 that are mainly realized by a computer program, and information between methods. And an impact development shared memory 345 used for transfer. Further, as the database, an impact development form database DB7 and an impact development result database DB8 are shown in the network monitoring device 3, and a trail accommodation configuration database DB9 is shown in the network configuration management device 5. Further, an upper search method 35 for searching in the upper direction and a lower search method 36 for searching in the lower direction with respect to the status change logging database DB3, the determination result database DB5, the network configuration database DB6, the trail accommodating configuration database DB9, and the like. It is shown.

  6 and 7 are diagrams showing examples of data structures of the state change logging database DB3 and the determination result database DB5. Although the data structures of the status change logging database DB3 and the determination result database DB5 are the same, the status change logging database DB3 stores all alarms (occurrence and recovery) from the monitored devices, whereas the determination result database DB5. Is different in that only the main cause alarm (occurrence only) determined from the state change logging database DB3 is stored.

  FIG. 8 is a diagram showing an example of the data structure of the path accommodation relation information in the network configuration database DB6, and includes items of its own trail instance ID, lower trail instance ID, and number of occurrences.

  FIG. 9 is a diagram showing an example of the data structure of the trail accommodation configuration database DB9, including items of update classification, update time, own trail instance ID, upper trail instance ID, upper trail duplication identification number, start date, and end date. It is out.

  FIG. 10 is a diagram illustrating an example of a concept of a trail group and information held by the trail group. (A) shows a network in which VLAN # 1 and service # 1 are located in a lower level of a redundant configuration with single-route links # 1 and # 2. In this case, although it is a single route, switching of the upper trail (separation method) occurs, so a trail group is virtually provided, and this trail group is associated with a switching time, a switching protection time, and a stop condition. Based on this information, the influence will be expanded. The trail group is also called LAG (lag). The switching time, switching protection time, and stop condition corresponding to the trail group are held in the network configuration database DB6.

The stop conditions include the following.
AND: When all the trails (multi-route configuration and single-route redundant configuration) are stopped, the accommodated trail is treated as a stop.
OR: Treats the accommodated trail as a stop when one or more trails (multi-route configuration and single-route redundant configuration) stop.
mCn: When n or more of m trails (multi-route configuration and single-route redundant configuration) constituted by a plurality stop, the accommodated trail is treated as a stop. Moreover, when the stop in m trails configured is 1 or more and less than n, it is treated as a deterioration in quality.

<Operation>
The outline of the processing will be described below with reference to FIG.

  Step S11: The impact development preprocessing method 341 is called from the monitoring terminal 4.

  Step S12: The influence development pre-processing method 341 calls the influence information setting method 343.

  Step S13: The influence information setting method 343 writes in the influence development shared memory 345 that it has been called normally.

  Step S14: The influence development pre-processing method 341 reads from the influence development shared memory 345 that the influence information setting method 343 has been called normally.

  Step S15: Return to the monitoring terminal 4 from the influence development pre-processing method 341.

  Step S16: The influence information setting method 343 deletes the past influence development result from the influence development result database DB8.

  Step S17: The influence information setting method 343 deletes the past influence development result from the influence development form database DB7.

  Step S18: The influence information setting method 343 calls the lower search method 36 and acquires the result. The influence information setting method 343 performs a lower stop determination process based on the acquired lower search result. When the trail has a redundant configuration, the next step S19 is performed, and stop determination is performed based on the result.

  Step S19: The influence information setting method 343 calls the upper search method 35 and acquires the result. Based on the acquired upper search result, upper stop determination processing is performed.

  Step S20: The influence information setting method 343 inserts the influence development result into the influence development result database DB8.

  Step S21: The influence information setting method 343 writes the influence development result in the influence development shared memory 345.

  Step S22: The influence deployment number acquisition method 344 is called from the monitoring terminal 4.

  Step S23: The influence development number acquisition method 344 reads the influence development result number from the influence development shared memory 345.

  Step S24: Return to the monitoring terminal 4 from the influence deployment number acquisition method 344.

  Step S25: The influence deployment result acquisition method 342 is called from the monitoring terminal 4.

  Step S26: The influence development result acquisition method 342 acquires the influence development result from the influence development result database DB8.

  Step S27: By returning to the monitoring terminal 4 from the influence development result acquisition method 342, the result is displayed on the influence development result screen of the monitoring terminal 4.

  The processing contents of main methods are shown below.

[Influence development pre-processing method 341]
・ Perform parameter check.
・ Exclusion processing is performed so that impact development processing is not started multiple times.
-Perform timer release processing.
Initialize the impact development shared memory 345.
A terminal identification ID is set in the influence development shared memory 345.
Set the IN parameter of the influence information setting method 343. The IN parameter includes the number of main causes, start time, end time, and instance ID.
Invoke the influence information setting method 343.
The activation of the influence information setting method 343 is monitored by the influence development shared memory 345.
• Set the OUT parameter. The OUT parameter includes the processing result (OK / NG).
-Return from the method.

[Influence information setting method 343]
・ Perform parameter check.
Delete past impact development results from the impact development result database DB8.
Delete past influence development form output results from the influence development form database DB7.
・ Acquire aggregation start time and aggregation end time from alarm analysis.
・ Repeat the following process for the number of main causes of IN parameter.
・ ・ Set alarm search start and end time. If the primary cause recovery time is 0,
Search start time = Aggregation start time Search end time = Aggregation end time If the recovery time of the main cause is not 0,
Search start time = main cause occurrence time Search end time = main cause recovery time.
Call the lower search method 36 to obtain the lower search result.
・ ・ If there is a duplicate row due to the effective date in the lower search result, it will be excluded from the stop judgment target.
.. When the number of lower search results exceeds the number of cases, the number of cases over flag in the impact development shared memory 345 is set to ON.
・ ・ Repeat the following process for the number of lower search results.
... A stop decision is made, and the redundancy stop rate, current state, and trouble time are calculated. When the lower search result has a redundant configuration, the upper search is performed and the upper stop determination is performed. Otherwise, the higher stop determination result is taken over.
... If the upper search result is over the number of cases, the over-count flag in the impact development shared memory 345 is set to ON.
... When the stop determination result reaches the display number of the influence development result screen, the result is inserted into the influence development result database DB8 and the displayable number is written in the influence development shared memory 345.
Insert the result into the impact development result database DB8.
-Write the number of cases that can be displayed and the total number of cases that have been judged to be stopped to the impact development shared memory 345
-Release the exclusion performed by the impact development preprocessing method 341.

[Influence development result acquisition method 342]
・ Perform parameter check.
-Refer to the impact development result database DB8 to obtain the impact deployment result.
• Set the OUT parameter.

[Influence Deployment Number Acquisition Method 344]
・ Perform parameter check.
Read the number of impact deployment results from the impact deployment shared memory 345.
-Read the number of over flags from the impact development shared memory 345.
• Set the OUT parameter.
・ Returns “5” if the number over flag is ON, and returns “0” if it ends normally.

  Next, the above-described lower stop determination process (step S18 in FIG. 5) will be described.

The lower stop determination process is performed in the following procedure.
(1) The lower stop determination follows the accommodation tier under the main cause, and takes over the current state, the redundant stop rate, and the trouble time from higher to lower.
(2) If the route is the target of the upper stop determination execution, the upper stop determination is performed, and the redundant stop rate, the current state, and the trouble time are acquired and set.
(3) In order to take over the determination results from the upper level to the lower level, an array for holding the determination results for the accommodation tiers is secured and held for each accommodation tier.
(4) The upper trail writes the determination result of its own trail at its own hierarchy position in the array.
(5) The lower trail acquires the result of the upper trail by reading the upper hierarchy position of the array.

  FIG. 11 is a diagram illustrating a processing example of lower stop determination. (A) is a network configuration, (b) is an array in which a determination result is written, and (c) is a relationship between a redundancy type and a stop determination method.

In FIG. 11, each trail (route) A to E performs processing as follows. It should be noted that in the processing of each trail, the necessity determination of upper stop determination is performed based on the redundancy type, the determination method of the own trail result, and the delivery contents to the lower order are also determined.
An example in which a failure occurs in Trail A and stops will be described.
-Trail A is written in the hierarchy "0".
Trail C-1 reads layer “0”.
-Write trail C-1 on level "1".
-Trail D reads layer "1".
-Trail D is written at level "2".
-Trail E reads level "2".
・ Trail E is written at level “3”.

  Next, the above-described upper stop determination process (step S19 in FIG. 5) will be described.

The upper stop determination process is performed in the following procedure.
(1) In the upper stop determination, the presence / absence of an alarm is determined for the upper search result, and the redundant stop rate, current state, and trouble time of each component are calculated.
(2) The processing is started from the lowest structure of the upper search result. If there is a higher structure in the route, the process is recursively searched, and the stop determination result of the higher structure is reflected in the root.
(3) Finally, the redundancy stop rate, current state, and trouble time of the lowest configuration are calculated.

  FIG. 12 is a diagram showing a processing example of the upper stop determination, and the processing is performed according to the following procedure. The broken-line square indicates the configuration (device as an element on the network), the solid-line square indicates the route, and the horizontal line in the square indicates the trail.

That is,
Step S31: Root A Higher Configuration Search Step S32: Root B-1 Higher Configuration Search Step S33: Route C Determination Step S34: Configuration C Determination Step S35: Configuration C Determination Result Return Step S36: Route B-1 Step S37: Other route search for route B-1 Step S38: Upper-layer configuration search for route B-2 Step S39: Determination of route D Step S40: Determination of configuration D Step S41: Return determination result of configuration D Step S42: Route B-2 determination Step S43: Configuration B determination Step S44: Configuration B determination result return Step S45: Route A determination Step S46: Configuration A determination (= higher stop determination result)
It becomes.

Further, there are the following three types of methods for tracing the upper search result.
(1) Upper configuration search: Search for a row in which a lower instance ID is the same as its own instance ID. In this case, it is repeated for the number of upper components.
(2) Ring search: A search is made for a line whose route sequence number is the same as its own route sequence number. In this case, the same route serial number is repeated.
(3) Route search: Searches for a line whose route sequence number is its own route sequence number + 1. In this case, the number of routes is repeated.

  FIG. 13 is a diagram showing an example of how to trace the upper search result. (A) shows the root hierarchical structure, and (b) shows the upper search result in the trail group A.

The processing procedure is
Step S51: Hit the route B-1 in the upper structure search of the trail group A Step S52: Hit the route C in the upper structure search of the route B-1 Step S53: Return from the route C to the route B-1 Step S54: In route search for route B-1, hit route B-2. Step S55: Hit route D in route configuration search of route B-2 Step S56: Return from route D to route B-2 Step S57: Route B-2 It will return to the trail group A.

Next, stop conditions will be described.
(1) When the stop condition is “AND” When the trail to be judged is a trail under a multi-route, the judgment is made based on the current status of the higher-order multi-route, and when the trail is a trail group, based on the current status of the higher-order trail.
-Current [Own trail]: Stop judgment condition [Current status of upper trail]: No normal number-Current status [Own trail]: Degraded quality Condition [Current status of upper trail]: No normal number and number of degraded quality-Current status [Own] Trail]: Normal judgment condition [Current status of the upper trail]: No stop count and no quality degradation (2) When the stop condition is “OR” When the trail to be judged is a trail under multiple routes, In the case of the current state of the route and the trail group, the determination is made based on the current state of the upper trail.
-Current status [Own trail]: Stop judgment condition [Upper trail current status]]: When the number of stops is 1 or more-Current status [Own trail]: Quality degradation judgment condition [Current trail status]: No stop count and quality When there is a decrease number ・ Current status [Own trail]: Judgment of normal condition [Current state of upper trail]: No stop count and no quality decrease count (all normal)
(3) When the stop condition is “mCn” When the trail to be judged is a trail under a multi-route, the judgment is made based on the current status of the upper multi-route, and when the trail is a trail group, the judgment is based on the current status of the upper trail.
Current status [Own trail]: Stop determination condition [Current status of upper trail]: When the number of stops and the number of quality degradations are n or more
(If the number of quality declines is n or more, it is determined to be stopped)
-Current status [Own trail]: Judgment of quality degradation Condition [Current status of upper trail]: When the number of stops and quality degradation is 1 or more and less than n-Current status [Own trail]: Normal judgment condition [Current status of upper trail] : When the number of stops and the number of quality degradation are 0

Next, the above-described upper stop determination process (step S19 in FIG. 5) will be described in more detail.
(1) Acquisition of Current Status / Redundant Stop Rate of Route FIG. 14 is a diagram showing a method for acquiring the current status / redundant stop rate.

The process shown in FIG. 14 is performed for each route of its own configuration, and the current state of the route and the redundancy stop rate are acquired.
(2) Configuration normal number / quality stop number / stop number setting The normal number, quality stop number, or stop number is added based on the current state of each route. At that time, it repeats the number of routes of its own configuration, and calculates the normal number of its own configuration, the number of quality stops, and the number of stops.
(3) Route trouble time acquisition / intermediate trouble time calculation of configuration FIG. 15 is a diagram showing a technique for obtaining trouble time and a continuous stop flag. FIG. 16 is a diagram showing an intermediate trouble time and a technique for acquiring the intermediate trouble time (continuous stop).

  The trouble time is held in two items, an intermediate trouble time and an intermediate trouble time (continuous stop). Since the method for calculating the trouble time is different between the case where all the routes of the configuration are continuously stopped and the case where it is not, two items are held. Further, whether or not to stop is retained by a continuous stop flag.

  These are repeated for the number of routes of the own configuration and calculated.

For the intermediate trouble time and the intermediate trouble time (continuous stop), for each repetition, the calculated intermediate trouble time and intermediate trouble time (continuous stop) are compared with the hold value, and the larger one is set as the hold value.
(4) Current Setting of Configuration FIG. 17 is a diagram showing a method for acquiring a stop condition based on the redundancy type of the own configuration and the lower configuration. FIG. 18 is a diagram illustrating a method for calculating the current state of the self-configuration based on the normal number, the number of quality stops, the number of stops and the number of routes, and stop conditions.

Based on the calculated normal number, quality stop number, stop number, and route number, the current state of the own configuration is set.
(5) Configuration Redundancy Stop Rate Setting FIG. 19 is a diagram showing a technique for calculating a redundancy stop rate based on the number of quality stops, the number of stops, and the number of routes in the higher configuration.

  Based on the calculated quality stop count, stop count, and route count, the redundant stop rate of its own configuration is calculated.

Inside the influence development, the numerator and denominator are held as two numerical items. If “0” is set in the denominator, it means that the redundant configuration is not used.
(6) Configuration trouble time setting FIG. 20 is a diagram showing a method of setting a continuous stop flag based on the current state of the configuration.

  Based on the calculated intermediate trouble time, the intermediate trouble time (continuous stop), and the current state calculated in the current setting, the trouble time and the continuous stop flag of the own configuration are set.

  Next, a specific example will be described.

  FIG. 21 is a diagram illustrating a network configuration of a specific example of stop determination. In the figure, in the trail group E, it is assumed that switching time: 8 s, switching protection time: 5 s, and stop condition: AND are set. As an example, the influence development when a failure occurs in section A will be described. FIG. 22 is a diagram showing the upper search result in the trail group E, and FIG. 23 is a diagram showing the influence development result seen from the section A.

  Step S61: Since a failure occurs in section A and it is determined as a main cause result, the lower part of section A is searched and link C (single route) is hit.

  Step S62: The lower order of the link C (single route) is searched, and the trail group E is hit.

  Step S63: The lower order of the trail group E is searched, and line # 1, line # 2, and line # 3 are hit.

  Step S64: Since the trail group E is searched in the middle of the lower search, the upper search is started. Trail group E has no alarm. Search for link C (single route).

  Step S65: Link C (single route) has no alarm. Search for section A.

Step S66: There is an alarm in section A. Get the value as follows: V1 to V20 correspond to the values in the column with the same reference numerals in FIG.
a. Current status of route = stop ⇒ V1
Route redundancy rate = 1/0 ⇒ V2
b. Configuration stop count = 1 Quality stop count = 0 Normal count = 0
c. Route trouble time = 0m0s0ms ⇒ V3
Route continuation stop flag = ON ⇒ V4
d. Route intermediate trouble time = 0m0s0ms
Intermediate trouble time of route (continuous stop) = 0m0s0ms
e. Intermediate trouble time of configuration = 0m0s0ms
Intermediate trouble time of construction (continuous stop) = 0m0s0ms
f. Configuration stop condition = AND
g. Current status of configuration = stop h. Redundancy stop rate of configuration = 1/0
i. Configuration trouble time = 0m0s0ms
Continuation stop flag = ON
Step S67: Return from section A to link C (single route). Get the value as follows:
a. Current status of route = stop ⇒ V5
Route redundancy rate = 1/0 ⇒ V6
b. Configuration stop count = 1 Quality stop count = 0 Normal count = 0
c. Route trouble time = 0m0s0ms ⇒ V7
Route continuation stop flag = ON ⇒ V8
d. Route intermediate trouble time = 0m8s0ms
Intermediate trouble time of route (continuous stop) = 0m0s0ms
e. Intermediate trouble time of configuration = 0m0s0ms
Intermediate trouble time of construction (continuous stop) = 0m0s0ms
Step S68: The link D (single route) is searched from the link C (single route).

  Step S69: Link D (single route) has no alarm. Search for section B.

Step S70: Section B has no alarm. Get the value as follows:
a. Current status of route = normal ⇒ V9
Route redundancy stop rate = 1/0 ⇒ V10
b. Configuration stop count = 0 Quality stop count = 0 Normal count = 1
c. Route trouble time = 0m0s0ms ⇒ V11
Route continuation stop flag = OFF ⇒ V12
d. Route intermediate trouble time = 0m0s0ms
Intermediate trouble time of route (continuous stop) = 0m0s0ms
e. Intermediate trouble time of configuration = 0m0s0ms
Intermediate trouble time of configuration = 0m0s0ms
f. Configuration stop condition = AND
g. Current status of configuration = normal h. Redundancy stop rate of configuration = 0/0
i. Configuration trouble time = 0m0s0ms
Configuration continuous stop flag = OFF
Step S71: Return from section B to link D (single route). Get the value as follows:
a. Current status of route = normal ⇒ V13
Route redundancy stop rate = 1/0 ⇒ V14
b. Number of configuration stops = 1 Quality stop count = 0 Normal count = 1
c. Route trouble time = 0m0s0ms ⇒ V15
Route continuous stop flag = OFF ⇒ V16
d. Route intermediate trouble time = 0m0s0ms
Intermediate trouble time of route (continuous stop) = 0m0s0ms
e. Intermediate trouble time of configuration = 0m8m0ms
Intermediate trouble time of construction (continuous stop) = 0m0s0ms
f. Configuration stop condition = AND
g. Current status of configuration = normal h. Redundancy stop rate of configuration = 1/2
i. Configuration trouble time = 0m8s0ms
Configuration continuous stop flag = OFF
Step S72: Return from “Link D (single route)” to “Trail group E”. Get the value as follows:
a. Current status of route = normal ⇒ V17
Route redundancy stop rate = 1/2 ⇒ V18
b. Configuration stop count = 0 Quality stop count = 0 Normal count = 1
c. Route trouble time = 0m8s0ms ⇒ V19
Route continuation stop flag = OFF ⇒ V20
d. Route intermediate trouble time = 0m0s0ms
Intermediate trouble time of route (continuous stop) = 0m0s0ms
e. Intermediate trouble time of configuration = 0m8s0ms
Intermediate trouble time of construction (continuous stop) = 0m0s0ms
f. Configuration stop condition = AND
g. Current status of configuration = normal h. Redundancy stop rate of configuration = 1/2
i. Configuration trouble time = 0m8s0ms
Configuration continuous stop flag = OFF
FIG. 23 shows the influence development result in which the upper search result is reflected in the lower search result created in steps S61 to S63.

  Next, FIG. 24 is a diagram illustrating an example of a network configuration when switching is performed in multiple stages.

  Also in this case, the trouble time can be calculated by applying the above-described processing. As an example, FIG. 25 shows an example of calculating the trouble time of the trail group (LAG Z) when trouble time occurs for VLAN A for each pattern. FIG. 26 shows an example of calculating the trouble time of the trail group (LAGZ) when trouble time occurs in both VLAN A and VLAN B for each pattern.

<Summary>
As described above, according to the embodiment of the present invention, there are the following advantages.
(1) Equipment failure, equipment work, trail failure, impact on end-to-end user lines that occur during trail work, and determination of affected lines when redundancy switching occurs during failure / work Since the trouble time is calculated, the operator (monitoring person) can reduce the burden that has conventionally been determined whether or not there is a manual influence.
(2) In determining the trouble time, since it is possible to cope with a multi-stage switching configuration, it has a versatile influence.
(3) The current status is displayed as “Normal”, “Stopped”, “Quality Stopped”, and if a redundant configuration is taken, the trouble time caused by switching is displayed even if “Normal” is displayed. Can be displayed easily and easily.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

It is a figure which shows the structural example of a network monitoring system. It is a figure which shows the example of the model which can perform stop determination and influence expansion | deployment by a conventional system. It is a figure which shows the example in case a stop generate | occur | produces by switching / switchback by a redundant structure. It is a figure which shows the example of the model which cannot perform stop determination and influence expansion by the conventional system. It is a figure which shows the structural example of the network monitoring apparatus concerning one Embodiment of this invention. It is a figure (the 1) which shows the data structure example of a status change logging database and a determination result database. It is FIG. (2) which shows the example of a data structure of a status change logging database and a determination result database. It is a figure which shows the data structural example of the path accommodation relation information of a network configuration database. It is a figure which shows the example of a data structure of a trail accommodation structure database. It is a figure which shows the example of the information which the concept of a trail group and the trail group hold | maintain. It is a figure which shows the process example of a low-order stop determination. It is a figure which shows the process example of a high-order stop determination. It is a figure which shows the example of how to follow a high-order search result. It is a figure which shows the method of the present condition and redundant stop rate acquisition. It is a figure which shows the technique of trouble time and acquisition of a continuation stop flag. It is a figure which shows the method of acquisition of intermediate trouble time and intermediate trouble time (continuation stop). It is a figure which shows the method of acquisition of stop conditions. It is a figure which shows the method of present condition calculation. It is a figure which shows the method of redundant stop rate calculation. It is a figure which shows the method of a continuation stop flag setting. It is a figure which shows the network structure of the specific example of a stop determination. It is a figure which shows the high-order search result in the trail group E. It is a figure which shows the influence expansion | deployment result seen from the section A. It is a figure which shows the example of a network structure in case switching is multistage. It is a figure which shows the trouble time of the trail group when trouble time arises with respect to VLAN A. It is a figure which shows the trouble time of the trail group (LAG Z) when trouble time arises in both VLAN A and VLAN B. FIG.

DESCRIPTION OF SYMBOLS 1 Monitoring object 2 Collection apparatus 3 Network monitoring apparatus 31 Information collection part 32 Occurrence management part 33 Main cause determination part 34 Influence expansion part 341 Influence expansion pre-processing method 342 Influence expansion result acquisition method 343 Influence information setting method 344 Acquisition of influence expansion number Method 345 Impact development shared memory 35 Upper search method 36 Lower search method DB1 Facility management database DB2 Name database DB3 Status change logging database DB4 Ongoing database DB5 Judgment result database DB6 Network configuration database DB7 Impact deployment report database DB8 Impact deployment result database DB9 Trail Containment configuration database 4 Monitoring terminal 5 Network configuration management device

Claims (6)

A network monitoring device that receives a failure alarm from a network and devices constituting the network, determines a main cause of the failure, and develops an influence on a lower level,
Based on the network configuration information, the alarm information is searched from the trail determined to be the main cause toward the lower trail, and a stop determination is performed,
When the trail in the middle of the lower stop determination is a trail group virtually set in the lower order of the redundant configuration by a single route, the alarm information is searched toward the upper trail based on the network configuration information, and the trail A network monitoring device comprising: a stop determination unit based on a switching time, a switching protection time, and a stop condition set for a group. As the stop condition,
"AND" that treats the trail that is accommodated as a stop when all of the trails configured by multiple stops.
“OR” that treats the trail that is accommodated as a stop when one of the multiple trails stops,
When n or more of m trails composed of a plurality of stops are stopped, the accommodated trail is treated as a stop, and when the configured stop of m trails is 1 or more and less than n, the quality deteriorates. The network monitoring apparatus according to claim 1, wherein “mCn” to be handled is defined. The network monitoring apparatus according to claim 1, wherein a stop time of a subordinate trail is determined according to a combination pattern of a redundancy switching time and a switching protection time. A method of receiving a failure alarm from a network and devices constituting the network, determining a main cause of the failure, and developing an influence on a lower level,
Based on the network configuration information, searching for alarm information from the trail determined to be the main cause toward the lower trail, and performing a stop determination;
When the trail in the middle of the lower stop determination is a trail group virtually set in the lower order of the redundant configuration by a single route, the alarm information is searched toward the upper trail based on the network configuration information, and the trail And a step of performing a stop determination based on a switching time, a switching protection time, and a stop condition set for the group. As the stop condition,
"AND" that treats the trail that is accommodated as a stop when all of the trails configured by multiple stops.
“OR” that treats the trail that is accommodated as a stop when one of the multiple trails stops,
When n or more of m trails composed of a plurality of stops are stopped, the accommodated trail is treated as a stop, and when the configured stop of m trails is 1 or more and less than n, the quality deteriorates. 5. The influence development determination method according to claim 4, wherein "mCn" to be handled is defined. 6. The influence development determination method according to claim 4, wherein a stop time of a subordinate trail is determined according to a combination pattern of a redundancy switching time and a switching protection time.

Images