JP2007060518A - Total management system for system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system total management system for saving on works for introduction of the system. <P>SOLUTION: The system total management system estimates and displays a cause of irregular/defective event by considering the present state of an IP network when an irregular/defective event is generated in a wide band monitoring and controlling system, or by cooperating with information of a non-IP network management apparatus such as SDH or the like. This system total management system also has the function to detect IP address used in the IP network 2 on the network 4 as the management object by searching response to the ping command. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a wide area monitoring control system that performs monitoring control of, for example, rivers, roads, dams, buildings, disaster prevention, CCTV systems (Closed Circuit Tele Vision System), etc., using SNMP (Simple Network Management Protocol) for IP network Systems that collect and store information, systems that collect and store security information such as IDS (Intrusion Detection System) and IPS (Intrusion Prevention System), and non-IP networks such as SDH (Synchronous Digital Hielachy) management devices By integrating with a system that collects and accumulates information on the system, the event generation factor is estimated and displayed from the IP network status and traffic trends when an event such as an abnormality or failure occurs in the wide-area monitoring and control system. It relates to the management system.

  The integrated system management system uses the ping (Packet InterNetwork Groper) command and SNMP (Simple Network Management Protocol) to monitor the status of devices and lines on the managed network and to detect events such as network abnormalities and failures. Estimate the occurrence factor when it occurs.

  FIG. 21 is a block diagram illustrating a configuration example of a network to be managed by the system comprehensive management system.

  In FIG. 21, there is a non-IP network portion 401 on the network 4 to be managed by the system comprehensive management system installed in the system comprehensive management server 1, and this non-IP network portion 401 is a non-IP network such as an SDH management device. Managed by the management device 402.

  An IP network portion 2 is in the network 4 to be managed by the system comprehensive management system, and a subnetwork 3 is in the IP network portion 2.

  On the IP network part 2, there are an L3 switch R1 (201), an L3 switch R2 (202), an L3 switch R3 (203), an L3 switch R4 (204), a network management server 208, and a wide area monitoring control. A server 209 is provided.

  On the subnetwork 3, there are an L2 switch B1 (301) and an L2 switch B2 (302), and an end device E1 (303), an end device E2 (304), and an end device E3 (305). .

  The IP network 2 is divided into sub-networks 3 by, for example, the L3 switch R4 (204). The sub-network 3 includes the L2 switches B1 (301) and B2 (302) and end devices E1 (303) and E2. (304) and terminal equipment E3 (305).

  By the way, in order for the system integrated management system in the system integrated management server 1 to manage the IP network part 2, the IP addresses used on the IP network to be managed have been clarified, and those IP addresses The types of devices that use the network, the subnetwork connected to the L3 switch, the devices existing on the subnetwork, and the subnetwork It is necessary that the connection relation of the equipment is clarified.

For example, when using the ping command, information on the IP address of the partner to be pinged is necessary.
When monitoring the status of a device, information to be acquired using SNMP or the like differs depending on the type of device, and thus information on the type of device is necessary.

  Furthermore, when a failure occurs in the network as shown in FIG. 22 and communication with the end device E2 (304) becomes impossible, the cause is a failure of the end device E2 (304) or a device on the communication path, for example, In order to estimate whether the failure is caused by the failure of the L2 switch B2 (302), information on the connection relation of the devices is necessary. As described above, information about the IP network 2 to be managed is necessary for the operation of the system comprehensive management system.

  As a method for determining only the IP network 2 and the type of the IP address and device used on the network, there is Patent Document 1.

