Network system and setting method

Abstract

To easily configure network devices without using a network diagram. [Solution] A designation unit allows a user to designate a device ID, a common item name, and a setting value without using a network diagram. A recording unit associates the designated device ID, the common item name, and the setting value and stores them in a memory unit. A reception unit accepts a device ID from a second user. An acquisition unit acquires from the memory unit the common item name and the setting value that are stored in association with the accepted device ID. A generation unit generates an individual module using the accepted device ID and the acquired common item name and setting value.

Description

[Technical Field]

[0001] The present invention relates to a network system and a setting method. [Background technology]

[0002] Conventionally, in order to use a device connected to a network, a user has had to configure network settings for the device and applications installed on the device. Patent document 1 discloses software that automatically generates configuration information for network devices in a network that is about to be constructed according to their model when network needs such as resource allocation and route selection are specified using a network diagram. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-368743 Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present invention is to provide a network system that allows easy configuration of network devices, and a method for configuring the network system. [Means for solving the problem]

[0005] According to one aspect of the present invention, a network system includes a storage server, a setting server, and a plurality of devices each capable of processing an individual module of a different format, wherein the individual modules include values ​​of a plurality of common items that are setting items commonly used regardless of the type of device, and the storage server includes a designation unit that allows a first user to designate, without using a network diagram, a device ID that is an ID that identifies one of the plurality of devices, a common item name that uniquely identifies one of the plurality of common items, and a setting value of the common item indicated by the common item name, and a setting value of the common item designated by the designation unit. and a recording unit that stores the individual module in a memory unit in association with the setting value received by the second user, wherein the setting server comprises a reception unit that receives the device ID from the second user, an acquisition unit that acquires from the memory unit the common item name and the setting value stored in association with the device ID received by the reception unit, and a generation unit that uses the device ID received by the reception unit and the common item name and the setting value acquired by the acquisition unit to generate the individual module in a format that can be processed by the device indicated by the device ID received by the reception unit, and each of the plurality of devices comprises a reception unit that receives the individual module generated by the setting server. [Effects of the Invention]

[0006] According to the above aspect, it is possible to easily configure network devices. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a schematic diagram showing a configuration of a network system according to a first embodiment. [Figure 2] FIG. 2 is a block diagram showing the software configuration of the database device according to the first embodiment. [Figure 3] 3A and 3B are diagrams illustrating an example of a module format and individual modules according to the first embodiment. [Figure 4] 10 is an example of an editing screen for a device table according to the first embodiment. [Figure 5] 10 is an example of an interface editing screen for a logical device according to the first embodiment. [Figure 6] 10 is an example of an interface addition screen for a logical device according to the first embodiment. [Figure 7] 10 is an example of an edit screen for an interface table according to the first embodiment. [Figure 8] FIG. 2 is a block diagram showing the software configuration of the setting device according to the first embodiment. [Figure 9] 4 is a first flowchart showing a setting process of a network device according to the first embodiment. [Figure 10] 10 is a second flowchart showing the device setting process according to the first embodiment. [Figure 11] 10 is a third flowchart showing the device setting process according to the first embodiment. [Figure 12] FIG. 1 is a schematic block diagram illustrating the configuration of a computer according to at least one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] First Embodiment Network System Configuration Hereinafter, the embodiments will be described in detail with reference to the drawings. FIG. 1 is a schematic diagram illustrating the configuration of a network system 1 according to a first embodiment. The network system 1 according to the first embodiment configures physical devices 50, which are devices for configuring a network for multiple plants P. The multiple plants P are installed in different areas. In the embodiment, a "physical device 50" refers to a physical device incorporating an electrical circuit. On the other hand, a device handled in a database during the design phase is referred to as a "logical device." By implementing a logical device through configuration of an unconfigured physical device 50, the physical device 50 becomes operational. Device configuration includes network configuration, software configuration, and hardware configuration. Examples of device configuration include installing an OS on a device, installing package management software, installing a specific version of specific software using package management software, initial configuration of the installed software, partitioning multiple storage devices, configuring whether to configure RAID for storage, configuring the RAID type, configuring the device boot order, configuring network boot, configuring local boot, and configuring remote storage mounting. In the embodiment, information used to configure an individual physical device 50 is called an "individual module." Examples of individual modules include a configuration file, a batch file for configuration, and a command sequence.

[0009] The network system 1 includes a database device 10 and a setting device 30. The database device 10 stores setting information of logical devices that should constitute a network of multiple plants P. The database device 10 has a CMDB (Configuration Management Database) and DCIM (Data Center Infrastructure Management) / IPAM (IP Address Management) function. The setting device 30 configures the physical devices 50 based on the information stored in the database device 10. The setting device 30 is installed in a setting facility C away from the plant P. The setting facility C may include one or more setting devices 30. When multiple setting devices 30 are installed, the multiple setting devices 30 can configure the physical devices 50 through parallel processing. The setting device 30 may be installed not only in the setting facility C but also in the plant P. When the setting device 30 is installed in the plant P, the setting device 30 can configure the physical devices 50 already installed in the plant P on-site. A user can access the user interface of the setting device 30 from any location via a network. For example, the setting device 30 has a web interface that can be displayed using a web browser. The setting device 30 may be configured by a UI server that provides a UI such as a web interface and multiple setting terminals that access the UI server. The UI server manages the generation conditions of individual modules and the execution order of the individual modules. The setting terminal generates individual modules in accordance with the generation conditions for the individual modules managed by the UI server, and executes the generated individual modules in the execution order managed by the UI server.

