JP6862902B2 - Configuration diagram generator, configuration diagram generation method and configuration diagram generation program - Google Patents

Description

The present invention relates to a configuration diagram generator, a configuration diagram generation method, and a configuration diagram generation program.

Conventionally, when designing a network, it is common to describe a logical configuration diagram and a physical configuration diagram. The logical configuration diagram is the configuration of a logical network that the user wants to create (hereinafter, it may be simply referred to as a logical network), and network information such as subnets and connection relationships, which are important information for the user, is described. However, device information such as routers and bridges that are not important to the user is often omitted. The physical configuration diagram is a configuration of a physical device in which a logical network actually operates (hereinafter, it may be simply referred to as a physical network).

In recent years, using protocols such as SNMP (Simple Network Management Protocol), CDP (Cisco Discovery Protocol), and LLDP (Link Layer Discovery Protocol), the physical device and connection configuration are searched from the actual physical network, and the physical configuration is performed. A technique for automatically generating a diagram is known.

Japanese Unexamined Patent Publication No. 2005-234705 International Publication No. 2007/110942 Japanese Unexamined Patent Publication No. 2002-368743

However, with the spread of virtual environments such as cloud systems, the frequency of changes in virtual networks is increasing, which not only puts a burden on the creation of logical configuration diagrams, but also makes the creation work itself difficult. ..

Generally, it is not possible to create a physical configuration diagram from a logical configuration diagram, and the user manually creates a physical configuration diagram or creates a physical configuration diagram from a physical network using the above technique. On the other hand, the technology to build a virtual network on a virtual environment has appeared, and users can freely arrange virtual devices on the cloud infrastructure to configure a virtual network. Since virtual devices can be freely arranged in a virtual environment to configure a virtual (physical) network, users frequently change the virtual network. For this reason, it becomes easy to create and change the virtual network, and the physical configuration diagram is frequently changed accordingly, which increases the burden on the user.

Also, in proportion to the size of the network, more information is used to determine the virtual device. For example, in a network with tens or hundreds of bases and subnets, it is difficult to manually manage the necessary information and select the appropriate device. In this way, as the frequency of changes in the virtual network increases, the manual creation of the physical configuration diagram increases the labor of work and causes an increase in design mistakes.

In one aspect, it is an object of the present invention to provide a configuration diagram generation device, a configuration diagram generation method, and a configuration diagram generation program capable of automatically generating a physical configuration diagram.

In the first plan, the configuration diagram generator has a detection unit that detects each object belonging to both ends of the link included in the logical configuration diagram from the logical configuration diagram in which network attribute information regarding the network is set. The configuration diagram generation device has a determination unit that determines the connection relationship of the links according to the network attribute information of the network to which each object belongs. The configuration diagram generator generates a specific unit that identifies the network device according to the determined connection relationship of the link, and a physical configuration diagram that complements the specified network device to the link of the logical configuration diagram. It has a generator and a generator.

According to one embodiment, the physical configuration diagram can be automatically generated.

FIG. 1 is a diagram illustrating a network design apparatus according to a first embodiment. FIG. 2 is a diagram illustrating a network design in a virtual environment. FIG. 3 is a functional block diagram showing a functional configuration of the network design device according to the first embodiment. FIG. 4 is a diagram showing an example of a logical configuration diagram stored in the logical configuration DB. FIG. 5 is a diagram showing the detailed contents of the objects in the logical configuration diagram. FIG. 6 is a diagram showing setting information of the entire logical configuration diagram. FIG. 7 is a diagram showing setting information of the base of the logical configuration diagram. FIG. 8 is a diagram showing a network connection relationship in the logical configuration diagram. FIG. 9 is a diagram showing network attribute information in the logical configuration diagram. FIG. 10 is a diagram showing the attribute information of the nodes in the logical configuration diagram. FIG. 11 is a diagram showing an example of information stored in the complementary device DB. FIG. 12 is a diagram showing the attribute information of the infrastructure stored in the physical configuration DB. FIG. 13 is a sequence diagram showing the flow of the entire process. FIG. 14 is a flowchart showing the flow of the attribute information generation process. FIG. 15 is a diagram illustrating an example of generating attribute information of each abstraction degree. FIG. 16 is a diagram for explaining the attribute information created from the logical configuration. FIG. 17 is a flowchart showing the overall flow of the complementary process. FIG. 18 is a flowchart showing a flow of complementary processing when the degree of abstraction is a base. FIG. 19 is a flowchart showing a flow of complementary processing when the degree of abstraction is a network. FIG. 20 is a flowchart showing the flow of complementary processing when the degree of abstraction is a node. FIG. 21 is a diagram illustrating device complementation. FIG. 22 is a diagram illustrating the generation of the physical configuration diagram. FIG. 23 is a diagram for explaining the detailed contents of the objects in the physical configuration diagram. FIG. 24 is a diagram showing setting information of the entire physical configuration diagram. FIG. 25 is a diagram showing setting information of the base 1 in the physical configuration diagram. FIG. 26 is a diagram showing setting information of the base 2 in the physical configuration diagram. FIG. 27 is a diagram showing a connection relationship of the network 1 in the physical configuration diagram. FIG. 28 is a diagram showing a connection relationship of the network 2 in the physical configuration diagram. FIG. 29 is a diagram showing a connection relationship of the network 3 in the physical configuration diagram. FIG. 30 is a diagram showing the attribute information of the nodes in the physical configuration diagram. FIG. 31 is a diagram illustrating the process according to the second embodiment. FIG. 32 is a diagram showing the attribute information of the infrastructure stored in the physical configuration DB according to the second embodiment. FIG. 33 is a diagram showing information stored in the complementary device DB according to the second embodiment. FIG. 34 is a diagram for explaining the complementation of the attribute information according to the second embodiment. FIG. 35 is a flowchart showing the flow of the complementary process according to the second embodiment. FIG. 36 is a diagram showing a physical configuration diagram generated in the second embodiment. FIG. 37 is a diagram illustrating details of the physical configuration according to the second embodiment. FIG. 38 is a diagram illustrating the process according to the third embodiment. FIG. 39 is a diagram showing the attribute information of the infrastructure stored in the physical configuration DB according to the third embodiment. FIG. 40 is a diagram showing information stored in the complementary device DB according to the third embodiment. FIG. 41 is a flowchart showing the flow of the complementary process according to the third embodiment. FIG. 42 is a diagram showing a physical configuration diagram generated in the third embodiment. FIG. 43 is a diagram for explaining the physical configuration added in the third embodiment. FIG. 44 is a diagram showing a hardware configuration example.

Hereinafter, examples of the configuration diagram generation device, the configuration diagram generation method, and the configuration diagram generation program disclosed in the present application will be described in detail with reference to the drawings. The present invention is not limited to this embodiment. In addition, each embodiment can be appropriately combined within a consistent range.

[overall structure]
FIG. 1 is a diagram illustrating a network design device 10 according to a first embodiment. The network design device 10 is a computer such as a server, and functions as a management tool for generating a physical configuration diagram and a physical network from a logical configuration diagram designed by a user. The network design device 10 can also be incorporated as a management tool into an existing server, management device, or the like.

Here, the logical configuration diagram designed by the user is a logical configuration diagram designed by the user in a state where the functions of the infrastructure are hidden, and network information such as subnets and connection relationships are described, but devices such as routers and bridges are described. Information is omitted. The physical configuration diagram is a configuration of a physical device in which the logical network defined in the logical configuration diagram actually operates. A physical network is a network diagram in which connection relationships such as subnets, infrastructures, and nodes are described by complementing physical devices with a logical network.

In recent years, there is a method of searching for a physical device and generating a physical configuration diagram. However, there is no method for automatically designing a physical configuration diagram from a logical configuration diagram. This is because it is difficult to design automatically because the physical network (physical topology) can have various configurations even if it is the same logical network, and in general, there are few changes once the physical network is laid. The reason may be that the design of the logical network that operates on it was important. Therefore, there is no tool for automatically designing the physical configuration diagram from the logical configuration diagram, and when designing a new physical network, the user has to create the physical configuration diagram by himself / herself.

