JP4714245B2 - Network visualization apparatus and method, program, and storage medium - Google Patents

Description

  The present invention relates to a technique for monitoring packets flowing on a network and assisting in identifying the cause of a network trouble.

  In order to identify the cause of a connection trouble in an IP (Internet Protocol) network, a tool for monitoring packets transmitted and received between terminals constituting the network has been proposed. Currently, one of the most common tools is Wireshark. The wire shark displays information obtained by reading packets flowing on the network as a list in units of packets. When an arbitrary packet is selected, detailed information on the packet can be browsed. This tool can be analyzed in detail, but all the information is textual information that contains many technical terms. For this reason, high skill is required to master the wire shark.

As a method of visualizing detailed packet information in an easy-to-understand manner rather than text information, a method of displaying a two-way exchange between computers as a ladder or a communication terminal placed on a concentric circle to communicate between terminals A method of displaying a state with a line segment connecting terminals placed on a circumference has been proposed. In addition, a bird's-eye view of the entire network configuration and a three-dimensional visualization method (for example, refer to Non-Patent Document 1) to make it partially easy to see in detail, or for easy understanding even when the number of terminals is large A method using a hyperbolic tree (for example, see Non-Patent Document 2) has been proposed.
Burns, C.I. M.M. , Kuo, J .; and Ng, S .; , “Ecological interface design: a new approach for visualizing network management”, Computer networks, vol. 43, pp. 369-388 (2003) Duez, P.M. P. and Victoria, K .; J. et al. "Ecological interface design for network management", Processeds of the Human Factors and Engineering Society 47th Annual Meeting, pp. 572-575 (2003)

  However, none of the methods takes into account that the visualized connection status information is associated with the configuration of a physical network wired with a cable.

  For example, in the case of a LAN (Local Area Network) configured in a home or office, a device in the LAN can be viewed as a physical terminal. Conventionally, the correspondence between visualized connection status information and devices in the LAN has not been considered. For this reason, when replacing a device for repairing a failure, it may take time to identify and check the device in the LAN.

  Therefore, an object of the present invention is to visualize network connection status information so as to be easily associated with a physical network configuration.

  In order to solve the above problems, the network visualization device according to the present invention uses the physical identifiers of the transmission source terminal and the transmission destination terminal and the logical identifiers of the transmission source terminal and the transmission destination terminal attached to the packet. Thus, the physical path of the packet is obtained.

Specifically, the network visualization device according to the present invention, from a packet transmitted and received between terminals constituting the network, a physical identifier and a logical identifier of a transmission source terminal and a transmission destination terminal of the packet, and Referring to the packet list acquisition unit for acquiring the type of protocol for packet communication and the connection status in the protocol, and the terminal list in which the physical identifier and the logical identifier are associated with the terminal identifier, the packet Determined by a pair of a terminal identifier corresponding to the physical identifier of the transmission source terminal acquired by the list acquisition unit and a terminal identifier corresponding to the physical identifier of the transmission destination terminal acquired by the packet list acquisition unit A protocol type for communication of the packet acquired by the packet list acquisition unit and the protocol And registering it as a route list corresponding to the packet together with the connection status in the packet, referring to the terminal list, and identifying the terminal identifier and the packet corresponding to the physical identifier of the transmission source terminal acquired by the packet list acquisition unit It is determined whether or not the terminal identifier corresponding to the logical identifier of the transmission source terminal acquired by the list acquisition unit is the same, and if not, the transmission source terminal acquired by the packet list acquisition unit A path defined by a pair of a terminal identifier corresponding to the physical identifier of the terminal and a terminal identifier corresponding to the logical identifier of the transmission source terminal acquired by the packet list acquisition unit, of the packet list acquisition unit The route corresponding to the packet together with the type of protocol for communication of the packet to be acquired and the connection status in the protocol Registering as a list, referring to the terminal list, the identifier of the terminal corresponding to the physical identifier of the destination terminal acquired by the packet list acquisition unit and the destination terminal acquired by the packet list acquisition unit It is determined whether or not the terminal identifier corresponding to the logical identifier is the same, and if not, the terminal identifier corresponding to the physical identifier of the destination terminal acquired by the packet list acquisition unit And a path defined by a pair of a terminal identifier corresponding to a logical identifier of the destination terminal acquired by the packet list acquisition unit, a protocol for communication of the packet acquired by the packet list acquisition unit And a route determination unit that registers the route list corresponding to the packet together with the type and the connection status in the protocol .

  Since the route determination unit searches for the physical route of the packet, information on the physical network configuration can be collected. Since the packet physical path is listed together with the protocol type and the connection status in the protocol, the network connection status information can be visualized so as to be easily associated with the physical network configuration. Become.

