JP2018037060A - Distribution system, control method of distribution system, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To suppress costs required for holding a network device setting which are generated in pre-installation or the like of the network device.SOLUTION: A setting distribution system 100 performs the following: when distributing a setting to a network device 111 in pre-installation processing or the like, creating a snap snapshot from the setting and storing it (S1103) when a snapshot corresponding to the latest version of the setting to be distributed does not exist (No in S1102); and when a snapshot corresponding to the latest setting exists (Yes in S1102), recording a relationship between the snapshot and the network device as a distribution destination (S1105) without creating a snapshot (without executing S1103), and distributing the snapshot (S1106).SELECTED DRAWING: Figure 11

Description

  The present invention relates to a distribution system for distributing settings to a network device, a method for controlling the distribution system, and a program.

  In recent years, it has become possible for a remote network device management apparatus to distribute various types of information that can be set in a network device using a notification protocol such as a Web service. In particular, in network devices such as image forming apparatuses that also have a copy function, facsimile function, etc., detailed information that could only be set and displayed only on the operation panel can be set by Web services. It has become. These pieces of information include an address book, a security policy, and the like in addition to printing-related settings and basic network settings such as IP addresses and subnet masks. When these settings are distributed to network devices, a copy of the distributed settings and the settings on the network device before distribution is created and stored separately for later reference and redistribution of settings. It is also possible.

  Japanese Patent Application Laid-Open No. 2004-228561 describes a technique for transferring settings to a plurality of network devices at once. In Patent Document 1, the current settings of the network device are acquired and saved before the settings are transferred, and when a problem occurs in the network device after the settings are transferred, the saved settings are used for the network. It is possible to restore the device state.

JP 2006-173679 A

  For example, when the same setting is distributed to a plurality of network devices, if a copy of the setting is created for each distribution, a plurality of copies are created for the same setting. Note that the setting can increase the data size. For this reason, the creation of an unnecessary copy has a problem such as increasing the storage cost for storing the settings.

  In a network device, there is a case where a work called pre-installation is performed in which a software setting or a configuration of a newly purchased network device is changed and then delivered to a customer. The setting may be updated at the start of the pre-installation of the network device. For example, creating a copy of the setting every time it is updated increases the storage cost.

  In view of the above problems, an object of the present invention is to provide a mechanism for reducing the storage cost required to maintain the network device settings that occur when a network device is installed in advance.

  The present invention is a distribution system that distributes setting information of a network device to a network device, and an update unit that can update the setting information and a setting information distribution process for the network device. A creation unit that creates a snapshot that is a copy of the setting information to be distributed and stores it in a storage unit, and a relationship between the snapshot of the setting information and a network device that is a distribution destination in the distribution processing Management means for recording and managing, and distribution means for distributing the snapshot of the setting information to the network device as the distribution destination as the distribution processing, wherein the creating means is the latest target for the distribution processing If the snapshot corresponding to the setting information does not exist in the storage unit, a snapshot is generated from the setting information. Create a shot, when the snapshot corresponding to the latest configuration information is present in said storage means, characterized in that it does not create a snapshot from the setting information.

  According to the present invention, it is possible to reduce the storage cost for holding the network device settings.

The figure which illustrates the structure of the network system of a present Example The figure which illustrates the structure of the network device setting which concerns on a present Example The figure which illustrates the structure of the setting snapshot which concerns on a present Example The figure which illustrates the software configuration of the Web server of Example 1. The figure which illustrates the composition of the setting edit screen in setting editor PC It is a figure which illustrates the software configuration of a network device. The figure which illustrates the composition of the installation start screen in the network device The figure which illustrates the setting management table concerning a present Example The figure which illustrates the snapshot management table concerning a present Example Flowchart illustrating network device setting update processing Flowchart illustrating the pre-installation process of the first embodiment The figure which illustrates the software configuration of the Web server of Example 2. The figure which illustrates the installation link management table which concerns on Example 2. FIG. Flowchart illustrating the pre-installation process of the second embodiment Flowchart illustrating the pre-installation process of the third embodiment The figure which illustrates the difference setting management table concerning Example 5. The figure which illustrates the difference snapshot management table concerning Example 5. Hardware configuration diagram of Web server and the like according to the present embodiment Hardware configuration diagram of network device according to the present embodiment Flowchart illustrating network device setting update processing according to embodiment 6 Flowchart illustrating network device pre-installation processing according to embodiment 6

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. In the following embodiments, pre-installation of a network device is described as an example, but the present invention is not limited to this.

  In the network device, there is a case where a work called “pre-installation” is performed in which the software setting or configuration change of the newly purchased network device is performed and then delivered to the customer. The setting editor who creates and edits the settings used in the previous installation, when requesting the previous installation work, notifies the installation worker who performs the previous installation work of the setting ID issued when creating the settings. To do. The installation operator who has received the setting ID inputs the setting ID received on the network device and starts the previous installation, so that the setting is applied by the function installed in the network device. In addition to creating one setting for each network device, it is possible to pre-install multiple network devices with one setting. In other words, one setting can be applied to a plurality of network devices.

  In this embodiment, the setting applied to the network device is left as evidence in the previous installation. Hereinafter, in order to leave the evidence, making a copy (duplication) of the setting and storing it separately is referred to as “creating a snapshot”. The created copy is called “snapshot”.

  Note that the setting editor can edit the settings after the request for installation and before the pre-installation work is started and during the pre-installation work. For this reason, even if a snapshot is acquired when the setting is edited, the setting may be different from the setting actually used in the previous installation of the network device, and the snapshot cannot be handled as evidence. For example, when the setting is edited after the pre-installation work is started, there is a possibility that the snapshot created when the setting is edited and the setting applied to the network device by the pre-installation work are different. Also, when one setting is applied to multiple network devices, the applied settings will be the same depending on the timing of editing and the timing of previous installation, even for network devices to which the same setting ID setting is applied. Not exclusively.

  Therefore, in this embodiment, when the installation operator starts the pre-installation of the network device, the setting snapshot is acquired, the pre-installation is performed using the snapshot, and the network device and the snapshot are linked. I do. As a result, the snapshot of the setting actually used in the previous installation is linked to the network device, and the snapshot can be handled as evidence.