Japanese Patent Laid-Open No. 2001-217832 (FIG. 1 and its description, etc.)

  As described above, in order to introduce the conventional system comprehensive management system, it has been necessary to clarify in advance the IP addresses and connection relationships used in the IP network portion to be managed.

  For the purpose of managing only an IP network, there is a method described in Patent Document 1 for detecting an IP address and a connection relationship. However, until now, in systems that manage networks including non-IP networks, detection of IP addresses and connection relationships has not been automated.

  In a network including such a non-IP network, there is a method of referring to a document created at the time of network construction as a method of clarifying an IP address. However, the method of referring to the document had the following two problems. The first problem is that the work of converting the contents of a document into a format that can be used by the integrated system management system requires manpower. The second problem is that if the network configuration is changed after the document to be referred to is created and the changed content is not reflected in the document, the written content will be incorrect. When there is an error in the description, there is a possibility that work for visually checking each device on the network may occur.

  For these reasons, there is a problem that it takes a lot of cost and time to introduce a system management system for a network including a non-IP network.

  Even if the IP addresses used on the IP network have been clarified, it is necessary to clarify the types of devices using those IP addresses. In order to clarify the type of device, a method similar to the method of clarifying the IP address can be used, but there is a similar problem in that it takes much cost and time.

  Even if the IP address used on the IP network and the type of device using the IP address are clarified, the subnetwork and subnetwork connected to each port of the L3 switch It is necessary to clarify the IP address. In order to clarify the subnetwork connected to the L3 switch and its IP address, the same method as the method of clarifying the IP address can be used, but the same problem that it takes a lot of cost and time There is.

  Even if the IP addresses used on the IP network, the devices using those IP addresses, and the sub-networks connected to each port of the L3 switch and their IP addresses are clarified, It is necessary to clarify the devices that exist on the subnetwork connected to the port.

  If there is no duplication in the IP address of the subnetwork connected to each port, the IP address used on the network, the device using those IP addresses, and the information of the subnetwork connected to each port of the L3 switch are clear In this case, it is possible to detect a device included in a subnetwork connected to each port by checking which subnetwork IP address is included in the IP address of each device.

  For example, consider the case shown in FIG. In FIG. 23 (a), the L3 switch R2 has a port P21 and a port P22, and an IP address “192.10.5.1” and a subnet mask “255.255.255.0” are set in the port P21. The port P21 is connected to the subnetwork 205 whose IP address is “192.10.5.0”, and the terminal device 206 is set with the IP address “192.10.5.3”. In this case, by examining the IP address of the end device 206 and the IP address of the subnetwork 205, it can be seen that the end device 206 belongs to the subnetwork 205.

  However, in the case of FIG. 23 (b), the subnetwork in which the terminal device 206 exists cannot be specified only from the IP address. In FIG. 23 (b), an IP address “192.10.5.2” and a subnet mask “255.255.255.0” are set to the port P22, and the port P22 is connected to the subnetwork 207 whose IP address is “192.10.5.0”. In FIG. 23 (b), there are two sub-networks with the IP address “192.10.5.0”, and it cannot be specified which sub-network the end device 206 belongs to based only on the IP address.

  As described above, when the same IP address is assigned to a plurality of sub-networks, there is a problem that the sub-network in which the device exists cannot be specified only from the IP address. Therefore, in such a case, a means capable of detecting devices belonging to each sub-network is necessary.

  Even if information such as the subnetwork connected to each port of the L3 switch, the IP address used on the subnetwork, and the type of device using the IP address has been clarified It is necessary to clarify the connection relationship of the equipment. In order to clarify the connection relation of the devices, a method similar to the method of clarifying the IP address can be used, but there is a similar problem that much cost and time are required.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a system comprehensive management system capable of saving labor at the time of system introduction.

  The overall system management system according to the present invention is capable of performing an abnormality / failure by considering the current state of the IP network when an abnormality / failure event of the wide-area monitoring control system occurs, or by linking with information of a non-IP network management device such as SDH. In the system total management system that can estimate and display the cause of the event, it has a function to detect the IP address used in the IP network part on the network to be managed by examining the response to the ping command It is a system comprehensive management system characterized by that.

  This invention estimates the cause of an abnormal / failure event by considering the current state of the IP network when an abnormal / failure event occurs in a wide-area monitoring and control system or by linking with information of a non-IP network management device such as SDH. The system integrated management system that can be displayed has a function to detect the IP address used in the IP network part on the network to be managed by examining the response to the ping command. There is an effect that it is possible to provide an integrated system management system that can save time.