[0010] The physical devices 50 are configured at a configuration facility C. The configured physical devices 50 are transported to the corresponding plants P and connected to the network of the plants P. The configuration facility C is responsible for configuring the physical devices 50 used in the multiple plants P. If a configuration device 30 is also provided in the plant P, the multiple physical devices 50 may be configured in the plant P. In other words, the physical devices 50 can be configured at any location as long as they can be connected to any of the configuration devices 30.

[0011] <Configuration of database device 10> FIG. 2 is a block diagram showing the software configuration of the database device 10 according to the first embodiment. The database device 10 includes a storage unit 11, a web server unit 12, a recording unit 13, and a query processing unit 14. The storage unit 11 stores a plant master 111 , a device type master 112 , a device table 113 , an interface table 114 , an IP address table 115 , a VLAN table 116 , a network address table 117 , a connection information table 118 , and a module format table 119 .

[0012] The plant master 111 is a table that stores information about the plant P in which the logical device is placed. For each plant P, the plant master 111 stores a plant ID, a plant name, and policy information indicating the security policy of the plant P in association with each other. The policy information indicates communication rules. The policy information is expressed, for example, using whether communication is permitted or not. In other words, if the target plant P has a first plant P1 and a second plant P2, the plant master 111 records policy information for the first plant and policy information for the second plant. The plant master 111 may also store information about the plant P, such as the organization name, owner name, geographical information, and location. The organization name is the name of the organization that operates the plant P. The owner name is the name of the owner of the plant P. The geographic information is the geographical position of the plant P expressed by latitude and longitude. The location is information indicating the location within the building of the plant P.

[0013] The device type master 112 is a table that stores information about the model of the physical device 50. The device type master 112 stores, for each model, a model ID (model name), conversion data, and default setting data in association with each other. An example of conversion data is data that associates common item names, regardless of model, with individual item names (device-processable item names) used in network configuration for that model. The conversion data is used to convert item names, etc., for configuration purposes during network configuration. The conversion data associates at least a common interface name with an individual interface name used in the configuration information for the physical device 50 of that model. Names (individual interface names) are assigned in advance to multiple network interfaces in the physical device 50 for each model, and network configuration requires identifying the network interface by its individual interface name. The individual interface name differs for each model of the physical device 50. For example, in a first model, the individual interface name of the first LAN interface from the top and first from the left may be "internal1," while in a second model, the individual interface name of the first LAN interface from the top and first from the left may be "lan1." Note that item names that require conversion are not limited to interface names. The default setting data stores the value of an item that can be uniquely determined in the network settings of the physical device 50. An example of an item stored in the default setting data is the setting language. For example, for a model that can be set to the language of the region where the device is installed (e.g., Japanese), "setting language="Japanese"" is stored in the default setting data, and for a model that cannot be set to the language of the region where the device is installed, "setting language="English"" is stored in the default setting data. The default setting data is expressed as a combination of an item name and a setting value, such as in JSON. The device type master 112 may further store information about the model of the physical device 50, such as the series name, manufacturer name, and platform information. The series name is the name of the series (brand, model) of the model. The platform information is information about the system that is installed as the platform for the model. For example, the platform information may include the name and version of the OS that is the operating platform for the software, or the database engine that is the operating platform for the database.

[0014] The device table 113 is a table that stores information about logical devices. For each logical device, the device table 113 stores a device ID, a device name, the plant ID of the plant P in which the logical device is installed, and a model ID indicating the model of the physical device 50 in which the logical device is implemented, in association with each other. The model ID is specified in the device type master 112. The device table 113 may also store, as logical device information, an owner name, a location, maintenance information, application setting information, and the like. The owner name is the name of the owner of the logical device. The owner name may represent the name of the owner of the plant P or the building in which the logical device is installed. The device table 113 may record multiple owner names for one logical device. The location is information indicating where the logical device is installed in the plant P. The location is lower-level information of the geographical information of the plant P and represents further divisions of the plant P, such as the building, floor, or room. The maintenance information is information such as the warranty period and maintenance contract period for the logical device. The application setting information is setting information for an application that runs on a physical device corresponding to a logical device, and includes, for example, the name and version of the application to be installed.