FIG. 1 is a diagram illustrating the configuration of a network system showing an embodiment of the present invention.
The setting distribution system 100 receives requests from the setting editor PC 110 and the network device 111 and performs processing.

  The setting editor PC 110 is assumed to be a PC (personal computer) or tablet computer operated by the user, an application server that provides services to the user, or the like. The setting editor PC 110 has a function of editing settings to be applied to the network device 111. However, the configuration may be such that the setting distribution system 100 has a setting editing function and provides a user interface (UI) to the setting editor PC 110. The setting editor PC 110 connects to the setting distribution system 100 via the network 112.

  The network device 111 functions as client software, and transmits an instruction from the user of the network device 111 to the setting distribution system 100. The network device 111 has a function of applying the setting information distributed from the setting distribution system 100 to itself. The network device 111 is connected to the setting distribution system 100 via the network 113.

  The setting distribution system 100 includes a Web server 101, a DB (database management server) 102, and a file server 103. The Web server 101 processes requests received from the setting editor PC 110 and the network device 111. The DB 102 stores various data for providing services. The file server 103 stores setting data distributed to the network device, various data for providing services, and the like.

  The setting distribution system 100 may be configured by a single device or a plurality of devices. For example, at least two of the functions of the Web server 101, the DB 102, and the file server 103 may be provided by a single device. The setting distribution system 100 may be configured with a cloud server or the like. For example, the setting distribution system 100 can be constructed using a public cloud service or the like.

  As described above, in this embodiment, the case where the setting applied to the network device is left as evidence in the previous installation will be described as an example, but the present invention is not limited to this. Any configuration may be used as long as the configuration distributed from the configuration distribution system and applied to the network device is left as evidence.

FIG. 2 is a diagram illustrating the configuration of the network device setting 201 according to the present embodiment.
The network device setting 201 is a file in which various setting information to be applied to the network device 111 is described.

  The network device setting 201 includes, for example, the firmware version of the network device 111, the IP address of the network device 111, the email address of the user of the network device 111, and the like.

  The setting items held by the network device setting 201 may differ depending on the model of the network device 111, the firmware / application to be installed, and the like. Further, the network device setting 201 is not limited to data in text format, and can also include data in various formats such as binary format data. Of the network device settings 201, setting data applied to the network device 111 is stored in the file server 103. In addition, the ID of the setting data of the network device setting 201 is stored in the DB 102.

FIG. 3 is a diagram illustrating the configuration of the setting snapshot 301 according to the present embodiment.
The setting snapshot 301 is a copy of the network device settings 201 at a certain point in time. The storage location of the setting snapshot 301 is the same as that of the network device setting 201 described above.

  Hereinafter, the hardware configuration of each device included in the network system of this embodiment will be described with reference to FIGS. 18 and 19.

FIG. 18 is a block diagram illustrating a hardware configuration of an information processing apparatus that can configure the Web server 101, DB 102, file server 103, and setting editor PC 110.
This information processing apparatus includes a CPU 3000, a main storage device 3001, a secondary storage device 3002, a user interface 3003, an external interface 3004, and the like.

  The CPU 3000 is a unit that executes a predetermined program and instructs various controls of the information processing apparatus. The main storage device 3001 is a work memory used when the CPU 3000 executes a program, and is realized by a RAM (Random Access Memory) or the like.

  The secondary storage device 3002 is realized by a non-volatile storage device such as a hard disk drive (HDD) or a solid state drive (SSD). The secondary storage device 3002 stores various programs and various data including application programs and OS (Operating System). Various programs stored in the secondary storage device 3002 are loaded into the main storage device 3001 when the CPU 3000 executes the programs.

The user interface 3003 is a unit having a function of accepting user operation input and a function of notifying the user. For example, the user interface 3003 can accept a signal corresponding to a user operation using a keyboard, a mouse, or the like. The user interface 3003 can output a notification to the user using a display or the like.
The external interface 3004 is connected to a network and enables communication with other devices.

  FIG. 19 is a block diagram illustrating a hardware configuration of the network device 111. As illustrated in FIG. Here, a multifunction device is used as an example of the network device 111. However, the network device 111 is not limited to the multifunction device, and the network device 111 includes various information processing apparatuses. For example, an image processing apparatus such as a printer and a scanner, a personal computer, a network camera, a navigation system, and various network home appliances such as an air conditioner and a television are also included in the network device 111 of this embodiment.

  The network device 111 according to the present embodiment roughly includes an image processing unit 2000, a printing unit 2006, a reading unit 2007, and the like.

The image processing unit 2000 includes a CPU 2001, a main storage device 2002, a secondary storage device 2003, a user interface 2004, an external interface 2005, and the like.
The CPU 2001 executes a predetermined program and instructs various controls of the network device 111.

  The main storage device 2002 is a work memory used when the CPU 2001 executes a program, and is realized by a RAM or the like. The secondary storage device 2003 is realized by a nonvolatile storage device such as an HDD or an SSD. The secondary storage device 2003 stores application programs, various programs such as an OS, various setting information, and the like. Various programs stored in the secondary storage device 2003 are loaded into the main storage device 2002 when the CPU 2001 executes the program.

  The user interface 2004 is a unit having a function of accepting a user's operation input, and is realized by a touch panel capable of touch operation, an operation panel having hard keys, or the like.

  The external interface 2005 is a network interface, for example, and can receive data from an external device and transmit data to the external device. For example, the external interface 2005 provides various management information of the network device 111 recorded in the secondary storage device 2003 to the outside via a protocol such as HTTP (Hypertext Transfer Protocol) or SNMP (Simple Network Management Protocol). Can be obtained from the outside. In the present embodiment, it is assumed that the external interface 2005 communicates with the setting distribution system 100 in order to exchange information.

  The printing unit 2006 is a hardware mechanism that forms an image when functions such as printing and copying are executed in the network device 111. The reading unit 2007 is a hardware mechanism that converts a document such as text or a photograph into electronic data when the network device 111 executes a function such as scanning or copying.

