Network system and configuration method

Abstract

Easily configure network devices without using network diagrams. [Solution] The designation unit allows the user to specify the device ID, common item name, and setting value without using a network diagram. The recording unit stores the designated device ID, common item name, and setting value in the storage unit in association with them. The reception unit receives the device ID from the second user. The acquisition unit retrieves the common item name and setting value stored in association with the received device ID from the storage unit. The generation unit generates individual modules using the received 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 Art

[0002] Conventionally, in order for a user to use a device connected to a network, it has been necessary to perform network settings for the device or an application installed on the device. Patent Document 1 discloses software that automatically generates setting information for network devices of a network to be constructed in accordance with the model thereof 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

Summary of the Invention

Problems to be Solved by the Invention

[0004] The technique described in Patent Document 1 is an essential configuration that uses a network diagram. However, while a network diagram can clearly show the connection relationship between devices, it is not possible to directly refer to the settings of individual devices or ports, and it may be difficult to confirm the information necessary for maintenance.

Means for Solving the Problems

[0005] According to one aspect of the present invention, a network system is a network system having a storage server, a configuration server, and a plurality of devices, each having different forms of individual modules that can be processed, wherein the individual modules include values ​​of a plurality of common items, which are configuration items that are used in common regardless of the type of device, and the storage server has a designation unit that allows a first user to specify, without using a network diagram, a device ID which is an ID that identifies one of the plurality of devices, a common item name which 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 specified by the designation unit, the common item name specified by the designation unit, and the specified by the designation unit The setting server comprises a recording unit that associates and stores setting values ​​in a storage unit, and the setting server comprises a receiving unit that receives the device ID from a second user, an acquisition unit that acquires the common item name and the setting value stored in association with the device ID received by the receiving unit from the storage unit, and a generation unit that uses the device ID received by the receiving unit and the common item name and the setting value acquired by the acquisition unit to generate an individual module in a format that can be processed by the device indicated by the device ID received by the receiving unit, and each of the plurality of devices comprises a receiving unit that receives the individual module generated by the setting server. [Effects of the Invention]

[0006] According to the above embodiment, network devices can be easily configured. [Brief explanation of the drawing]

[0007] [Figure 1] This is a schematic diagram showing the configuration of the network system according to the first embodiment. [Figure 2] This is a block diagram showing the software configuration of a database device according to the first embodiment. [Figure 3] This figure shows an example of a module format and individual modules according to the first embodiment. [Figure 4] This is an example of the device table editing screen according to the first embodiment. [Figure 5] This is an example of the interface editing screen for a logical device according to the first embodiment. [Figure 6] This is an example of the interface addition screen for a logical device according to the first embodiment. [Figure 7] This is an example of the editing screen for the interface table according to the first embodiment. [Figure 8] This is a block diagram showing the software configuration of a setting device according to the first embodiment. [Figure 9] This is a first flowchart illustrating the configuration process for network equipment according to the first embodiment. [Figure 10] This is a second flowchart illustrating the setup process for the device according to the first embodiment. [Figure 11] This is a third flowchart showing the device configuration process according to the first embodiment. [Figure 12] This is a schematic block diagram showing the configuration of a computer according to at least one embodiment. [Modes for carrying out the invention]

[0008] <First Embodiment> Network System Configuration The embodiments will be described in detail below with reference to the drawings. Figure 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 configures physical devices 50, which are equipment for configuring a network of multiple plants P. Each of the multiple plants P is located in a different area. In this embodiment, "physical device 50" refers to physical equipment that has an electrical circuit built in. On the other hand, equipment handled on a database during the design phase is called a "logical device". By implementing logical devices through the configuration of unconfigured physical devices 50, the physical devices 50 become operational. Equipment configuration includes network configuration, software configuration, and hardware configuration. Examples of equipment configuration include OS installation on equipment, package management software installation, installation of a specific version of specific software using package management software, initial setup of installed software, partition configuration of multiple storage devices, setting whether or not to configure RAID for storage, setting the type of RAID, setting the boot order of equipment, network boot configuration, local boot configuration, and setting the mount of remote storage. In this embodiment, the information used to configure individual physical devices 50 is referred to as an "individual module." Examples of individual modules include configuration files, configuration batch files, and command sequences.

