JP6871804B2 - Network configuration survey device, network configuration survey program, and network configuration survey method - Google Patents

Description

The present invention relates to the investigation of network configuration.

Conventionally, a system for monitoring a device via a network has been known in order to recognize the state of a device connected to the network or a failure that has occurred in the device. For example, Patent Document 1 describes a subsystem composed of a plurality of monitored devices having an SNMP (Simple Network Management Protocol) agent function connected to a network and a lower monitoring device having an SNMP manager function for managing them. , The system is configured with the upper monitoring device that manages these multiple subsystems, each lower monitoring device monitors the status of the monitored device in the subsystem, and only the failure occurrence and status change are transferred to the upper monitoring device. Is disclosed.

Japanese Unexamined Patent Publication No. 2014-6829

By the way, when displaying the status of the monitored device, if the configuration of the network to which the monitored device is connected is also displayed, the display will be easier for the user to understand. For that purpose, it is necessary to investigate the network configuration and the devices connected to the network.

An object of the present invention is to investigate the configuration of a network and the devices connected to the network in a relatively short time.

The network configuration investigation device according to one aspect of the present invention issues a routing information acquisition command for an agent that is operating in a device whose type is a computer and a device investigation unit that investigates the type of each device on the network. When it is transmitted and the acquisition of the routing information is successful, the contents of the routing information are registered in the routing information table, and network configuration information indicating the relationship between the plurality of devices on the network is generated based on the routing information table. It has a network research department.

According to the present invention, the network configuration and the devices connected to the network can be investigated in a relatively short time.

The schematic diagram which shows an example of the network configuration which concerns on Embodiments 1 and 2. The block diagram which shows the configuration example of the network configuration investigation apparatus which concerns on Embodiment 1. FIG. A table diagram showing an example of a device information table. The flowchart which shows the output process of the device information file which concerns on Embodiment 1. The block diagram which shows the configuration example of the network configuration investigation apparatus which concerns on Embodiment 2. FIG. The table figure which shows the example of the PING investigation table. A table diagram showing an example of a routing information table. A table diagram showing an example of a GW (Gateway) information table. A table diagram showing an example of a router information table. The table diagram which shows the example of the HUB information table. A table diagram showing an example of a monitored device table. A table diagram showing an example of a non-monitored device table. A table diagram showing an example of a network configuration information file. The flowchart which shows the output process of the network configuration information file which concerns on Embodiment 2. FIG. 14 is a continuation flowchart of FIG. FIG. 15 is a continuation flowchart of FIG. FIG. 16 is a continuation flowchart of FIG. FIG. 17 is a continuation flowchart of FIG. FIG. 18 is a continuation flowchart of FIG. FIG. 19 is a continuation flowchart of FIG. FIG. 20 is a continuation flowchart of FIG. The figure which shows the information used for the determination of an address. The block diagram which shows the example of the hardware configuration of the network configuration investigation apparatus which concerns on this invention.

Hereinafter, embodiments will be described with reference to the drawings.

(Embodiment 1)
<Overview>
First, the outline of the first embodiment will be described with reference to the network configuration example shown in FIG.

The network configuration survey device 10 surveys the network configuration and the devices connected to the network, and outputs the survey results as a device information file 103 (see FIG. 2). In the case of the network configuration shown in FIG. 1, the network configuration investigation device 10 includes the device names of Rower1, Gateway1, Client1 (own device 10), Server1, Printer1, Printer2, Gateway2, Route2, and Client3 (PC), and the device names of Client3 (PC). The device information file 103 (see FIG. 2) including the IP address set in the device (hereinafter, simply referred to as “address”) is output. Hereinafter, a detailed description will be given. Although the intelligent HUB (hereinafter referred to as "HUB") is not shown in FIG. 1, the HUB may be arranged on the network.

<Structure>
Next, the configuration of the network configuration survey device will be described with reference to FIG. The network configuration survey device 10 includes a file reading unit 20, a PING survey unit 21, a device survey unit 22, a device information file generation unit 23, an address survey range setting file 101, a PING survey table 300, and an additional device table. It includes 102 and a device information table 200, and outputs a device information file 103.

As shown in FIG. 3, the device information table 200 includes a device name 201 which is a device name, a device type 202 which is a device type of the device name 201, and an address 203 set in the device of the device name 201. , Manages records including polling 204 indicating whether the device with device name 201 supports SNMP polling, and trap 205 indicating whether the device with device name 201 supports SNMP traps. To do. The additional device table 102 has the same configuration as the device information table 200.

The file reading unit 20 reads the following device information file 103 into the device information table 200.

The PING investigation unit 21 transmits a PING to an address within the range of each segment (see FIG. 1) preset in the address investigation range setting file 101, and sends a PING response (ICMP) to the address returned. Register in the PING survey table 300. The details of the processing of the PING investigation unit 21 will be described later with reference to the flowchart of FIG. The details of the PING survey table 300 will be described later with reference to FIG. 6 in the second embodiment (see FIG. 6).

The device survey unit 22 specifies the type of device at the address 301 registered in the PING survey table 300. Further, when the device investigation unit 22 newly detects a device that is not recorded in the previous device information file, the device investigation unit 22 registers the newly detected device in the additional device table 102. The details of the processing of the device investigation unit 22 will be described later with reference to the flowchart of FIG.