FIG. 2 is a diagram illustrating a network design in a virtual environment. As shown in FIG. 2, the user generates a logical configuration diagram and also generates a physical configuration diagram according to the logical configuration diagram. Here, since the physical network (physical topology) can have various configurations even in the same logical network, the physical configuration diagram created by the user also becomes a physical configuration diagram (virtual physical configuration diagram) having various configurations. ..

Then, the user uses the management tool to generate a physical network from the created logical configuration diagram and physical configuration diagram. Again, since the physical configuration diagram is a virtual physical configuration diagram for the user, the physical network generated by the management tool is also a physical network of various forms (virtual physical network). As described above, since the physical configuration diagram cannot be simply created only by the logical network, trial and error increases and the burden on the user increases. Further, the user has to recreate the physical configuration diagram every time the virtual environment is added or modified, and the work efficiency is not good.

Therefore, the network design device 10 according to the first embodiment acquires a logical configuration diagram in which attribute information regarding the network to which each object constituting the system belongs and link information regarding the connection relationship between the objects are set. Then, the network design device 10 determines the connection relationship of the link according to the attribute information of each object belonging to both ends of the link specified by the link information. After that, the network design device 10 identifies the network device according to the connection relationship of the determined link, and generates a physical configuration diagram complementing the specified network device at both ends or the middle of the link included in the logical configuration diagram. ..

That is, the network design device 10 causes the user to create a logical configuration diagram while hiding the functions of the infrastructure including the cloud, and based on the attribute information for each degree of abstraction at both ends of each link in the logical configuration, the necessary network. Complements the device and automatically generates a physical configuration diagram. Therefore, since the network design device 10 can automatically generate a physical configuration diagram, the burden on the user is reduced even when the frequency of changing the virtual network is increasing with the spread of virtual environments such as cloud systems. it can. In this embodiment, the infrastructure represents a user's on-premises base or cloud service. Further, the abstraction degree is information indicating the inclusion relationship of network components, the abstraction degree 1 is the broadest concept and includes the network and the node, and the abstraction degree 2 is the next broadest concept and the node. The abstraction level 3 is the narrowest concept and corresponds to a node.

[Functional configuration]
FIG. 3 is a functional block diagram showing a functional configuration of the network design device 10 according to the first embodiment. As shown in FIG. 3, the network design device 10 includes a logical configuration DB 11, a complementary device DB 12, a physical configuration DB 13, a reception unit 20, a logical configuration management unit 21, an automatic completion processing unit 22, and an infrastructure setting unit 23.

The logical configuration DB 11, the complementary device DB 12, and the physical configuration DB 13 are databases stored in a storage device such as a memory or a hard disk. The reception unit 20, the logical configuration management unit 21, the automatic completion processing unit 22, and the infrastructure setting unit 23 are examples of electronic circuits included in the processor and examples of processes executed by the processor.

The logical configuration DB 11 is a database that stores a logical configuration diagram created by the user in a state where the functions of the infrastructure including the cloud are hidden. The user arranges objects for each degree of abstraction and designs a logical network (logical configuration diagram). Objects of each degree of abstraction include infrastructure (bases), networks included in the infrastructure (objects grouped by subnets, etc.), and nodes included in the network (network functions such as hosts and load balancers). is there. Also, design the connection relationship (link) between each object. Devices such as routers and switches that connect the network can be omitted. Multiple networks can be the same infrastructure. The user sets the minimum information required for network construction as attribute information.

FIG. 4 is a diagram showing an example of a logical configuration diagram stored in the logical configuration DB 11. As shown in FIG. 4, the logical configuration diagram created by the user has the highest level of abstraction (1) as base 1 (hereinafter referred to as base 1).
Set site1 and base2, then set network 1-3 (hereinafter sometimes referred to as nw1 etc.) as the next highest level of abstraction (2), and set the lowest level of abstraction (may be described as nw1 etc.). As 3), a plurality of nodes (hereinafter, may be referred to as nodes) are set.

Further, the base 1 has a network 1 and a network 2 connected by a link 2, the network 1 has three nodes, and the network 2 has two nodes. Then, "infrastructure = infrastructure 1, subnet = 192.168.1.0/24" is set as attribute information in network 1, and "infrastructure = infrastructure 1, subnet = 192.168.2.0 /" is set in network 2 as attribute information. 24, 192.168.10.0/24, ”is set. In the following, infrastructure may be referred to as infra.

Further, the base 2 has a network 3 connected by a link 1, and the network 3 has two nodes. Then, "infrastructure = infrastructure 2, subnet = 192.168.3.0/24, 192.168.10.0/24," is set in the network 3 as attribute information.

Here, the details of the logical configuration diagram generated by the user will be described with reference to FIGS. 5 to 10. FIG. 5 is a diagram showing the detailed contents of the objects in the logical configuration diagram. As shown in FIG. 5, as “Parameter, value”, “base, link” is set in association with the identification number “ID = 1” in the logical configuration diagram. As shown in FIG. 5, the detailed information of each object is set in an array. Specifically, the "base" is a pointer to an array that sets the details of the base set in the logical configuration diagram, and the "link" is an array that sets the detailed information of the link 1 that connects the bases. Is a pointer to. Further, in the array "base", "base 1" and "base 2" for identifying the base are set, and in the array "network", "network 1", "network 2" and "network" for identifying the network are set. "3" is set, "link 2" to "link 6" for identifying the link are set in the array "link", and "node 1" to "node 7" for identifying the node are set in the array "node". Is set.

FIG. 6 is a diagram showing setting information of the entire logical configuration diagram. In FIG. 6, the connection relationship of each array is set. Specifically, a pointer to the array of objects that is the end point of the link 1 is set in the array of "link 1". For example, "base-a, base-b, network-a, network-b, node-a, node-b, attribute information" is set in the array of "link 1".

Here, "base-a" is a pointer to the array of "base 1" which is one base connected by link 1, and "base-b" is the other base connected by link 1. It is a pointer to an array of a certain "base 2". "Network-a" is a pointer to an array of "network 2" which is one network connected by link 1, and "Network-b" is "network" which is the other network connected by link 1. It is a pointer to the array of "3". "Node-a" is a pointer to the array of "node 5" which is one node connected by link 1, and "node-b" is the other node connected by link 1 "node". It is a pointer to the array of "6". Further, as the attribute information of the link 1, it is set that the Type of the link 1 is the Internet.

That is, according to the setting of FIG. 6, the link 1 is the Internet connecting the base 1 and the base 2, the link connecting the network 2 and the network 3, and the end point of the link 1 is the node 5 belonging to the network 2. It can be seen that the node 6 belongs to the network 3. Similarly, it can be seen that the base 1 has a network 1 and a network 2, the network 1 has nodes 1 to 3, and the network 2 has nodes 4 to 5. Further, it can be seen that the base 2 has the network 3, and the network 3 has the nodes 6 to 7.

FIG. 7 is a diagram showing setting information of the base of the logical configuration diagram. Similar to FIG. 6 and the like, FIG. 7 is set in a format in which the information set in each base is referred to by a pointer to an array of objects. Specifically, for the base 1, the network 1 and the network 2 are set as Networks, the link 2 is set as the link, and the infrastructure 1 is set as the attribute information. Similarly, for the base 2, the network 3 is set as Networks, nothing is set as a link, and the infrastructure 2 is set as attribute information.

Considering such a reference relationship, it can be seen from FIG. 7 that the base 1 is an infrastructure (infra1) having a network 1, a network 2, and a link 2. Further, it can be seen that the base 2 is an infrastructure (infra2) having a network 3 but no link. Further, it can be seen that the link 2 is a link (line) connecting the network 1 and the network 2, and the node 3 and the node 4 are end points.

FIG. 8 is a diagram showing a network connection relationship in the logical configuration diagram. Similarly to FIG. 6 and the like, FIG. 8 is set in a format in which each setting information is referred to by a pointer to an array of objects. As a result, it can be seen that the following contents are set. For example, the network 1 has a link 3 and a link 4, the link 3 has a node 1 and a node 2 as end points, and the link 4 has a node 2 and a node 3 as end points. The network 2 has a link 5, and the link 5 has nodes 4 and 5 as endpoints. The network 3 has a link 6, which has nodes 6 and 7 as endpoints.