[0009] The network system 1 comprises a database device 10 and a configuration device 30. The database device 10 stores configuration information for logical devices that should constitute the network of multiple plants P. The database device 10 has CMDB (Configuration Management Database) and DCIM (Data Center Infrastructure Management) / IPAM (IP Address Management) functions. The configuration device 30 configures the physical device 50 based on the information stored in the database device 10. The configuration device 30 is located in a configuration facility C, which is separate from plant P. The configuration facility C may have one configuration device 30 or multiple configuration devices 30. If there are multiple configuration devices 30, they can configure the physical device 50 in parallel. The configuration device 30 may be located not only in the configuration facility C but also in plant P. If the configuration device 30 is located in plant P, it can configure physical devices 50 already installed in plant P on-site. Users can access the user interface of the configuration device 30 from any location via a network. For example, the configuration device 30 has a web interface that can be displayed by a web browser. The configuration device 30 may consist of a UI server that provides a UI such as a web interface, and multiple configuration terminals that access the UI server. The UI server manages the generation conditions for individual modules and the execution order of individual modules. The configuration terminal generates individual modules according to the generation conditions for 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 the configuration facility C. The configured physical devices 50 are transported to the corresponding plant P and connected to the plant P's network. The configuration facility C is responsible for configuring the multiple physical devices 50 used in the multiple plants P. If a configuration device 30 is also provided in plant P, the multiple physical devices 50 may be configured in that plant P. In other words, the physical devices 50 can be configured at any location that is connected to any of the configuration devices 30.

[0011] Configuration of Database Device 10 Figure 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 where the logical device is arranged. For each plant P, the plant master 111 stores, in association, a plant ID, a plant name, and policy information indicating the security policy of the plant P. The policy information indicates the rules of communication. The policy information is expressed, for example, using permission and non - permission of communication. That is, when the target plant P has a first plant P1 and a second plant P2, the plant master 111 records the policy information of the first plant and the policy information of the second plant. The plant master 111 may further store information such as an organization name, an owner name, geographical information, and a location as information about the plant P. The organization name is the name of the organization operating the plant P. The owner name is the name of the owner of the plant P. The geographical information is the geographical location 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 models of the physical devices 50. For each model, the device type master 112 stores, in association, a model ID (model name), conversion data, and default setting data. An example of the conversion data is data that associates a common item name independent of the model with an individual item name (device - processable item name) used for the network setting of the model. The conversion data is used to convert the name etc. of an item for setting during network setting. In the conversion data, at least the common interface name and the individual interface name used for the setting information of the physical device 50 of the model are associated. The physical device 50 has a name (individual interface name) assigned in advance to a plurality of network interfaces for each model, and in network setting, it is necessary to specify the network interface by the individual interface name. The individual interface name is different for each model of the physical device 50. For example, in the first model, the individual interface name of the first - row - first - from - the - left LAN interface is "internal1", while in the second model, the individual interface name of the first - row - first - from - the - left LAN interface may be "lan1". Note that the item names that require conversion are not limited to interface names. The default - setting data stores the values of items uniquely determined in the network setting 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 set the language of the region where it is installed (e.g., Japanese) in the language setting, store "setting language = \"japanese\"" in the default - setting data, and for a model that cannot set the language of the region where it is installed, store "setting language = \"english\"" in the default - setting data. The default - setting data is expressed by a combination of an item name and a setting value, such as json. The device type master 112 may store information about the physical device 50, including its model, series name, manufacturer name, and platform information. The series name is the name of the series (brand, model) of the device in question. The platform information is information about the system on which the device is installed as a platform. For example, platform information may include the names and versions of the operating system (OS), which is the operating base for software, or the database engine, which is the operating base for databases.