FIG. 4 is a diagram illustrating a software configuration of the Web server 101 according to the first embodiment.
The Web server 101 includes functional units such as a setting update unit 401, a setting distribution unit 402, a snapshot creation unit 403, and an installation history management unit 404. These functional units are realized by the CPU 3000 of the Web server 101 reading out and executing a program stored in the secondary storage device 3002 to the main storage device 3001 as necessary.

  The setting update unit 401 stores the network device setting 201 received from the setting editor PC 110 in the DB 102 and the file server 103. For example, the setting update unit 401 stores management attribute information such as a path on the file server 103 in the network device setting 201 in the DB 102, and stores setting data itself in the file server 103. The setting data itself of the network device setting 201 can also be stored in the DB 102.

  The setting distribution unit 402 distributes the setting snapshot 301 to the network device 111 in response to a request from the network device 111. Note that the setting snapshot 301 to be distributed uses the one created by requesting the snapshot creating unit 403. In this embodiment, the created setting snapshot 301 is used. However, a configuration in which the setting distribution unit 402 distributes the network device setting 201 to the network device 111 may be used.

  The snapshot creation unit 403 creates a setting snapshot 301 that is a snapshot of the network device setting 201 in response to a request from the setting distribution unit 402. If a snapshot of the requested network device setting 201 already exists, the existing setting snapshot 301 is returned to the setting distribution unit 402 without creating a snapshot. A method for determining whether or not the requested network device setting 201 has a snapshot will be described later.

  The installation history management unit 404 maps the snapshot ID of the setting snapshot 301 used in the previous installation of the network device 111 to the network device ID of the network device 111 and records it in the DB 102. As the network device ID of the network device 111, for example, the serial number of the network device is used. By mapping and managing the network device ID and the snapshot ID in this way, the setting snapshot 301 used in the previous installation of the network device can be specified, and can be used as evidence for the previous installation.

  FIG. 5 is a diagram exemplifying a configuration of a setting editing screen 501 in the setting editor PC 110. The setting editing screen 501 is displayed on the user interface 3003 of the setting editor PC 110 in accordance with a predetermined operation by the setting editor or the like.

  The user of the setting editor PC 110 can edit the setting value for each network device setting 201 and save the setting during and after the setting editing. When a save instruction (pressing the save button 502) is issued on the setting editing screen 501, the setting update unit 401 of the setting distribution system 100 that has received a request from the setting editor PC 110 displays the setting editing screen 501 The settings edited in the editing area 503 are stored in the DB 102 and the file server 103. As described above, the network device setting 201 stored in the setting distribution system 100 can be updated from the setting editor PC 110 via the setting update unit 401.

FIG. 6 is a diagram illustrating a software configuration of the network device 111.
The network device 111 includes functional units such as a setting acquisition unit 601 and a setting application unit 602. These functional units are realized by the CPU 2001 of the network device 111 reading out and executing the program stored in the secondary storage device 2003 to the main storage device 2002 as necessary.

  The setting acquisition unit 601 acquires the setting snapshot 301 from the setting distribution unit 402 of the setting distribution system 100. The setting snapshot 301 to be acquired is created from the network device setting 201 specified by the method shown in FIG. Note that the setting acquisition unit 601 transmits the network device ID of the network device 111 to the setting distribution system 100 when acquiring the setting snapshot 301.

  The setting application unit 602 applies the setting snapshot 301 acquired by the setting acquisition unit 601 to the network device 111.

  FIG. 7 is a diagram illustrating a configuration of the installation start screen 701 in the network device 111. The installation start screen 701 is displayed on the user interface 2004 of the network device 111 in accordance with a predetermined operation by an installation operator or the like.

  On the installation start screen 701, the setting ID of the network device setting 201 is designated by the setting ID input unit 702, and then the installation start is instructed (by pressing the setting start button 703). The acquisition of the shot 301 is started.

  In this embodiment, it is assumed that the setting ID of the network device setting 201 is input using a UI owned by the network device. Therefore, a number is assumed for convenience, but a character string other than a number is used. Even if is used, this embodiment can be realized. Alternatively, the setting ID may be specified by causing the reading unit 2007 to read a barcode or the like corresponding to the setting ID.

FIG. 8 is a diagram illustrating a setting management table 801 according to the present embodiment.
The setting management table 801 is held by the DB 102.
The setting management table 801 holds the setting ID of the network device setting 201, the file path of the network device setting 201 on the file server 103, and the snapshot ID of the setting snapshot 301 associated with the network device setting 201.

  A state in which the setting ID and the snapshot ID are recorded on the setting management table 801 is referred to as “there is a setting link” in the network device setting 201 having the setting ID. Further, a state in which the setting ID is recorded on the setting management table 801 but no snapshot ID is recorded is referred to as “no setting link” in the network device setting 201 having the setting ID. Recording a snapshot ID in a state where there is no setting link in the network device setting 201 is referred to as “creating a setting link” in the network device setting 201. Furthermore, deleting a snapshot ID in a state where there is a setting link in the network device setting 201 is referred to as “deleting a setting link” of the network device setting 201.

  The setting update unit 401 refers to the setting ID and snapshot ID on the setting management table 801 when updating the network device setting 201, and deletes the setting link when the network device setting 201 to be updated has a setting link. To do. As a result, the snapshot ID is deleted from the setting management table 801. Further, the setting update unit 401 stores the network device setting 201 to be updated in a location (on the file server 103 in this embodiment) specified by the file path of the setting management table 801.

  The snapshot creation unit 403 refers to the setting ID and the snapshot ID on the setting management table 801 in response to a snapshot creation request, and determines whether there is a setting link of the network device setting 201 used in the previous installation. . When there is no setting link, the setting snapshot 301 of the network device setting 201 is created, and the setting link of the network device setting 201 is created using the snapshot ID of the setting snapshot 301. As a result, the snapshot ID is recorded in the setting management table 801.

FIG. 9 is a diagram illustrating a snapshot management table 901 according to the present embodiment.
The snapshot management table 901 is held by the DB 102.
The snapshot management table 901 holds the snapshot ID of the setting snapshot 301 and the file path of the setting snapshot 301 on the file server 103.

  The setting distribution unit 402 refers to the snapshot ID and file path of the snapshot management table 901, and acquires the file path from the snapshot ID of the snapshot 301. Then, the setting distribution unit 402 acquires the setting snapshot 301 from the location specified by the file path on the file server 103, and distributes the setting snapshot 301 to the network device 111.

  The snapshot creation unit 403 generates a snapshot ID and a file path and records them in the snapshot management table 901. In addition, the snapshot creation unit 403 creates a setting snapshot 301 of the network device setting 201 and stores the setting snapshot 301 in the file path on the file server 103. A series of processes from generation of the snapshot ID to storage on the file server 103 is referred to as “creating a snapshot”.

  FIG. 10 is a flowchart illustrating an example of network device setting 201 update processing. The processing shown in this flowchart is realized by the CPU 3000 of the Web server 101 reading and executing a program stored in the secondary storage device 3002 to the main storage device 3001 as necessary.

  In response to a request from the setting editor PC 110, the CPU 3000 of the Web server 101 starts setting update processing for the network device setting 201 received from the setting editor PC 110 (S1001). The setting editor PC 110 transmits the setting data and setting ID of the network device setting 201 to the Web server 101 at the time of the request.