The device information file generation unit 23 together outputs the device information registered in the device information table 200 and the additional device table 102 as the device information file 103.

<Flowchart>
Next, the flow of processing until the device information file 103 is output will be described with reference to the flowchart of FIG.

First, the file reading unit 20 reads the previous device information file 103 into the device information table 200 (ST100).

Next, the PING investigation unit 21 transmits an echo request (PING request) related to ICMP to an address within each segment range preset in the address investigation range setting file 101 (ST101). At this time, the PING investigation unit 21 transmits an echo request to each address by multithread processing in order to shorten the processing time required for ST101.

Next, the PING investigation unit 21 executes the following processes from ST102 to ST110 (hereinafter referred to as “LOOP1”) for each address to which PING is transmitted in ST101. In the description of LOOP1, the address to be processed is referred to as a "target address".

The PING investigation unit 21 determines whether or not there is an echo response related to ICMP from the target address (ST102). If the determination result of ST102 is "NO", the PING investigation unit 21 advances the process to the next LOOP1.

When the determination result of ST102 is "YES", the device investigation unit (SNMP manager) 22 specifies the OID (ObjectID) corresponding to the device information in the MIB (Management Information Base) tree for the target address, and specifies the SNMP. Send a GetRequest message according to (ST103).

Next, the device investigation unit 22 determines the type of the device at the target address (referred to as “target device”) by using the device information returned from the device at the target address in response to the GetRequest message of ST103 (ST104). .. The device information includes information corresponding to items 201 to 205 of the device information table 200.

(A1) Hereinafter, a case where the device investigation unit 22 succeeds in receiving the device information and the determination result of ST104 based on the device information is “router, printer or HUB” will be described.

The device investigation unit 22 determines whether or not the target device is not registered in the device information table 200 (that is, is a newly detected device) (ST105). If the determination result of ST105 is "NO", the equipment investigation unit 22 advances the processing to the next LOOP1. When the determination result of ST105 is "YES", the device investigation unit 22 adds the device information of the target device to the additional device table 102 (ST106), and proceeds to the next LOOP1.

(A2) Hereinafter, a case where the device investigation unit 22 fails to receive the device information or the determination result of ST104 based on the received device information is “unknown” will be described.

The device investigation unit 22 transmits a command for acquiring device information for the agent to the target address (ST107). Here, the agent is a predetermined program running on a PC, and when it receives a command to acquire the device information, it returns various information held by its own PC. Next, the device investigation unit 22 determines the type of the target device by using the response information to the acquisition command for the agent transmitted in ST107 (ST108).

(B1) Hereinafter, a case where the device investigation unit 22 succeeds in receiving the response information for the acquisition command for the agent and the determination result of ST108 based on the response information is “server or client” will be described.

The device investigation unit 22 determines whether or not the target device is not registered in the device information table 200 (that is, is a newly detected device) (ST109). If the determination result of ST109 is "NO", the equipment investigation unit 22 advances the processing to the next LOOP1. When the determination result of ST109 is "YES", the device investigation unit 22 adds the device information of the target device to the additional device table 102 (ST110), and proceeds to the next LOOP1.

(B2) Hereinafter, a case where the device investigation unit 22 fails to receive the response information for the acquisition command for the agent, or the determination result of ST108 based on the received response information is “unknown” will be described. In this case, the equipment investigation unit 22 advances the processing to the next LOOP1.

After all the processing of LOOP1 is completed, the device information file generation unit 23 determines whether or not a record is registered in the additional device table 102 (ST111). When the determination result of ST111 is "NO", the device information file generation unit 23 outputs the contents of the device information table 200 as the device information file 103 (ST113), and ends this process. When the determination result of ST111 is "YES", the device information file generation unit 23 adds the record of the additional device table 102 to the device information table 200 (ST112), and then adds the contents of the device information table 200 to the device information. It is output as a file 103 (ST113), and this process is terminated.

<Effect>
By the above processing, the network configuration investigation device 10 automatically detects the device connected to the network, and provides various information (device name 201, device type 202, address 203, etc.) of the detected device to the device information. It can be output to file 103.

(Embodiment 2)
<Overview>
In the second embodiment, the network configuration is investigated using the device information file 103 output by the process described in the first embodiment, and the network configuration information file is output. Specifically, in the case of the network configuration shown in FIG. 1, in the network configuration investigation device 10, the upper part of Route1 is connected to the Internet, Gateway1 is connected to the lower part of Route1, and Client1 and Service1 are connected to the lower part of Gateway1. , Internet1, Printer2, Gateway2, and Route2 are connected, Client2 is connected below Gateway2, and Clinent3 is connected below Router2, and a network configuration information file indicating that the network configuration information file is output is output. Hereinafter, a detailed description will be given. Although HUB is not shown in FIG. 1, HUB may be arranged on the network.