Further, the physical route of the packet can be searched based on the logical identifier attached to the packet. Thereby, information on the configuration of the physical network can be collected.

In the network visualization device according to the present invention, a network configuration composed of the routes registered in the route list is displayed by the route determination unit, and is registered as the route list on the route of the network configuration. It is preferable to further comprise display means for displaying the type of protocol being used and the connection status of the protocol.
In addition to displaying the physical route of the packet, the connection status in the protocol can be displayed.

The network visualization method according to the present invention includes a physical identifier and a logical identifier of the transmission source terminal and the transmission destination terminal of the packet, and communication of the packet, from the packet transmitted and received between the terminals. Packet list acquisition procedure for acquiring protocol type and connection status in the protocol,
The terminal identifier and the packet corresponding to the physical identifier of the source terminal acquired in the packet list acquisition procedure with reference to a terminal list in which a physical identifier and a logical identifier are associated with the terminal identifier A route defined by a pair with a terminal identifier corresponding to a physical identifier of the destination terminal acquired in the list acquisition procedure, a protocol type for communication of the packet acquired in the packet list acquisition procedure, and Registering as a route list corresponding to a packet together with the connection status in the protocol, referring to the terminal list, the identifier of the terminal and the packet corresponding to the physical identifier of the transmission source terminal acquired in the packet list acquisition procedure The identifier of the terminal corresponding to the logical identifier of the source terminal acquired in the list acquisition procedure is If it is not the same, the identifier of the terminal corresponding to the physical identifier of the transmission source terminal acquired in the packet list acquisition procedure and the transmission source acquired in the packet list acquisition procedure The route defined by the pair of the terminal identifier corresponding to the terminal logical identifier corresponds to the packet together with the type of protocol for communication of the packet acquired in the packet list acquisition procedure and the connection status in the protocol. Registering as a route list, referring to the terminal list, the terminal identifier corresponding to the physical identifier of the destination terminal acquired in the packet list acquisition procedure and the destination terminal acquired in the packet list acquisition procedure It is determined whether or not the terminal identifier corresponding to the logical identifier is the same. A pair of a terminal identifier corresponding to the physical identifier of the destination terminal acquired in the packet list acquisition procedure and a terminal identifier corresponding to the logical identifier of the destination terminal acquired in the packet list acquisition procedure. A route determination procedure for registering a defined route as a route list corresponding to a packet together with a type of protocol for communication of the packet acquired in the packet list acquisition procedure and a connection status in the protocol , and To do.

  Since the physical route of the packet is searched in the route determination procedure, information on the physical network configuration can be collected. Since the packet physical path is listed together with the protocol type and the connection status in the protocol, the network connection status information can be visualized so as to be easily associated with the physical network configuration. Become.

Further, the physical route of the packet can be searched based on the logical identifier attached to the packet. Thereby, information on the configuration of the physical network can be collected.

In the network visualization method according to the present invention, after the route determination procedure, a network configuration composed of routes registered as the route list is displayed, and the route list is displayed on the route of the network configuration. It is preferable to further include a display procedure for displaying the type of the registered protocol and the connection status in the protocol.
In addition to displaying the physical route of the packet, the connection status in the protocol can be displayed.

The program according to the present invention is a program for causing a computer to execute a packet list acquisition procedure and a route determination procedure or a packet list acquisition procedure, a route determination procedure and a display procedure in the network visualization method according to the present invention. The computer-readable recording medium according to the present invention is a computer-readable recording medium recording the program according to the present invention.
By installing the program according to the present invention on a computer, the computer can execute the network visualization method according to the present invention.

  According to the present invention, network connection status information can be visualized so as to be easily associated with a physical network configuration.