FIG. 9 is a diagram showing network attribute information in the logical configuration diagram. As shown in FIG. 9, "infrastructure = infrastructure 1, subnet = 192.168.1.0/24" is set in network 1, and "infrastructure = infrastructure 2, subnet = 192.168.2.0/24, 192.168" is set in network 2. ".10.0/24" is set, and "infrastructure = infrastructure 2, subnet = 192.168.3.0/24, 192.168.10.0/24" is set in the network 3. Further, "line" is set as the type of links 3, 4, 5, and 6.

FIG. 10 is a diagram showing the attribute information of the nodes in the logical configuration diagram. Similar to FIG. 6 and the like, FIG. 10 also sets detailed information to be referred to by the pointer. As shown in FIG. 10, node 1 is a server, node 2 is a load balancer, node 3 is a firewall, node 4 is an IDS (Intrusion Detection System), and node 5 is a WOC (Wild Area Network). Optimization Controller), node 6 is a WOC, and node 7 is a terminal.

Returning to FIG. 3, the complement device DB 12 is a database that stores information about network devices that complement the logical configuration diagram. FIG. 11 is a diagram showing an example of information stored in the complementary device DB 12. As shown in FIG. 11, the complement device DB 12 stores the “abstraction level, complement device” in association with each other. As shown in FIG. 11, when the abstraction degree 1 is specified as NAT (Network Address Translation), the abstraction degree 2 is specified as a remote bridge, and the abstraction degree 3 is specified as none, the complemented devices are a remote router and a NAT router. If the combination does not correspond to the combination shown in FIG. 11, an error will occur.

The physical configuration DB 13 is a database that stores the generated physical configuration diagram and physical network. In addition, the physical configuration DB 13 also stores the attribute information of each infrastructure in advance. FIG. 12 is a diagram showing the attribute information of the infrastructure stored in the physical configuration DB. As shown in FIG. 12, the physical configuration DB 13 stores "NF-to-NF connection method = router" as the attribute information of the infrastructure 1, and stores "NF-to-NF connection method = SW (switch)" as the attribute information of the infrastructure 2. ..

The reception unit 20 is a processing unit that provides an interface to the GUI in the management tool and transmits the message received from the GUI and the logical configuration diagram data to the logical configuration management unit. The GUI acts as an intermediary between the user and the management tool. It does not necessarily have to be a GUI, as long as a message can be sent to the reception unit 20. The user creates a logical configuration diagram on this GUI and gives instructions for completion and setting. The GUI sends an instruction message and logical configuration diagram data to the API (reception unit 20) of the management tool.

The logical configuration management unit 21 is a processing unit that executes various processes on messages and logical configuration diagram data received from the GUI through the reception unit 20. The logical configuration management unit 21 saves the logical configuration diagram data in the logical configuration DB 11, outputs a completion instruction to the automatic completion processing unit 22, and outputs a setting instruction to the infrastructure to the infrastructure setting unit 23.

The automatic completion processing unit 22 is a processing unit that verifies the connectivity of the logical configuration diagram and complements the necessary network devices. The automatic completion processing unit 22 saves the complemented result in the physical configuration DB 13 as a physical configuration diagram.

The infrastructure setting unit 23 is a processing unit that sets the infrastructure based on the physical configuration diagram. The infrastructure is the infrastructure on which the network managed by the user operates, such as the virtual environment (cloud) and the user's on-premises base.

Next, the processing content executed by each processing unit and the flowchart of each processing unit will be described together. Here, the whole process, the attribute information generation process, and the complement process will be described.

(Overall processing)
FIG. 13 is a sequence diagram showing the flow of the entire process. As shown in FIG. 13, a user designs a logical network (logical configuration diagram) by arranging objects for each degree of abstraction using a GUI (Graphical User Interface) (S101). The reception unit 20 receives the logical configuration diagram generated by the user via the GUI (S102) and outputs it to the logical configuration management unit 21 (S103). The logical configuration management unit 21 saves the notified logical configuration diagram in the logical configuration DB 11 (S104).

After that, the user outputs a completion instruction using the GUI (S105). Then, the reception unit 20 receives the complement instruction via the GUI (S106), and outputs the complement instruction to the logical configuration management unit 21 (S107). The logical configuration management unit 21 transmits a completion instruction to the automatic completion processing unit 22 for the logical configuration diagram (S108).

Upon receiving this completion instruction, the automatic completion processing unit 22 acquires a logical configuration diagram from the logical configuration DB 11 (S109 and S110), and also acquires a connection method which is infra attribute information from the physical configuration DB 13 (S111 and S112). , The attribute information generation process (S113) and the complement process (S114) are executed to generate the physical configuration diagram. Then, the automatic completion processing unit 22 saves the generated physical configuration diagram in the physical configuration DB 13 (S115).

After that, the user who receives the completion result through the GUI instructs the setting of the logical network (logical configuration diagram) to the infrastructure on the GUI (S116). The GUI instructs the logical configuration management unit 21 to make settings via the reception unit 20 (S117 and S118). Next, the logical configuration management unit 21 instructs the infrastructure setting unit 23 to set the designated logical configuration diagram (S119). The infrastructure setting unit 23 acquires the physical configuration diagram corresponding to the logical configuration diagram from the physical configuration DB 13 (S120 and S121), and sets it in each infrastructure according to the physical configuration (S122).

(Generation process of attribute information)
Next, the attribute information generation process executed by the auto-completion processing unit 22 will be described. This process corresponds to S113 in FIG. The automatic completion processing unit 22 generates attribute information of each abstraction degree based on the attribute information set by the user with respect to the instructed logical configuration diagram. The auto-completion processing unit 22 integrates the attribute information of the abstraction degree lower than the processing target to determine the attribute information of the processing target. Further, the automatic completion processing unit 22 determines the attribute information of the processing target from the attribute information of the higher abstraction degree when there is no attribute information of the abstraction degree lower than the processing target.

(1) Process flow FIG. 14 is a flowchart showing a flow of attribute information generation processing. As shown in FIG. 14, the auto-completion processing unit 22 executes the loop processing of S201 or later in order from the abstraction degree 1, and executes the loop processing of S202 or later for each abstraction degree.

Specifically, the auto-completion processing unit 22 determines, for each object of each abstraction degree, whether or not there is an object of an abstraction degree lower than the object to be processed (S203). Then, when the object of the abstraction degree lower than the object to be processed does not exist (S203: No), the automatic completion processing unit 22 determines whether or not the object of the abstraction degree higher than the object to be processed exists. Judgment (S204).

Here, the auto-completion processing unit 22 determines whether or not there is empty attribute information in the adjacent object when an object having a higher abstraction level than the object to be processed exists (S204: Yes) (S205). ). Then, when there is empty attribute information (S205: Yes), the auto-completion processing unit 22 extracts and sets the attribute information of the processing target from the attribute information of the object of the higher abstraction degree (S206), and sets the next object. S202 or later is executed. In S204, the auto-completion processing unit 22 sets the next object when there is no object with a higher level of abstraction than the object to be processed (S204: No) or when there is no empty attribute information (S205: No). S202 or later is executed.

On the other hand, when the automatic completion processing unit 22 has an object with a lower abstraction level than the object to be processed (S203: Yes) and the adjacent object has empty attribute information (S207: Yes), the processing target The attribute information is set by calculating the logical sum of the attribute information of the object of the lower abstraction degree (S208), and S202 or later is executed for the next object. Note that the auto-completion processing unit 22 is next even when there is an object with a lower abstraction level than the object to be processed (S203: Yes) and when there is no empty attribute information (S207: No). Execute S202 or later for the object.