As shown in FIG. 5, the network configuration investigation device 10 includes the network investigation unit 32 and the HUB investigation unit in addition to the functions 20, 21, 22, 23 and the data 101, 102, 103, 200, 300 shown in FIG. A network configuration information file including 33, a network configuration information generation unit 34, a GW information table 340, a router information table 360, a HUB information table 380, a monitored device table 400, and a non-monitored device table 420. Output 500. First, each data 300, 320, 340, 380, 400, 420, 500 will be described, and then each function 32, 33, 34 will be described.

<Data>
Next, the PING survey table 300 will be described with reference to FIG. The PING investigation table 300 manages a record including the address 301 that returned the echo response, the monitoring target flag 302 indicating whether or not the device at the address 301 is the monitoring target, and the MAC address 303 of the device at the address 301. .. The monitoring target flag 302 indicates, for example, that "0" is a monitoring target, "1" is a non-monitoring target, and "2" is a monitoring target GW.

Next, the routing information table 320 will be described with reference to FIG. 7. The routing information table 320 contains a record including a destination 321 and a subnet mask 322 for the destination 321, a GW address 323 at the destination 321 and a GW confirmation flag 324 indicating whether or not the processing related to the GW address 323 is confirmed. to manage. The GW confirmation flag 324 indicates, for example, that "0" is unconfirmed and "1" is confirmed.

Next, the GW information table 340 will be described with reference to FIG. The GW information table 340 manages a record including the device name 341 of the GW and one or more addresses 342a and 342b set in the GW of the device name 341. The GW information table 340 is used when creating the router information table 360 described later.

Next, the router information table 360 will be described with reference to FIG. The router information table 360 shows whether or not the processing for the device name 361 of the router, the router address 362 of the device name 361, the upper address 363 and the lower address 364 set in the device name 361, and the device name 361 is completed. The completion flag 365 indicating the above and the record including the completion flag 365 are managed.

Next, the HUB information table 380 will be described with reference to FIG. The HUB information table 380 manages a record including the HUB port number 381, the MAC address 382 of the device connected to the HUB port number 381, and the device name 383 of the device having the MAC address 382. The HUB information table 380 is generated for each HUB.

Next, the monitored device table 400 will be described with reference to FIG. The monitored device table 400 is a starting point in the network configuration of the device name 401 of the device to be monitored, the device type 402 of the device name 401, the device address 403 of the device name 401, and the device name 401. A record including 404 and the power state 405 of the device with the device name 401 is managed. A device name, the Internet, or the like is registered at the starting point 404.

Next, the non-monitoring target device table 420 will be described with reference to FIG. The non-monitoring target device table 420 shows the device name 421 of the non-monitoring target device, the device type 422 of the device with the device name 421, the address 423 of the device with the device name 421, and the network configuration of the device with the device name 421. The record including the starting point 424 in the above and the power supply state 425 of the device with the device name 421 is managed. The device name or the Internet is registered at the starting point 424.

Next, the network configuration information file 500 will be described with reference to FIG. The network configuration information file 500 is a file in which the records of the monitored device table 400 and the non-monitored device table 420 are combined and output to a file. Therefore, each item 501 to 505 of the network configuration information file 500 is the same as each item 401 to 405 (or 421 to 425) of the monitored device table 400 (or the non-monitored device table 420).

<Function>
The device survey unit 22 investigates whether or not the device at address 301 of the PING survey table 300 is the monitoring target and the MAC address of the device, and registers the device in the PING survey table 300. The details of the processing of the device investigation unit 22 will be described later with reference to the flowcharts of FIGS. 14 to 21 (mainly FIG. 14).

The network investigation unit 32 investigates the network configuration using the routing information table 320, the GW information table 340, and the router information table 360, and registers the investigation results in the monitored device table 400 and the non-monitored device table 420. To do. The details of the processing of the network investigation unit 32 will be described later with reference to the flowcharts of FIGS. 14 to 21.

The HUB investigation unit 33 inquires of the intelligent HUB connected to the network by SNMP message or the like, investigates each device connected to the HUB, and obtains the investigation result (HUB port number, MAC address, etc.). Register in the HUB information table 380. Then, the HUB investigation unit 33 uses the contents of the HUB information table 380 to identify the devices whose starting points 404 and 323 of the monitored / non-monitored device tables 400 and 420 are set to HUB. The details of the processing of the HUB investigation unit 33 will be described later with reference to the flowcharts of FIGS. 14 to 21 (mainly FIG. 20).

The network configuration information generation unit 34 combines the records of both the monitored device table 400 and the non-monitored device table 420 and outputs the records to the network configuration information file 500. The details of the processing of the network configuration information generation unit 34 will be described later with reference to the flowcharts of FIGS. 14 to 21 (mainly FIG. 21).

<Flowchart>
Hereinafter, the flow of processing until the network configuration information file is output will be described with reference to the flowcharts of FIGS. 14 to 21.

First, the process shown in FIG. 14 will be described.

The file reading unit 20 reads the information of the monitored device among the devices recorded in the device information file 103 (see FIG. 2) into the monitored device table 400, and the non-monitored device (for example, the device type is GW). Or the information of the unknown device) is read into the non-monitored device table 420 (ST301).

Next, the file reading unit 20 reads the device name and address of the device type "router" among the devices recorded in the device information file 103 into the router information table 360 (ST302).