Embodiment 1 FIG.
A first embodiment of the present invention will be described with reference to FIG. 1 and FIG. FIG. 1 is an example showing an operation of a function for clarifying an IP address used on a management target IP network in a configuration example of a network to be managed by the system integrated management system. FIG. 2 is a flowchart showing details of the operation in FIG. 1 and 2, the same reference numerals are given to the same or corresponding parts as those in FIGS. 21 to 23 described above, and in the following description of the first embodiment of the present invention, FIGS. Description of the same or corresponding parts will be omitted, and description will be made mainly on parts different from those in FIGS.

  In this function of the system illustrated in FIG. 1, the system integrated management server 1 executes a ping command for an IP address that may be used on the IP network 2 to be managed. Then, the IP address used is detected from the response.

  Next, details of the operation in the first embodiment will be described with reference to FIG.

  First, a certain IP address is pinged (step S501).

  Next, it is confirmed whether or not there is a response (step S502). If there is a response to the ping, it is determined that the IP address is used on the network (step S503). This is performed for all IP addresses that may be used on the managed network (step S504).

  As a result, all IP addresses used on the network can be detected.

  By adding the functions as described above to the system comprehensive management system, it is possible to obtain the latest network configuration information and to save labor that a person performs at the time of introduction.

Embodiment 2. FIG.
A second embodiment of the present invention will be described with reference to FIGS. FIG. 3 is an example showing the operation of the function for determining the type of device in the configuration example of the network to be managed by the system total management system. FIG. 4 is a flowchart showing details of the operation in FIG. 3 and 4, the same reference numerals are given to the same or corresponding parts as in FIGS. 21 to 23 and FIGS. 1 to 2 described above, and in the following description of the first embodiment of the present invention, The description of the same or corresponding parts as those in FIGS. 21 to 23 and FIGS. 1 to 2 will be omitted, and the parts different from those in FIGS. 21 to 23 and FIGS.

  FIG. 3 shows an example of the operation of a function for determining the type of device. This function determines the type of device by acquiring information about the device by using a traceroute command or SNMP as shown in FIG. To do.

  Next, detailed operations in the second embodiment will be described with reference to FIG.

  First, a trace route is performed for the IP address used on the network to be managed (step S701).

  Next, it is checked whether the device is compatible with SNMP (step S702). For a device that does not support SNMP, it is further determined whether it is a terminal device or an L3 switch based on the result of step S701 (step S703, step S706, step S707). If a device that does not support SNMP exists on the communication path between the system general management server and another device on the IP network, the device that does not support SNMP is determined as an L3 switch. A device that does not support SNMP that is not determined as an L3 switch is determined as a terminal device.

  The SNMP-compatible device determines whether it is a terminal device by referring to the MIB (Management Information Base) (steps S704 and S708). The determination is made, for example, by referring to the MIB sysDescr (1.3.6.1.2.1.1.1). For devices that are not terminal devices, the L2 switch and the L3 switch are discriminated by referring to the ipForwarding (1.3.6.1.2.1.4.1) of the MIB (steps S705, S709, and S710). Such device type determination is performed for all the used IP addresses (step S711).

  In this way, it is possible to determine the type of device that uses the IP address.

  By adding the functions as described above to the system comprehensive management system, it is possible to save work performed by a person at the time of introduction.

