Network system and method for setting it up

Abstract

Easily configure network devices without using network diagrams. [Solution] The designation unit allows a device ID, common item name, and setting value to be designated without using a network diagram. The recording unit associates the designated device ID, common item name, and setting value and stores them in the memory unit. The reception unit accepts the device ID from a second user. The acquisition unit acquires the common item name and setting value to be stored in association with the accepted device ID from the memory unit. The 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 needs to configure network settings for the device or an application installed on the device. Patent document 1 discloses software that uses a network diagram to specify network needs such as resource allocation and route selection, and automatically generates configuration information for network devices in the network that is about to be constructed according to the model of the device. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2002-368743 A Summary of the Invention [Problem to be solved by the invention]

[0004] The technology described in Patent Document 1 requires the use of a network diagram. However, while a network diagram can clearly show the connection relationships between devices, it does not allow direct reference to the settings of individual devices or port settings, which can make it difficult to check information required for maintenance. [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, the individual modules including values ​​of a plurality of common items that are setting items commonly used regardless of the type of device, the storage server including 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, the device ID designated by the designation unit, the common item name designated by the designation unit, and the setting value of the common item designated by the designation unit. the setting server comprises a reception unit that receives the device ID from the second user, an acquisition unit that acquires from the storage unit the common item name and the setting value stored in association with the device ID accepted by the acceptance unit, and a generation unit that uses the device ID accepted by the acceptance 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 accepted by the acceptance unit, and each of the multiple devices comprises a receiving unit that receives the individual module generated by the setting server. Effect of the Invention

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

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

[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 showing the configuration of a network system 1 according to the first embodiment. The network system 1 according to the first embodiment performs configuration of a physical device 50, which is a device for configuring a network of a plurality of plants P. The plurality of plants P are provided in different areas. In the embodiment, the "physical device 50" refers to a physical device that incorporates an electric circuit. On the other hand, a device that is handled on a database in the design stage is called a "logical device". By implementing a logical device by configuring an unconfigured physical device 50, the physical device 50 becomes operable. The 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 a specific software using package management software, initial settings of the installed software, partition configuration of multiple storage devices, setting whether or not to configure a RAID for storage, setting the type of RAID, setting the boot order of the device, setting network boot, setting local boot, setting mounting of remote storage, and the like. In the embodiment, information used to configure an individual physical device 50 is called an "individual module." Examples of the individual module 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 configure a network of a plurality of plants P. The database device 10 has a configuration management database (CMDB) and a data center infrastructure management (DCIM) / IP address management (IPAM) function. The setting device 30 sets the physical device 50 based on the information stored in the database device 10. The setting device 30 is provided in a setting facility C away from the plant P. The setting facility C may be provided with one setting device 30 or multiple setting devices 30. When multiple setting devices 30 are provided, the multiple setting devices 30 can set the physical device 50 by parallel processing. The setting device 30 may be provided not only in the setting facility C but also in the plant P. When the setting device 30 is provided in the plant P, the setting device 30 can set the physical device 50 already provided 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 by a web browser. The setting device 30 may be composed of 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 according to the generation conditions of 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 setting facility C. The configured physical devices 50 are transported to the corresponding plants P and connected to the network of the plants P. The setting facility C is responsible for setting the physical devices 50 used in the multiple plants P. If a setting 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 the location can be connected to any of the setting devices 30.

[0011] Configuration of the 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. The plant master 111 stores, for each plant P, 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 the rules for communication. The policy information is expressed, for example, using permission and denial of communication. In other words, when the target plant P has a first plant P1 and a second plant P2, the plant master 111 records the policy information for the first plant and the policy information for the second plant. The plant master 111 may further store information such as an organization name, an owner name, geographical information, and location as information about the plant P. 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 geographic position of the plant P represented 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 the conversion data is data in which a common item name that is not dependent on the model is associated with an individual item name (device processable item name) used in network settings of the model. The conversion data is used to convert the name of an item for setting when setting the network. In the conversion data, at least a common interface name is associated with an individual interface name used in setting information of the physical device 50 of the model. In the physical device 50, names (individual interface names) are assigned in advance to a plurality of network interfaces for each model, and in network settings, it is necessary to identify the network interface by the 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 left in the first row from the top may be "internal1", whereas in a second model, the individual interface name of the first LAN interface from the left in the first row from the top may be "lan1". Note that the item name that needs to be converted is not limited to the interface name. The default setting data stores the value of an item that is 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 in which 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 in which 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 JSON. The device type master 112 may further store the series name, manufacturer name, platform information, etc., as information on the model of the physical device 50. The series name is the name of the series (brand, model) of the model. The platform information is information on the system introduced as the platform of the model. For example, the platform information may include the name and version of the OS that is the operating platform of the software, or the database engine that is the operating platform of the database.

[0014] The device table 113 is a table that stores information about logical devices. The device table 113 stores, for each logical device, a device ID, a device name, a 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 by the device type master 112. The device table 113 may further store an owner name, a location, maintenance information, application setting information, and the like, as information about the logical device. The owner name is the name of the owner of the logical device. The owner name may indicate the name of the owner of the plant P or the building in which the logical device is installed. In the device table 113, a plurality of owner names may be recorded for one logical device. The location is information indicating the place where the logical device is installed in the plant P. The location is subordinate information of the geographical information of the plant P, and indicates a place in the plant P that is further divided, such as a building, a floor, or a room. The maintenance information is information such as the warranty period and the maintenance contract period of 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 is a table that stores information on network interfaces provided in logical devices. The interface table 114 stores an interface ID, a device ID of a logical device, and a common interface name in association with each other. The common interface name is a name for identifying a physical network interface, regardless of the model of the physical device 50. For example, when the physical device 50 has a plurality of network interfaces, the plurality of network interfaces are usually arranged on the same surface of the housing. 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 abstracted without specifying a physical location. In this case, the network system 1 can determine the physical location by combining the common interface name with the conversion data, and can make it usable as the interface name of the setting. For example, the common interface name of the Nth row from the top and the Mth row from the left may be "LAN_N / M". Specifically, the common interface name of the second row from the top and the fourth row 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 the information of the network interface. The type indicates, for example, wired and wireless, which are physical interfaces, bands, and LAG (Link Aggregation Group), VPN (Virtual Private Network), and the like, which are virtual interfaces. 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 be made to exist virtually on different networks. The VLAN ID is an ID associated with the information of a VLAN stored in the VLAN table 116 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 the IP address value and an interface ID indicating the interface to which the IP address is assigned in association with each other.

[0017] The VLAN table 116 is a table that stores setting information of 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 the VLAN ID is unique in the same plant, but overlapping is allowed in different plants, and overlapping may also be allowed within the same plant. Note that a prefix related to a VLAN can be obtained by referring to the network address table 117.

[0018] The network address table 117 is a table for managing 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 for uniquely identifying a network segment. The prefix is ​​a prefix value of a network address for identifying the network segment. The VLAN ID is a VLAN ID indicating a VLAN associated with the network segment. If no VLAN is set in the network segment, the value of the VLAN ID may be blank. In this embodiment, the network address table stores a VLAN ID to enable reference to the corresponding VLAN, but in other embodiments, for example, a primary key of the VLAN table 116 may be stored 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 source device ID, a source interface ID, a destination device ID, and a destination interface ID in association with each other. A combination of a device ID and an interface ID may be handled as a single item value. Note that in other embodiments, the connection information table 118 may store a source interface ID and a destination interface ID 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 a module format MF, which is a format of an individual module for setting the physical device 50, for each model of the physical device 50. FIG. 3 is a diagram showing an example of a module format MF and an individual module IM according to the first embodiment. The individual module IM includes, for each item to be set, 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 set. Examples of the command name include "set" and "change". Examples of the first parameter include "hostname", "language", and "timeout". Note that, depending on the command, there may be one parameter or three or more parameters. In the module format MF, as shown in FIG. 3, the first parameter and the second parameter are represented by variables, and the value of the variable indicates the item name or setting value to be substituted.

[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 device table 113. {interface.common_name} is a variable for substituting a common interface name from interface table 114. {ipaddress.ipaddress} is a variable for substituting an IP address from IP address table 115. {vlan.vlan_id} is a variable for substituting a VLAN ID from VLAN table 116. {vlan.vlan_name} is a variable for substituting a VLAN name from VLAN table 116. By substituting values ​​for each variable in the module format MF, an individual module IM is generated as shown in Fig. 3. The value substituted for each variable may be the value of each table itself, or may be a value obtained by performing a predetermined conversion process on the value in the table.

[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 edit screen, which is a web page for editing the values ​​of the table stored in storage unit 11, and displays the edit screen on the web browser. Web server unit 12 receives input of table values ​​from the administrator via the edit screen.

[0023] FIG. 4 shows an example of an editing screen for the device table 113 according to the first embodiment. The editing screen of 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 in which the device name, plant name, and model name are displayed 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 among the plant names stored in the plant master 111. The model name can be selected from among 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 of 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 detail button of the device list L1 is pressed, an individual detailed edit screen of the logical device corresponding to the pressed row is displayed. The individual detailed edit screen includes an input form for each item of the logical device, and each item can be edited. In other words, the user may perform parallel editing processing for multiple logical devices using the input form of the device list L1 shown in FIG. 4, or may perform editing processing for each individual logical device from the detailed edit screen.

[0024] FIG. 5 shows an example of an interface editing screen for a logical device according to the first embodiment. When a user presses an interface edit button in the device list L1, the web server unit 12 generates an edit screen for the interface of the logical device corresponding to the pressed row. The logical device interface edit screen 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 in which the IP address and connection destination are displayed 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 of the IP addresses registered in IP address table 115. When an IP address not registered in IP address table 115 is entered into the input form, recording unit 13 creates information relating to the IP address and newly registers the information in 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 among the device names stored in the device table 113. The common interface name can be selected from among 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 shows an example of an interface addition screen for a logical device according to the first embodiment. The logical device interface editing screen includes a Create button. When the Add button is pressed, an interface adding screen is displayed that accepts input of information on a new interface that the logical device has. The logical device interface adding screen includes input forms for each item related to the new interface. Specifically, the interface adding screen includes input forms for the device name, common interface name, IP address, connection destination, and the like. In the interface adding screen, the name of the selected logical device is input in advance in the logical device input form. In another embodiment, the connection destination may be edited in a connection information setting screen that is provided separately from the interface adding 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 of 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 of the interface list L2 is an input form. Specifically, the interface list L2 is a list that stores the interface ID, device name, common interface name, and IP address for each interface. In the interface list L2, the cells in which the device name, interface name, and IP address are displayed 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 related to 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 character string and a drop-down list. The interface name can be selected from a list of interface names that are predetermined and available. In addition, when an interface name that is not registered in the interface table 114 is input in the input form, the recording unit 13 creates information on the interface related to 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 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 of the IP addresses 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 relating 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 name and common interface name on the editing screens shown in Figs. 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 a plurality of 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 value changed on the editing screen displayed by the web server unit 12. For example, when the device name in the device list L1 shown in Fig. 4 is changed, the recording unit 13 identifies the device ID related to 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 the plant name in the device list L1 shown in Fig. 4 is changed, the recording unit 13 identifies the device ID related to 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 a 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 addition 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 memory 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 a 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 related to the device ID input from the database device 10 in the physical device 50. Specifically, a query for obtaining information is generated based on the device ID input to the receiving unit 32, and the generated query is transmitted to the database device 10. This enables the acquiring unit 33 to acquire information used to create an individual module IM for implementing a logical device in the physical device 50 from the database device 10 as a response to the query. 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 or not an individual item name is set in the conversion data for each of the item name and the setting value 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. In the example of the common interface name, an individual item name is set for the setting value, but an individual item name may be set for the item name in other items. For example, in a case where there exists a model that sets a 32-bit value indicating a subnet mask and a model that sets an integer value indicating a prefix length in order to set an area indicating a 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 area". For example, in a case where the host name to be set for the 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 for realizing the function of the determination unit 34 may be recorded in the database device 10. In this case, the setting device 30 may have the function 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 a plurality of setting devices 30, the functions of the determination unit 34 can be managed in a centralized 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 is 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 is not set, the determination unit 35 determines to use an 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 configuration unit 37 executes the configuration of the physical device 50 using the individual module IM generated by the generation unit . The programs for realizing 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 the programs from the database device 10 and executing them. Note that the programs may be prepared for each model of the device to which they are applied, and may be selected and executed according to the model of the physical device 50.

[0035] About network design FIG. 9 is a first flowchart showing the setting process of a 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). Since a 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. 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). 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] FIG. 10 is a second flowchart showing the device setting process according to the first embodiment. When the design is completed, the configuration operator determines the model of the physical device 50 that implements 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] FIG. 11 is a third flowchart showing the device setting process according to the first embodiment. Next, the device installation worker connects the unconfigured physical device 50 related to 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 by a LAN, or may be connected via other means such as a 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 to 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 obtain 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) related to the value of the model ID related to the first tuple from the device type master 112; A query to acquire a tuple (fourth tuple) related to the value of the plant ID related to the first tuple from the plant master 111; A query to acquire a tuple (fifth tuple) related to the value of the interface ID related to the second tuple from the IP address table 115; A query to obtain a tuple (sixth tuple) related to the model ID related to the first tuple from the module format table 119; and queries 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 device names, IP addresses 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 processes of steps S9 to S11 below.