Embodiments of the present invention will be described with reference to the accompanying drawings. The embodiment described below is an example of the configuration of the present invention, and the present invention is not limited to the following embodiment.
FIG. 1 is a schematic configuration diagram of a network visualization device according to the present embodiment. The network visualization device 10 obtains a packet to be transmitted / received between terminals constituting the network 20 to be monitored, thereby visualizing the information on the connection status of the network so that it can be easily associated with the physical network configuration. In this embodiment, for easy understanding, a case will be described in which the network 20 to be monitored is a LAN in which a PC 21, a router 22, and a PC 23 are physically connected in series.

  The network visualization device 10 includes a packet acquisition unit 11, a packet list acquisition unit 12, a route determination unit 13, a connection status determination unit 14, a display unit 15, a terminal list storage unit 16, and a route list storage unit 17. And a packet-to-path correspondence notation unit 18. The terminal list storage unit 16, the route list storage unit 17, and the packet-to-path correspondence notation unit 18 may use a common storage unit provided in the network visualization device 10.

  The packet acquisition unit 11 acquires a packet to be transmitted / received between terminals constituting the monitoring target network. For example, in the monitoring target network 20 shown in FIG. 1, a route connecting the PC 21 and the router 22 is used as an example of an arbitrary route. In this case, the switching hub 24 is inserted in the path between the PC 21 and the router 22, a monitoring PC is connected to the switching hub 24, and packets are acquired via the network interface card of this PC. The acquired packet is sent to the packet list acquisition unit 12.

  The packet list acquisition unit 12 creates and stores a packet list for each packet acquired by the packet acquisition unit 11. The packet list includes at least a packet ID, a time, a physical identifier of a transmission source and a transmission destination, a logical identifier of a transmission source and a transmission destination, a type of protocol for packet communication, communication contents, and a connection status in the protocol. . The physical identifier can identify the PC 21, router 22, and PC 23, which are physical terminals indicated by the identifier, and may be a MAC address, for example. The logical identifier is assigned to the physical terminals PC 21, router 22, and PC 23 and can be changed. For example, an IP address, an IPX address, a URL, and a computer name are conceivable. In this embodiment, an example in which a MAC address is used as a physical identifier and an IP address is used as a logical identifier will be described as an example.

  FIG. 2 shows an example of the packet list. When a page acquisition request is transmitted from the PC 21 to the PC 23 shown in FIG. 1 using the HTTP protocol, the packet list includes a packet ID = 1, a time = 13: 01: 5 on May 19, 2008, the source terminal Physical identifier = MAC address a, physical identifier of destination terminal = MAC address b, logical identifier of source terminal = IP address A, logical identifier of destination terminal = IP address C, protocol = HTTP, communication content = “page acquisition request” is recorded. Further, when a notification of communication completion is transmitted from the PC 23 to the PC 21 shown in FIG. 1 using the HTTP protocol, the packet list includes a packet ID = 2, a time = 13: 01: 6 on May 19, 2008, Source terminal physical identifier = MAC address b, destination terminal physical identifier = MAC address a, source terminal logical identifier = IP address C, destination terminal logical identifier = IP address A, protocol = HTTP, communication content = “200 OK” are recorded.

  The route determination unit 13 determines a physical route corresponding to each packet, registers it in the route list, associates the registered route with the packet, and records them in the packet-to-route correspondence table storage unit 18 as a packet-to-route correspondence table. . In the determination of the physical route, for example, the terminal identifier corresponding to the physical identifier and the logical identifier of the transmission source terminal and the transmission destination terminal described in the packet are stored in the terminal list storage unit 16. The determination is made by selecting from the terminal list and obtaining a route defined by the pair of identifiers of the selected terminal.

  The connection status determination unit 14 determines the type of protocol corresponding to each packet and the connection status in the protocol, and the route corresponding to the packet is stored in the packet correspondence route correspondence table recorded in the packet-to-route correspondence table storage unit 18. And the connection status of the corresponding route in the route list storage unit 17 is updated.

  Based on the terminal list stored in the terminal list storage unit 16 and the route list data stored in the route list storage unit 17, the display unit 15 displays a network configuration diagram and each protocol for each route connecting terminals. Displays the connection status of. FIG. 3 shows a display example of the display unit 15.

  The terminal list storage unit 16 stores a terminal list. The terminal list is a list in which identifiers of terminals constituting the network and physical identifiers and logical identifiers of the terminals are associated with each other.

  FIG. 4 shows an example of the terminal list. The terminal identification ID = 1 as the PC 21 identifier, the MAC address = a as the physical identifier, and the IP address = A as the logical identifier are stored in association with each other. The terminal identification ID = 2 as the identifier of the router 22, the MAC address = b as the physical identifier, and the IP address = B as the logical identifier are stored in association with each other. Regarding the terminal identification ID = 3 as the identifier of the PC 23, the IP address = C is stored in association with the logical identifier. The physical identifier of the PC 23 is blank.

  The route list storage unit 17 stores a route list of the network 20 to be monitored. FIG. 5 shows an example of the route list. The route list includes at least a route ID, a pair of terminal IDs constituting the route, and a connection status of each protocol. The connection status of each protocol is, for example, a normal packet sequence of each protocol. If it cannot be determined by the sequence, it is stored as being inspected.

  The packet-to-path correspondence notation unit 18 stores a packet-to-path correspondence table indicating a path corresponding to each packet. FIG. 6 shows an example of the packet-to-path correspondence table. The packet-to-path correspondence table includes at least a packet ID and a path ID.

  FIG. 7 is a flowchart illustrating an example of a network visualization method according to the present embodiment. The network visualization method according to the present embodiment includes a packet list acquisition procedure S1, a route determination procedure, a connection status determination procedure S7, a completion confirmation procedure S8, and a display procedure S9. The route determination procedure includes steps S2, S3, S4, S5, and S6. The program according to the present embodiment is a program for causing a computer to execute the network visualization method according to the present embodiment.

  In the packet list acquisition procedure S1, the packet list acquisition unit 12 uses the physical and logical identifiers of the transmission source terminal and the transmission destination terminal of the packet and the packet communication from the packets transmitted and received between the terminals. Protocol type and connection status in the protocol are acquired, and a packet list is stored. Then, the route determination unit 13 reads the packet list stored in the packet list acquisition unit 12 for each packet in the oldest order, and proceeds to step S2.

  In step S2, the route determination unit 13 corresponds to the physical and logical identifiers of the transmission source terminal and the transmission destination terminal described in the packet as the route corresponding to the packet ID acquired by the packet list acquisition unit 12. 5 is selected from the terminal list stored in the terminal list storage unit 16 and the path defined by the selected terminal identifier pair is associated with the packet in the packet-to-path correspondence table. Register to the list.

  If it is the packet ID1 shown in FIG. 2, in step S2, the MAC address a which is the physical identifier of the transmission source and the MAC address b which is the physical identifier of the transmission destination are obtained, and these are shown in FIG. A pair of terminal ID1 and terminal ID2 corresponding to MAC addresses a and b, which are physical identifiers, is selected from the list. This pair of terminal IDs is registered as a route ID 1 in the route list shown in FIG. Then, the route ID 1 is acquired from the route list, and the packet ID 1 and the route ID 1 are associated and recorded in the packet-to-route correspondence table shown in FIG. Thereby, a route defined by a pair of terminal identifiers recorded in the route list can be registered as a route corresponding to the packet ID1. Then, it progresses to step S3.

  In step S3, the route determination unit 13 determines whether or not the physical identifier of the transmission source terminal acquired by the packet list acquisition unit 12 and the terminal identifier corresponding to the logical identifier are the same, as shown in FIG. Judgment is made from the list. If they are the same, the process proceeds to step S5.

  In the example of packet ID1 shown in FIG. 2, the logical identifier of the transmission source is IP address A in step S3. Since the physical identifier of the transmission source is the MAC address a, the IP address A is acquired as a corresponding logical identifier with reference to the terminal list shown in FIG. As a result, since the terminal ID1 indicated by the logical identifier of the transmission source of the packet ID1 and the terminal ID1 indicated by the physical identifier of the transmission source are the same, the process proceeds to step S5.

  In the example of the packet ID2 shown in FIG. 2, the logical identifier of the transmission source is the IP address C in step S3. Since the physical identifier of the transmission source is the MAC address b, the IP address B is acquired as a corresponding logical identifier with reference to the terminal list shown in FIG. As a result, since the terminal ID 3 indicated by the logical identifier of the packet ID 2 is different from the terminal ID 2 indicated by the physical identifier of the transmission source, the process proceeds to step S4.

  In the above example, whether the terminal indicated by the logical identifier of the transmission source is the same as the terminal indicated by the physical identifier of the transmission source is a logical identifier corresponding to the physical identifier of the transmission source, 4 was obtained by referring to the terminal list shown in FIG. However, there are cases in which a logical identifier corresponding to a physical identifier is not registered in the terminal list shown in FIG. In that case, the determination can be made in consideration of the restrictions of the network 20 to be monitored.

  For example, when a packet between the router 22 and the PC 21 is monitored as in the network 20 illustrated in FIG. 1, the transmission destination or transmission source indicated by the physical identifier is the PC 21 or the router 22. Since it is a LAN, these logical identifiers are local IP addresses. On the other hand, when a global IP address is specified as a logical identifier, it is estimated that the terminal indicated by the logical identifier of the transmission source is different from the terminal indicated by the physical identifier of the transmission source. It is also possible.

  In step S4, the route determination unit 13 adds, as a route corresponding to the packet, a route determined by a pair of a terminal identifier corresponding to a physical identifier and a logical identifier of the transmission source terminal to the route list. For example, in the example of the packet ID 2 shown in FIG. 2, the terminal ID 3 corresponding to the IP address C, which is a logical identifier of the transmission source, is acquired with reference to the terminal list shown in FIG. Next, with reference to the terminal list shown in FIG. 4, the terminal ID 2 corresponding to the MAC address b, which is the physical identifier of the transmission source, is acquired. A route ID 2 composed of a pair of terminal ID 2 and terminal ID 3 is registered in the route list shown in FIG. Then, the route ID 2 is acquired from the route list, and the packet ID 2 and the route ID 2 are associated and recorded in the packet-to-route correspondence table shown in FIG. Thereafter, the process proceeds to step S5.

  In step S5, the route determination unit 13 determines whether or not the physical identifier of the transmission destination terminal acquired by the packet list acquisition unit 12 and the identifier of the terminal corresponding to the logical identifier are the same, as shown in FIG. Judgment is made from the list. If they are the same, the process proceeds to the connection status judgment procedure S7, and if different, the process proceeds to step S6. When the logical identifier corresponding to the physical identifier is not registered in the terminal list shown in FIG. 4, the determination can be made in consideration of the restrictions of the network 20 to be monitored as in step S3.

  In the example of the packet ID 1 shown in FIG. 2, the logical identifier of the transmission destination is the IP address C in step S5. Since the physical identifier of the transmission destination is the MAC address b, the IP address B is acquired as the corresponding logical identifier with reference to the terminal list shown in FIG. As a result, since the terminal ID 3 indicated by the logical identifier of the transmission destination of the packet ID 1 is different from the terminal ID 2 indicated by the physical identifier of the transmission destination, the process proceeds to step S6.

  In the example of packet ID2 shown in FIG. 2, the logical identifier of the transmission destination is IP address A in step S5. Since the physical identifier of the transmission destination is the MAC address a, the IP address A is acquired as a corresponding logical identifier with reference to the terminal list shown in FIG. As a result, since the terminal ID1 indicated by the logical identifier of the transmission destination of the packet ID1 and the terminal ID1 indicated by the physical identifier of the transmission destination are the same, the process proceeds to the connection status determination procedure S7.

  In step S6, the route determination unit 13 determines a pair corresponding to the physical identifier of the transmission destination terminal and the identifier of the terminal corresponding to the logical identifier as the route corresponding to the packet ID acquired by the packet list acquisition unit 12. Add a route to the route list. For example, in the example of the packet ID 1 shown in FIG. 2, the terminal ID 3 corresponding to the IP address C, which is a logical identifier of the transmission destination, is acquired with reference to the terminal list shown in FIG. Next, with reference to the terminal list shown in FIG. 4, the terminal ID 2 corresponding to the MAC address b, which is the physical identifier of the transmission destination, is acquired. With reference to the route list shown in FIG. 5, a route ID 2 composed of a pair of terminal ID 3 and terminal ID 2 is acquired from the route list shown in FIG. Then, the packet ID 2 and the route ID 2 are associated and recorded in the packet-to-route correspondence table shown in FIG. Then, it progresses to connection condition determination procedure S7.

  In the connection status determination procedure S7, the connection status determination unit 14 determines the connection status in the protocol acquired by the packet list acquisition unit 12, and records the result in the route list shown in FIG. For example, the connection status in the protocol is determined by comparing the connection status in the protocol with the normal packet sequence of each protocol. In this case, for example, it is determined to be normal if it is the same as one of the sequences, and abnormal if it is different from any of the sequences. If it is the same as any one of the sequences, the connection state of the sequence may be recorded in the route list shown in FIG. If the sequence cannot be determined, it is determined that the inspection is being performed, and the connection status of “inspection” is recorded in at least the route list. When an abnormal response is returned or when there is no normal response within the set time, it may be determined as abnormal. Thereafter, the process proceeds to the completion confirmation procedure S8. In the completion confirmation procedure S8, it is determined whether or not the processing of all packets has been completed. If completed, the process proceeds to the display procedure S9, and if not completed, the process proceeds to the packet list acquisition procedure S1.

  For example, in the case of the packet ID 1 shown in FIG. 2, in the connection status determination procedure S <b> 7, the communication content is a page acquisition request. When the packet ID 1 passes through the switching hub 24 shown in FIG. 1, it is not known whether the connection status in the protocol is normal. For this reason, the connection status determination unit 14 determines that the inspection is in progress. The route ID 1 and route ID 2 corresponding to the packet ID 1 are obtained with reference to the packet-to-route correspondence table shown in FIG. 6, and the connection status of the HTTP protocol of the route ID 1 and route ID 2 in the route list shown in FIG. Update "medium".

  In the case of the packet ID 2 shown in FIG. 2, the communication content is “200 OK”. In the HTTP protocol, when a page acquisition request is made, it is normal that a response of “200 OK” is returned within a certain time. For this reason, it turns out that it is a reply with respect to either of the past packets. The protocol of the packet ID 2 stored in the packet list shown in FIG. 2 is the same HTTP as the packet ID 1 and the time is 1 second after the packet ID 1. In packet ID1, the logical identifiers of the transmission source and transmission destination of packet ID2 are the same, and the logical identifiers of the transmission destination and transmission source of packet ID2 are the same. Thereby, the connection status determination part 14 can determine with the connection status in the protocol for communication of packet ID1 being normal.

  When the connection status determination unit 14 determines that the connection status in the protocol for communication with the packet ID 1 is normal, the path ID corresponding to the packet ID 2 is referred to from the packet-to-path correspondence table shown in FIG. The connection status of the HTTP protocol of route ID1 and route ID2 in the route list shown is updated to be OK. An example of the route list in this case is shown in FIG.

  In the display procedure S9, based on the data in the terminal list shown in FIG. 4 and the route list shown in FIG. 5, the network configuration diagram and the connection status of each protocol of the route between the terminals in the configuration diagram are displayed. In the network configuration diagram, each terminal in the terminal list is connected to a pair of terminals indicated in the route list by a line segment, and the connection status of each protocol is displayed in the middle of the line segment. FIG. 3 shows a display example corresponding to the route list shown in FIG. FIG. 9 shows a display example corresponding to the route list shown in FIG. In the example shown in FIG. 9, only HTTP is displayed as a protocol, but it is also assumed that a plurality of protocols such as IP and DNS are displayed at the same time.

  The present invention can be used to isolate the cause of a network trouble in a LAN or the like.