Embodiment 3 FIG.
A third embodiment of the present invention will be described with reference to FIG. FIG. 5 is an example showing the operation of the function of determining the type of device for estimating the subnetwork connection relationship in the configuration example of the network to be managed by the system comprehensive management system. In FIG. 5, the same or corresponding parts as those in FIGS. 21 to 23 and FIGS. 1 to 4 are denoted by the same reference numerals. In the following description of the first embodiment of the present invention, FIGS. The description of the same or corresponding parts as those in FIGS. 23 and 1 to 4 will be omitted, and the parts different from those in FIGS. 21 to 23 and FIGS. 1 to 4 will be mainly described.

  In FIG. 5, the IP address “192.10.10.1” and the subnet mask “255.255.255.0” are set to the port P4 of the L3 switch R4. In this function, first, information on the IP address and subnet mask set for the port P4 is acquired by SNMP. The IP address and subnet mask are obtained from, for example, the MIB's ipAddrTable (1.3.6.1.2.1.4.20). The subnetwork address is obtained by ANDing the acquired IP address and subnet mask. In this example, “192.10.10.0” is obtained as the IP address of the subnetwork. As described above, the IP address of the subnetwork connected to the port P4 of the L3 switch R4 is “192.10.10.0”.

  By performing such an operation on all L3 switches, it is possible to estimate all the sub-networks existing on the IP network and their IP addresses. In addition, the connection relationship between the L3 switch and the sub-network can be estimated.

  By adding the functions as described above to the system comprehensive management system, it is possible to save work performed by a person at the time of introduction.

Embodiment 4 FIG.
A fourth embodiment of the present invention will be described with reference to FIGS. FIG. 6 is an example showing an operation of a function for detecting a device included in a sub-network in a configuration example of a network to be managed by the system integrated management system. FIG. 7 is a diagram illustrating an example of items included in the ipNetToMediaTable. 6 and 7, the same reference numerals are given to the same or corresponding parts as in FIGS. 21 to 23 and FIGS. 1 to 5 described above, and in the following description of Embodiment 1 of the present invention, 21 to 23 and FIGS. 1 to 5 will not be described for the same or corresponding parts, and the parts different from FIGS. 21 to 23 and FIGS. 1 to 5 will be mainly described.

  FIG. 6 is an example showing the operation of the function of detecting devices included in the subnetwork. As shown in FIG. 6, the devices included in each sub-network are detected by referring to the ipNetToMediaTable (1.3.1.3.6.1.2.1.4.22) held by the L3 switch by SNMP.

  FIG. 7 shows items included in the ipNetToMediaTable. The ipNetToMediaNetAddress in the ipNetToMediaTable stores the IP address information of the device ahead of each port. Therefore, if the subnetwork connected to each port of the L3 switch is clear, devices belonging to each subnetwork can be detected.

  By adding the above functions to the system integrated management system, the system integrated management system can detect devices belonging to each sub-network.