For example, in the case of a node, the auto-completion processing unit 22 selects the infrastructure attribute information from the network infrastructure and the subnet attribute information from the network subnet attribute information. Here, the required subnet of the subnet attribute information differs depending on the node type. For example, there are two WOCs and one FW. The subnet selected takes precedence over the subnet of the adjacent node. Further, when the subnet of the adjacent node is empty or insufficient, the auto-completion processing unit 22 selects from the smallest subnet of the network. In this way, the automatic completion processing unit 22 generates attribute information for the logical configuration diagram of FIG.

(2) Specific Example Here, a specific example of generating attribute information for the logical configuration diagram of FIG. 4 will be described. FIG. 15 is a diagram illustrating an example of generating attribute information of each abstraction degree. The nodes are node 1 in order from the left of network 1, and the right end of network 3 is node 7. Further, here, it is assumed that the adjacent object has a free subnet. Further, for networks 1 to 3, as shown in FIG. 15, attribute information has already been set at the time of the logical configuration diagram.

For example, the auto-completion processing unit 22 has a lower object for the base 1, so that each subnet of "infrastructure 1" set in the lower object "192.168.1.0/24, 192.168.2.0/24, 192.168" Set ".10.0/24" to the attribute information of base 1. Similarly, for the base 2, the auto-completion processing unit 22 sets each subnet "192.168.3.0/24, 192.168.10.0/24" of the "infrastructure 2" set in the lower object as the attribute information of the base 2. To do.

Further, when the auto-completion processing unit 22 generates infrastructure attribute information for node 1, it specifies that there is no lower object, network 1 exists as a higher object, and node 1 is a server (FIG. 10). reference). Then, the auto-completion processing unit 22 determines that one subnet is set because the type is a server, and sets the attribute information "infrastructure 1, 192.168.1.0/24" of the network 1 as the attribute information of the node 1. The auto-completion processing unit 22 also determines that the node 2 (load balancer) and the node 3 (FW) are the same as the node 1, and the attribute information of the network 1 “Infrastructure 1, 192.168.1.0/24” is used as the attribute information. "Is set.

Further, when the auto-completion processing unit 22 generates infrastructure attribute information for node 4, it specifies that there is no lower object, network 2 exists as a higher object, and node 4 is an IDS (FIG. 10). reference). Then, the auto-completion processing unit 22 determines that one subnet is set because the type is IDS, and sets the attribute information "infrastructure 1, 192.168.10.0/24" of the network 2 as the attribute information of the node 4.

Further, when the auto-completion processing unit 22 generates the attribute information of the infrastructure for the node 5, it specifies that there is no lower object, the network 2 exists as the upper object, and the node 4 is the WOC (FIG. 10). reference). Then, the auto-completion processing unit 22 determines that two subnets are set because the type is WOC, and as the attribute information of the node 5, the attribute information of the network 2 "Infrastructure 1, 192.168.2.0/24, 192.168.10.0/24, "Is set.

Further, when the automatic completion processing unit 22 generates the attribute information of the infrastructure for the node 6, it specifies that there is no lower object, the network 3 exists as the upper object, and the node 6 is a WOC (FIG. 10). reference). Then, the auto-completion processing unit 22 determines that two subnets are set because the type is WOC, and as the attribute information of the node 6, the attribute information of the network 3 "Infrastructure 2, 192.168.3.0/24, 192.168.10.0/24, "Is set.

Further, when the automatic completion processing unit 22 generates the attribute information of the infrastructure for the node 7, it specifies that there is no lower object, the network 3 exists as the upper object, and the node 7 is a terminal (FIG. 10). reference). Then, the auto-completion processing unit 22 determines that one subnet is set because the type is a terminal, and sets the attribute information "infrastructure 2, 192.168.10.0/24" of the network 3 as the attribute information of the node 7.

In this way, the auto-completion processing unit 22 executes the flow shown in FIG. 14 in the order of the base, the network, and the node having a high degree of abstraction, and the attribute information generated for each object is shown in FIG. FIG. 16 is a diagram for explaining the attribute information created from the logical configuration. Comparing FIG. 16 and FIG. 4, in the logical configuration diagram, only the attribute information of the networks 1 to 3 was added, but the auto-completion processing unit 22 causes each node (node 1) according to the connection relationship of each object. Attribute information can also be added to 7) and bases (site1, site2).

(Complementary processing)
Next, the completion process executed by the automatic completion processing unit 22 will be described. This process corresponds to S114 of FIG. At each abstraction level, the auto-completion processing unit 22 determines the required Network Function (hereinafter, may be referred to as NF) based on the attribute information possessed by the objects at both ends of the link, and completes from the NF for each abstraction level. Decide which device to use.

That is, the auto-completion processing unit 22 determines the required NF for the link included in the logical configuration diagram from the attribute information of the objects at both ends of the link for the abstraction degree lower than the abstraction degree to which the link belongs. Then, the automatic completion processing unit 22 determines the network device to be complemented from the NF determined for each degree of abstraction. After that, the automatic completion processing unit 22 complements the network device to the logical configuration diagram and generates the physical configuration diagram. Then, the automatic completion processing unit 22 saves the complemented result as a physical configuration diagram in the physical configuration DB 13, and notifies the logical configuration management unit 21 of the completion of the complement processing. Further, the logical configuration management unit 21 that has received the notification notifies the user of the completion result via the GUI or the like.

Infrastructure attribute information is required to determine NF at a node. The attribute information of this infrastructure is information for determining router connection, switch (SW) connection, and the like. In this embodiment, the connection method shown in FIG. 12 is stored in advance in the physical configuration DB 13 as the attribute information of this infrastructure. It is assumed that the connection method shown in FIG. 12 is generated by the vendor of the network design device and saved in advance.

(1) Process flow (overall)
FIG. 17 is a flowchart showing the overall flow of the complementary process. As shown in FIG. 17, the auto-completion processing unit 22 executes the loop processing of S301 or later in order from the link having the smallest identifier for each link, and executes the loop processing of S302 or later in order from the abstraction degree 1 for each abstraction degree.

Specifically, the auto-completion processing unit 22 selects one link and complements each of the base (abstraction level 1), network (abstraction level 2), and node (abstraction level 3) to which the link belongs. Execute the determination (S303). Then, the automatic completion processing unit 22 determines the completion device based on the NF (completion NF) of the completion target determined for each abstraction degree and the information stored in the completion device DB 12 (S304).

(2) Complementation between bases FIG. 18 is a flowchart showing a flow of complement processing when the degree of abstraction is a base. As shown in FIG. 18, the automatic completion processing unit 22 acquires the attribute information of the bases at both ends of the link from the creation result of the attribute information shown in FIG. 16 (S401), and the attribute information of the subnets of both bases is duplicated. It is determined whether or not there is (S402).

Then, when the automatic completion processing unit 22 determines that the complement NF is NAT (S403) when the attribute information of the subnets of both bases is duplicated (S402: Yes), the automatic complement processing unit 22 determines that the attribute information of the subnets of both bases is not duplicated. (S402: No), it is determined that there is no complementary NF (S404).

(3) Complementation between networks FIG. 19 is a flowchart showing a flow of complement processing when the degree of abstraction is a network. As shown in FIG. 19, the auto-completion processing unit 22 acquires the attribute information of the networks at both ends of the link from the creation result of the attribute information shown in FIG. 16 (S501), and the infrastructure attribute information of both networks completely matches. Whether or not it is determined (S502).

Then, the automatic completion processing unit 22 complements when the infrastructure attribute information of both networks is exactly the same (S502: Yes) and when the attribute information of the subnets of both networks is one and the same (S503: Yes). The NF is determined to be a bridge (S504).

On the other hand, when the attribute information of the subnets of both networks is not one or the same (S503: No), the auto-completion processing unit 22 has duplicate attribute information in the attribute information of the subnets of both networks. Whether or not it is determined (S505). Then, the automatic completion processing unit 22 determines that the completion NF is NAT (S506) when there is duplicate attribute information (S505: Yes), and when there is no duplicate attribute information (S505: No). The complementary NF is determined to be the router (S507).

Further, when the infrastructure attribute information of both networks does not completely match (S502: No), the automatic completion processing unit 22 determines whether or not the attribute information of the subnets of both networks is one and the same (S508). ).