[0015] The interface table 114 stores information about network interfaces provided in logical devices. The interface table 114 associates and stores interface IDs, device IDs of logical devices, and common interface names. The common interface name is a name for identifying a physical network interface regardless of the model of the physical device 50. For example, if the physical device 50 has multiple network interfaces, the multiple network interfaces are typically arranged on the same side of the chassis. The common interface name according to the first embodiment may identify the network interface by its row number and column number. However, it is preferable that the common interface name is abstract and does not specify a physical location. In this case, the network system 1 can determine the physical location by combining the common interface name with conversion data, which can be used as the interface name for configuration. For example, the common interface name of the Nth LAN interface from the top and the Mth LAN interface from the left may be "LAN_N / M." Specifically, the common interface name of the second LAN interface from the top and the fourth LAN interface from the left may be "LAN_02 / 04." The common interface name is an example of a common item name. Furthermore, the common interface name according to the first embodiment may identify the network interface by a number regardless of the physical location. The interface table 114 may further store type information, VLAN ID, and the like as information about the network interface. The type indicates, for example, physical interfaces such as wired and wireless, band, and virtual interfaces such as LAG (Link Aggregation Group) and VPN (Virtual Private Network). The VLAN ID is an ID indicating a group of VLANs that divide a network into virtual logical groups. By using a VLAN, multiple physical devices provided on the same physical network can exist virtually on different networks. The VLAN ID is an ID associated with VLAN information stored in the VLAN table 116, which will be described later. If the network is not divided by VLANs, the value of the VLAN ID may be blank.

[0016] The IP address table 115 is a table for storing information on IP addresses assigned to network interfaces of logical devices. The IP address table 115 stores IP address values ​​in association with interface IDs that indicate the interfaces to which the IP addresses are assigned.

[0017] The VLAN table 116 is a table that stores configuration information for a virtual local area network (VLAN) of a logical device. The VLAN table 116 stores a VLAN ID, a VLAN name, and a plant ID in association with each other. The VLAN ID is identification information for identifying a VLAN. It is preferable that a VLAN ID be unique within the same plant, but overlapping is permitted between different plants, and overlapping may also be permitted within the same plant. The prefix associated with the VLAN can be obtained by referring to the network address table 117.

[0018] The network address table 117 is a table that manages information related to network segments. The network address table 117 stores a network segment ID, a prefix, a plant ID, and a VLAN ID in association with each other. The network segment ID is identification information that uniquely identifies a network segment. The prefix is ​​the prefix value of a network address for identifying the network segment. The VLAN ID is a VLAN ID that indicates the VLAN associated with the network segment. If no VLAN is set for the network segment, the value of the VLAN ID may be blank. In this embodiment, the network address table stores a VLAN ID so that the corresponding VLAN can be referenced. However, in other embodiments, the network address table may store, for example, a primary key of the VLAN table 116 instead of the VLAN ID.

[0019] The connection information table 118 is a table for managing information regarding connections between network interfaces. The connection information table 118 stores a device ID of a connection source, an interface ID of a connection source, a device ID of a connection destination, and an interface ID of a connection destination in association with each other. A combination of a device ID and an interface ID may be treated as a single value. In another embodiment, the connection information table 118 may store an interface ID of a connection source and an interface ID of a connection destination in association with each other. In this case, the network system 1 can identify the device ID from the interface ID by referring to the interface table 114.

[0020] The module format table 119 is a table that stores, for each model of physical device 50, a module format MF, which is the format of an individual module for configuring a physical device 50. FIG. 3 is a diagram showing examples of a module format MF and an individual module IM according to the first embodiment. For each item to be configured, the individual module IM includes a command name, a first parameter indicating the item to be executed, and a second parameter indicating the setting value of the item. The command name may be different for each physical device 50 and for each item to be configured. Examples of command names include "set" and "change." Examples of first parameters include "hostname," "language," and "timeout." Note that some commands may have one parameter or three or more parameters. In the module format MF, as shown in FIG. 3, the first and second parameters are represented by variables, and the values ​​of the variables represent the item names or setting values ​​to be assigned.

[0021] 3, the module format MF includes variables {device.name}, {interface.common_name}, {ip_address.ip_address}, {vlan.vlan_id}, and {vlan.vlan_name}. {device.name} is a variable for substituting a device name from the device table 113. {interface.common_name} is a variable for substituting a common interface name from the interface table 114. {ipaddress.ipaddress} is a variable for substituting an IP address from the IP address table 115. {vlan.vlan_id} is a variable for substituting a VLAN ID from the VLAN table 116. {vlan.vlan_name} is a variable for substituting a VLAN name from the VLAN table 116. By substituting values ​​for each variable in the module format MF, an individual module IM is generated as shown in Figure 3. The values ​​substituted for each variable may be the table values ​​themselves, or may be values ​​obtained by performing a predetermined conversion process on the table values.

[0022] Web server unit 12 receives access from an administrator of network system 1 via a web browser or the like. In response to the access, web server unit 12 creates an editing screen, which is a web page for editing the table values ​​stored in storage unit 11, and displays the editing screen on the web browser. Web server unit 12 receives input of table values ​​from the administrator via the editing screen.