Embodiment 5. FIG.
Embodiment 5 of the present invention will be described with reference to FIGS. FIG. 8 is an example showing an operation of a function for estimating a connection relation of devices in a sub-network used for communication in a configuration example of a network to be managed by the system comprehensive management system. FIG. 9 is an operation flow diagram of FIG. 8, FIG. 10 is a diagram showing a list of ports passing through, FIG. 11 is a diagram showing a list of ports passing through immediately before, and FIG. 12 is a diagram showing connection examples of end devices. FIG. 13 is a diagram showing an example of the connection relationship of the L2 switch. 8 to 13, the same or corresponding parts as those in FIGS. 21 to 23 and FIGS. 1 to 7 are denoted by the same reference numerals. In the following description of the first embodiment of the present invention, 21 to 23 and FIGS. 1 to 7 will not be described for the same or corresponding parts, and different parts from FIGS. 21 to 23 and FIGS. 1 to 7 will be mainly described.

  FIG. 8 is an example showing the operation of the function for estimating the connection relationship of devices in the sub-network used for communication. In FIG. 8, B11, B12, and B13 represent B1 ports, and B21, B22, and B23 represent B2 ports. As shown in FIG. 8, the system integrated management server estimates the connection relation of devices by acquiring information about the devices existing in the sub-network 3 using a ping command and SNMP.

  Detailed operation in the fifth embodiment will be described with reference to FIGS.

  First, information on the number of received octets for each port is obtained from all L2 switches existing in the subnetwork by SNMP (step S1201). For the number of received octets for each port, refer to the value of MIB ifInOctets (1.3.6.1.2.1.2.2.1.10), for example.

  Next, a ping command is executed a certain number of times for any device in the sub-network (step S1202).

  Information on the number of received octets for each port is acquired again from all L2 switches existing in the subnetwork (step S1203).

  The difference between the number of received octets for each port acquired in step S1203 and the information on the number of received octets acquired before that is taken to check whether the difference exceeds the threshold. The port that exceeds the threshold is recorded as a port that passes during communication with the device that is the target of the ping command in step S1202 (step S1204). Information about all the ports in the sub-network is acquired (step S1205).

  A table as shown in FIG. 10 is obtained by arranging the information acquired by the above operation in ascending order of the number of ports passing through.

  For the table in FIG. 10, the operation of deleting the passing port displayed at the top of the row from the bottom row is repeated. For example, the port B11 in the first line is deleted from the second and subsequent lines.

  By repeating this, the table in FIG. 11 is obtained. The table in Fig. 11 shows the list of ports that are closest to each device among the ports that pass when the end device communicates with the Master Management Server, and the lines that are used when the L2 switch communicates with the Master Management Server. A list of ports at both ends of the line closest to each device.

  Therefore, by selecting only the end device row from the table of FIG. 11, a list of ports connected to the end device shown in FIG. 12 is obtained.

  Further, the table shown in FIG. 13 (a) is obtained from the information in the row of the L2 switch. Furthermore, the table shown in FIG. 13B can be obtained by adding the information shown in FIG. 12 to the table shown in FIG. The table in FIG. 13 (b) is a list of devices connected to each port of the L2 switch.

  By doing so, it is possible to detect the connection relationship of devices in the sub-network. In the above description, the number of received octets for each port is described in order to check the connection relationship. However, the number of received octets is not necessarily required, and a change in communication amount may be checked. For example, the connection relation can be detected in the same manner even when the number of transmission octets (ifOutOctets) is used.

  By adding the functions as described above to the system comprehensive management system, it is possible to save work performed by a person at the time of introduction.