[0014] The device table 113 is a table that stores information about logical devices. For each logical device, the device table 113 stores the device ID, device name, plant ID of the plant P where the logical device is installed, and model ID indicating the model of the physical device 50 on which the logical device is implemented, in association with each other. The model ID is defined in the device type master 112. The device table 113 may also store information about the logical device, such as the owner name, location, maintenance information, and application setting information. 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 building where the logical device is installed. The device table 113 may record multiple owner names for a single logical device. The location is information indicating the place in plant P where the logical device is installed. The location is sub-information of the geographical information of plant P, and represents a further subdivided location within plant P, such as a building, floor, or room. Maintenance information is information such as the warranty period and maintenance contract period of the logical device. Application configuration information refers to the configuration information of an application running on a physical device corresponding to a logical device. This information includes, for example, the name and version of the application being installed.

[0015] The interface table 114 is a table that stores information about network interfaces provided on a logical device. The interface table 114 stores the interface ID, the device ID of the logical device, and the common interface name in association with each other. The common interface name is a name for identifying a physical network interface, independent of the model of the physical device 50. For example, if the physical device 50 has multiple network interfaces, the multiple network interfaces are usually arranged on the same side of the enclosure. In the first embodiment, the common interface name 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 the physical location. In this case, the network system 1 can determine the physical location by combining the common interface name and the conversion data, and make it available for use as the interface name for configuration. For example, the common interface name of the LAN interface in the Nth row from the top and the Mth from the left may be "LAN_N / M". Specifically, the common interface name of the LAN interface in the 2nd row from the top and the 4th 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 be a number that identifies the network interface regardless of its physical location. The interface table 114 may also store network interface information, such as type information and VLAN ID. The type indicates, for example, physical interfaces such as wired and wireless, bandwidth, and virtual interfaces such as LAG (Link Aggregation Group) and VPN (Virtual Private Network). The VLAN ID is an ID that indicates a group of VLANs that divide the network into virtual logical groups. By using VLANs, multiple physical devices located on the same physical network can be virtually made to exist on different networks. The VLAN ID is an ID associated with the VLAN information stored in the VLAN table 116, described later. Note that if the network is not divided by VLANs, the VLAN ID value may be blank.

[0016] The IP address table 115 is a table that stores information about IP addresses assigned to the network interface of a logical device. The IP address table 115 stores the IP address value in association with the interface ID that indicates the interface to which the IP address is assigned.

[0017] The VLAN table 116 is a table that stores configuration information for the VLAN (Virtual Local Area Network) of a logical device. The VLAN table 116 stores the VLAN ID, VLAN name, and plant ID in association. The VLAN ID is identification information for identifying a VLAN. It is preferable that the VLAN ID be unique within the same plant, but duplicates are permitted between different plants, and may also be permitted within the same plant. The VLAN prefix can be obtained by referring to the network address table 117.

[0018] The network address table 117 is a table that manages information about network segments. The network address table 117 stores the network segment ID, prefix, plant ID, and 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 the network address used to identify the network segment. The VLAN ID is the VLAN ID that indicates the VLAN associated with the network segment. If no VLAN is configured for the network segment, the VLAN ID value may be blank. In this embodiment, the network address table stores the VLAN ID to allow referencing of the corresponding VLAN, but in other embodiments, the primary key of, for example, 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 the source device ID, the source interface ID, the destination device ID, and the destination interface ID in association. The combination of device ID and interface ID may be treated as a single value. In other embodiments, the connection information table 118 may store the source interface ID and the destination interface ID in association. 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 module format MF, which is the format of an individual module for configuring the physical device 50, for each model of the physical device 50. Figure 3 shows an example of module format MF and 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 that item. The command name may differ 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, while others may have three or more. In the module format MF, as shown in Figure 3, the first and second parameters are represented by variables, and the values ​​of these variables represent the item name or setting value to be assigned.

