Management system, management method, and management program

Abstract

This management system (100), which manages migration from a migration source NW device (10) to a migration destination NW device (20), among NW devices that communicate with other communication devices on a network, comprises: a conversion unit that converts a system of configuration data for setting the operation of the migration source NW device (10) into configuration data according to a system of configuration data of the migration destination NW device (20), by using a general-purpose parameter table in which each service can be associated on a user-by-user basis, and applies the converted configuration data to the migration destination NW device (20).

Description

[Technical Field]

[0001] The present invention relates to a management system, a management method, and a management program. [Background technology]

[0002] When upgrading or upgrading network devices that make up a network (NW), there are cases where the current NW device is migrated to a successor NW device. In this case, if the current NW device and the successor NW device have different configuration systems, it is necessary to convert the configuration data of the current NW device to the configuration data of the successor NW device. Note that configuration data is setting data that sets the operation of the NW device.

[0003] Here, a data migration method for migrating data between different databases has been proposed (see Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6059682 Summary of the Invention [Problem to be solved by the invention]

[0005] FIG. 12 is a diagram illustrating a configuration conversion process using conventional technology. The configuration data of a network device has a structure in which multiple pieces of linked setting information are arranged in a nested manner. However, as shown in the example of pre-conversion configuration data and the example of post-conversion configuration data in FIG. 12, the data structure of the configuration data differs depending on the configuration system, such as the combination of linked setting information and the nesting relationship. Therefore, unlike a database structure, a simple one-to-one conversion is not possible for configuration data.

[0006] The method described in Patent Document 1 is based on a database structure in which headers and values ​​are arranged in parallel, and the conversion logic is simple. Therefore, the method described in Patent Document 1, which is specialized for database structures such as migration between different databases, cannot be applied to configuration data migration between network devices with different configuration systems.

[0007] The present invention has been made in view of the above, and has as its object to provide a management system, a management method, and a management program that enable the transfer of configuration data between network devices with different configuration systems. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the objectives, the management system of the present invention is a management system that manages migration from a source network device to a destination network device among network devices that communicate with other communication devices on a network, and is characterized by having a conversion unit that uses a general-purpose parameter table that can associate each service on a user basis to convert a first setting data system that configures the operation of the source network device into second setting data that conforms to the setting data system of the destination network device, and applies the second setting data to the destination network device. [Effects of the Invention]

[0009] According to the present invention, it is possible to transfer configuration data between network devices with different configuration systems. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram illustrating an example of a configuration of a management system according to an embodiment. [Figure 2] FIG. 2 is a block diagram illustrating an example of the configuration of the conversion device illustrated in FIG. [Figure 3] FIG. 3 is a diagram showing an example of the data structure of the general-purpose parameter table. [Figure 4] FIG. 4 is a diagram illustrating the processing of the conversion unit shown in FIG. [Figure 5] FIG. 5 is a diagram illustrating the processing of the conversion unit shown in FIG. [Figure 6] FIG. 6 is a block diagram illustrating an example of the configuration of the verification device illustrated in FIG. [Figure 7] FIG. 7 is a diagram illustrating the process of the confirmation unit shown in FIG. [Figure 8] FIG. 8 is a sequence diagram illustrating an example of a processing procedure of the management processing according to the embodiment. [Figure 9] FIG. 9 is a sequence diagram illustrating an example of a processing procedure of the confirmation processing according to the embodiment. [Figure 10] FIG. 10 is a block diagram showing an example of the configuration of a source network (NW) device. [Figure 11] FIG. 11 is a diagram illustrating an example of a computer that implements a conversion device, a verification device, and a migration source NW device by executing a program. [Figure 12] FIG. 12 is a diagram illustrating a configuration conversion process to which the conventional technology is applied. DETAILED DESCRIPTION OF THE INVENTION

[0011] The following describes in detail embodiments of a management system, a management method, and a management program according to the present application, with reference to the accompanying drawings. Note that the management system, the management method, and the management program according to the present application are not limited to these embodiments.

[0012] [Embodiment Mode] First, an embodiment will be described. In the embodiment, a management system that manages the migration of a configuration from a source NW device to a destination NW device among network devices that communicate with other communication devices on a network (NW) will be described.

[0013] In this embodiment, a case will be described in which the configuration data systems of the source network device and the destination network device are different. Note that the configuration data is setting data that sets the operation of the network device, and has a structure in which multiple linked setting information (parameters) are arranged in a nested manner. "The configuration data systems are different" means that the combinations of linked parameters and the nesting relationships are different.

[0014] [Communication system configuration] The configuration of a management system according to an embodiment will be described below: Fig. 1 is a block diagram showing an example of the configuration of a management system according to an embodiment.

[0015] 1, a management system 100 according to an embodiment manages the migration of configuration data between a source network device 10 and a destination network device 20, among network devices that communicate with other communication devices on a network. The management system 100 includes a conversion device 30 and a confirmation device 40.

[0016] The conversion device 30 is provided between the source network device 10 and the destination network device 20. The conversion device 30 uses a general-purpose parameter table that can associate each service on a user-by-user basis to convert the system of config data C1 (first setting data) of the source network device 10 into config data Ct (second setting data) that conforms to the system of config data of the destination network device 20. The conversion device 30 applies the converted config data Ct to the destination network device 20.

[0017] The confirmation device 40 confirms that the handover of setting information is being performed normally between the source network device 10 and the destination network device 20, which have different configuration data systems. The confirmation device 40 receives as input the configuration data C2 (third configuration data) applied to the destination network device 20 and the first parameter table T1 (described later) created by the conversion device 30. The confirmation device 40 confirms that the migration of the configuration data C1 to the destination network device 20 is being performed normally based on the configuration data C2 and the first parameter table T1.

[0018] [Conversion device] Next, a description will be given of the conversion device 30. Fig. 2 is a block diagram showing an example of the configuration of the conversion device 30 shown in Fig. 1. As shown in Fig. 2, the conversion device 30 includes a communication unit 31, a storage unit 32, and a control unit 33.

[0019] The communication unit 31 is a communication interface for transmitting and receiving various information to and from other devices connected via a network, etc. The communication unit 31 is realized by a NIC (Network Interface Card) or the like, and performs communication between the control unit 33 (described later) and other devices (for example, the source NW device 10, the destination NW device 20, and the confirmation device 40) via telecommunication lines such as a LAN (Local Area Network) or the Internet.

[0020] The storage unit 32 is a storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The storage unit 32 may be a data-rewritable semiconductor memory such as a RAM (Random Access Memory), a flash memory, or an NVSRAM (Non-Volatile Static Random Access Memory). The storage unit 32 stores an OS (Operating System) and various programs executed by the conversion device 30. The storage unit 32 also stores various information used in the execution of the programs. The storage unit 32 stores a general-purpose parameter table 321, system data 322, pre-conversion configuration data 323, a first parameter table 324, and post-conversion configuration data 325.

[0021] The general-purpose parameter table 321 is a general-purpose parameter table created by the parameter table creation unit 332. FIG. 3 is a diagram showing an example of the data configuration of the general-purpose parameter table. In the general-purpose parameter table 321, each service item is associated with a user, as shown in the general-purpose parameter table T in FIG. 3. The service items are classified into whether or not the service is available and each option. In the general-purpose parameter table 321, each item and its arrangement are set so that each service and each service option can be associated on a user-by-user basis.

[0022] The architecture data 322 indicates the architecture of the configuration data of each network device. Specifically, the architecture data 322 indicates the format of the configuration data of each network device, for example, the combination of parameters to be linked and the nesting structure of the combination.

[0023] The pre-conversion configuration data 323 is, for example, configuration data (for example, configuration data C1) of the source network device 10. The first parameter table 324 is a first parameter table (for example, first parameter table T1) created by a generation unit 334 (described later). The post-conversion configuration data 325 is, for example, configuration data (for example, configuration data Ct) to be applied to the destination network device 20 created by a generation unit 334 (described later).

[0024] The control unit 33 controls the entire conversion device 30. The control unit 33 is, for example, an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The control unit 33 also has an internal memory for storing programs that define various processing procedures and control data, and executes each process using the internal memory. The control unit 33 also functions as various processing units by running various programs. The control unit 33 has a conversion unit 331.

[0025] The conversion unit 331 uses a general-purpose parameter table to convert the system of the configuration data C1 of the source network device 10 into configuration data Ct that conforms to the system of the configuration data of the destination network device 20. The conversion unit 331 applies the configuration data Ct to the destination network device 20. The conversion unit 331 has a parameter table creation unit 332, an extraction unit 333 (first extraction unit), a generation unit 334, and an application unit 335. FIGS. 4 and 5 are diagrams for explaining the processing of the conversion unit 331 shown in FIG. 2.

[0026] The parameter table creation unit 332 creates a general-purpose parameter table that can associate each service on a user-by-user basis. The parameter table creation unit 332 creates, for example, the general-purpose parameter table T shown in Fig. 3. The parameter table creation unit 332 creates the general-purpose parameter table T when migrating a network device, and may also create the general-purpose parameter table T in advance.

[0027] The extraction unit 333 extracts each parameter from the configuration data C1 and writes each extracted parameter in a corresponding cell of the general-purpose parameter table T to create a first parameter table T1 corresponding to the configuration data C1. For example, as shown in Fig. 4, a case will be described in which the configuration data C1 has a nested relationship in which services and options are linked for each user.

[0028] In this case, the extraction unit 333 extracts the data "Service x setting," "Service x option setting 1," and "Service x option setting 2" from the area W1 for user 1 of the configuration data C1 ((1) in FIG. 4). Then, the extraction unit 333 reflects the extracted contents by entering them in cells C11, C12, and C13 corresponding to service x and its options 1 and 2 in row R1 of the first parameter table T1 ((2) in FIG. 4).

[0029] Then, the extraction unit 333 extracts parameters related to service y from area W2 of the configuration data C1 and reflects the extracted data in cells C14 and C15 corresponding to the item of service y in row R1 of the first parameter table T1. The extraction unit 333 extracts parameters from area W3 of the configuration data C1 and reflects the extracted parameters in cell C16 corresponding to the filter item in row R1 of the first parameter table T1. Similarly, the extraction unit 333 extracts parameters from the configuration data C1 for user 2 and writes the extracted parameters in the corresponding cells in row R2 of the general-purpose parameter table T.

[0030] In this way, the extraction unit 333 extracts each linked parameter for each user from the configuration data C1 and enters it in the corresponding cell of the general-purpose parameter table T, thereby creating a first parameter table T1 that reflects the parameters of the configuration data C1. The extraction unit 333 outputs the created first parameter table T1 to the confirmation device 40.

[0031] The generation unit 334 generates configuration data Ct in which the parameters written in each cell of the first parameter table T1 are arranged according to the configuration data system applied to the destination NW device 20. For example, as shown in the configuration data Ct in Fig. 5, a case will be described in which the configuration data system of the destination NW device 20 has a nested relationship in which users and options are linked for each service.

[0032] In this case, the generation unit 334 places the contents written in cells C11, C12, and C13 related to service x in row R1 of the first parameter table T1 in the setting area W11 of service x ((3) in FIG. 5), and places "user 1" in area W12, indicating that the parameters in the setting area W11 are linked to user 1. Furthermore, the generation unit 334 places the contents written in cells C14 and C15 related to service y in row R1 of the first parameter table T1 in the setting area W13 of service y ((3) in FIG. 5). Similarly, the generation unit 334 generates the configuration data Ct by placing the contents of each cell in row R2 and subsequent rows of the first parameter table T1 in the corresponding areas.

[0033] The application unit 335 applies the configuration data Ct generated by the generation unit 334 to the destination network device 20.

[0034] [Verification device] Next, a description will be given of the confirmation device 40. Fig. 6 is a block diagram showing an example of the configuration of the confirmation device 40 shown in Fig. 1. As shown in Fig. 6, the confirmation device 40 has a communication unit 41, a storage unit 42, and a control unit 43.

[0035] The communication unit 41 is a communication interface for transmitting and receiving various information to and from other devices connected via a network, etc. The communication unit 41 is realized by a NIC, etc., and performs communication between the control unit 43 (described later) and other devices (e.g., the destination NW device 20, the conversion device 30) via telecommunication lines such as a LAN or the Internet.

[0036] The storage unit 42 is a storage device such as an HDD or SSD. The storage unit 42 may be a data-rewritable semiconductor memory such as a RAM, a flash memory, or an NVSRAM. The storage unit 42 stores an OS and various programs executed by the verification device 40. The storage unit 42 also stores various information used in the execution of the programs. The storage unit 42 stores a general-purpose parameter table 421 having the same configuration as the general-purpose parameter table 321, system data 322, a first parameter table 324 (e.g., first parameter table T1), post-application configuration data 425 (e.g., configuration data C2) applied to the destination NW device 20, and a second parameter table 426 (e.g., second parameter table T2) created by an extraction unit 433 (described later).

[0037] The control unit 43 controls the entire verification device 40. The control unit 43 is, for example, an electronic circuit such as a CPU or MPU, or an integrated circuit such as an ASIC or FPGA. The control unit 43 also has an internal memory for storing programs that define various processing procedures and control data, and executes each process using the internal memory. The control unit 43 also functions as various processing units by running various programs. The control unit 43 has a verification unit 431.

[0038] The confirmation unit 431 receives as input the configuration data C2 applied to the destination network device 20 and the first parameter table T1. The confirmation unit 431 compares the parameters of the configuration data C2 with the parameters of the first parameter table T1, and confirms that the migration of the configuration data C1 to the destination network device 20 has been performed normally. The confirmation unit 431 includes a parameter table creation unit 432, an extraction unit 433 (second extraction unit), a comparison unit 434, and a determination unit 435. FIG. 7 is a diagram illustrating the processing of the confirmation unit 431 shown in FIG. 6.

[0039] The parameter table creation unit 432 has the same function as the parameter table creation unit 332, and creates a general-purpose parameter table T' (not shown) having the same configuration as the general-purpose parameter table T.

[0040] The extraction unit 433 extracts each parameter from the configuration data C2 and enters each extracted parameter in the corresponding cell of the general-purpose parameter table T' created by the parameter table creation unit 432, thereby creating a second parameter table corresponding to the configuration data C2.

[0041] For example, the extraction unit 433 extracts the data "Service x option setting 1," "Service x option setting 2," and "User 1" from areas W21 and W22 for service x in the configuration data C2 ((1) in FIG. 7). Then, the extraction unit 433 reflects the extracted contents by entering them in cells C2-11, C2-12, and C2-13 in row R1-1 of the second parameter table T2 that correspond to service x and its options 1 and 2 ((2) in FIG. 7). Similarly, the extraction unit 433 extracts parameters for service y from area W23 of the configuration data C2, and reflects the extracted parameters in cells C2-14 and C2-15 that correspond to the item of service y in row R1-1 of the second parameter table T2.

[0042] In this way, the extraction unit 433 extracts each parameter from the configuration data C2 and enters it in the corresponding cell of the general-purpose parameter table T', thereby creating a second parameter table T2 that reflects the parameters of the configuration data C2.

[0043] The collation unit 434 collates the second parameter table T2 with the first parameter table T1. The second parameter table T2 and the first parameter table T1 have the same configuration. Therefore, when collating the second parameter table T2 with the first parameter table T1, the collation unit 434 performs the collation by comparing the contents of cells at the same position. For example, in the example of FIG. 7, the collation unit 434 collates the contents written in cell C2-11 of the second parameter table T2 with the contents written in cell C11 of the first parameter table T1 ((3) of FIG. 7). The collation unit 434 collates the contents written in cell C2-12 of the second parameter table T2 with the contents written in cell C12 of the first parameter table T1 ((3) of FIG. 7).

[0044] If the second parameter table T2 and the first parameter table T1 match, the determination unit 435 determines that the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally. In this case, the determination unit 435 notifies the management server (not shown) of the management system 100 that the migration of the configuration data between the migration source NW device 10 and the migration destination NW device 20 has been performed normally.

[0045] On the other hand, if the second parameter table T2 and the first parameter table T1 do not match, the determination unit 435 determines that the migration of the configuration data C1 to the destination NW device 20 has not been performed normally. In this case, the determination unit 435 notifies the management server of the management system 100 of the mismatched parameter information and that the migration of the configuration data between the source NW device 10 and the destination NW device 20 has not been performed normally.

[0046] [Administrative Processing] Next, a description will be given of management processing executed by the management system 100. Fig. 8 is a sequence diagram showing an example of a processing procedure of the management processing according to the embodiment.

[0047] 8, when migrating a configuration from a source network device 10 to a destination network device 20, first, the conversion device 30 receives pre-conversion configuration data C1 from the source network device 10 (step S1). The conversion device 30 creates a general-purpose parameter table T (step S2).

[0048] The conversion device 30 extracts each parameter from the configuration data C1 and writes and reflects each extracted parameter in the corresponding cell of the general-purpose parameter table T (step S3), thereby creating a first parameter table T1 corresponding to the configuration data C1.

[0049] The conversion device 30 generates configuration data Ct conforming to the system of the destination NW device 20 by arranging the parameters written in each cell of the first parameter table T1 according to the system of the configuration data applied to the destination NW device 20 (step S4). Then, the conversion device 30 transmits the configuration data Ct (converted configuration data) to the destination NW device 20 (step S5), and applies the configuration data Ct to the destination NW device 20 (step S6).

[0050] [Confirmation process] Next, a description will be given of the confirmation process executed by the management system 100. Fig. 9 is a sequence diagram showing an example of the processing procedure of the confirmation process according to the embodiment.

[0051] 9, the confirmation device 40 receives the configuration data C2 applied to the destination NW device 20 from the destination NW device 20 (step S11). Note that the confirmation device 40 has already acquired the first parameter table T1 created by the conversion device 30.

[0052] The verification device 40 creates a general-purpose parameter table T' having the same configuration as the general-purpose parameter table T (step S12). The verification device 40 extracts each parameter from the configuration data C2 and writes and reflects each extracted parameter in the corresponding cell of the general-purpose parameter table T' created in step S11 (step S13), thereby creating a second parameter table T2 corresponding to the configuration data C2.

[0053] The confirmation device 40 compares the second parameter table T2 with the first parameter table T1 (step S14). Based on the comparison result of step S14, the confirmation device 40 determines whether the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally (step S15).

[0054] [Effects of the embodiment] In this way, in the embodiment, a general-purpose parameter table that can associate each service on a user-by-user basis is used to convert the system of configuration data C1 that configures the operation of the source NW device 10 into configuration data Ct that conforms to the system of configuration data of the destination NW device 20.

[0055] Specifically, in the embodiment, each parameter is extracted from the configuration data C1, and each extracted parameter is entered in the corresponding cell of a general-purpose parameter table T to create a first parameter table T1 corresponding to the configuration data C1. Then, in the embodiment, configuration data Ct is generated in which the parameters entered in each cell of the first parameter table T1 are arranged according to the configuration data system applied to the migration destination NW device 20. This makes it possible in the embodiment to migrate configuration data between network devices with different configuration systems.

[0056] Furthermore, when migrating from current network equipment to successor network equipment, especially in a telecommunications carrier network, it is necessary to minimize the impact on user communications. To achieve this, it is necessary to ensure that the configuration information of the current network equipment is properly transferred to the configuration of the successor network equipment after conversion. However, when the configuration systems are different, it is not possible to confirm whether the configuration information has been transferred by simply comparing that there are no differences.

[0057] In contrast to this, in this embodiment, based on the configuration data C2 applied to the migration destination NW device 20 and the first parameter table T1, it is confirmed whether the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally.

[0058] Specifically, in the embodiment, each parameter is extracted from the configuration data C2, and each extracted parameter is entered in a corresponding cell of a general-purpose parameter table T' having the same configuration as the general-purpose parameter table, thereby creating a second parameter table T2 corresponding to the configuration data C2. Then, in the embodiment, by comparing the second parameter table T2 with the first parameter table T1, it is confirmed whether the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally, thereby confirming whether the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally.

[0059] As a result, according to the embodiment, even if the configuration systems are different, it is possible to appropriately check whether the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally.

[0060] As described above, according to the embodiment, even if the configuration systems are different between the source network device 10 and the destination network device 20, configuration conversion and normality confirmation can be appropriately performed.

[0061] [Modification of the embodiment] The source network device may have the functions of the conversion device 30. FIG. 10 is a block diagram showing an example of the configuration of the source network device. As shown in FIG. 10, the source network device 210 may have a configuration including a conversion unit 331. In this case, the processing performed by the conversion device 30 is executed by the source network device 210. The communication unit 211 has the same function as the communication unit 11 shown in FIG. 2, and the storage unit 212 has the same function as the storage unit 12 shown in FIG. 2. The control unit 213 has the same function as the control unit 13 shown in FIG. 2, and includes a NW processing unit 2131 that executes various processes between the network devices, and a conversion unit 331.

[0062] [System configuration of the embodiment] The components of the conversion device 30, the confirmation device 40, and the source network device 210 are conceptual functional components and do not necessarily need to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of the functions of the conversion device 30, the confirmation device 40, and the source network device 210 is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed or integrated in any unit depending on various loads, usage conditions, etc.

[0063] Furthermore, all or any part of the processes performed in the conversion device 30, the confirmation device 40, and the source NW device 210 may be realized by a CPU, a GPU (Graphics Processing Unit), and a program analyzed and executed by the CPU and the GPU. Furthermore, each process performed in the conversion device 30, the confirmation device 40, and the source NW device 210 may be realized as hardware using wired logic.

[0064] Furthermore, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually. Alternatively, all or part of the processes described as being performed manually can be performed automatically using a known method. In addition, the processing procedures, control procedures, specific names, and information including various data and parameters described above and illustrated can be changed as appropriate unless otherwise specified.

[0065] [program] 11 is a diagram showing an example of a computer in which a conversion device 30, a confirmation device 40, and a source NW device 210 are realized by executing a program. The computer 1000 has, for example, a memory 1010 and a CPU 1020. The computer 1000 also has a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These components are connected by a bus 1080.

[0066] The memory 1010 includes a ROM 1011 and a RAM 1012. The ROM 1011 stores a boot program such as a BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to a hard disk drive 1090. The disk drive interface 1040 is connected to a disk drive 1100. A removable storage medium such as a magnetic disk or optical disk is inserted into the disk drive 1100. The serial port interface 1050 is connected to a mouse 1110 and a keyboard 1120, for example. The video adapter 1060 is connected to a display 1130, for example.

[0067] The hard disk drive 1090 stores, for example, an OS (Operating System) 1091, an application program 1092, a program module 1093, and program data 1094. That is, the programs that define the processes of the conversion device 30, the confirmation device 40, and the source NW device 210 are implemented as program modules 1093 in which code executable by the computer 1000 is written. The program modules 1093 are stored, for example, in the hard disk drive 1090. For example, the program modules 1093 for executing processes similar to those of the functional configurations of the conversion device 30, the confirmation device 40, and the source NW device 210 are stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced by an SSD (Solid State Drive).

[0068] Furthermore, setting data used in the processing of the above-described embodiment is stored as program data 1094, for example, in memory 1010 or hard disk drive 1090. Then, CPU 1020 reads program module 1093 and program data 1094 stored in memory 1010 or hard disk drive 1090 into RAM 1012 as necessary and executes them.

[0069] The program module 1093 and program data 1094 are not limited to being stored in the hard disk drive 1090, but may also be stored in, for example, a removable storage medium and read by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and program data 1094 may be stored in another computer connected via a network (such as a local area network (LAN) or a wide area network (WAN)). The program module 1093 and program data 1094 may then be read by the CPU 1020 from the other computer via the network interface 1070.

[0070] Although the present invention has been described above as an embodiment, the present invention is not limited to the descriptions and drawings that form part of the disclosure of the present invention. In other words, other embodiments, examples, and operational techniques that can be made by those skilled in the art based on the present invention are all included in the scope of the present invention. [Explanation of symbols]

[0071] 10 Source network device 20 Destination network device 30 Conversion Device 31, 41, 211 Communications Department 32,42,212 Storage section 33,43,213 Control Unit 40 Verification device 100 Management Systems 331 Conversion Unit 332,432 Parameter Table Creation Department 333,433 Extraction part 334 Generation part 335 Application section 431 Confirmation Department 434 Matching Unit 435 Judgment section 2131 Network Processing Unit

Claims

1. A management system for managing migration from a source network device to a destination network device among network devices that communicate with other communication devices on a network, comprising: a conversion unit that, when setting data for setting the operation of a network device has a structure in which user identification information and a plurality of parameters related to services for the user are linked and arranged in a nested manner, converts a system of first setting data for setting the operation of the source network device into second setting data that conforms to the system of setting data of the destination network device by using a general-purpose parameter table that can associate each service on a user-by-user basis, and applies the second setting data to the destination network device. and The conversion unit a first extraction unit that extracts each parameter from the first setting data and writes each extracted parameter in a corresponding cell of the general-purpose parameter table to create a first parameter table corresponding to the first setting data; a generating unit that generates the second setting data by arranging the parameters described in each cell of the first parameter table in accordance with a setting data system to be applied to the migration destination network device; an application unit that applies the second configuration data to the migration destination network device; A management system comprising:

2. a confirmation unit that confirms whether or not the first setting data has been successfully transferred to the destination network device based on the third setting data applied to the destination network device and the first parameter table; The management system according to claim 1 , further comprising:

3. The confirmation unit a second extraction unit that extracts each parameter from the third setting data and writes each extracted parameter in a corresponding cell of a parameter table having the same configuration as the general-purpose parameter table, thereby creating a second parameter table corresponding to the third setting data; a collation unit that compares the second parameter table with the first parameter table; a determination unit that determines that the migration of the first setting data to the migration destination network device is being performed normally when the second parameter table and the first parameter table match, and that the migration of the first setting data to the migration destination network device is not being performed normally when the second parameter table and the first parameter table do not match; 3. The management system according to claim 2, further comprising:

4. A management method executed by a management system that manages migration from a source network device to a destination network device among network devices that communicate with other communication devices on a network, comprising: The management system has a conversion device, a step in which, when the configuration data for configuring the operation of the network device has a structure in which user identification information and a plurality of parameters related to services for the user are linked and arranged in a nested manner, the conversion device converts the system of first configuration data for configuring the operation of the source network device into second configuration data that conforms to the system of configuration data of the destination network device using a general-purpose parameter table that can associate each service on a user-by-user basis, and applies the second configuration data to the destination network device; Including, The applying step comprises: a first extraction step of extracting each parameter from the first setting data and entering each extracted parameter in a corresponding cell of the general-purpose parameter table to create a first parameter table corresponding to the first setting data; a generating step of generating the second setting data in which the parameters described in each cell of the first parameter table are arranged in accordance with a setting data system to be applied to the destination network device; an application step of applying the second configuration data to the migration destination network device; A management method comprising:

5. When the configuration data for configuring the operation of the network device has a structure in which user identification information and a plurality of parameters related to services for the user are linked and arranged in a nested manner, converting first configuration data for configuring the operation of the source network device into second configuration data that conforms to the configuration data system of the destination network device using a general-purpose parameter table that can associate each service on a user-by-user basis, and applying the second configuration data to the destination network device. on the computer, The applying step comprises: a first extraction step of extracting each parameter from the first setting data and entering each extracted parameter in a corresponding cell of the general-purpose parameter table to create a first parameter table corresponding to the first setting data; a generating step of generating the second setting data in which the parameters described in each cell of the first parameter table are arranged in accordance with a system of setting data to be applied to the destination network device; an application step of applying the second configuration data to the migration destination network device; Management program including.

Images