[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 an 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 so as to comply with the security policy of the plant P, based on the policy information acquired in step S6. 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. Also, for example, 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, when a router of manufacturer X and a router of manufacturer Y exist on a certain communication path, the router of manufacturer X and the router of manufacturer Y may have different data processing procedures. The router of 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 value according to the processing procedure for each manufacturer. The processing procedure for each manufacturer may be recorded in the database device 10 in advance, for example. The applicable interface is information that specifies the input interface of the manufacturer Y's router or the output interface of the manufacturer Y's router.

[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 sets 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 a command to the physical device 50 in accordance with the batch file. If the individual module IM is a command string, the setting unit 37 transmits the command string to the physical device 50.

[0044] This completes the configuration of the physical device 50. The configured physical device is then transported to the corresponding plant P, where it is incorporated into the network.

[0045] Here, a specific example of network construction work will be described. For example, when a physical device 50A is provided in the first plant P1 and a physical device 50B is provided in the second plant P2, an installation worker temporarily installs the physical device 50A and the physical device 50B in the network setting facility C. The installation worker first connects the physical device 50A to the setting device 30. The installation worker inputs the device ID of a logical device to be implemented in the physical device 50A to 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 set by the individual module IM so as 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 a logical device to be implemented in the physical device 50B to 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 set 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 setup 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 setting device 30 of the network system 1 includes a reception unit 32, an acquisition unit 33, and a generation unit 36. The reception unit 32 accepts a device ID from a second user such as a setting operator. The acquisition unit 33 acquires from the storage unit 11 the common item name and the setting value that are stored in association with the device ID accepted by the reception unit 32. The generation unit 36 ​​uses the device ID accepted by the acceptance 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 accepted by the acceptance 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 set network devices without using a network diagram. While a network diagram allows the connection relationships between network devices to be intuitively understood, it is difficult to check the setting values, and when there are a large number of devices, it may become difficult to read the connection relationships. In contrast, the network system 1 according to the first embodiment allows the information of the network devices to be set 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 changes are possible. That is, in other embodiments, the order of the above-mentioned processes may be changed as appropriate. Also, some of the processes may be executed in parallel. The database device 10 and the setting device 30 according to the above-described embodiment may each be configured by a single computer, or may be configured separately on multiple computers and function by the multiple computers working together. 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 install and set applications for the physical device 50 with a similar configuration. 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 a computer configuration according to at least one embodiment. The computer 70 comprises a processor 71, a main memory 72, a storage 73, and an interface 74. The above-mentioned database device 10 and setting device 30 are each implemented in a computer 70. The operations of the above-mentioned processing units are stored in the storage 73 in the form of a program. The processor 71 reads the program from the storage 73, loads it in the main memory 72, and executes the above-mentioned processing in accordance with the program. The processor 71 also secures storage areas in the main memory 72 corresponding to the above-mentioned 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 a part of the functions to be performed by the computer 70. For example, the program may be for realizing the functions by combining with other programs already stored in the storage or by combining with other programs implemented in other devices. 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 the above configuration 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, a part or all of the functions realized by the processor 71 may be realized by the integrated circuit. Such an integrated circuit is also included in 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, a semiconductor memory, etc. 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. In addition, 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-mentioned processing. In at least one embodiment, storage 73 is a non-transitory tangible storage medium.

[0054] The program may be for realizing part of the above-mentioned functions. Furthermore, the program may be a so-called difference file (difference program) that realizes the above-mentioned functions in combination with another program already stored in the 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 network system having a storage server, a setting server, and a plurality of devices each having a different type of processable individual module, The individual module includes values ​​of a plurality of common items that are setting items commonly used regardless of the type of device, The storage server includes: a designation unit that allows a first user to designate a device ID that is an ID for identifying 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, without using a network diagram; a recording unit that causes a storage unit to store the device ID designated by the designation unit, a common item name designated by the designation unit, and a setting value designated by the designation unit in association with each other; Equipped with The configuration server, a reception unit that receives the device ID from a second user; an acquisition unit that acquires from the storage unit the common item name and the setting value that are stored in association with the device ID accepted by the acceptance unit; a generation unit that generates the individual module in a format that can be processed by a device indicated by the device ID accepted by the acceptance unit, using the device ID accepted by the acceptance unit and the common item name and the setting value acquired by the acquisition unit; Equipped with Each of the plurality of devices comprises: a receiving unit for receiving the individual module generated by the configuration server; A network system comprising:

2. the designation unit causes a display unit to display an edit list that is a list showing a relationship between the common item name and the setting value for each device ID, the edit list including a setting value form in which at least the setting value can be edited. The network system according to claim 1 .

3. the editing list includes a common item name form in which the common item name can be edited; In the common item name form, the common item name can be selected from a list of names that can be used as a predetermined common item name. The network system according to claim 2 .

4. The individual module generated by the generator includes one or more commands, The command includes a command name and a first parameter indicating an item to be executed; The configuration server, a determination unit that determines whether or not a device-processable item name defined as a name processable by the device exists for the common item name acquired by the acquisition unit; a determination unit that, when a device-processable item name exists for the common item name acquired by the acquisition unit, determines the device-processable item name corresponding to the common item name as a first parameter of the command, and, when a device-processable item name does not exist for the common item name acquired by the acquisition unit, determines a setting value corresponding to the common item name as the first parameter; The network system of claim 1 further comprising:

5. The acquisition unit transmits the device ID accepted by the acceptance unit to the storage server, and receives the common item name and the setting value stored in association with the device ID from the storage server. The network system according to claim 1 .

6. The acquisition unit acquires the common item name and the setting value stored in the storage unit in association with the device ID by issuing a query including the device ID accepted by the acceptance unit to the storage server. The network system according to claim 1 .

7. The individual module generated by the generator includes one or more commands, The command is represented by a command name and a first parameter indicating an item on which the command is to be executed; the storage unit stores, for each type of device, the common item name and a device processable item name defined as a name processable by the device for the common item name used in an individual module of the device in association with each other; The configuration server, a storage unit that stores a format of an individual module that associates the common item name with a command name used to set an item related to the common item name for each type of device; a determination unit that determines whether or not the device processable item name exists for an item corresponding to the common item name acquired by the acquisition unit; a determination unit that, when a device-processable item name exists for an item corresponding to the common item name acquired by the acquisition unit, determines the device-processable item name corresponding to the common item name as a first parameter of the command, and, when a device-processable item name does not exist for an item corresponding to the common item name acquired by the acquisition unit, determines the common item name as the first parameter; Further equipped with The generating unit generates, for each of the common item names, the command including the command name stored by the storing unit in association with the common item name and the first parameter determined by the determining unit. The network system according to claim 1 .

8. the individual modules generated by the generation unit include a module for performing network settings for an application of a device indicated by the device ID accepted by the acceptance unit; The network system according to claim 1 .

9. the plurality of devices includes a first device and a second device; The storage server and the configuration server are installed in a network configuration 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. The network system according to any one of claims 1 to 8.

10. The storage unit is First policy information indicating a security policy of the first plant; Second policy information indicating a security policy of the second plant; Remember The network system according to claim 9.

11. A method for setting up a network system according to claim 10, comprising the steps of: a temporary installation step of temporarily installing the first device and the second device in the network setting facility; a first instruction step of instructing the generating unit to generate a first individual module, which is the individual module that can be processed by the first device, by using the common item name and the setting value associated with the device ID that is accepted by the accepting unit and indicates the first device, and the first policy information; a second instruction step of instructing the generating unit to generate a second individual module, which is the individual module that can be processed by the second device, by using the common item name and the setting value associated with the device ID that is accepted by the accepting unit and indicates the second device, and the second policy information; a first installation step of installing the first device, which is network-configured based on the first individual module, in the first plant; a second installation step of installing the second device, which is network-configured based on the second individual module, in the second plant; A setting method having the following features:

Images