First, in S1002, the setting update unit 401 refers to the setting management table 801 using the setting ID of the network device setting 201 requested to update, and the network device setting 201 requested to update has a setting link. It is determined whether or not. If it is determined that there is a setting link (Yes in S1002), the setting update unit 401 advances the process to S1003.
In S1003, the setting update unit 401 deletes the link and advances the process to S1004.

  On the other hand, if it is determined that there is no setting link (No in S1002), the setting updating unit 401 advances the process to S1004.

  In step S1004, the setting update unit 401 acquires the corresponding file path from the record in which the setting ID of the network device setting 201 in the setting management table 801 is recorded. Then, the setting update unit 401 stores the network device setting 201 in the file path on the file server 103. Then, the setting update process ends.

  FIG. 11 is a flowchart illustrating the pre-installation process of the network device 111 according to the first embodiment. The processes indicated by S1102 to S1106 in this flowchart are realized by the CPU 3000 of the Web server 101 reading out and executing a program stored in the secondary storage device 3002 to the main storage device 3001 as necessary. Further, the processing shown in S1107 is realized by the CPU 2001 of the network device 111 reading and executing the program stored in the secondary storage device 2003 to the main storage device 2002 as necessary.

  The CPU 3000 of the Web server 101 starts the pre-installation process in response to the pre-installation process request from the network device 111 (S1101). At the time of this request, the network device 111 transmits the network device ID of the network device 111 and the setting ID of the network device setting 201 to the setting distribution system 100.

  In S1102, the snapshot creation unit 403 refers to the setting management table 801 using the setting ID, and determines whether there is a setting link in the network device setting 201 indicated by the setting ID. If it is determined that there is a setting link (Yes in S1102), the snapshot creation unit 403 shifts the process to S1105.

On the other hand, if it is determined that there is no setting link (No in S1102), the snapshot creation unit 403 advances the process to S1003.
In S1103, the snapshot creation unit 403 creates the setting snapshot 301 according to the method described in the description of FIG.
Next, in S1104, the snapshot creation unit 403 creates a setting link for the network device setting 201 in accordance with the method described in FIG. 8, and shifts the processing to S1105.

  In S1105, the installation history management unit 404 records information for associating the network device ID with the snapshot ID indicated by the setting link in the DB 102. That is, the installation history management unit 404 records and manages the relationship between the snapshot of the setting information to be distributed and the network device that is the distribution destination.

  Next, in S1106, the setting distribution unit 402 acquires the corresponding setting snapshot 301 from the snapshot ID according to the method described in FIG. 9, and distributes the setting snapshot 301 to the network device 111. .

  In response to the distribution of the setting snapshot 301 in S1106, the setting acquisition unit 601 of the network device 111 acquires the setting snapshot 301. In step S <b> 1107, the setting application unit 602 applies the setting snapshot 301 distributed by the setting distribution unit 402 and acquired by the setting acquisition unit 601 to the network device 111.

  If an error occurs in either the distribution process in S1106 or the application process in S1107, and the setting distributed from the setting distribution system 100 is not applied to the network device 111, it is recorded in the DB 102 in S1105. Information for associating the network device ID and the snapshot ID may be deleted.

  As described above, by determining the necessity of snapshot creation based on the presence / absence of the setting link of the network device setting 201, snapshot creation can be suppressed to the minimum necessary.

  As described above, according to the present embodiment, when the pre-installation of the network device is started, it is determined whether the setting has been updated since the last use in the pre-installation, and the snap is performed only when it has been updated. Configure to create a shot. That is, when the setting distribution system according to the present exemplary embodiment distributes the setting to the network device, the snapshot that is a copy of the setting is created and stored, and the snapshot and the network that is the distribution destination are stored. The association with the device is recorded, and the snapshot is distributed to the network device as the distribution destination. Furthermore, when there is no snapshot corresponding to the updated latest setting, the setting distribution system of the present embodiment creates a snapshot from the setting, and there is a snapshot corresponding to the latest setting. In this case, the snapshot is not created from the setting.

  With such a configuration, it is possible to suppress the creation of snapshots to the minimum necessary (suppress the creation of useless snapshots), and as a result, it is possible to reduce the storage cost that occurs in the previous installation. In particular, when installing multiple network devices in advance using a single setting (ie, when distributing and applying a single setting to multiple network devices), the storage cost can be reduced compared to the conventional case. It is possible to reduce.

  The network device setting 201 may be composed of two types of settings: a common setting for each network device model and an individual setting that is different for each network device. Hereinafter, this embodiment will be described.

  A common setting for each network device model is referred to as a “network device common setting”, and an individual setting different for each network device is referred to as a “network device individual setting”. A setting snapshot 301 corresponding to “network device common setting” is referred to as “common setting snapshot”, and a setting snapshot 301 corresponding to “network device individual setting” is referred to as “individual setting snapshot”.

  The network device common setting and the network device individual setting have the same configuration as the network device setting 201 of the first embodiment except for differences described later. That is, the network device common setting and the network device individual setting are registered and managed in the setting management table 801, respectively. Further, the common setting snapshot and the individual setting snapshot have the same configuration as the setting snapshot 301 of the first embodiment except for the differences described later. That is, the common setting snapshot and the individual setting snapshot are registered and managed in the snapshot management table 901, respectively.

  As a difference, the network device individual setting has a setting ID of the network device common setting. Further, the setting ID of the network device setting 201 specified on the installation start screen 701 (FIG. 7) of the network device 111 is the setting ID of the network device individual setting. The individual setting snapshot has a setting ID of network device common setting.

  If the network device setting 201 is composed of two types of settings, an unnecessary snapshot will be created unless the creation of a snapshot is determined for each network device common setting and each network device individual setting. As a result, the storage cost of the previous installation may be increased.

Therefore, in the second embodiment, when the network device setting 201 is configured from two types of settings, a configuration is described in which the creation of a snapshot is suppressed to the minimum necessary and the storage cost generated in the previous installation is reduced.
First, differences from the first embodiment will be described with reference to FIGS.

FIG. 12 is a diagram illustrating a software configuration of the Web server 101 according to the second embodiment, and the same components as those in FIG. 4 are denoted by the same reference numerals.
The Web server 101 according to the second embodiment includes a function unit of an installation link management unit 1201 in addition to a setting update unit 401, a setting distribution unit 402, a snapshot creation unit 403, and an installation history management unit 404. These functional units are realized by the CPU 3000 of the Web server 101 reading out and executing a program stored in the secondary storage device 3002 to the main storage device 3001 as necessary.

  The installation link management unit 1201 refers to an installation link management table 1301 shown in FIG. 13 described later, and determines whether there is an installation link described later. A method for determining whether there is an installation link will be described later. Further, the installation link management unit 1201 updates the installation link management table 1301 and creates an installation link. A method for creating the installation link will be described later.

  When the installation link management unit 1201 refers to and updates the installation link management table 1301, the common setting snapshot ID that is the snapshot ID of the common setting snapshot and the individual setting snapshot that is the snapshot ID of the individual setting snapshot ID is used. Further, the installation link management unit 1201 refers to the installation link management table 1301 and acquires a common setting snapshot ID and an individual setting snapshot ID corresponding to the installation link ID using an installation link ID described later.