Next, the PING investigation unit 21 transmits an echo request (PING request) to an address within each segment range preset in the address investigation range setting file 101 (see FIG. 2) (ST303). At this time, the PING investigation unit 21 transmits an echo request to each address by multithread processing in order to shorten the processing time required for ST303.

Next, the PING investigation unit 21 registers the address that returned the echo response in the PING investigation table 300 (ST304). At this time, in the PING investigation table 300, the device investigation unit 22 sets the monitoring target flag 302 to "0" when the device at the address 301 is the monitoring target, and monitors the device at the address 301 when the device is the non-monitoring target. Register "1" in the flag 302.

Next, the network configuration survey device 10 executes the following processes from ST305 to ST310 (referred to as "LOOP2") for each address 301 registered in the PING survey table 300. In the description of LOOP2, the processing target address 301 of the PING search table 300 is referred to as a “target address”.

Next, the device investigation unit 22 investigates the MAC address of the device of the target address and registers it in the PING investigation table 300 (ST305).

Next, the network investigation unit 32 determines whether or not the device at the target address (referred to as the “target device”) is the monitoring target and the device type of the target device is “PC” (ST306). If the determination result of ST306 is "NO", the network investigation unit 32 advances the process to the next LOOP2.

When the determination result of ST306 is "YES", the network investigation unit 32 transmits a command for acquiring routing information for the agent to the target device (that is, a PC) (ST307).

The network investigation unit 32 determines whether or not the response to the acquisition command of ST307 has been successfully received (ST308).

When the determination result of ST308 is "YES", the network investigation unit 32 registers the contents of the routing information acquired by the response in the destination 321 of the routing information table 320, the subnet mask 322, and the GW address 323. Further, the network investigation unit 32 registers "0" in the GW confirmation flag 324 (ST309). Then, the network investigation unit 32 advances the processing to the next LOOP2.

When the determination result of ST308 is "NO", the network investigation unit 32 registers the information of the target device in the device name 401, device type 402, and address 403 of the monitored device table 400. Further, the network investigation unit 32 registers "OFF" in the power supply state 405 (ST310). Then, the network investigation unit 32 advances the processing to the next LOOP2.

After all the processing of LOOP2 is completed, the network investigation unit 32 deletes the record of the address 423 that is not registered in the PING investigation table 300 from the non-monitoring target device table 420 (ST311). Then, the network configuration investigation device 10 advances the process to "A" shown in FIG.

Next, the continuation of the process of FIG. 14 will be described with reference to FIG.

The network investigation unit 32 executes the following processes from ST321 to ST3341 (referred to as “LOOP3”) for each record registered in the routing information table 320. In the description of LOOP3, the record to be processed in the routing information table 320 is referred to as a "target record".

The network investigation unit 32 determines whether or not the destination 321 of the target record is "0.0.0.0" (ST321).

(C1) Hereinafter, processing when the determination result of ST321 is “YES” will be described.

The network investigation unit 32 determines whether or not the GW address 323 of the target record belongs to the same segment as its own network configuration investigation device 10 (ST322). When the determination result of ST322 is "NO", the network investigation unit 32 deletes the target record from the routing information table 320 (ST323), and proceeds to the process to ST340.

When the determination result of ST322 is "YES", the network investigation unit 32 sets the device name corresponding to the GW address 323 of the target record and the GW for the device name 361 and the lower address 364 of the router information table 360, respectively. Register the address 323. Further, the network investigation unit 32 identifies the address 301 of the PING investigation table 300 which is the same as the GW address 323 of the target record, and changes the monitoring target flag 302 associated with the specified address 301 to "2". To do. Further, the network investigation unit 32 changes the GW confirmation flag 324 of the target record to "1" (ST324). Then, the network investigation unit 32 advances the processing to ST340.

(C2) Hereinafter, processing when the determination result of ST321 is "NO" will be described.

In the routing information table 320, when the destination 321 is the same segment as the destination 321 of the target record and there is another record in which the GW confirmation flag 324 is "0", the network investigation unit 32 determines the other record. And the GW confirmation flag 324 of the target record (referred to as "record of the same segment") is changed to "1" (ST331).

Next, the network investigation unit 32 determines whether or not the record of the same segment is registered in the router information table 360 (ST332). If the determination result of ST332 is "YES", the network investigation unit 32 advances the process to the next LOOP3.

When the determination result of ST332 is "NO", the network investigation unit 32 registers the device name of the GW address 323 of the target record in the device name 361 of the router information table 360. Further, the network investigation unit 32 identifies the address 301 of the PING investigation table 300 that matches the GW address 323 of the target record, and changes the monitoring target flag associated with the specified address 301 to "2". Further, the network investigation unit 32 registers the device name and the GW address 323 of the GW address 323 of the target record in the device name 341 and the address 342 of the GW information table 340 (ST333). Then, the network investigation unit 32 advances the processing to ST340.

(C3) Hereinafter, the processing after ST340 will be described.

The network investigation unit 32 determines whether or not the GW address 323 of the target record exists at the address 301 of the PING investigation table 300 (ST340). If the determination result of ST340 is "YES", the network investigation unit 32 proceeds to the next LOOP3.