[0021] In the example shown in Figure 3, the module format MF includes the variables {device.name}, {interface.common_name}, {ip_address.ip_address}, {vlan.vlan_id}, and {vlan.vlan_name}. {device.name} is a variable used to assign the device name from device table 113. {interface.common_name} is a variable used to assign the common interface name from interface table 114. {ipaddress.ipaddress} is a variable used to assign the IP address from IP address table 115. {vlan.vlan_id} is a variable used to assign the VLAN ID from VLAN table 116. {vlan.vlan_name} is a variable used to assign the VLAN name from VLAN table 116. By assigning values ​​to each variable in the module format MF, individual module IMs are generated as shown in Figure 3. Note that the values ​​assigned to each variable can be the values ​​from the respective tables themselves, or values ​​from the tables that have undergone a predetermined conversion process.

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

[0023] Figure 4 shows an example of the editing screen for the device table 113 according to the first embodiment. The editing screen for device table 113 includes a device list L1, in which logical devices are arranged vertically and item names are arranged horizontally. Each cell in device list L1 is an input form. Specifically, 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 the interface edit button and detail button. Of the cells in device list L1 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 plant master 111. The model name can be selected from the model names stored in device type master 112. Device list L1 is an example of an editing list. The editing screen for device table 113 includes an add button. When the add button is pressed, an add screen appears that accepts input for information about a new logical device. When the details button in device list L1 is pressed, the individual details editing screen for the logical device corresponding to the pressed row is displayed. The individual details editing screen includes input forms for each item of the logical device, and each item can be edited. In other words, the user may perform editing operations on multiple logical devices in parallel using the input forms in device list L1 shown in Figure 4, or they may perform editing operations on individual logical devices from the details editing screen.

[0024] Figure 5 shows an example of the interface editing screen for a logical device according to the first embodiment. When a user clicks the edit button for an interface in the device list L1, the web server unit 12 generates an editing screen for the interface of the logical device corresponding to the clicked row. The logical device interface editing screen includes an individual interface list L11, which displays the interfaces of the selected logical device vertically and the item names 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. Of 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. Each IP address is assigned a delete button (the "×" button in Figure 5), and pressing the assigned delete button deletes the IP address. Pressing the add button displays a combo box. In this combo box, one IP address can be selected from the IP address table 115. If 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 that IP address and registers that 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 dropdown list for the device name and a dropdown list for the common interface name. 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, associated with the model of the logical device selected in the device name dropdown list.

[0025] Figure 6 shows an example of the interface addition screen for a logic 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 for information about the new interface provided by 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 device name, common interface name, IP address, and connection destination. In the logical device input form on the interface addition screen, the name of the selected logical device is pre-filled. In other embodiments, the connection destination may be edited on a connection information setting screen, which is provided separately from the interface addition screen.

[0026] Figure 7 shows an example of the editing screen for the interface table 114 according to the first embodiment. The web server unit 12 can create an editing screen to edit information about multiple interfaces registered in the interface table 114. The editing screen for Interface Table 114 includes Interface List L2, which arranges the interfaces of each logical device vertically and the item names horizontally. Each cell in Interface List L2 is an input form. Specifically, Interface List L2 is a list that stores the interface ID, device name, common interface name, and IP address for each interface. Of Interface List L2, the cells 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 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. A combo box is a form that combines a text box that accepts free text input and a drop-down list. The interface name can be selected from a predetermined list of available interface names. If an interface name not registered in Interface Table 114 is entered into the input form, the recording unit 13 creates information about the interface related to that interface name and newly registers that information in Interface Table 114. Interface List L2 is an example of an editing list. The IP address input form includes a list and an add button. The list displays the IP addresses assigned to the interface. Each IP address is assigned a delete button (the "×" button in Figure 7), and pressing the assigned delete button deletes the IP address. Pressing the add button displays a combo box. In this combo box, one IP address can be selected from the IP address table 115. If 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 that IP address and registers that information in the IP address table 115. The selected or entered IP address is added to the interface list L2. The editing screen for interface table 114 includes an add button. When the add button is pressed, an add screen appears that accepts input for new interface information.

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