Then, when the attribute information of the subnets of both networks is one and the same (S508: Yes), the automatic completion processing unit 22 determines the completion NF as the remote bridge (S509). On the other hand, when the attribute information of the subnets of both networks is not one or the same (S508: No), the automatic completion processing unit 22 determines the completion NF as the remote router (S510).

(4) Complementation between nodes FIG. 20 is a flowchart showing a flow of complement processing when the degree of abstraction is a node. As shown in FIG. 20, the auto-completion processing unit 22 acquires the attribute information of the nodes at both ends of the link from the creation result of the attribute information shown in FIG. 16 (S601). Subsequently, the auto-completion processing unit 22 acquires the NF-to-NF connection method of the infrastructure to which the node belongs according to the connection method shown in FIG. 12 for both nodes (S602).

Then, when the nodes belong to the same network (S603: Yes), the auto-completion processing unit 22 determines that the completion NF is a device (Value) corresponding to the NF-to-NF connection method (S604). On the other hand, when the nodes do not belong to the same network (S603: No), the auto-completion processing unit 22 determines that there is no completion NF (S605).

(5) Specific Example FIG. 21 is a diagram illustrating device complementation. Here, the complement of link 1 in FIG. 21 will be described. The auto-completion processing unit 22 determines that the completion NF is NAT because "192.168.10.0/24" is duplicated for the subnet of the base (abstraction level 1) of the link 1. Further, the automatic completion processing unit 22 determines that the completion NF is a remote router because the attribute information of the subnets of the network (abstraction level 2) of the link 1 is not exactly the same and is not even one. Further, in the auto-completion processing unit 22, regarding the node 5 (abstraction degree 3) and the node 6 (abstraction degree 3) which are the end points of the link 1, the node 5 belongs to the infrastructure 1 and the node 6 belongs to the infrastructure 2. Since it belongs to different nodes, it is determined that there is no complementary NF.

In this way, the auto-completion processing unit 22 determines "NAT, remote router, none" as the completion NF of the abstraction degree (1, 2, 3). Then, the automatic completion processing unit 22 determines the completion device "remote router, NAT router" corresponding to "NAT, remote router, none" from the completion device DB 12 shown in FIG.

As a result, the automatic completion processing unit 22 generates a physical configuration diagram in which the complement device "remote router, NAT router" is added to the end point of the link 1 of the logical configuration diagram. Specifically, the auto-completion processing unit 22 sets a remote router on the infrastructure 1 which is the younger side of the infrastructure, and sets a NAT router on the infrastructure 2 which is not the younger side of the infrastructure.

FIG. 22 shows a list of complementary devices determined for each link in the logical configuration diagram by the above-mentioned processing. FIG. 22 is a diagram illustrating the generation of the physical configuration diagram. The auto-completion processing unit 22 determines the complement device "remote router, NAT router" for the link 1, the complement device "router" for the link 2-5, and the complement device "SW" for the link 6 by the above-described processing. To determine.

Then, the automatic completion processing unit 22 sets a "remote router, NAT router" on the link 1 between the base 1 and the base 2. The auto-completion processing unit 22 sets a "router" on the link 2 between the network 1 and the network 2. The auto-completion processing unit 22 sets "routers" for each of the link 3 between the node 1 and the node 2, the link 4 between the node 2 and the node 3, and the link 5 between the node 4 and the node 5. To do. The auto-completion processing unit 22 sets "SW" for the link 6 between the node 6 and the node 7.

As a result, the auto-completion processing unit 22 updates the nodes and the like with the addition of network devices, that is, the addition of new nodes. Specifically, the auto-completion processing unit 22 generates a node 11 at the end point of the link 1 that complements the remote router, and generates a node 12 at the end point of the link 1 that complements the NAT router. Further, the auto-completion processing unit 22 generates a node 21 on the link 2 that complements the router. Further, the auto-completion processing unit 22 generates a node 31, a node 32, and a node 33 for each of the link 3, the link 4, and the link 5 that complement the router. The auto-completion processing unit 22 creates a node 34 on the link 6 that complements the SW.

Further, the auto-completion processing unit 22 also executes the addition of links with the addition of nodes. Specifically, the auto-completion processing unit 22 has a link 11 between the node 5 and the node 11 with the addition of the node 11, and a link 12 between the node 12 and the node 6 with the addition of the node 12. And add. Further, the auto-completion processing unit 22 adds the link 21 between the node 3 and the node 21 and the link 22 between the node 21 and the node 4 with the addition of the node 21.

Further, the auto-completion processing unit 22 adds a link 31 between the node 1 and the node 31 and a link 32 between the node 31 and the node 2 with the addition of the node 31. Similarly, the auto-completion processing unit 22 adds a link 33 between the node 2 and the node 32 and a link 34 between the node 32 and the node 3 with the addition of the node 32. Similarly, the auto-completion processing unit 22 adds the link 35 between the node 4 and the node 33 and the link 36 between the node 33 and the node 5 with the addition of the node 33. Further, the auto-completion processing unit 22 adds a link 37 between the node 6 and the node 34, and adds a link 38 between the node 34 and the node 7 with the addition of the node 34.

In this way, the automatic completion processing unit 22 generates attribute information of each object according to the design information of the logical configuration diagram, and complements the network device according to the attribute information of each object. Then, the automatic completion processing unit 22 generates a physical configuration diagram as shown in the lower figure of FIG. 22.

(6) Details of Physical Configuration Here, with reference to FIGS. 23 to 30, details of the physical configuration diagram generated by the automatic completion processing unit 22 using the information of the logical configuration diagram and the like will be described. The information described here is information generated by the auto-completion processing unit 22 when the physical configuration diagram is generated. In addition, in FIGS. 23 to 30, as in FIG. 6, the reference relationship is shown by the pointer.

FIG. 23 is a diagram for explaining the detailed contents of the objects in the physical configuration diagram. As shown in FIG. 23, the automatic completion processing unit 22 adds an array of nodes 11, nodes 12, nodes 21, nodes 31, nodes 32, nodes 33, and nodes 34 in addition to the objects in the logical configuration diagram of FIG. Then, link 11, link 12, link 21, link 22, and link 31-38 are added.

FIG. 24 is a diagram showing setting information of the entire physical configuration diagram. As shown in FIG. 24, the auto-completion processing unit 22 adds a node to the base and updates the end point of the link 1 from the state of the logical configuration diagram of FIG. Specifically, the auto-completion processing unit 22 newly adds the node 11 and the node 21 to the base 1 (site 1), and newly adds the node 12 to the base 2 (site 2). Further, the auto-completion processing unit 22 updates the node 5 to the node 11 and the node 6 to the node 12 for the node 5 and the node 6 which are the end points of the link 1.

FIG. 25 is a diagram showing setting information of the base 1 in the physical configuration diagram. As shown in FIG. 25, as compared with FIG. 24 of the logical configuration diagram, the link 11 and the link 21 and the link 22 are stored instead of the link 2 in the array referred to by the link (Links) of the base 1. Further, the array of the link 11 refers to the network 2 of the network array, and refers to the node 5 and the node 11 of the node array. The array of links 21 refers to network 1 of the network array and references node 3 and node 21 of the node array. The array of links 22 refers to network 2 of the network array and refers to node 4 and node 21 of the node array.

FIG. 26 is a diagram showing setting information of the base 2 in the physical configuration diagram. As shown in FIG. 26, as compared with FIG. 24 of the logical configuration diagram, the link 12 is stored instead of the link 2 in the array referenced by the links (Links) of the base 2. In addition, the node (Nodes) of the base 2 and the node 12 of the node array are referred to. Further, the array of the link 12 refers to the network 3 of the network array that refers to the node 6 of the node array, and refers to the node 12 and the node 6 of the node array.

FIG. 27 is a diagram showing a connection relationship of the network 1 in the physical configuration diagram. As shown in FIG. 27, as compared with FIG. 8 of the logical configuration diagram, the nodes of the network 1 refer to the node array having the nodes 1-3 and the nodes 31-32 as elements, and link the network 1. (Links) refers to a link array having links 31-34 as an element. Further, the link 31 refers to the node 1 and the node 31 of the node array, the link 32 refers to the node 31 and the node 2 of the node array, and the link 33 refers to the node 2 and the node 32 of the node array. Link 34 refers to node 32 and node 3 in the node array.