When the determination result of ST340 is "NO", the network investigation unit 32 sets the device name corresponding to the GW address 323 of the target record, the device type of the device with the device name, and the GW address 323 to the non-monitoring target device table 420. It is registered in the device name 421, the device type 422, and the address 423 (ST341). Then, the network investigation unit 32 advances the processing to the next LOOP3.

After all the processing of LOOP3 is completed, the network investigation unit 32 advances the processing to "B" shown in FIG.

Next, the continuation of the process of FIG. 15 will be described with reference to FIG.

The network investigation unit 32 determines whether or not any of the GW addresses 323 whose GW confirmation flag 324 in the routing information table 320 is "0" matches the address 301 of the PING investigation table 300 (ST361). .. If the determination result of ST361 is "NO", the network investigation unit 32 advances the process to ST371.

When the determination result of ST361 is "YES", the network investigation unit 32 registers the device name of the GW address 323 that matches in ST361 in the device name 361 of the router information table 360. Further, the network investigation unit 32 changes the monitoring target flag associated with the address 301 matched in ST361 to "2" in the PING investigation table 300. Further, the network investigation unit 32 registers the GW address 323 matched in ST361 in the address 342 associated with the device name 341 of the GW address 323 matched in ST361 of the GW information table 340. Further, the network investigation unit 32 changes the GW confirmation flag 324 associated with the GW address 323 matched in ST361 to "1" in the routing information table 320 (ST362). Then, the network investigation unit 32 advances the processing to ST371.

Hereinafter, the processing after ST371 will be described.

The network investigation unit 32 determines whether or not there is a destination 321 whose GW confirmation flag 324 is "0" in the routing information table 320 whose segment matches the address 301 of the PING investigation table 300 (ST371). ). When the determination result of ST371 is "NO", the network investigation unit 32 advances the process to "C" shown in FIG.

When the determination result of ST371 is "YES", the network investigation unit 32 registers the device name of the GW address 323 associated with the destination 321 matched in ST371 in the device name 361 of the router information table 360. Further, the network investigation unit 32 registers the device name of the GW address 323 and the GW address 323 associated with the destination 321 matched in ST371 in the device name 341 and the address 342 of the GW information table 340. Further, the network investigation unit 32 changes the GW confirmation flag 324 associated with the destination 321 matched in ST371 to "1" in the routing information table 320 (ST372). Then, the network investigation unit 32 advances the processing to “C” shown in FIG.

Next, the continuation of the process of FIG. 16 will be described with reference to FIG.

The network investigation unit 32 performs the following ST401 to ST412 processing (referred to as "LOOP4") for each record in which the router address 362 belongs to the same segment as its own network configuration investigation device 10 in the router information table 360. Execute. In the description of LOOP4, the record to be processed in the router information table 360 is referred to as a "target record".

The network investigation unit 32 determines whether or not the completion flag 365 of the target record is “0” (ST401). If the determination result of ST401 is "NO", the network investigation unit 32 proceeds to the next LOOP4. When the determination result of ST401 is "YES", the network investigation unit 32 determines whether or not the device name 361 of the target record is "router" (ST402).

(D1) Hereinafter, the case where the determination result of ST402 is “YES” will be described.

The network investigation unit 32 acquires the information of the router (referred to as “target router”) of the target record by using the SNMP command (ST403). The router information includes at least the addresses set for each network interface of the target router.

Next, the network investigation unit 32 determines whether or not the address on the Internet side is set in the target router based on the router information acquired in ST403 (ST404). For example, when the address other than the address shown in FIG. 22 is set, the network investigation unit 32 determines that the address on the Internet side is set.

When the determination result of ST404 is "YES", the network investigation unit 32 registers "Internet" in the upper address 363, the router address 362 in the lower address 364, and "1" in the completion flag 365 in the target record ( ST405). Then, the network investigation unit 32 advances the processing to the next LOOP4.

When the determination result of ST404 is "NO", the network investigation unit 32 sets the router address 362 as the upper address 363 and the router address on the other segment side included in the router information as the lower address 364 in the target record as a completion flag. Register "1" in 365 (ST406).

Next, the network investigation unit 32 deletes a record whose address 423 matches the router address on the other segment side from the PING investigation table 300 and the non-monitoring target device table 420 (ST407).

Next, the network investigation unit 32 determines whether or not there is a record of a router belonging to the same segment as the router address on the other segment side in the router information table 360 (ST413). When the determination result of ST413 is "YES", the network investigation unit 32 executes the process from ST401 for the record determined to belong to the same segment in ST408. If the determination result of ST413 is "NO", the network investigation unit 32 advances the process to the next LOOP4.

(D2) Hereinafter, the case where the determination result of ST402 is "NO" will be described.

The network investigation unit 32 determines whether or not a record exists in the GW information table 340 (ST411). If the determination result of ST411 is "NO", the network investigation unit 32 advances the process to the next LOOP4.

When the determination result of ST411 is "YES", the network investigation unit 32 identifies an address 342 belonging to the same segment as the default GW address of the network configuration investigation device 10 from the GW information table 340, and targets the specified address 342. Register at the upper address 363 of the record. Further, the network configuration investigation device 10 registers the other address associated with the address specified above in the GW information table 340 in the lower address 364 of the target record. Further, the network investigation unit 32 changes the completion flag 365 of the target record to "1". Further, the network investigation unit 32 registers the above-mentioned upper address 363 at the address 423 of the corresponding device name 421 in the non-monitoring target device table 420. Then, the network investigation unit 32 advances the processing to the above-mentioned ST413 (ST412).