[0028] The recording unit 13 updates the table based on the values ​​changed in the editing screen displayed by the web server unit 12. For example, if the device name in the device list L1 shown in Figure 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, if the plant name in the device list L1 shown in Figure 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, if the device name in the interface list L2 shown in Figure 7 is changed, the recording unit 13 identifies the interface ID corresponding 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, if the value of the IP address in the interface list L2 shown in Figure 7 is changed, the recording unit 13 identifies the interface ID corresponding 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 the data entered into the add screen, which is displayed when the add button on the editing screen is pressed.

[0029] The query processing unit 14 retrieves information stored in the storage unit 11 according to the input query.

[0030] 《Setting device 30》 Figure 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 reception unit 32, an acquisition unit 33, a determination unit 34, a decision unit 35, a generation unit 36, and a setting unit 37.

[0031] The reception unit 32 receives input of the device ID of the logical device to be implemented on the physical device 50 from the worker who configures the physical device 50. The acquisition unit 33 acquires information used to create individual module IMs for implementing logical devices with device IDs input from the database device 10 onto the physical device 50. Specifically, it generates a query to obtain information based on the device ID input to the reception unit 32 and sends the generated query to the database device 10. As a result, the acquisition unit 33 can acquire information from the database device 10 as a response to the query, which is used to create individual module IMs for implementing logical devices onto the physical device 50. The information acquired by the acquisition unit 33 includes 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 converted data for each item name and setting value acquired by the acquisition unit 33. For example, the determination unit 34 determines that the corresponding individual item name (individual interface name) is set in the converted 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 for other items, an individual item name may be set for the item name. For example, if there are models that set a 32-bit value indicating the subnet mask and models that set an integer value representing the prefix length to set the area 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 area". For example, if the hostname to be set on the device cannot be set to the device name registered on the storage server due to specifications such as character limits, the individual item name "abbreviated hostname" may be set for the item name "device name". The program that implements the functions of the determination unit 34 may be stored in the database device 10. In this case, the setting device 30 may function as the determination unit 34 by downloading and executing the program from the database device 10. In this case, even if the network system 1 has multiple setting devices 30, the functions of the determination unit 34 can be centrally managed.

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

[0034] The generation unit 36 ​​generates individual module IMs used to implement logical devices into physical devices 50 by applying the information acquired by the acquisition unit 33 and the values ​​determined by the determination unit 35 to the format stored in the storage unit 31. The configuration unit 37 uses the individual module IM generated by the generation unit 36 ​​to configure the physical device 50. The programs that implement the functions of the acquisition unit 33, the determination unit 35, and the generation unit 36 ​​may be stored in the database device 10. In this case, the setting device 30 may download and execute the programs from the database device 10 to provide the functions of the acquisition unit 33, the determination unit 35, and the generation unit 36. The programs may be prepared separately for each type of device to which they apply, and may be selected and executed according to the type of physical device 50.

[0035] Regarding network design Figure 9 is a first flowchart showing the configuration process for network equipment according to the first embodiment. The network designer accesses the database device 10 and enters network design information into the device table 113, interface table 114, and IP address table 115 (step S1). Note that the specific model of the physical device 50 may not be determined during the network design phase, so the model ID value in the device table 113 may be blank during the design phase. Note that if the model of the physical device 50 to be implemented does not exist in the device type master 112, the designer enters the model information into the device type master 112 as design information (step S2). Note that the entry of model information into the device type master 112 only needs to be done when the model of the physical device 50 is determined. 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 in step S2.

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