[0023] FIG. 4 shows an example of an editing screen for the device table 113 according to the first embodiment. The editing screen for the device table 113 includes a device list L1 in which logical devices are arranged vertically and item names are arranged horizontally. Each cell in the device list L1 is an input form. Specifically, the device list L1 is a list that stores the device ID, device name, plant name, and model name for each logical device, as well as an edit button and a details button for the interface. In the device list L1, the cells that display the device name, plant name, and model name are input forms. The input form for the device name is a text box, and the input forms for the plant name and model name are drop-down lists. The plant name can be selected from the plant names stored in the plant master 111. The model name can be selected from the model names stored in the device type master 112. The device list L1 is an example of an editing list. An Add button is included on the editing screen for the device table 113. When the Add button is pressed, an Add screen is displayed that accepts input of information about a new logical device. When the Details button in the device list L1 is pressed, an individual detailed editing screen for the logical device corresponding to the pressed row is displayed. The individual detailed editing screen includes an input form for each item of the logical device, and each item can be edited. In other words, the user can perform editing processes for multiple logical devices in parallel using the input form of the device list L1 shown in Figure 4, or can perform editing processes for individual logical devices from the detailed editing screen.

[0024] 5 is an example of an interface editing screen for a logical device according to the first embodiment. When a user presses an interface editing button in the device list L1, the web server unit 12 generates an interface editing screen for the logical device corresponding to the pressed row. The interface editing screen for the logical device includes an individual interface list L11 in which the interfaces of the selected logical device are arranged vertically and item names are arranged horizontally. Each cell in the individual interface list L11 is an input form. Specifically, the individual interface list L11 is a list that stores the interface ID, common interface name, IP address, and connection destination for each interface. In the individual interface list L11, the cells that display the IP address and connection destination are input forms. The IP address input form includes a list and an Add button. The list displays the IP addresses assigned to the interface. A Delete button (the "X" button in FIG. 5) is assigned to each IP address, and pressing the assigned Delete button deletes the IP address. Pressing the Add button displays a combo box. In the combo box, it is possible to select one IP address from those registered in the IP address table 115. When an IP address not registered in the IP address table 115 is entered into the input form, the recording unit 13 creates information related to the IP address and newly registers the information in the IP address table 115. The selected or entered IP address is added to the list. The input form for the connection destination includes a drop-down list of device names and a drop-down list of common interface names. The device name can be selected from the device names stored in the device table 113. The common interface name can be selected from the common interface names stored in the device type master 112 in association with the model of the logical device selected in the device name drop-down list.

[0025] FIG. 6 is an example of an interface addition screen for a logical device according to the first embodiment. The interface editing screen for a logical device includes a Create button. When the Add button is pressed, an interface addition screen is displayed, which accepts input of information about a new interface provided for the logical device. The interface addition screen for a logical device includes input forms for each item related to the new interface. Specifically, the interface addition screen includes input forms for the device name, common interface name, IP address, connection destination, and the like. The name of the selected logical device is pre-entered in the input form for the logical device on the interface addition screen. Note that in other embodiments, the connection destination may be edited on a connection information setting screen that is provided separately from the interface addition screen.

[0026] FIG. 7 shows an example of an editing screen for the interface table 114 according to the first embodiment. The web server unit 12 can create an editing screen for editing information relating to a plurality of interfaces registered in the interface table 114. The editing screen for the interface table 114 includes an interface list L2 in which the interfaces of each logical device are arranged vertically and the item names are arranged horizontally. Each cell in the interface list L2 is an input form. Specifically, the interface list L2 stores the interface ID, device name, common interface name, and IP address for each interface. The cells in the interface list L2 that display the device name, interface name, and IP address are input forms. The input form for the device name is a drop-down list. The device name can be selected from the device names stored in the device table 113. The drop-down list for the device name is an example of a common item name form. The input form for the interface name is a combo box. The combo box is a form that combines a text box that accepts free input of a string and a drop-down list. The interface name can be selected from a predetermined list of available interface names. Furthermore, if an interface name not registered in the interface table 114 is entered in the input form, the recording unit 13 creates interface information for the interface name and newly registers the information in the interface table 114. The interface list L2 is an example of an edit list. The IP address input form includes a list and an Add button. The list displays the IP addresses assigned to the interface. A Delete button (the "X" button in FIG. 7) is assigned to each IP address, and pressing the assigned Delete button deletes the IP address. Pressing the Add button displays a combo box. In the combo box, it is possible to select one IP address from those registered in the IP address table 115. When an IP address not registered in the IP address table 115 is entered into the input form, the recording unit 13 creates information related to the IP address and newly registers the information in the IP address table 115. The selected or entered IP address is added to the interface list L2. An Add button is included on the editing screen for the interface table 114. When the Add button is pressed, an Add screen is displayed that accepts input of information about a new interface.