After all the processing of LOOP4 is completed, the network investigation unit 32 advances the processing to "D" shown in FIG.

Next, the continuation of the process of FIG. 17 will be described with reference to FIG.

The network investigation unit 32 executes the following ST421 to ST431 processes (referred to as “LOOP5”) for each record in which the completion flag 365 is “0” and the device name 361 is “GW” in the router information table 360. In the description of LOOP5, the record to be processed in the router information table 360 is referred to as a "target record". Further, the device name 361 of the target record in the router information table 360 is referred to as the target device name 361.

The network investigation unit 32 determines whether or not the record of the completion flag 365 “0” and the device name 365 “router” exists in the router information table 360 (ST421).

(E1) Hereinafter, the case where the determination result of ST421 is “YES” will be described.

The network investigation unit 32 registers the device name 361 of the router in ST421 at the upper address 361 of the target record. Further, the network investigation unit 32 registers the address 342 of the device name 341, which is the same as the target device name 361 of the GW information table 340, in the lower address 364 of the target record. Further, the network investigation unit 32 changes the completion flag 365 of the target record to "1". Further, the network investigation unit 32 registers the lower address 364 at the address 423 associated with the same device name 421 as the target device name 361 in the non-monitoring target device table 420 (ST422). Then, the network investigation unit 32 advances the processing to the next LOOP 5.

(E2) Hereinafter, the case where the determination result of ST421 is “NO” will be described.

The network investigation unit 32 identifies the device name 341 of the GW information table 340 which is the same as the target device name 361, and registers the address 342 associated with the specified device name 341 in the lower address 364. Further, the network investigation unit 32 changes the completion flag 365 of the target record to "1". Further, the network investigation unit 32 identifies the device name 421 of the non-monitoring target device table 420 which is the same as the target device name 361, and registers the lower address 364 at the address 423 associated with the specified device name 421. (ST423). Then, the network investigation unit 32 advances the processing to the next LOOP 5.

After all the processing of LOOP5 is completed, the network investigation unit 32 processes the following ST431 (“LOOP6”” for each record in which the completion flag 365 of the router information table 360 is “0” and the device name 361 is “router”. ) Is executed. In the description of LOOP6, the record to be processed in the router information table 360 is referred to as a "target record".

The network investigation unit 32 registers "Internet" at the upper address 363 of the target record. Further, the network investigation unit 32 registers the router address 362 of the target record in the lower address 364 of the target record. Further, the network investigation unit 32 changes the completion flag 365 of the target record to "1" (ST431). Then, the network investigation unit 32 advances the processing to the next LOOP6.

After all the processing of LOOP6 is completed, the network investigation unit 32 advances the processing to "E" shown in FIG.

Next, the continuation of the process of FIG. 18 will be described with reference to FIG.

The network investigation unit 32 executes the following ST501 to ST531 processes (referred to as “LOOP7”) for each record of the monitored device table 400 and the non-monitored device table 420. In the description of LOOP 7, the record to be processed in the monitored device table 400 and the non-monitored device table 420 is referred to as a “target record”. Further, the device names 401 and 421 of the target record are referred to as "target device names".

The network investigation unit 32 determines the type of the device of the target record from the device types 402 and 422 of the target record (ST501).

(F1) Hereinafter, the case where the determination result of ST501 is “router” will be described.

The network investigation unit 32 determines whether or not the upper address 363 associated with the same device name 361 as the target device names 401 and 421 in the router information table 360 is "Internet" (ST502).

When the determination result of ST502 is "YES", the network investigation unit 32 registers "Internet" at the starting point 404 of the target record (ST503). Then, the network investigation unit 32 advances the processing to the next LOOP 7.

When the determination result of ST502 is "NO", the network investigation unit 32 finds that the target device names 401 and 421 and the device name 361 match from the router information table 360, and the addresses 403 and 423 of the target device names 401 and 421. Identifies a subordinate address 364 with the same segment as. Then, the network investigation unit 32 registers the specified lower address 364 at the starting point 404 of the target record (ST504). Then, the network investigation unit 32 advances the processing to the next LOOP 7.

(F2) Hereinafter, the case where the determination result of ST501 is “PC, printer or HUB” will be described.

From the router information table 360, the network investigation unit 32 identifies a lower address 364 having the same segment as the addresses 403 and 423 of the target device names 401 and 421. Then, the network investigation unit 32 registers the specified lower address 364 at the starting point 404 of the target record (ST511). Then, the network investigation unit 32 advances the processing to the next LOOP 7.

(F3) Hereinafter, the case where the determination result of ST501 is “GW” will be described.

If the upper address 363 is not registered in the record of the same device name 361 as the target device names 401 and 402 in the router information table 360, the network investigation unit 32 registers "Internet" at the starting point 404 of the target record and registers the upper address. When 363 is the device name of the router, the device name of the router is registered at the starting point 404 of the target record. In other cases, the network investigation unit 32 identifies the lower address 364 whose segment is the same as that of the upper address 363 from the router information table 360, and registers the specified lower address 364 in the starting point 404 of the target record ( ST521). Then, the network investigation unit 32 advances the processing to the next LOOP 7.