[0037] Figure 11 is a third flowchart showing the device setup process according to the first embodiment. Next, the device installer connects the unconfigured physical device 50 corresponding to the determined model to the configuration device 30 (step S4). The physical device 50 and the configuration device 30 may be connected via a network, such as a LAN, or via other means such as USB. At the stage of implementing the logical device on 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 configuration operator inputs the device ID of the logical device to be implemented on the physical device 50 connected in step S4 into the configuration device 30. The reception unit 32 of the configuration device 30 accepts the input value of the device ID (step S5).

[0039] The acquisition unit 33 generates a query to obtain information from the database device 10 using the device ID value entered in step S4, and sends 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) from device table 113, where the entered value is the device ID. A query to retrieve a tuple (second tuple) from interface table 114, where the input value is the device ID. A query to retrieve the tuple (third tuple) related to the model ID value of the first tuple from the device type master 112. A query to retrieve the tuple (fourth tuple) related to the plant ID value related to the first tuple from plant master 111. A query to retrieve the tuple (5th tuple) related to the interface ID value of the 2nd tuple from the IP address table 115. A query to retrieve the tuple (6th tuple) related to the model ID related to the 1st tuple from the module format table 119. This also includes queries to retrieve other tuples related to the device associated with the first tuple. Although both the first and second tuples are tuples that have the input value as the device ID, the first tuple is a tuple from the device table and the second tuple is a tuple from the interface table, so they have different values. The query processing unit 14 of the database device 10 retrieves information from each table according to the query sent from the setting device 30 and sends it back to the setting device 30. The acquisition unit 33 acquires information from the database device 10 as a response to the query (step S7). As a result, the acquisition unit 33 acquires from the database device 10 the device name, IP address of each interface, setting values ​​such as default setting data, policy information, module format MF, conversion data, etc.

[0040] The setting device 30 selects each parameter variable included in the module format MF obtained in step S7 (step S8), and then executes the following processes from steps S9 to S11.

[0041] The determination unit 34 determines whether the common item name of the selected parameter is subject to conversion data. Specifically, the determination unit 34 determines whether the common item name of the selected parameter is subject to conversion by the conversion data obtained in step S7 (step S9). If the common item name of the selected parameter is subject to conversion (step S9: YES), the decision 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 subject to conversion by the conversion data (step S9: NO), the decision unit 35 does not change the value of the parameter (step S11).

[0042] Once all common item names to be converted in the module format MF have been replaced with individual item names, the generation unit 36 ​​assigns the setting values ​​obtained in step S7 to the variables representing each parameter of the module format MF (step S12). At this time, the generation unit 36 ​​adjusts the value of the second parameter to comply with the security policy of plant P based on the policy information obtained in step S6. Specifically, the generation unit 36 ​​generates the setting values ​​of the parameters to be combined with the module format MF based on the policy information obtained in step S6 and the setting values ​​obtained in step S7. The generation unit 36 ​​substitutes the setting values ​​generated from the policy information into the variables of the module format MF that correspond to the parameters generated from the policy information. The generation unit 36 ​​substitutes the setting values ​​obtained in step S7 into the other variables of the module format MF. Furthermore, since data processing procedures differ depending on the manufacturer, for example, the generation unit 36 ​​may adjust the value of the second parameter according to the manufacturer. For example, if there are routers from manufacturer X and routers from manufacturer Y in a certain communication path, the data processing procedures of the routers from manufacturer X and manufacturer Y may differ. The router from manufacturer X needs to set values ​​for the following set of parameters. ·From ·To • Input Interface Output interface, • Communication protocol • Communication available / not available For routers from manufacturer Y, the following parameter values ​​must be set for both the input and output interfaces. ·From ·To • Communication protocol • Applicable Interfaces • Communication available / not available Thus, if the data processing procedures differ depending on the manufacturer, the generation unit 36 ​​sets the parameter values ​​according to the processing procedures for each manufacturer. The processing procedures for each manufacturer may, for example, be recorded in advance in the database device 10. The applicable interface is information that identifies either the input interface or the output interface of a router from manufacturer Y.

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