[0027] As described above, the web server unit 12 accepts input of values ​​of common item names such as device names and common interface names on the editing screens shown in Figures 4 to 7. In other words, the web server unit 12 is an example of a designation unit that allows a user to designate a device ID, a common item name that uniquely identifies one of multiple common items, and a setting value of the common item indicated by the common item name without using a network diagram. Note that in other embodiments, the designation unit does not have to be a web server unit. In other words, the network system 1 according to other embodiments may accept designation of setting values ​​without going through a web interface.

[0028] The recording unit 13 updates the table based on the values ​​changed on the editing screen displayed by the web server unit 12. For example, when a device name is changed in the device list L1 shown in Fig. 4, the recording unit 13 identifies the device ID for the changed row and updates the value of the device name associated with the identified device ID in the device table 113 to the changed value. Also, for example, when a plant name is changed in the device list L1 shown in Fig. 4, the recording unit 13 identifies the device ID for the rewritten row and updates the value of the plant ID associated with the identified device ID in the device table 113 to the value of the plant ID associated with the changed plant name in the plant master 111. For example, when a device name in the interface list L2 shown in Fig. 7 is changed, the recording unit 13 identifies the interface ID related to the changed row, and updates the value of the device ID associated with the identified interface ID in the interface table 114 to the value of the device ID associated with the changed device name in the device table 113. Also, for example, when the value of an IP address in the interface list L2 shown in Fig. 7 is changed, the recording unit 13 identifies the interface ID related to the rewritten row, and updates the value of the interface ID associated with the changed IP address in the IP address table 115 to the identified interface ID. Furthermore, the recording unit 13 updates the table based on data entered on the add screen that is displayed when the add button on the edit screen is pressed.

[0029] The query processing unit 14 acquires information stored in the storage unit 11 in accordance with the input query.

[0030] Setting device 30 FIG. 8 is a block diagram showing the software configuration of the setting device 30 according to the first embodiment. The setting device 30 includes a storage unit 31 , a receiving unit 32 , an acquiring unit 33 , a determining unit 34 , a deciding unit 35 , a generating unit 36 ​​, and a setting unit 37 .

[0031] The receiving unit 32 receives an input of the device ID of the logical device to be implemented in the physical device 50 from an operator who configures the physical device 50 . The acquiring unit 33 acquires information used to create an individual module IM for implementing a logical device associated with the device ID input from the database device 10 in the physical device 50. Specifically, the acquiring unit 33 generates a query for obtaining information based on the device ID input to the receiving unit 32, and transmits the generated query to the database device 10. This allows the acquiring unit 33 to acquire, as a response to the query, information used to create an individual module IM for implementing the logical device in the physical device 50 from the database device 10. The information acquired by the acquiring unit 33 includes pairs of item names and setting values, default setting data, and conversion data.

[0032] The determination unit 34 determines whether an individual item name is set in the conversion data for each of the item names and setting values ​​acquired by the acquisition unit 33. For example, the determination unit 34 determines that a corresponding individual item name (individual interface name) is set in the conversion data for the setting value "LAN_01 / 01" associated with the item name "common interface name" acquired from the interface table. Note that in the example of the common interface name, an individual item name is set for the setting value, but for other items, individual item names may be set for the item names. For example, in the case where there are models that set a 32-bit value indicating a subnet mask and models that set an integer value indicating a prefix length to set the field indicating the network address in an IP address, the individual item name "subnet mask" or the individual item name "prefix length" may be set for the item name "network address field." For example, if the host name to be set for a device cannot be set to the device name registered in the storage server due to specifications such as a character limit, the individual item name "short host name" may be set for the item name "device name." A program that realizes the functions of the determination unit 34 may be recorded in the database device 10. In this case, the setting device 30 may have the functions of the determination unit 34 by downloading the program from the database device 10 and executing it. In this case, even if the network system 1 has multiple setting devices 30, the functions of the determination unit 34 can be managed in a unified manner.

[0033] The determination unit 35 determines a value to be used for the first parameter of the individual module IM. When the determination unit 34 determines that an individual item name has been set, the determination unit 35 determines to use the individual item name for the first parameter of the individual module IM. When the determination unit 34 determines that an individual item name has not been set, the determination unit 35 determines to use the item name or a set value for the first parameter of the individual module IM.

[0034] The generation unit 36 ​​generates an individual module IM used to implement the logical device in the physical device 50 by applying the information acquired by the acquisition unit 33 and the value determined by the determination unit 35 to a format stored in the memory unit 31. The setting unit 37 sets up the physical device 50 using the individual module IM generated by the generating unit 36 ​​. The programs that realize the functions of the acquiring unit 33, the determining unit 35, and the generating unit 36 ​​may be recorded in the database device 10. In this case, the setting device 30 may have the functions of the acquiring unit 33, the determining unit 35, and the generating unit 36 ​​by downloading and executing the programs from the database device 10. Note that the programs may be prepared for each model of device to which they are applied, and may be selected and executed according to the model of the physical device 50.