FIG. 13 is a diagram illustrating an installation link management table 1301 according to the second embodiment.
The installation link management table 1301 is held by the DB.
The installation link management table 1301 holds a common setting snapshot ID, an individual setting snapshot ID, and an installation link ID described later.

  The state where the common setting snapshot ID and the individual setting snapshot ID are recorded on the installation link management table 1301 is referred to as “the common setting snapshot and the individual setting snapshot have an installation link”. The installation link has an installation link ID. Generating the installation link ID and recording the common setting snapshot ID, the individual setting snapshot ID, and the installation link ID in the table are referred to as “creating an installation link of the common setting snapshot and the individual setting snapshot”. .

  FIG. 14 is a flowchart illustrating the pre-installation processing of the network device 111 using the network device common setting and the network device individual setting according to the second embodiment. The processes indicated by S1402 to S1411 in this flowchart are realized by the CPU 3000 of the Web server 101 reading out and executing a program stored in the secondary storage device 3002 to the main storage device 3001 as necessary. The processing shown in S1412 is realized by the CPU 2001 of the network device 111 reading out and executing the program stored in the secondary storage device 2003 to the main storage device 2002 as necessary.

  The CPU 3000 of the Web server 101 starts pre-installation processing in response to a request from the network device 111 (S1401). At the time of this request, the network device 111 transmits the network device ID of the network device 111 and the setting ID of the network device individual setting to the setting distribution system 100.

  In S1402, the snapshot creation unit 403 refers to the setting management table 801 and determines whether there is a setting link in the network device individual setting. When it is determined that there is a setting link (Yes in S1402), the snapshot creation unit 403 shifts the process to S1405.

On the other hand, when it is determined that there is no setting link (No in S1402), the snapshot creation unit 403 advances the process to S1403.
In S1403, the snapshot creation unit 403 creates an individual setting snapshot according to the method described in the description of FIG. Next, in S1404, the snapshot creation unit 403 creates a setting link for the network device individual setting according to the method described in FIG. 8, and shifts the processing to S1405.

  In S1405, the snapshot creation unit 403 acquires the setting ID of the network device common setting that the network device individual setting has. Further, the snapshot creation unit 403 refers to the setting management table 801 using the setting ID, and determines whether there is a setting link in the network device common setting. If it is determined that there is a setting link (Yes in S1405), the snapshot creation unit 403 shifts the processing to S1408.

On the other hand, when it is determined that there is no setting link (No in S1405), the snapshot creation unit 403 advances the process to S1406.
In S1406, the snapshot creation unit 403 creates a common setting snapshot according to the method described in the description of FIG. Next, in S1407, the snapshot creation unit 403 creates a setting link for the network device common setting according to the method described in FIG. 8, and shifts the processing to S1408.

  In step S1408, the installation link management unit 1201 determines whether there is an installation link in the network device common setting and the network device individual setting according to the method described in FIG. If it is determined that there is an installation link (Yes in S1408), the installation link management unit 1201 shifts the processing to S1410.

On the other hand, when it is determined that there is no installation link (No in S1408), the installation link management unit 1201 advances the process to S1409.
In S1409, the installation link management unit 1201 creates installation links for the network device common setting and the network device individual setting according to the method described in FIG. 13, and shifts the processing to S1410.

In S1410, the installation history management unit 404 records information for associating the network device ID with the installation link ID of the installation link in the DB 102.
Next, in S1411, the installation link management unit 1201 acquires the common setting snapshot ID and the individual setting snapshot ID from the installation link management table 1301 using the installation link ID. In addition, the setting distribution unit 402 acquires a corresponding individual setting snapshot from the individual setting snapshot ID according to the method described in the description of FIG. Further, according to the method described in the description of FIG. 9, the corresponding common setting snapshot is acquired from the common setting snapshot ID and distributed to the network device 111.

  In response to the distribution of the individual setting snapshot and the common setting snapshot in S1411, the setting acquisition unit 601 of the network device 111 acquires the individual setting snapshot and the common setting snapshot. In step S1412, the setting application unit 602 applies the common setting snapshot and the individual setting snapshot distributed by the setting distribution unit 402 and acquired by the setting acquisition unit 601 to the network device 111.

  In the present embodiment, the case where the network device setting 201 includes two types of settings, that is, a common setting for each network device model and an individual setting different for each network device has been described as an example. However, the network device setting 201 may be composed of three or more types of settings. For example, at least one of the common setting and the individual setting may be configured by a plurality of types, and as a result, the network device setting 201 may be configured by three or more types of settings.

  As described above, a mechanism is provided for determining the necessity of creating a snapshot for each type of setting. As a result, even when the network device settings 201 are composed of a plurality of types, it is possible to minimize the creation of snapshots and reduce storage costs.

  When the setting distribution system 100 is constructed using a public cloud service or the like, the file server 103 has eventual consistency as a characteristic of the public cloud service or the like. Therefore, after updating the data, there may be a slight time lag until the update is reliably reflected. In the case of the present embodiment, the following problems occur when the setting snapshot 301 is distributed to the network device 111 after the snapshot creating unit 403 creates the setting snapshot 301. When the snapshot 301 is distributed, the creation process of the setting snapshot 301 may not be completely completed, and there is a possibility that the setting snapshot 301 cannot be distributed.

  Therefore, in the third embodiment, a configuration that solves the above-described problem by executing a process of replacing the setting snapshot 301 and the network device setting 201 after the setting snapshot 301 is created will be described.

  In the present embodiment, differences from the first embodiment will be mainly described with reference to FIG. Note that each step described in FIG. 15 is the same as FIG. 11 except for S1506, and thus description thereof will be omitted.

  FIG. 15 is a flowchart illustrating the pre-installation processing of the network device 111 including replacement of the network device setting 201 and the setting snapshot 301 according to the third embodiment. The processing indicated by S1502 to S1507 in this flowchart is realized by the CPU 3000 of the Web server 101 reading out and executing the program stored in the secondary storage device 3002 to the main storage device 3001 as necessary. Further, the processing shown in S1508 is realized by the CPU 2001 of the network device 111 reading and executing the program stored in the secondary storage device 2003 to the main storage device 2002 as necessary.