Embodiment 6 FIG.
A sixth embodiment of the present invention will be described with reference to FIGS. FIG. 14 shows an example of the operation of a function for detecting a connection relationship more accurately by combining spanning tree information in a configuration example of a network to be managed by the system total management system. 15 is a diagram showing examples of bridge identifiers and port identifiers, FIG. 16 is a flowchart showing the operation examples of FIG. 14, a flowchart showing the operation examples of FIG. 14, and FIG. 18 is an example of the information acquired in FIG. FIG. 19 is a diagram illustrating a connection destination example, and FIG. 20 is a diagram illustrating a case where the above-described fifth embodiment can be used but the sixth embodiment can be used. 14 to 20, the same or corresponding parts as those in FIGS. 21 to 23 and FIGS. 1 to 13 are denoted by the same reference numerals. In the following description of the first embodiment of the present invention, The description of the same or corresponding parts as those in FIGS. 21 to 23 and FIGS. 1 to 13 will be omitted, and the parts different from FIGS. 21 to 23 and FIGS. 1 to 13 will be mainly described.

  In the method described in the fifth embodiment, only the traffic of each port is referred to check the connection relation in the sub-network. When the L2 switch supports MIB dot1dStpPortTable (1.3.6.1.2.1.17.2.15), the connection relationship can be detected more accurately by combining the spanning tree information with the method of Embodiment 5. Is possible.

  FIG. 14 is an example showing the operation of the sixth embodiment. In FIG. 14, spanning tree bridge identifiers as shown in FIG. 15 (a) are set in L3 switch R4 and L2 switches B1 and B2, and port identifiers as shown in FIG. 15 (b) are set for each port. Is set. In the sixth embodiment, as shown in FIG. 14, first, spanning tree information is acquired from the L2 switch using SNMP, and the connection relationship between the L2 switches is detected. Thereafter, the connection relationship between the end devices is detected using the same method as in the fifth embodiment.

  The detailed operation of the sixth embodiment will be described with reference to FIGS. FIG. 16 is a flowchart of the operation for detecting the connection relationship between the L2 switches. In the sixth embodiment, first, the bridge identifier of the designated bridge (Designated Bridge) on the line to which each port of the L2 switch is connected using SNMP and the port identifier of the port used by the designated bridge for connection to the line are used. Obtain (step S1901). FIG. 17 shows the MIB that is referred to when acquiring the bridge identifier and the port identifier. FIG. 18 shows the results obtained in the case of FIG.

  Next, a device having each bridge identifier is identified (step S1902). The lower 48 bits of the bridge identifier are the MAC addresses of the switch corresponding to the bridge identification. Therefore, a switch corresponding to a bridge identifier can be specified by acquiring a MAC address from each bridge identifier and searching for a switch having the MAC address. To check the MAC address of each switch, refer to MIB ifPhysAddress (1.3.6.1.2.1.2.2.1.6), for example.

  Then, the connection relationship between the L2 switches is detected from the acquired information (step S1903). In this process, first, a table for writing the port and its connection destination is prepared for each L2 switch. Next, the designated bridge on the line is registered as a connection destination in the row of the port where the designated bridge on the line to which each port is connected is another switch. At this time, the connection destination port can also be specified by examining the lower 8 bits of the port identifier. FIG. 19A shows a table obtained in the case of FIG. 14 as an example of the table to which the information on the designated bridge is added. Then, the connection source is added as a connection destination to the row corresponding to the port registered as the connection destination in the table of FIG. 19 (a). FIG. 19 (b) shows a table in which connection destinations are newly added to FIG. 19 (a).

  Finally, the connection relationship between the end devices is detected using the same method as in the fifth embodiment (step S1904). At this time, it is not necessary to refer to the traffic of a port whose connection relation has already been found. In the example of FIG. 14, the traffic of B11, B13, and B21 may not be referred to.

  As described above, the connection relationship in the sub-network can be detected.

  In the method of the fifth embodiment, when there is a redundant configuration such as a loop, only the connection relation used for communication is detected, and the connection relation not used for communication is not detected. As an example in which the connection relationship is not detected, a case as shown in FIG. 20 can be considered. In FIG. 20, B14 represents a port of the L2 switch B1, and B24 represents a port of the L2 switch B2. Since the connection between B14 and B24 is redundant to the connection between B13 and B21, it is not normally used for communication. For this reason, for example, when the ping command is executed for the L2 switch B2, the traffic of the ports B14 and B24 does not increase. Therefore, the connection relationship between B14 and B24 cannot be detected simply by referring to the port traffic as in the fifth embodiment. However, when each L2 switch is compatible with dot1dStpPortTable, it is possible to detect such a connection relationship by using the method of the sixth embodiment.