[0035] <<Network design>> FIG. 9 is a first flowchart showing the setting process of the network device according to the first embodiment. A network designer accesses the database device 10 and inputs network design information into the device table 113, the interface table 114, and the IP address table 115 (step S1). Note that, since the specific model of the physical device 50 may not be decided at the network design stage, the value of the model ID in the device table 113 may be blank at the design stage. Note that, if the model of the physical device 50 to be implemented does not exist in the device type master 112, the designer inputs model information into the device type master 112 as design information (step S2). Note that the model information may be input into the device type master 112 when the model of the physical device 50 is decided. If the model of the physical device 50 to be implemented exists in the device type master 112, the designer does not need to perform the process of step S2.

[0036] 10 is a second flowchart showing the device configuration process according to the first embodiment. When the design is completed, the configuration operator determines the model of the physical device 50 that will implement each logical device registered in the device table 113. The network configuration operator links the design information with the model information by inputting a value indicating the determined model into the model ID of the device table 113 (step S3).

[0037] 11 is a third flowchart showing the device setting process according to the first embodiment. Next, the device installer connects the unconfigured physical device 50 of the determined model to the setting device 30 (step S4). The physical device 50 and the setting device 30 may be connected via a network, such as a LAN, or via other means such as USB. At the stage of implementing a logical device in the physical device 50, at least the model ID of the model to be configured must be recorded in the device table 113.

[0038] The network setup operator inputs the device ID of the logical device to be implemented in the physical device 50 connected in step S4 into the setup device 30. The reception unit 32 of the setup device 30 receives the input of the device ID value (step S5).

[0039] The acquisition unit 33 generates a query for obtaining information from the database device 10 using the value of the device ID input in step S4, and transmits the query to the database device 10 (step S6). The query generated by the acquisition unit 33 is A query to retrieve a tuple (first tuple) having the input value as the device ID from the device table 113. A query to obtain a tuple (second tuple) having the input value as the device ID from the interface table 114; A query to acquire a tuple (third tuple) relating to the value of the model ID relating to the first tuple from the device type master 112; A query to acquire a tuple (fourth tuple) relating to the value of the plant ID relating to the first tuple from the plant master 111; A query to acquire a tuple (fifth tuple) relating to the value of the interface ID relating to the second tuple from the IP address table 115; A query to obtain a tuple (sixth tuple) relating to the model ID relating to the first tuple from the module format table 119; It also includes a query to obtain tuples related to other devices associated with the first tuple. Note that although the first tuple and the second tuple are both tuples that have the input value as the device ID, they have different values ​​because the first tuple is a tuple in the device table and the second tuple is a tuple in the interface table. The query processing unit 14 of the database device 10 acquires information from each table in accordance with the query sent from the setting device 30 and sends the information to the setting device 30 . The acquiring unit 33 acquires information as a response to the query from the database device 10 (step S7). As a result, the acquiring unit 33 acquires from the database device 10 the device name, the IP address of each interface, setting values ​​such as default setting data, policy information, module format MF, conversion data, and the like.

[0040] The setting device 30 selects one by one the parameter variables included in the module format MF acquired in step S7 (step S8), and executes the following processing from step S9 to step S11.

[0041] The determination unit 34 determines whether the common item name of the selected parameter is a target of conversion data. Specifically, the determination unit 34 determines whether the common item name of the selected parameter is a target of conversion by the conversion data acquired in step S7 (step S9). If the common item name of the selected parameter is a target of conversion (step S9: YES), the determination unit 35 replaces the common item name of the parameter with the individual item name associated with the common item name in the conversion data (step S10). If the common item name of the selected parameter is not a target of conversion by the conversion data (step S9: NO), the determination unit 35 does not change the value of the parameter (step S11).

[0042] When all common item names to be converted in the module format MF have been replaced with individual item names, the generating unit 36 ​​assigns the setting values ​​acquired in step S7 to variables representing the parameters of the module format MF (step S12). At this time, the generation unit 36 ​​adjusts the value of the second parameter based on the policy information acquired in step S6 so as to comply with the security policy of the plant P. Specifically, the generation unit 36 ​​generates setting values ​​of parameters to be combined with the module format MF based on the policy information acquired in step S6 and the setting values ​​acquired in step S7. The generation unit 36 ​​assigns the setting values ​​generated from the policy information to variables of the module format MF that correspond to the parameters generated from the policy information. The generation unit 36 ​​assigns the setting values ​​acquired in step S7 to other variables of the module format MF. Furthermore, since data processing procedures differ depending on the manufacturer, the generation unit 36 ​​may adjust the value of the second parameter depending on the manufacturer. For example, if a router from manufacturer X and a router from manufacturer Y exist on a certain communication path, the data processing procedures of the router from manufacturer X and the router from manufacturer Y may differ. The router from manufacturer X needs to set values ​​for the following parameter group: From To Input interface Output interface, Communication Protocol · Communication availability Manufacturer Y's router must set the following parameter values ​​for each input and output interface: From To Communication Protocol Applicable interface · Communication availability In this way, when the data processing procedure differs depending on the manufacturer, the generating unit 36 ​​sets the parameter values ​​in accordance with the processing procedure for each manufacturer. The processing procedure for each manufacturer may be recorded in advance in the database device 10, for example. The applicable interface is information that specifies the input interface of the router of manufacturer Y or the output interface of the router of manufacturer Y.