First, S1501 to S1505 are the same as S1101 to S1105 in FIG.
Next, in S1506, the snapshot creation unit 403 executes the following replacement process for the network device setting 201 and the setting snapshot 301. The snapshot creation unit 403 acquires the file path of the network device setting 201 from the setting management table 801, and the file path of the setting snapshot 301 from the snapshot management table 901. Further, the snapshot creation unit 403 overwrites the file path of the setting snapshot 301 in the snapshot management table 901 with the file path of the acquired network device setting 201. Also, the snapshot creation unit 403 overwrites the file path of the network device setting 201 in the setting management table 801 with the file path of the acquired setting snapshot 301.
S1507 to S1508 are the same as S1106 to S1107 in FIG.

  As shown above, after creating a snapshot, swap the settings with the snapshot. At this time, the replacement is executed by rewriting the record on the DB 102 instead of performing the replacement by setting or copying the snapshot. Accordingly, it is possible to ensure that the snapshot can be acquired when the snapshot is distributed to the device.

  The setting delivery unit 402 may be configured to determine whether to create the setting snapshot 301 using the update date / time of the network device setting 201 and the creation date / time of the setting snapshot 301. Hereinafter, the difference between the fourth embodiment and the first embodiment will be described.

  An item for recording the last update date and time of the network device setting 201 is added to the setting management table 801 (not shown). In addition, an item for recording the creation date and time of the setting snapshot 301 is added to the snapshot management table 901 (not shown). In addition, an item for recording the setting ID of the network device setting 201 that is the creation source of the setting snapshot 301 is added to the snapshot management table 901 (not shown).

  When updating the network device setting 201, the setting update unit 401 also records the last update date and time of the network device setting 201 in the setting management table 801. When creating the setting snapshot 301, the snapshot creation unit 403 also records the creation date and time of the setting snapshot 301 in the snapshot management table 901. The snapshot creation unit 403 also records in the snapshot management table 901 the setting ID of the network device setting 201 that is the creation source of the setting snapshot 301.

  The snapshot creation unit 403 acquires the last update date / time of the target network device setting 201 from the setting management table 801 when determining whether to create the setting snapshot 301. Then, the snapshot creation unit 403 refers to the snapshot management table 901 and acquires a list of setting snapshots 301 created from the network device setting 201. The snapshot creation unit 403 determines that it is necessary to create the setting snapshot 301 when there is no match in the list between the last update date and time and the creation date and time of the snapshot 301.

  As described above, it is possible to determine whether to create a snapshot by a method other than the presence / absence of a link to the setting snapshot 301 in the network device setting 201.

  The setting snapshot 301 need only include data that can restore the state of the network device setting 201 at a certain point in time. Therefore, the setting snapshot 301 may be configured by difference information from the previously created snapshot 301 (that is, difference information between the setting before update and the setting after update). Note that the setting snapshot 301 created for the first time includes all data of the network device setting 201 because there is no difference from the snapshot 301 created last time. In the fifth embodiment, differences from the first embodiment will be mainly described with reference to FIGS. 16 and 17.

FIG. 16 is a diagram illustrating a difference setting management table 1601 according to the fifth embodiment.
The difference setting management table 1601 is obtained by adding an item for recording the snapshot ID of the latest setting snapshot 301 of the network device setting 201 to the setting management table 801. This item is called “latest snapshot ID” of the network device setting 201.

  When creating the setting snapshot 301, the snapshot creation unit 403 updates the latest snapshot ID with the snapshot ID of the created setting snapshot 301 in addition to the processing described in the first embodiment.

FIG. 17 is a diagram illustrating a differential snapshot management table 1701 according to the fifth embodiment.
The differential snapshot management table 1701 is obtained by adding an item to the snapshot management table 901 to record the snapshot ID of the setting snapshot 301 of the previous generation created for the same network device setting 201. is there. This item is called “previous generation snapshot ID” of the setting snapshot 301. That is, the differential snapshot management table 1701 associates the latest generation setting snapshot with the previous generation setting snapshot.

  In creating the setting snapshot 301 of the network device setting 201, the snapshot creating unit 403 executes the following processing in addition to the processing described in the first embodiment. The snapshot creation unit 403 acquires the latest snapshot ID of the network device setting 201 recorded in the difference setting management table 1601. Then, when the snapshot ID and file path of the created setting snapshot 301 are written into the differential snapshot management table 1701, the acquired latest snapshot ID is written into the previous generation snapshot ID.

  The acquisition of the latest snapshot ID from the difference setting management table 1601 is executed before the latest snapshot ID is updated by the process shown in FIG. If the latest snapshot ID of the network device setting 201 is not recorded, the previous generation snapshot ID of the differential snapshot management table 1701 is not recorded.

  When the setting distribution unit 402 acquires the setting snapshot 301 from the snapshot ID and distributes the setting snapshot 301 to the network device 111, the setting distribution unit 402 executes the following process to restore the network device setting 201 from the plurality of setting snapshots 301. Referring to the differential snapshot management table 1701, the previous generation snapshot ID and file path corresponding to the snapshot ID are acquired. If the previous generation snapshot ID is recorded, the above process is executed again using the snapshot ID as a snapshot ID. When the previous generation snapshot ID is not recorded, the above-described processing is terminated. A series of setting snapshots 301 is acquired from the file server 103 using a series of file paths acquired by repeating the above process. Then, the obtained series of setting snapshots 301 are combined to restore the network device setting 201, and the restored network device setting 201 is distributed to the network device 111.

  As described above, the setting snapshot 301 can be configured based on difference information from the previously created snapshot 301.

  In the previous installation of the network device 111, there are few cases where the network device setting 201 used in the previous installation is once edited again and used in another previous installation. Therefore, in many cases, the contents of the network device setting 201 and the setting snapshot 301 are the same. In this way, the same data is held redundantly, resulting in waste in terms of storage cost. In order to solve this problem, the sixth embodiment is configured to determine whether to create the setting snapshot 301 based on whether or not the network device setting 201 has been used in the past in the setting update and setting distribution processing. To do. Hereinafter, the difference between the sixth embodiment and the first embodiment will be described.

  When updating the network device setting 201, the setting update unit 401 according to the sixth embodiment refers to the setting management table 801 and determines whether there is a history used in the installation. As for the history used in the installation, it is determined that there is a history when “there is a setting link”, and it is determined that there is no history when there is no setting link. When there is a history, it is called “there is installation usage history”, and when there is no history, it is called “no installation usage history”. The installation usage history corresponds to the distribution history to the network device. That is, the network device setting in which the installation usage history exists corresponds to the setting that has been distributed in the previous installation or the like. On the other hand, a network device setting for which no installation usage history exists corresponds to a setting that has not yet been distributed by previous installation or the like.

  When updating the setting, if the network device setting 201 has an installation usage history (a setting that has been distributed before), the setting updating unit 401 deletes the setting link of the network device setting 201. The process of deleting the setting link is referred to as “deleting the installation usage history”. Further, the setting update unit 401 stores the updated network device setting 201 at a location indicated by the file path of the network device setting 201 on the setting management table 801. Details are shown in a setting distribution unit 402 described later. In this case, the location indicated by the file path is a location different from the location where the network device settings before the update are stored. That is, if there is an installation usage history in the network device setting 201 to be updated, the setting update unit 401 deletes the installation usage history and updates it to a location different from the network device setting before the update. You will save the network device settings. In this way, overwriting of the distributed network device setting is prevented.

  If there is no installation usage history (in the case of a setting that has not yet been distributed), the setting update unit 401 updates the network device setting updated to the location indicated by the file path of the network device setting 201 on the setting management table 801. Save 201.

  The setting distribution unit 402 distributes the network device setting 201 to the network device 111 in response to a request from the network device 111. When there is an installation usage history in the network device setting 201, the setting distribution unit 402 acquires a file path from the snapshot management table 901 using the snapshot ID indicated by the installation usage history, that is, the setting link holds. . Then, the setting snapshot 301 is acquired from the location specified by the file path on the file server 103 and distributed to the network device 111. That is, when there is a distribution history in the network device setting to be distributed, the setting distribution unit 402 distributes the network device setting specified from the distribution history.

  When there is no installation / use history in the network device setting 201, the setting distribution unit 402 uses the snapshot management table 901 to store the file path of the network device setting 201 recorded in the setting management table 801 and the newly issued snapshot ID. Record a new record. Then, the setting distribution unit 402 acquires the setting snapshot 301 from the location specified by the file path on the file server 103, and distributes the setting snapshot 301 to the network device 111. Furthermore, the setting distribution unit 402 issues a new file path and overwrites and records it as the file path of the network device setting 201 on the setting management table 801. The setting distribution unit 402 records the newly issued snapshot ID as a snapshot ID on the setting management table 801. That is, the setting distribution unit 402 distributes the network device setting stored in the file path of the setting management table 801 when there is no distribution history in the network device setting to be distributed. Further, the setting distribution unit 402 creates a new storage destination (file path) in preparation for the case where the network device setting is updated, and updates the file path of the setting management table 801 with the file path. .