1 is a schematic configuration diagram of a network visualization device according to the present embodiment. It is an example of a packet list. It is an example of a display of a display part. It is an example of a terminal list. It is an example of a route list. It is an example of a packet pair path correspondence table. It is a flowchart which shows an example of the network visualization method which concerns on this embodiment. It is an example of a route list when the connection status of the HTTP protocol is OK. 9 shows a display example corresponding to the route list shown in FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Network visualization apparatus 11 Packet acquisition part 12 Packet list acquisition part 13 Path | route determination part 14 Connection condition determination part 15 Display part 16 Terminal list memory | storage part 17 Path | route list memory | storage part 18 Packet-to-path corresponding notation part 20 Network 21 PC
22 router 23 PC
24 Switching hub

Claims (6)

From packets transmitted and received between terminals constituting the network, physical identifiers and logical identifiers of transmission source terminals and transmission destination terminals of the packets, types of protocols for packet communication, and connection statuses in the protocols A packet list acquisition unit for acquiring
Referring to a terminal list in which physical identifiers and logical identifiers are associated with terminal identifiers, terminal identifiers and packets corresponding to the physical identifiers of the transmission source terminals acquired by the packet list acquisition unit The route defined by a pair with the identifier of the terminal corresponding to the physical identifier of the destination terminal acquired by the list acquisition unit, the type of protocol for communication of the packet acquired by the packet list acquisition unit, and Register as a route list corresponding to the packet along with the connection status in the protocol,
Referring to the terminal list, the identifier of the terminal corresponding to the physical identifier of the transmission source terminal acquired by the packet list acquisition unit and the logical identifier of the transmission source terminal acquired by the packet list acquisition unit It is determined whether or not the corresponding terminal identifier is the same, and if not, the terminal identifier and the packet list acquisition corresponding to the physical identifier of the transmission source terminal acquired by the packet list acquisition unit A route defined by a pair with a terminal identifier corresponding to a logical identifier of the transmission source terminal acquired by the transmission unit, a type of protocol for communication of the packet acquired by the packet list acquisition unit, and the protocol Register as a route list corresponding to the packet along with the connection status,
Referring to the terminal list, the identifier of the terminal corresponding to the physical identifier of the destination terminal acquired by the packet list acquisition unit and the logical identifier of the destination terminal acquired by the packet list acquisition unit It is determined whether or not the corresponding terminal identifier is the same, and if not, the terminal identifier and the packet list acquisition corresponding to the physical identifier of the destination terminal acquired by the packet list acquisition unit A route defined by a pair with a terminal identifier corresponding to a logical identifier of the destination terminal acquired by the unit, a protocol type for communication of the packet acquired by the packet list acquisition unit, and the protocol A route determination unit that registers as a route list corresponding to the packet together with the connection status ;
A network visualization device comprising: Displays the network configuration composed of the routes registered in the route list by the route determination unit, and the type of protocol registered as the route list on the route of the network configuration and the connection in the protocol The network visualization apparatus according to claim 1 , further comprising display means for displaying a status. From the packet transmitted / received between the terminals, the physical identifier and logical identifier of the transmission source terminal and the transmission destination terminal of the packet, the type of protocol for packet communication, and the connection status in the protocol Packet list acquisition procedure to be acquired;
The terminal identifier and the packet corresponding to the physical identifier of the source terminal acquired in the packet list acquisition procedure with reference to a terminal list in which a physical identifier and a logical identifier are associated with the terminal identifier A route defined by a pair with a terminal identifier corresponding to a physical identifier of the destination terminal acquired in the list acquisition procedure, a protocol type for communication of the packet acquired in the packet list acquisition procedure, and Register as a route list corresponding to the packet along with the connection status in the protocol,
Referring to the terminal list, the identifier of the terminal corresponding to the physical identifier of the transmission source terminal acquired in the packet list acquisition procedure and the logical identifier of the transmission source terminal acquired in the packet list acquisition procedure It is determined whether or not the corresponding terminal identifier is the same, and if not, the terminal identifier and the packet list acquisition corresponding to the physical identifier of the transmission source terminal acquired in the packet list acquisition procedure A route defined by a pair with a terminal identifier corresponding to a logical identifier of the transmission source terminal acquired in the procedure, a protocol type for communication of the packet acquired in the packet list acquisition procedure, and the protocol Register as a route list corresponding to the packet along with the connection status,
Referring to the terminal list, the terminal identifier corresponding to the physical identifier of the destination terminal acquired in the packet list acquisition procedure and the logical identifier of the destination terminal acquired in the packet list acquisition procedure It is determined whether or not the corresponding terminal identifier is the same, and if not, the terminal identifier and the packet list acquisition corresponding to the physical identifier of the destination terminal acquired in the packet list acquisition procedure A route defined by a pair with a terminal identifier corresponding to the logical identifier of the destination terminal acquired in the procedure, the type of protocol for communication of the packet acquired in the packet list acquisition procedure, and the protocol A route determination procedure for registering as a route list corresponding to the packet together with the connection status ;
A network visualization method characterized by comprising: After the route determination procedure, a network configuration composed of the routes registered as the route list is displayed, and the protocol type and the protocol registered as the route list on the route of the network configuration The network visualization method according to claim 3 , further comprising a display procedure for displaying a connection status in the network. The computer, the packet list acquisition procedure described in the packet list acquisition procedure and path determination procedure or claim 4 according to claim 3, the program for executing a path determination procedure and display procedure. A computer-readable recording medium on which the program according to claim 5 is recorded.

Images