Hereinafter, the case where the determination result of ST501 is “other (unknown)” will be described.

When the network investigation unit 32 can identify the lower address 364 whose segment is the same as the addresses 403 and 423 of the target device names 401 and 421 from the router information table 360, the specified lower address 364 is set as the starting point 404 of the target record. sign up.

On the other hand, when the above cannot be specified, the network investigation unit 32 identifies the destination 321 having the same segment as the addresses 403 and 423 of the target device names 401 and 421 from the routing information table 320, and the non-monitoring target device table 420. Therefore, the device name 421 associated with the address 423 that matches the specified destination 321 is specified. Then, the network investigation unit 32 registers the specified device name 421 at the starting point 404 of the target record (ST531). Then, the network investigation unit 32 advances the processing to the next LOOP 7.

After all the processing of LOOP7 is completed, the network configuration investigation device 10 advances the processing to "F" shown in FIG.

Next, the continuation of the process of FIG. 19 will be described with reference to FIG.

The HUB investigation unit 33 executes the following ST601 to ST603 processes (referred to as "LOOP8") for each intelligent HUB on the network. In the description of LOOP8, the intelligent HUB to be processed is referred to as "target HUB".

The HUB investigation unit 33 acquires each HUB port number and the MAC address of the device connected to the HUB port number from the target HUB, and registers them in the HUB port number 381 and the MAC address 382 of the HUB information table 380. (ST601).

Next, the HUB investigation unit 33 identifies the MAC address 303 of the PING investigation table 300 that matches the MAC address 382, and identifies the address 301 associated with the identified MAC address 303. Then, the HUB investigation unit 33 identifies the addresses 403 and 423 of the monitored / non-monitored target device tables 400 and 420 that match the specified address 301, and the device name associated with the specified address 403 and 423. Identify 401 and 421. Then, the HUB investigation unit 33 registers the specified device names 401 and 421 in the device name 383 of the HUB information table 380 (ST602).

Next, the HUB investigation unit 33 deletes the record of the same device name 383 as the device of the starting point 404 for the target HUB from the HUB information table 380. Further, the HUB investigation unit 33 deletes another record having the same HUB port number 381 as the HUB port number 381 of the deleted record from the HUB information table 380 (ST603). Then, the HUB investigation unit 33 advances the processing to the next LOOP 8.

After all the processing of LOOP8 is completed, the HUB investigation unit 33 determines whether or not a plurality of HUBs exist (ST610).

When the determination result of ST610 is "NO", the HUB investigation unit 33 determines that the device names 401 and 421 of the monitored / non-monitored device table 400 match the device names 383 of the HUB information table 380, and the starting points 404 and 424 of the records. Let be "HUB". Then, the HUB investigation unit 33 advances the processing to “G” in FIG. 21 (ST611).

When the determination result of ST610 is "YES", the HUB investigation unit 33 executes the following ST612 processing (referred to as "LOOP9") for each HUB information table 380 in descending order of the number of registered records. In the description of LOOP 9, the HUB information table 380 to be processed is referred to as a "target HUB information table".

The HUB investigation unit 33 sets the starting point of the record in which the device names 401 and 421 of the monitored / non-monitored device tables 400 and 420 match the device name 383 of the target HUB information table 380 to correspond to the target HUB information table. HUB ". Then, the HUB investigation unit 33 advances the processing to the next LOOP 9 (ST612).

After all the processing of LOOP 9 is completed, the network configuration investigation device 10 advances the processing to "G" in FIG.

Next, the continuation of the process of FIG. 20 will be described with reference to FIG.

The network configuration information generation unit 34 determines whether or not the starting points 404 and 424 are registered in all the records of the monitored / non-monitored target device tables 400 and 420 (ST621).

When the determination result of ST621 is "NO", the network configuration information generation unit 34 outputs an error response (ST640) and ends this process.

When the determination result of ST621 is "YES", the network configuration information generation unit 34 determines whether or not the existing devices are different between the device information file 103 and the monitored device table 400 (ST622). ..

When the determination result of ST622 is "YES", the network configuration information generation unit 34 sets the update flag to "0" (ST623) and proceeds to the process to ST630.

When the determination result of ST622 is "NO", the network configuration information generation unit 34 has changed the power supply state 405 of any of the devices in the monitored device table 400 as compared with the previous network configuration information file 500. Alternatively, it is determined whether or not an unknown device has been added or deleted in the non-monitored device table 420 (ST624).

When the determination result of ST624 is "YES", the network configuration information generation unit 34 sets the update flag to "1" (ST625) and proceeds to the process to ST630.

If the determination result of ST624 is "NO", the network configuration investigation device 10 advances the process to ST631.

Hereinafter, the processing after ST630 will be described.

The network configuration information generation unit 34 outputs the update flag of ST623 or ST625, the monitored device table 400, and the non-monitored device table 420 as the network configuration information file 500 (ST630).

Next, the network configuration information generation unit 34 outputs a normal response (ST631), and ends this process.