As described above, when there is no distribution history in the distribution target network device setting, the setting distribution unit 402 distributes the network device setting 201 instead of creating a new snapshot. As a result, it is possible to prevent the network device setting 201 and the setting snapshot 301 having the same contents from being held redundantly, and to reduce the waste of storage costs. Note that the setting distribution unit 402 determines a new storage destination of the updated network device setting 201 and updates the setting management table 801 in preparation for updating the network device setting 201 at the time of distribution. Thereby, it is possible to prevent the evidence of the distributed network device setting from being lost by overwriting by updating. Therefore, when the setting update unit 401 performs the update, if there is an installation usage history in the network device setting 201 to be updated, the updated network device setting is placed in a location different from the network device setting before the update. Can be saved.
A series of processes for updating the records on the snapshot management table 901 and the setting management table 801 will be referred to as “creating an installation usage history”.

  FIG. 20 is a flowchart illustrating the update process of the network device setting 201 according to the sixth embodiment. The processes shown in S2002 to S2004 in this flowchart are realized by the CPU 3000 of the Web server 101 reading out and executing a program stored in the secondary storage device 3002 to the main storage device 3001 as necessary.

  In response to a request from the setting editor PC 110, the CPU 3000 of the Web server 101 starts setting update processing of the network device setting 201 received from the setting editor PC 110 (S2001). The setting editor PC 110 transmits the setting data and setting ID of the network device setting 201 to the Web server 101 at the time of the request.

  First, in S2002, the setting update unit 401 refers to the setting management table 801 using the setting ID of the network device setting 201 requested to be updated, and the installation usage history is stored in the network device setting 201 requested to be updated. It is determined whether or not there is. If it is determined that there is an installation usage history (Yes in S2002), the setting update unit 401 advances the process to S2003. In S2003, the setting update unit 401 deletes the installation / use history and advances the process to S2004.

  On the other hand, when it is determined that there is no installation / use history (No in S2002), the setting update unit 401 advances the process to S2004.

In S2004, the setting update unit 401 stores the network device setting 201 in the location indicated by the file path of the network device setting 201 on the setting management table 801. At this time, if the installation / use history exists, the setting update unit 401 stores the updated network device setting in a location different from the network device setting before the update. On the other hand, when there is no installation usage history, the setting update unit 401 overwrites the network device setting before the update with the updated network device setting.
After the process of S2004, the setting update unit 401 ends the setting update process.

  FIG. 21 is a flowchart illustrating the pre-installation process of the network device setting 201 according to the sixth embodiment. The processing indicated by S2102 to S2105 in this flowchart is realized by the CPU 3000 of the Web server 101 reading out and executing the program stored in the secondary storage device 3002 to the main storage device 3001 as necessary. Further, the process indicated by S2106 is realized by the CPU 2001 of the network device 111 reading and executing the program stored in the secondary storage device 2003 to the main storage device 2002 as necessary.

  The CPU 3000 of the Web server 101 starts the pre-installation process in response to the pre-installation process request from the network device 111 (S2101). At the time of this request, the network device 111 transmits the network device ID of the network device 111 and the setting ID of the network device setting 201 to the setting distribution system 100.