FIG. 28 is a diagram showing a connection relationship of the network 2 in the physical configuration diagram. As shown in FIG. 28, as compared with FIG. 8 of the logical configuration diagram, the nodes of the network 2 refer to the node array having the nodes 4-5 and the node 33 as elements, and the links of the network 2 (Links). ) Refers to a link array having links 35-36 as an element. Further, the link 35 refers to the node 4 and the node 33 of the node array, and the link 36 refers to the node 33 and the node 5 of the node array.

FIG. 29 is a diagram showing a connection relationship of the network 3 in the physical configuration diagram. As shown in FIG. 29, as compared with FIG. 8 of the logical configuration diagram, the nodes of the network 3 refer to the node array having the nodes 6-7 and the node 34 as elements, and the links of the network 3 (Links). ) Refers to a link array having links 37-38 as an element. Further, the link 37 refers to the node 6 and the node 34 of the node array, and the link 38 refers to the node 34 and the node 7 of the node array.

FIG. 30 is a diagram showing the attribute information of the nodes in the physical configuration diagram. Note that nodes 1 to 7 are omitted because they are unchanged from the logical configuration diagram. As shown in FIG. 30, an array of nodes 11, 12, 21, 31-34 is added from the logical configuration diagram. Node 11 is a remote router belonging to infrastructure 1, and node 21 is a router belonging to infrastructure 1. Nodes 31, 32, and 33 are routers belonging to infrastructure 1. The node 12 is a remote router and a NAT router belonging to the infrastructure 2, and the node 34 is a SW belonging to the infrastructure 2.

[effect]
The network design device 10 according to the first embodiment can automatically generate a physical configuration diagram for configuring a virtual network by estimating it from a logical configuration diagram created by a user. In addition, since the physical configuration diagram is automatically generated by simply recreating the logical configuration diagram according to the increase or decrease of the virtual environment, the burden on the user can be reduced and the network design can be speeded up. In addition, it will be easier to build networks and network services that link services between data centers and bases around the world, which previously required manual physical configuration design.

In the first embodiment, an example of complementing a network device such as a router has been described, but the network device that can complement is not limited to this. For example, it is possible to supplement network devices suitable for cloud services such as PaaS (Platform as a Service) and Infrastructure as a Service (IAAS).

PaaS is a service that provides a platform that includes libraries necessary for building and operating software, and IaaS is a service that provides the infrastructure necessary for building and operating virtual machines and networks. PaaS generally has only an interface for external connection (Internet), but IaaS does not have an interface for external connection by default. Therefore, in order to connect PaaS and IaaS, Proxy for external connection is required for IaaS. Therefore, in the second embodiment, an example in which Proxy is complemented with respect to the logical configuration diagram created by the user will be described.

[Explanation of Example 2]
FIG. 31 is a diagram illustrating the process according to the second embodiment. As shown in FIG. 31, the network design device 10 accepts a logical configuration in which the base 1 including the node 1 and the network 1 and the base 2 including the node 2 and the network 2 are connected by a link 1 as a logical configuration diagram. .. Here, a subnet (192.168.1.0/24) is set as attribute information in the network 1, and an infrastructure (infra1) is set as attribute information in the base 1. Further, a subnet (192.168.2.0/24) is set as attribute information in the network 2, and an infrastructure (infra2) is set as attribute information in the base 2.

Then, when the network design device 10 can further identify that the attribute information (Layering) of the infrastructure 1 is PaaS and the attribute information (Layering) of the infrastructure 2 is IaaS, the network design device 10 connects the infrastructure 1 and the infrastructure 2. Complement Proxy as a device. That is, the network design device 10 complements the Proxy connecting the base 1 and the base 2 with the logical configuration diagram.

Here, the points different from those of the first embodiment will be described. First, as the connection method (infrastructure attribute information) stored in advance in the second embodiment, "Layering" is stored in addition to the NF-to-NF connection method. FIG. 32 is a diagram showing the attribute information of the infrastructure stored in the physical configuration DB 13 according to the second embodiment. As shown in FIG. 32, the physical configuration DB 13 stores "Layering = PaaS" in addition to "NF-to-NF connection method = router" as the attribute information of the infrastructure 1, and "NF-to-NF connection method =" as the attribute information of the infrastructure 2. Memorize "Layering = IaaS" in addition to "SW". As a result, the network design device 10 can specify that the base 1 of the logical configuration diagram provides the PaaS and the base 2 provides the IaaS by storing this attribute information in advance.

Next, the complementary device DB 12 of the second embodiment stores a combination for specifying the “Proxy” with respect to the complementary device list shown in FIG. FIG. 33 is a diagram showing information stored in the complementary device DB according to the second embodiment. As shown in FIG. 33, the complementary device DB 12 has "Proxy, Remote Bridge, none, Proxy (IaaS side)" and "Proxy, Remote Router, none," as "abstraction level (1, 2, 3), complementary device". Remember "Proxy (IaaS side)". As a result, when it is specified that the abstraction degree (1) is Proxy, the abstraction degree (2) is Remote Router, and the abstraction degree (3) is none, the network design device 10 decides to complement the Proxy on the IaaS side. Can be done.

[Generation of attribute information]
The network design device 10 according to the second embodiment generates attribute information of each abstraction degree based on the attribute information set by the user with respect to the instructed logical configuration diagram by the same method as that of the first embodiment. The detailed description will be omitted because it is the same as that of the first embodiment.

FIG. 34 is a diagram for explaining the complementation of the attribute information according to the second embodiment. The upper diagram of FIG. 34 shows the attribute information set in the logical configuration diagram generated by the user, and the lower diagram of FIG. 34 is the attribute information generated by the network design device 10 based on the logical configuration diagram. As shown in FIG. 34, the network design device 10 has the subnet of the base 1 and the base 2, the infrastructure of the network 1 and the network 2, and the infrastructure of the node 1 and the node 2 with respect to the attribute information of the logical configuration diagram created by the user. And subnet are additionally generated.

[Processing flow]
Next, the flow of the complementary process according to the second embodiment will be described. Here, the flow when the abstraction level is the base will be described. Since the flow having a degree of abstraction other than the base is the same as that of the first embodiment, detailed description thereof will be omitted. FIG. 35 is a flowchart showing the flow of the complementary process according to the second embodiment.

As shown in FIG. 35, the automatic complement processing unit 22 acquires the attribute information of the bases at both ends of the link from the creation result of the attribute information shown in FIG. 34 (S701), and the attribute information of the infrastructure shown in FIG. 32 (S701). (Connection method) is referred to, and the attribute information of the layering of the infrastructure is acquired based on the infra attribute information of each base (S702).

Then, when the attribute information of the layering of the two bases is PaaS and IaaS (S703: Yes), the automatic completion processing unit 22 determines the completion NF as Proxy (S704). On the other hand, when the layering attribute information of the two bases is not PaaS and IaaS (S703: No), the auto-completion processing unit 22 determines whether or not the attribute information of the subnets of both bases is duplicated (S705). ..

Then, the auto-completion processing unit 22 determines that the complement NF is NAT (S706) when the attribute information of the subnets of both bases is duplicated (S705: Yes), and the attribute information of the subnets of both bases is not duplicated. (S705: No), it is determined that there is no complementary NF (S707).

[Physical configuration]
FIG. 36 is a diagram showing a physical configuration diagram generated in the second embodiment. As shown in the upper figure of FIG. 36, as a result of the above-mentioned processing, the network design device 10 determines that the abstraction degrees 1 to 3 of the link 1 are "proxy, remote router, none", and as a result, the complementary device of the link 1 is used. Decide as "Proxy (IaaS side)". Therefore, as shown in the lower figure of FIG. 36, the network design device 10 adds the Proxy to the base 2 on the IaaS side of the end points of the link 1.