[0044] This configures the physical device 50. The configured physical device is then transported to the corresponding plant P, where it is integrated into the network.

[0045] Here, we will explain an example of a specific network construction process. For example, if physical device 50A is installed in the first plant P1 and physical device 50B is installed in the second plant P2, the installation worker temporarily installs physical device 50A and physical device 50B in the network configuration facility C. The installation worker first connects physical device 50A to the configuration device 30. The installation worker instructs the configuration device 30 to generate an individual module IM that physical device 50A can process by inputting the device ID of the logical device to be implemented in physical device 50A. As a result, the configuration device 30 generates the individual module IM according to the process shown in Figure 11 and configures the network settings of physical device 50A. At this time, 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 configuration device 30. The installer instructs the configuration device 30 to generate an individual module IM that the physical device 50B can process by inputting the device ID of the logical device to be implemented on the physical device 50B. As a result, the configuration device 30 generates the individual module IM according to the process shown in Figure 11 and configures the network settings of the physical device 50B. At this time, the physical device 50A is configured by the individual module IM to comply with the security policy of the second plant P2.

[0047] The installation worker installs the network-configured physical device 50A into Plant 1 P1. The configuration worker then installs the network-configured physical device 50B into Plant 2 P2.

[0048] Action / Effect 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 specify 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 for the common item indicated by the common item name, without using a network diagram. The recording unit 13 stores the device ID specified by the web server unit 12, the common item name specified by the web server unit 12, and the setting value specified by the web server unit 12 in association with each other 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 receives the device ID from a second user, such as a setting worker. The acquisition unit 33 acquires the common item name and setting value stored in association with the device ID received by the reception unit 32 from the storage unit 11. The generation unit 36 ​​uses the device ID received by the reception unit 32 and the common item name and setting value obtained 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 is equipped with a reception unit that receives the individual module IM generated by the setting device 30. As a result, network system 1 can easily configure network devices without using a network diagram. While network diagrams allow for an intuitive understanding of the connection relationships between network devices, it is difficult to check settings and other information, and in cases where there are many devices, the connection relationships may become even more difficult to interpret. In contrast, according to network system 1 of the first embodiment, network device information can be configured using a database device 10 with DCIM / IPAM functionality.

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

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

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

[0052] The program may be for implementing some of the functions that the computer 70 is to perform. For example, the program may perform functions in combination with other programs already stored in storage, or in combination with other programs implemented on other devices. In other embodiments, 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 implemented by the processor 71 may be implemented by the integrated circuit. Such an integrated circuit is also included as an example of a processor. In other embodiments, the computer 70 may be virtualized on one or more computers.

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

[0054] Furthermore, the program may be intended to implement some of the functions described above. In addition, the program may be a so-called differential file (differential program) that implements the functions described above in combination with other programs already stored in storage 73. [Explanation of Symbols]

[0055] 1…Network System 10…Database Device 11…Storage 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…Configuration Device 31…Storage Unit 32…Reception Unit 33…Acquisition Unit 34…Determination Unit 35…Decision Unit 36…Generation Unit 37…Configuration Unit 50…Physical Device 70…Computer 71…Processor 72…Main Memory 73…Storage 74…Interface C…Network Configuration Facility L1…Device List L2…Interface List P…Plant MF…Module Format IM…Individual Module

Claims