<Effect>
By the above processing, the network configuration investigation device 10 automatically detects the network configuration related to the device connected to the network, and the information related to the detected network configuration (device names 401, 421, device type 402, 422, The address 403, 424, starting point 404, 424) can be output to the network configuration information 500.

Further, as described above, the network configuration investigation device 10 collects information on the network configuration in cooperation with the agent and / or the intelligent HUB, etc., to generate network configuration information across segments in a relatively short time. be able to.

Although the embodiments according to the present invention have been described in detail with reference to the drawings, the functions of the device 10 described above can be realized by a computer program.

FIG. 23 is a diagram showing a hardware configuration of a computer that realizes the functions of the device 10 by a program. The computer 1100 includes an input device 1101 such as a keyboard, a mouse, and a touch pad, an output device 1102 such as a display and a speaker, a CPU (Central Processing Unit) 1103, a ROM (Read Only Memory) 1104, and a RAM (Random Access Memory) 1105. A storage device 1106 such as a hard disk device or SSD (Solid State Drive), a reading device 1107 that reads information from a recording medium such as a DVD-ROM (Digital Versatile Disk Read Only Memory) or a USB (Universal Serial Bus) memory, via a network. A transmission / reception device 1108 for communication is provided, and each unit is connected by a bus 1109.

Then, the reading device 1107 reads the program from the recording medium on which the program for realizing the function of the device 10 is recorded, and stores the program in the storage device 1106. Alternatively, the transmission / reception device 1108 communicates with the server device connected to the network, and stores the program downloaded from the server device for realizing the function of each device in the storage device 1106.

Then, the CPU 1103 copies the program stored in the storage device 1106 to the RAM 1105, and sequentially reads and executes the instructions included in the program from the RAM 1105, thereby realizing the function of the device 10.

The present invention is useful for system diagnostic devices, methods, and programs that visually present the network configuration and the status of each device connected to the network.

10 Network configuration survey device 20 File reading unit 21 PING survey unit 22 Equipment survey department 23 Device information file generation unit 32 Network survey unit 33 HUB survey unit 34 Network configuration information generation unit 101 Address survey range setting file 102 Additional device table 103 Device information File 200 Device information table 300 PING survey table 320 Routing information table 340 GW (Gateway) information table 360 Router information table 380 HUB information table 400 Monitored device table 420 Non-monitored device table 500 Network configuration information file

Claims (7)

A network configuration survey device that surveys the configuration of a network to which multiple devices are connected.
The Equipment Investigation Department, which investigates the types of each equipment on the network,
When the acquisition command of the routing information for the agent operating in the device whose type is a computer is transmitted and the acquisition of the routing information is successful, the contents of the routing information are registered in the routing information table and the routing information table is registered. A network research unit that generates network configuration information indicating the relationship between the plurality of devices on the network based on
A network configuration survey device equipped with. The network research department
A first SNMP message for acquiring an address related to the network interface of the router device is transmitted to a device whose type is a router, and based on the address related to the network interface acquired by the first SNMP message. The upper address and the lower address of the router device are specified, the specified upper address and the lower address are registered in the router information table, and the network configuration information is generated based on the router information table.
The network configuration investigation device according to claim 1. Further equipped with a PING investigation unit, which sends an echo request to an address within a predetermined range and registers the address returning the echo response in the PING investigation table.
The equipment research department
A second SNMP message for acquiring device information is sent to the registered address in the PING search table, and the device information is acquired.
If the acquisition of the device information is successful, the type of the device with the registered address is specified based on the device information.
If the acquisition of the device information fails, a device information acquisition command for the agent is sent to the registered address, and the device type of the registered address is specified based on the device information acquired by the acquisition command. ,
The network configuration investigation device according to claim 1 or 2. The network contains a number of different segments.
The agent is operating in a device that belongs to a segment different from the segment to which the own device belongs.
The network investigation unit generates configuration information of the network including the plurality of different segments.
The network configuration investigation device according to any one of claims 1 to 3. A third SNMP message for acquiring the status of each port of the HUB device and the information of the device connected to each port is transmitted to the device whose type is HUB, and the third SNMP message is transmitted. The HUB investigation unit, which identifies the relationship between the plurality of devices on the network by using the information acquired by the above-mentioned device, is further provided.
The network configuration investigation device according to any one of claims 1 to 4. A network configuration survey program that investigates the configuration of a network to which multiple devices are connected.
The device investigation process for investigating the type of each device on the network and
When the acquisition command of the routing information for the agent operating in the device whose type is a computer is transmitted and the acquisition of the routing information is successful, the contents of the routing information are registered in the routing information table and the routing information table is registered. A network investigation process that generates network configuration information indicating the relationship between the plurality of devices on the network based on
A network configuration survey program that lets a computer run. This is a method of investigating the configuration of a network to which multiple devices are connected.
A device survey step for investigating the type of each device on the network, and
When the acquisition command of the routing information for the agent operating in the device whose type is a computer is transmitted and the acquisition of the routing information is successful, the contents of the routing information are registered in the routing information table and the routing information table is registered. A network survey step that generates network configuration information indicating the relationship between the plurality of devices on the network based on
Network configuration survey method.

Images