As a result, the auto-completion processing unit 22 updates the node and the like with the addition of the Proxy which is a new node. Specifically, the auto-completion processing unit 22 generates a node 11 at the end point of the link 1 that complements the Proxy. Further, the auto-completion processing unit 22 also executes the addition of links with the addition of nodes. Specifically, the auto-completion processing unit 22 adds a link 11 between the node 11 and the node 2 with the addition of the node 11.

In this way, the automatic completion processing unit 22 generates attribute information of each object according to the design information of the logical configuration diagram, and complements the network device according to the attribute information of each object. Then, the automatic completion processing unit 22 generates a physical configuration diagram as shown in the lower figure of FIG. 36.

FIG. 37 is a diagram illustrating details of the physical configuration according to the second embodiment. As a change from the logical configuration, as shown in FIG. 37, a node 11 is newly associated with the node-b of the link 1 of the link array. In addition, "infrastructure (infra2), Subnets (192.168.2.0/24, 10.0.0.0/24)" are newly set as attribute information in the node 11 of the node array. Further, the link 11 and the node 11 are newly associated with the base 2 in the base arrangement. The network 2, the node 11, and the node 2 are associated with the array of the links 11.

A global IP (Internet Protocol) address is set for the external (Internet) connection of the Proxy. The method of acquiring this global IP address differs depending on the infrastructure, but for example, in the case of a cloud service, a fee is charged and the cloud vendor pays it out.

[effect]
As described above, the network design device 10 is not limited to network devices related to internal networks such as routers and bridges, but can also complement network devices suitable for cloud services such as PaaS and IaaS. Therefore, the versatility of the network design using the network design device 10 can be increased, and the burden on the user can be reduced.

In the first and second embodiments, examples of complementing network devices such as routers and proxies have been described, but the network devices that can be complemented are not limited to this. For example, it can complement network devices such as GW (GateWay) of VPN (Virtual Private Network).

When connecting between IaaS or between IaaS and user bases (on-premises bases, etc.) via the Internet, it is necessary to make a VPN connection to ensure security. Therefore, in the third embodiment, the GW of the VPN is complemented with respect to the logical configuration diagram created by the user.

[Explanation of Example 3]
FIG. 38 is a diagram illustrating the process according to the third embodiment. As shown in FIG. 38, the network design device 10 accepts a logical configuration in which the base 1 including the node 1 and the network 2 and the base 2 including the node 2 and the network 2 are connected by a link 1 as a logical configuration diagram. .. Here, a subnet (192.168.1.0/24) is set as attribute information in the network 1, and an infrastructure (infra1) is set as attribute information in the base 1. Further, a subnet (192.168.2.0/24) is set as attribute information in the network 2, and an infrastructure (infra2) is set as attribute information in the base 2. Further, Type (Internet) is set as attribute information for the link 1.

Then, when the network design device 10 can further identify that the attribute information (Layering) of the infrastructure 1 is IaaS and the attribute information (Layering) of the infrastructure 2 is an on-premises base, the network design device 10 connects the infrastructure 1 and the infrastructure 2. Complement the VPN GW as a device to do. That is, the network design device 10 complements the GW of the VPN connecting the base 1 and the base 2 with the logical configuration diagram.

Here, the points different from those of the first and second embodiments will be described. First, as the infrastructure attribute information stored in advance in the first embodiment, "Layering" is stored in addition to the NF-to-NF connection method. FIG. 39 is a diagram showing the attribute information of the infrastructure stored in the physical configuration DB 13 according to the third embodiment. As shown in FIG. 39, the physical configuration DB 13 stores "Layering = IaaS" in addition to "NF-to-NF connection method = router" as the attribute information of the infrastructure 1, and "NF-to-NF connection method =" as the attribute information of the infrastructure 2. In addition to "SW", "Layering = On-premise" is stored. As a result, the network design device 10 can identify that the base 1 of the logical configuration diagram provides the IaaS and the base 2 is the on-premises base by storing this attribute information in advance.