In step S2102, the setting distribution unit 402 refers to the setting management table 801 using the setting ID, and determines whether there is an installation usage history in the network device setting 201 indicated by the setting ID. If it is determined that there is no installation / use history (No in S2102), the setting distribution unit 402 advances the process to S2103. In S2103, the setting distribution unit 402 creates an installation usage history in the network device setting 201. That is, the setting distribution unit 402 newly records the file path of the network device setting 201 recorded in the setting management table 801 and the newly issued snapshot ID in the snapshot management table 901. Furthermore, the setting distribution unit 402 issues a new file path and overwrites and records it as the file path of the network device setting 201 on the setting management table 801. Furthermore, the setting distribution unit 402 records the newly issued snapshot ID as the snapshot ID of the network device setting 201 on the setting management table 801.
After the process of S2103, the setting distribution unit 402 advances the process to S2104.

  On the other hand, if it is determined that there is an installation usage history (Yes in S2102), the setting distribution unit 402 advances the process to S2104.

  In S2104, the setting distribution unit 402 acquires the corresponding setting snapshot 301 from the setting snapshot ID and distributes the setting snapshot 301 to the network device 111 according to the method described in the description of FIG.

  In step S2105, the installation history management unit 404 records information for associating the network device ID and the snapshot ID in the DB 102 in accordance with the method described in FIG. In step S2106, the setting application unit 602 applies the setting snapshot 301 distributed by the setting distribution unit 402 to the network device 111.

  If an error occurs in either the distribution process in S2104 or the application process in S2106, and the setting distributed from the setting distribution system 100 is not applied to the network device 111, it is recorded in the DB 102 in S2105. Information for associating the network device ID and the snapshot ID may be deleted.

  In the above description, when there is no distribution history, the setting distribution unit 402 creates a new storage destination of the updated network device setting 201 and updates the setting management table 801 in preparation for the update of the network device setting 201. The configuration is shown. However, the setting update unit 401 may perform the process of creating a new storage destination of the updated network device setting 201 and updating the setting management table 801. Specifically, when there is no distribution history at the time of update, the setting update unit 401 creates a new storage destination of the updated network device setting 201 and updates the setting management table 801, and the updated storage destination In addition, the updated network device setting 201 may be stored.

  As described above, according to the sixth embodiment, the setting update and setting distribution processes are switched according to the presence / absence of the installation / use history of the network device setting 201. This makes it possible to suppress the creation frequency of the setting snapshot 301 as compared with the first embodiment in which the setting snapshot 301 is created uniformly at the time of initial setting distribution using the network device setting 201. As a result, it is possible to reduce the storage cost generated in the previous installation.

  As described above, according to each of the above-described embodiments, it is possible to reduce the storage cost required for holding the network device setting that occurs when the network device is installed in advance.

In addition, the structure of the various data mentioned above and its content are not limited to this, You may be comprised with various structures and content according to a use and the objective.
Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or storage medium. Specifically, the present invention may be applied to a system composed of a plurality of devices, or may be applied to an apparatus composed of a single device.
Moreover, all the structures which combined said each Example are also contained in this invention.

(Other examples)
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in the computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.
Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of one device.
The present invention is not limited to the above embodiments, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and these are excluded from the scope of the present invention. is not. That is, the present invention includes all the combinations of the above-described embodiments and modifications thereof.

100 setting distribution system
111 Network devices
401 Setting update section
402 Setting distribution section
403 Snapshot creation part
404 Installation History Management Department

Claims (10)

A distribution system for distributing setting information of a network device to a network device,
Update means capable of updating the setting information;
When performing distribution processing of setting information to the network device, a creation unit that creates a snapshot that is a copy of the setting information to be distributed and stores the snapshot in a storage unit;
Management means for recording and managing the association between the snapshot of the setting information and a network device that is a distribution destination in the distribution processing;
Distribution means for distributing a snapshot of the setting information to the network device as the distribution destination as the distribution processing;
The creation unit creates a snapshot from the setting information when the snapshot corresponding to the latest setting information to be distributed is not present in the storage unit, and corresponds to the latest setting information A distribution system characterized by not creating a snapshot from the setting information when a snapshot exists in the storage means. The setting information includes a plurality of types of setting information,
The creation means creates a snapshot for each type of the setting information,
An association means for associating each snapshot created for each type of the setting information;
The distribution system according to claim 1, wherein the distribution unit distributes each snapshot associated by the association unit.   The distribution system according to claim 2, wherein the plurality of types of setting information includes setting information common to a plurality of network devices and individual setting information for each network device.   2. The setting distribution system according to claim 1, further comprising a switching unit that replaces a snapshot of setting information to be distributed and setting information of a creation source of the snapshot before distribution by the distribution unit. The creation unit creates the snapshot, and if a snapshot corresponding to the setting information before the update by the update unit exists in the storage unit, the snapshot and the after update by the update unit Create difference information with the setting information as a snapshot,
An association means for associating a snapshot corresponding to the setting information before the update and a snapshot corresponding to the difference information;
The distribution system according to claim 1, wherein the distribution unit restores setting information from each snapshot associated by the association unit, and distributes the restored setting information. A distribution system for distributing setting information of a network device to a network device,
Storage means for storing the setting information;
Update means capable of updating the setting information;
Distribution means for distributing setting information to the network device;
A first management unit that manages a storage destination of the setting information and information that can specify a storage destination of the setting information when the setting information is distributed as a distribution history of the setting information;
A second management means for recording and managing a relationship between a storage destination of the distributed setting information and a network device serving as a distribution destination;
The distribution means distributes the setting information stored in the storage destination specified from the distribution history when the distribution history exists in the setting information to be distributed, and when the distribution history does not exist Performs distribution of the setting information to be distributed stored in the storage location managed by the first management unit, and registration of the distribution history in the first management unit,
The update unit overwrites and saves the setting information when there is no distribution history in the setting information to be updated, and saves the setting information before updating by deleting the distribution history when the distribution history exists. A distribution system characterized by storing updated setting information in a different location. When the distribution information does not exist in the setting information to be distributed, the distribution unit further stores a storage destination of the setting information to be distributed managed by the first management unit. Update first,
The distribution system according to claim 6, wherein the location different from the storage location of the setting information before update is the storage location of the setting information updated by the distribution means.   When the distribution history exists, the update unit deletes the distribution history, updates the storage destination of the setting information to be updated managed by the first management unit to a new storage destination, and updates the update history. 7. The distribution system according to claim 6, wherein the updated setting information is stored in a new storage destination different from the storage destination of the setting information before update. A distribution system control method for distributing setting information of a network device to a network device, comprising:
An update step capable of updating the setting information;
A creation step of creating a snapshot that is a copy of the setting information to be distributed and storing it in a storage means when performing distribution of the setting information to the network device;
A management step for recording a relationship between the snapshot of the setting information and a network device that is a distribution destination in the distribution processing;
A distribution step of distributing the snapshot of the setting information to the network device as the distribution destination as the distribution processing;
In the creation step, when a snapshot corresponding to the latest setting information to be distributed is not present in the storage unit, a snapshot is created from the setting information, and the latest setting information is handled. A delivery system control method characterized by not creating a snapshot from the setting information when a snapshot exists in the storage means.   The program for functioning a computer as a means of any one of Claims 1-8.

Images