[0043] An individual module IM is generated by substituting values ​​for the variables in all rows of the module format MF. The setting unit 37 configures the physical device 50 connected in step S3 in accordance with the generated individual module IM (step S13). If the individual module IM is a configuration file, the setting unit 37 records the configuration file in the physical device 50. If the individual module IM is a batch file, the setting unit 37 executes the batch file. After executing the batch file, the setting unit 37 transmits commands to the physical device 50 in accordance with the batch file. If the individual module IM is a command sequence, the setting unit 37 transmits the command sequence to the physical device 50.

[0044] This completes the configuration of the physical device 50. The configured physical device is transported to the corresponding plant P and incorporated into the network there.

[0045] Here, a specific example of network construction work will be described. For example, when a physical device 50A is installed in the first plant P1 and a physical device 50B is installed in the second plant P2, an installer temporarily installs the physical device 50A and the physical device 50B in the network setting facility C. The installer first connects the physical device 50A to the setting device 30. The installer inputs the device ID of the logical device to be implemented in the physical device 50A into the setting device 30, thereby instructing the setting device 30 to generate an individual module IM that can be processed by the physical device 50A. As a result, the setting device 30 generates the individual module IM according to the process shown in FIG. 11 and performs network settings for the physical device 50A. At this time, the physical device 50A is configured by the individual module IM to comply with the security policy of the first plant P1.

[0046] Next, the installer connects the physical device 50B to the setting device 30. The installer inputs the device ID of the logical device to be implemented in the physical device 50B into the setting device 30, thereby instructing the setting device 30 to generate an individual module IM that can be processed by the physical device 50B. As a result, the setting device 30 generates the individual module IM according to the process shown in FIG. 11 and performs network settings for the physical device 50B. At this time, the physical device 50A is configured by the individual module IM so as to comply with the security policy of the second plant P2.

[0047] The installation worker installs the network-configured physical device 50A in the first plant P1, and the configuration worker installs the network-configured physical device 50B in the second plant P2.

[0048] Actions and Effects As described above, the database device 10 of the network system 1 according to the first embodiment includes a web server unit 12 (designation unit) and a recording unit 13. The web server unit 12 allows a first user, such as a network designer, to designate a device ID that identifies one of a plurality of logical devices, a common item name that uniquely identifies one of a plurality of common items, and a setting value of the common item indicated by the common item name, without using a network diagram. The recording unit 13 associates the device ID designated by the web server unit 12, the common item name designated by the web server unit 12, and the setting value designated by the web server unit 12, and stores them in the storage unit 11. The configuration device 30 of the network system 1 includes a receiving unit 32, an acquiring unit 33, and a generating unit 36. The receiving unit 32 accepts a device ID from a second user, such as a configuration operator. The acquiring unit 33 acquires, from the storage unit 11, the common item name and the setting value to be stored in association with the device ID accepted by the accepting unit 32. The generation unit 36 ​​uses the device ID received by the reception unit 32 and the common item name and setting value acquired by the acquisition unit 33 to generate an individual module IM in a format that can be processed by the logical device indicated by the device ID received by the reception unit 32. Each of the multiple devices includes a receiving unit that receives the individual module IM generated by the setting device 30. This allows the network system 1 to easily configure network devices without using a network diagram. While a network diagram allows intuitive understanding of the connection relationships between network devices, it can be difficult to check setting values, and when there are a large number of devices, it can actually become difficult to read the connection relationships. In contrast, the network system 1 according to the first embodiment allows information about network devices to be configured using a database device 10 having DCIM / IPAM functions.

[0049] Other Embodiments Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design modifications are possible. That is, in other embodiments, the order of the above-described processes may be changed as appropriate. Furthermore, some processes may be executed in parallel. The database device 10 and the setting device 30 according to the above-described embodiments may each be configured as a single computer, or may be configured as separate computers that function in cooperation with each other. In another embodiment, the database device 10 and the setting device 30 may be implemented on the same computer.

[0050] The database device 10 and the setting device 30 according to the above-described embodiment perform network settings for the physical device 50, which is a network device, but are not limited to this. For example, the database device 10 and the setting device 30 according to other embodiments may have a similar configuration to install and set up applications for the physical device 50. For example, the database device 10 may be used for license management of applications.