1 is a diagram showing a first embodiment of the present invention, which is an example showing an operation of a function for clarifying an IP address used on a management target IP network in a configuration example of a network that is a management target of the system integrated management system. FIG. is there. It is a figure which shows Embodiment 1 of this invention, and is a flowchart which shows the detail of operation | movement in FIG. It is a figure which shows Embodiment 2 of this invention, and is an example which shows operation | movement of the function which determines the classification of an apparatus in the structural example of the network used as the management object of a system integrated management system. It is a figure which shows Embodiment 2 of this invention, and is a flowchart which shows the detail of operation | movement in FIG. It is a figure which shows Embodiment 3 of this invention, and is an example which shows the operation | movement of the function which determines the classification of the apparatus which estimates the connection relationship of a subnetwork in the structural example of the network used as the management object of a system integrated management system. It is a figure which shows Embodiment 4 of this invention, and is an example which shows operation | movement of the function which detects the apparatus contained in a subnetwork in the structural example of the network used as the management object of a system integrated management system. It is a figure which shows Embodiment 4 of this invention, and is a figure which shows the example of the item contained in ipNetToMediaTable. It is a figure which shows Embodiment 5 of this invention, and is an example which shows operation | movement of the function which estimates the connection relation of the apparatus in the subnetwork used for communication in the structural example of the network used as the management object of a system integrated management system. . It is a figure which shows Embodiment 5 of this invention, and is an operation | movement flowchart of FIG. It is a figure which shows Embodiment 5 of this invention, and is a figure which shows the list of the ports which pass. It is a figure which shows Embodiment 5 of this invention, and is a figure which shows the example of the list of the ports which pass immediately before. It is a figure which shows Embodiment 5 of this invention, and is a figure which shows the example of the connection relation of a terminal device. It is a figure which shows Embodiment 5 of this invention, and is a figure which shows the example of the connection relation of L2 switch. The figure which shows Embodiment 6 of this invention, and the example which shows the operation | movement of the function which detects a connection relationship more correctly by combining the information of a spanning tree in the structural example of the network used as the management object of a system integrated management system. It is. It is a figure which shows Embodiment 6 of this invention, and is a figure which shows the example of a bridge identifier and a port identifier. It is a figure which shows Embodiment 6 of this invention, and is a flowchart which shows the operation example of FIG. It is a figure which shows Embodiment 6 of this invention, and is a flowchart which shows the operation example of FIG. It is a figure which shows Embodiment 6 of this invention, and is a figure which shows the example of the information acquired in FIG. It is a figure which shows Embodiment 6 of this invention, and is a figure which shows the example of a connecting point. It is a figure which shows Embodiment 6 of this invention, and is a figure which shows the example in case the above-mentioned Embodiment 5 cannot be used but Embodiment 6 can be used. It is a block diagram which shows the general structural example of the network used as the management object of a system total management system. It is a figure explaining the subject in the structure of the network used as the management object of the conventional system integrated management system. It is a figure explaining the subject in the structure of the network used as the management object of the conventional system integrated management system.

Explanation of symbols

1 system total management server,
2 IP network part
201 L3 switch R1,
202 L3 switch R2,
203 L3 switch R3,
204 L3 switch R4,
205 subnetworks,
206 Terminal equipment,
207 subnetwork,
208 network management server,
209 Wide area monitoring and control server,
3 Subnetwork,
301 L2 switch B1,
302 L2 switch B2,
303 Terminal equipment E1,
304 Terminal equipment E2,
305 Terminal equipment E3,
4 System managed network.

Claims (5)

  It is possible to estimate and display the cause of an abnormality / failure event by considering the current state of the IP network when an abnormality / failure event occurs in a wide-area monitoring control system, or by linking with information of a non-IP network management device such as SDH. A comprehensive system management system that has a function to detect the IP address used in the IP network part on the managed network by examining the response to the ping command. system.   The system integrated management system according to claim 1, wherein the function of determining the type of the device using the IP address by acquiring MIB information from the device using the IP address using SNMP. System management system characterized by   3. The system comprehensive management system according to claim 2, wherein a function of detecting a connection relationship between the L3 switch in the IP network and the sub-network is obtained by acquiring the IP address and subnet mask of the port using SNMP. System comprehensive management system characterized by that.   4. The system integrated management system according to claim 3, wherein the system integrated management system has a function of detecting devices belonging to the sub-network by acquiring port information using SNMP. .   5. The system overall management system according to claim 4, wherein the number of received packets for each port is increased using ICMP, and the change in the number of received packets for each port is examined using SNMP to connect devices in the sub-network. A system comprehensive management system characterized by having a function of detecting a relationship.

Images