1. A network system comprising a storage server, a configuration server, and multiple devices, each capable of processing individual modules of different formats, The aforementioned individual module includes values ​​for several common items, which are settings that are used in common regardless of the type of device. The aforementioned storage server is A specification unit that allows a first user to specify, without using a network diagram, a device ID which is an ID that identifies one of the aforementioned multiple devices, a common item name which uniquely identifies one of the aforementioned multiple common items, and the setting value of the common item indicated by the common item name. A recording unit that stores in a storage unit the device ID specified by the designation unit, the common item name specified by the designation unit, and the setting value specified by the designation unit in association with each other. Equipped with, The aforementioned configuration server is A reception unit that receives the device ID from a second user, An acquisition unit that acquires the common item name and the setting value stored in association with the device ID received by the reception unit from the storage unit, A generation unit generates an individual module in a format that can be processed by the device indicated by the device ID received by the reception unit, using the device ID received by the reception unit, the common item name and the setting value obtained by the acquisition unit, Equipped with, Each of the aforementioned plurality of devices is A receiving unit that receives the individual modules generated by the aforementioned configuration server, A network system characterized by having the following features.

2. The designated unit displays an editable list in the display unit that shows the relationship between the common item name and the setting value for each device ID, and includes at least a setting value form on which the setting value can be edited. The network system according to claim 1.

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

4. The individual modules generated by the generation unit include one or more commands. The command includes a command name and a first parameter indicating the item to be executed. The aforementioned configuration server is A determination unit determines whether or not there is a device-processable item name defined as a name that can be processed by the device among the common item names acquired by the acquisition unit, A determination unit determines the device-processable item name corresponding to the common item name as the first parameter of the command when a device-processable item name exists for the common item name acquired by the acquisition unit, and determines the setting value corresponding to the common item name as the first parameter when a device-processable item name does not exist for the common item name acquired by the acquisition unit. The network system according to claim 1, further comprising:

5. The acquisition unit transmits the device ID received by the reception 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 obtains the common item name and the setting value stored in the storage unit in association with the device ID by issuing a query to the storage server that includes the device ID received by the reception unit. The network system according to claim 1.

7. The individual modules generated by the generation unit include one or more commands. The command is represented by a command name and a first parameter indicating the item to which the command is executed. The storage unit stores, for each type of device, the common item name and the device-processable item name, which is defined as a name that can be processed by the device for the common item name used in the individual modules of the device, in association with each other. The aforementioned configuration server is A holding unit holds the format of an individual module that associates the common item name with the command name used to set the 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 the item corresponding to the common item name acquired by the acquisition unit, A determination unit determines the device-processable item name corresponding to the common item name acquired by the acquisition unit as the first parameter of the command if a device-processable item name exists for the item corresponding to the common item name acquired by the acquisition unit, and determines the common item name as the first parameter if a device-processable item name does not exist for the item corresponding to the common item name acquired by the acquisition unit, Furthermore, The generation unit generates a command for each common item name, which includes the command name held by the holding unit in association with the common item name, and the first parameter determined by the determination unit. The network system according to claim 1.

8. The individual modules generated by the generation unit include a module for configuring the network settings of the device application indicated by the device ID received by the reception unit. The network system according to claim 1.

9. The plurality of devices include a first device and a second device, The aforementioned storage server and the aforementioned configuration server are installed in the network configuration facility. The first device is installed in the first plant, which is located in an area different from the network configuration facility. The second device is installed in the second plant, which is located in a different area from the network configuration facility and the first plant. A network system according to any one of claims 1 to 8.

10. The aforementioned storage unit is The first policy information, which shows the security policy of the first plant, The second policy information, which shows the security policy of the second plant, Remember The network system according to claim 9.

11. A method for configuring a network system according to claim 10, A temporary installation step of temporarily installing the first device and the second device in the network configuration facility, A first instruction step involves instructing the generation unit to generate a first individual module, which is an individual module that the first device can process, using the device ID received by the reception unit, the common item name and the setting value associated with the device ID indicating the first device, and the first policy information. A second instruction step involves instructing the generation unit to generate a second individual module, which is an individual module that the second device can process, using the device ID received by the reception unit, the common item name and the setting value associated with the device ID indicating the second device, and the second policy information. A first installation step involves installing the first device, which is networked based on the first individual module, in the first plant. A second installation step involves installing the second device, which is networked based on the second individual module, in the second plant. A configuration method that includes [the specified feature].

Images