[0051] <Computer Configuration> FIG. 12 is a schematic block diagram illustrating the configuration of a computer according to at least one embodiment. The computer 70 includes a processor 71 , a main memory 72 , a storage 73 , and an interface 74 . The above-described database device 10 and setting device 30 are each implemented in a computer 70. The operations of the above-described processing units are stored in the form of a program in a storage 73. A processor 71 reads the program from the storage 73, loads it into a main memory 72, and executes the above-described processing in accordance with the program. The processor 71 also allocates storage areas in the main memory 72 corresponding to the above-described storage units in accordance with the program. Examples of the processor 71 include a CPU (Central Processing Unit), a GPU (Graphic Processing Unit), and a microprocessor.

[0052] The program may be for realizing some of the functions to be performed by the computer 70. For example, the program may be combined with other programs already stored in storage or implemented in other devices to perform the functions. In another embodiment, the computer 70 may include a custom LSI (Large Scale Integrated Circuit) such as a PLD (Programmable Logic Device) in addition to or instead of the above configuration. Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), and FPGA (Field Programmable Gate Array). In this case, some or all of the functions realized by the processor 71 may be realized by the integrated circuit. Such an integrated circuit is also an example of a processor. In another embodiment, the computer 70 may be virtualized on one or more computers.

[0053] Examples of storage 73 include a magnetic disk, a magneto-optical disk, an optical disk, and a semiconductor memory. Storage 73 may be an internal medium directly connected to the bus of computer 70, or an external medium connected to computer 70 via interface 74 or a communication line. Furthermore, when this program is distributed to computer 70 via a communication line, computer 70 that receives the program may load the program into main memory 72 and execute the above-described processing. In at least one embodiment, storage 73 is a non-transitory tangible storage medium.

[0054] The program may also be a program for realizing part of the above-described functions. Furthermore, the program may be a so-called differential file (differential program) that realizes the above-described functions in combination with another program already stored in storage 73. [Explanation of symbols]

[0055] 1...Network system 10...Database device 11...Memory unit 111...Plant master 112...Device type master 113...Device table 114...Interface table 115...IP address table 12...Web server unit 13...Recording unit 14...Query processing unit 30...Setting device 31...Memory unit 32...Reception unit 33...Acquisition unit 34...Determination unit 35...Decision unit 36...Generation unit 37...Setting unit 50...Physical device 70...Computer 71...Processor 72...Main memory 73...Storage 74...Interface C...Network setting facility L1...Device list L2...Interface list P...Plant MF...Module format IM...Individual module

Claims

1. A server; Multiple devices with different formats of individual modules that can be processed, A network system having: the plurality of devices includes a first device and a second device different from the first device; The server a generation unit that generates a first individual module that is the individual module in a format that can be processed by the first device, and a second individual module that is the individual module in a format that can be processed by the second device; Including, The first device a first receiving unit that receives the first individual module generated by the generating unit; Including, The second device a second receiving unit that receives the second individual module generated by the generating unit; Including, the first device is installed in a first plant; the second device is installed in a second plant that is in an area different from the first plant; the generation unit generates the first individual module using first policy information indicating a security policy of the first plant, and generates the second individual module using second policy information indicating a security policy of the second plant. A network system comprising:

2. A server; Multiple devices with different formats of individual modules that can be processed, A network system having: the plurality of devices includes a first device and a second device different from the first device; The server a generation unit that generates a first individual module, which is the individual module in a format that can be processed by the first device, and a second individual module, which is the individual module in a format that can be processed by the second device, using a table that associates devices with setting values; Including, The first device a first receiving unit that receives the first individual module generated by the generating unit; Including, The second device a second receiving unit that receives the second individual module generated by the generating unit; Including, A network system comprising:

3. A server; Multiple devices with different formats of individual modules that can be processed, A method for configuring a network system having: the plurality of devices includes a first device and a second device different from the first device; The server a generation unit that generates a first individual module that is the individual module in a format that can be processed by the first device, and a second individual module that is the individual module in a format that can be processed by the second device; Including, The first device a first receiving unit that receives the first individual module generated by the generating unit; Including, The second device a second receiving unit that receives the second individual module generated by the generating unit; Including, The network system setting method includes: A temporary installation step; Instruction steps and a first installation step; a second installation step; Including, The server is installed in a network setting facility; the first device is installed in a first plant that is in an area different from the network setting facility; the second device is installed in a second plant that is in an area different from the network setting facility and the first plant; In the temporary installation step, the first device and the second device are temporarily installed in the network setting facility; In the instructing step, the generating unit is instructed to generate the first individual module and the second individual module; In the first installation step, the first device configured as a network based on the first individual module is installed in the first plant; In the second installation step, the second device configured as a network based on the second individual module is installed in the second plant. A setting method characterized by:

4. The server a display control means for causing a display unit to display a first device ID, which is an ID for identifying the first device, and first plant information, which indicates the first plant, in association with each other, and for causing a display unit to display a second device ID, which is an ID for identifying the second device, and second plant information, which indicates the second plant, in association with each other; 2. The network system according to claim 1, further comprising:

5. the first device and the server are installed in a first plant; 3. The network system according to claim 1, wherein:

Images