Next, the complementary device DB 12 of the third embodiment stores a combination for specifying the “VPN GW” with respect to the complementary device list shown in FIG. 33. FIG. 40 is a diagram showing information stored in the complementary device DB according to the third embodiment. As shown in FIG. 40, the complementary device DB 12 has "VPN GW, Remote Bridge, none, VPN GW (for layer 2)", "VPN GW, Remote" as "abstract degree (1, 2, 3), complementary device". Router, None, VPN GW (for Layer 3) "," NAT + VPN GW, Remote Bridge, None, (VPN GW (for Layer 3), NAT + VPN GW (for Layer 3) "," NAT + VPN GW, Remote Router, None, ( "VPN GW (for layer 3), NAT + VPN GW (for layer 3)" is stored. As a result, in the network design device 10, the degree of abstraction (1) is VPN GW, the degree of abstraction (2) is Remote Router, and the degree of abstraction ( When 3) is identified as none, it can be determined to complement the VPN GW for Layer 3.

[Generation of attribute information]
The network design device 10 according to the third embodiment generates attribute information of each abstraction degree based on the attribute information set by the user with respect to the instructed logical configuration diagram by the same method as that of the first embodiment. The detailed description will be omitted because it is the same as that of the first and second embodiments.

[Processing flow]
Next, the flow of the complementary process according to the third embodiment will be described. Here, the flow when the abstraction level is the base will be described. Since the flow having a degree of abstraction other than the base is the same as that of the first and second embodiments, detailed description thereof will be omitted. FIG. 41 is a flowchart showing the flow of the complementary process according to the third embodiment.

As shown in FIG. 41, the auto-completion processing unit 22 acquires the attribute information of the bases at both ends of the link from the creation result of the attribute information (S801), and refers to the attribute information (connection method) of infra shown in FIG. 39. Then, the attribute information of the layering of the infrastructure is acquired based on the infra attribute information of each base (S802).

Then, when the attribute information of the layering of the two bases is PaaS and IaaS (S803: Yes), the automatic completion processing unit 22 determines the completion NF as Proxy (S804). On the other hand, when the attribute information of the layering of the two bases is not PaaS and IaaS (S803: No), the automatic completion processing unit 22 determines whether or not the type of the link is the Internet (S805).

Then, when the type of the link is the Internet (S805: Yes), the automatic completion processing unit 22 determines whether or not the attribute information of the subnets of both bases is duplicated (S806).

Here, the auto-completion processing unit 22 determines that the complement NF is NAT + VPN GW (S807) when the attribute information of the subnets of both bases is duplicated (S806: Yes), and the attribute information of the subnets of both bases is duplicated. If not (S806: No), the complementary NF is determined to be VPN GW (S808).

On the other hand, when the type of the link is not the Internet (S805: No), the automatic completion processing unit 22 determines whether or not the attribute information of the subnets of both bases is duplicated (S809).

Here, when the automatic completion processing unit 22 determines that the completion NF is NAT (S810) when the attribute information of the subnets of both bases is duplicated (S809: Yes), the attribute information of the subnets of both bases is not duplicated. In the case (S809: No), it is determined that there is no complementary NF (S811).

[Physical configuration]
FIG. 42 is a diagram showing a physical configuration diagram generated in the third embodiment. As shown in the upper figure of FIG. 42, as a result of the above-mentioned processing, the network design device 10 determines that the abstraction degrees 1 to 3 of the link 1 are "VPN GW, remote router, none", and as a result, the complementary device of the link 1. Is determined as "VPN GW (L3)". Therefore, as shown in the lower figure of FIG. 42, the network design device 10 adds a VPN GW for layer 3 at both end points of the link 1.

As a result, the auto-completion processing unit 22 updates the nodes and the like with the addition of the two VPN GWs that are new nodes. Specifically, the auto-completion processing unit 22 adds a VPN GW as a node 11 and a node 12 at the end point of the link 1. Further, the auto-completion processing unit 22 also executes the addition of links with the addition of nodes. Specifically, the auto-completion processing unit 22 adds a link 11 between the node 1 and the node 11 with the addition of the node 11. Further, the auto-completion processing unit 22 adds a link 12 between the node 12 and the node 2 with the addition of the node 12.

In this way, the automatic completion processing unit 22 generates attribute information of each object according to the design information of the logical configuration diagram, and complements the network device according to the attribute information of each object. Then, the automatic completion processing unit 22 generates a physical configuration diagram as shown in the lower figure of FIG. 42.

FIG. 43 is a diagram for explaining the physical configuration added in the third embodiment. As a change from the logical configuration, as shown in FIG. 43, an array of nodes 11 and an array of nodes 12 are newly generated. "Infrastructure (infra1), Subnets (192.168.1.0/24, 10.0.0.0/24), Type (VPN GW (L3))" are newly set as the attribute information of node 11, and as the attribute information of node 12, "Infrastructure (infra2), Subnets (192.168.2.0/24, 10.1.0.0/24), Type (VPN GW (L3))" will be newly set. A global IP address is set for the external (Internet) connection of the VPN GW. The method of acquiring this global IP address differs depending on the infrastructure, but for example, in the case of a cloud service, a fee is charged and the cloud vendor pays it out.

[effect]
As described above, the network design device 10 is not limited to network devices related to the internal network such as routers and bridges, but determines the status of connecting the external network and the internal network, and automatically complements the network devices such as VPN GW. You can also do it. Therefore, the versatility of the network design using the network design device 10 can be increased, and the burden on the user can be reduced.

By the way, although the examples of the present invention have been described so far, the present invention may be implemented in various different forms other than the above-mentioned examples. Therefore, different embodiments will be described below.

[Abstract]
In Examples 1-3, an example using three abstractions has been described, but the present invention is not limited to this, and the same processing may be performed even if the number is two or four or more. it can.

[system]
Information including processing procedures, control procedures, specific names, various data and parameters shown in written documents and drawings can be arbitrarily changed unless otherwise specified.

Further, each component of each of the illustrated devices is a functional concept, and does not necessarily have to be physically configured as shown in the figure. That is, the specific form of distribution / integration of each device is not limited to the one shown in the figure. That is, all or a part thereof can be functionally or physically distributed / integrated in any unit according to various loads, usage conditions, and the like. Further, each processing function performed by each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.

[Hardware configuration]
FIG. 44 is a diagram showing a hardware configuration example. As shown in FIG. 44, the network design device 10 includes a communication interface 10a, an input device 10b, an output device 10c, an HDD (Hard Disk Drive) 10d, a RAM (Random Access Memory) 10e, and a CPU (Central Processing Unit) 10f. ..

The communication interface 10a is a network interface card, a short-range wireless interface, or the like that controls communication of other devices. The input device 10b is a device that receives input from the user, such as a mouse or a keyboard. The output device 10c is a device that outputs various information, such as a display. The HDD 10d is a storage device that stores various types of information.

The RAM 10e is an example of a memory, and in addition, a RAM (Random Access Memory) such as an SDRAM (Synchronous Dynamic Random Access Memory), a ROM (Read Only Memory), a flash memory, or the like can be adopted. The CPU 10f is an example of a processor, and in addition, a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), a PLD (Programmable Logic Device) and the like can be adopted.

Further, the network design device 10 operates as an information processing device that executes a configuration diagram generation method by reading and executing a program. That is, the network design device 10 executes a program that executes the same functions as the reception unit 20, the logical configuration management unit 21, the auto-completion processing unit 22, and the infrastructure setting unit 23. As a result, the network design device 10 can execute a process of executing the same functions as the reception unit 20, the logical configuration management unit 21, the auto-completion processing unit 22, and the infrastructure setting unit 23. The program referred to in the other embodiment is not limited to being executed by the network design device 10. For example, the present invention can be similarly applied when another computer or server executes a program, or when they execute a program in cooperation with each other.

This program can be distributed over networks such as the Internet. In addition, this program is recorded on a computer-readable recording medium such as a hard disk, flexible disk (FD), CD-ROM, MO (Magneto-Optical disk), or DVD (Digital Versatile Disc), and is recorded from the recording medium by the computer. It can be executed by being read.

10 Network design device 11 Logical configuration DB
12 Complementary device DB
13 Physical configuration DB
20 Reception Department 21 Logical Configuration Management Department 22 Auto Complementary Processing Department 23 Infrastructure Setting Department

Claims (9)

The device information related to each object constituting the system is omitted, and the logical configuration diagram in which the network attribute information including the connection relationship related to the network and the link information related to the connection relationship between the objects are set is included in the logical configuration diagram. A detector that detects each object belonging to both ends of the link
A determination unit that determines the connection relationship of the link according to the network attribute information of the network to which each object belongs, and a determination unit.
With reference to the storage unit that stores information about each network device to be complemented to the logical configuration diagram, a specific unit that identifies the network device required for the determined connection relationship of the link, and a specific unit.
The link included in the logical configuration diagram has a generation unit that generates a physical configuration diagram having a configuration in which network devices, which are physical devices, are arranged in the logical configuration diagram by complementing the specified network device. A block diagram generator characterized by the above. The determination unit determines the connection relationship of the link for each object connected by the link for each degree of abstraction indicating the inclusion relationship of the components of the network.
The configuration diagram generation device according to claim 1, wherein the specific unit identifies the complementary network device based on each connection relationship of the links determined for each degree of abstraction. For the upper object including the network as a lower object, the logical sum of the network attribute information of the network included in the upper object is set as the attribute information, and the lower object included in the network as the lower object. The configuration diagram according to claim 2, wherein the object further has an attribute information setting unit for selecting and setting the attribute information from the network attribute information of the network included in the lower object. Generator. When the determination unit specifies a connection relationship for the link in a state where a hierarchical structure of bases, networks, and nodes is set as the object in the logical configuration diagram, the determination unit determines the connection relationship between the objects connected by the link. , Determine the connection relationship between the objects below the object,
The configuration diagram generation device according to claim 3, wherein the specific unit identifies the complementary network device based on each determined connection relationship. The determination unit, for links connecting between said bases, the end points of the links connecting the connection relationship between the locations, connections between networks configured to end points of the link connecting between said bases, between the bases Judge each of the connection relationships between the nodes that are
The specific unit is characterized in that a network device corresponding to a combination of a connection relationship between the bases, a connection relationship between the networks, and a connection relationship between the nodes is specified from a list of predefined network devices. Item 4. The configuration diagram generating device according to item 4. Regarding the link connecting the networks, the determination unit determines each of the connection relationship between the networks and the connection relationship between the nodes which are the end points of the links connecting the networks.
The configuration diagram according to claim 5, wherein the specific unit specifies a network device corresponding to a combination of a connection relationship between the networks and a connection relationship between the nodes from a list of network devices defined in advance. Generator. The determination unit determines the connection relationship between the nodes for the link connecting the nodes.
The configuration diagram generation device according to claim 6, wherein the specific unit identifies network devices corresponding to the connection relationship between the nodes from a list of network devices defined in advance. The computer
The device information related to each object constituting the system is omitted, and the logical configuration diagram in which the network attribute information including the connection relationship related to the network and the link information related to the connection relationship between the objects are set is included in the logical configuration diagram. Detects each object belonging to both ends of the link
With reference to the storage unit that stores information about each network device to be complemented to the logical configuration diagram, the network device required for the determined connection relationship of the link is specified.
Identify the network device according to the determined connection relationship of the link,
By complementing the specified network device with the link of the logical configuration diagram, a process of generating a physical configuration diagram having a configuration in which the network device which is a physical device is arranged in the logical configuration diagram is executed. A method for generating a configuration diagram, which comprises. On the computer
The device information related to each object constituting the system is omitted, and the logical configuration diagram in which the network attribute information including the connection relationship related to the network and the link information related to the connection relationship between the objects are set is included in the logical configuration diagram. Detects each object belonging to both ends of the link
With reference to the storage unit that stores information about each network device to be complemented to the logical configuration diagram, the network device required for the determined connection relationship of the link is specified.
Identify the network device according to the determined connection relationship of the link,
By complementing the specified network device with the link of the logical configuration diagram, a process of generating a physical configuration diagram having a configuration in which the network device which is a physical device is arranged in the logical configuration diagram is executed. A block diagram generation program characterized by.

Images