Management system, management method and management program

Abstract

A management system (100) comprising: a conversion device (30) including a first extraction unit for extracting set contents for each network (NW) function, as first summary information, from first setting data which sets operations of a migration source NW device (10), and a conversion unit for converting the system of the first setting data which sets the operation of the migration source NW device (10) into second setting data conforming to the system of setting data for a migration destination NW device (20), and applying the second setting data to the migration destination NW device (20); and a verifying device (40) including a determination unit for determining, on the basis of the first summary information and third setting data applied to the migration destination NW device (20), whether migration to the first setting data migration destination NW device (20) is carried out normally.

Description

[Technical field]

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

[0002] Migrating network (NW) devices requires migrating the configuration information of the old devices and switching routes. The migration of device configuration information involves extracting the configuration information (config data) of the source NW device, converting it to configuration information for the destination NW device, and applying the config data to the destination device.

[0003] If a difference in device configuration occurs between the source network device and the destination network device, it can cause delays in the start of services for customer users, or the inability to provide services, etc. For this reason, it is necessary to check that there are no errors in the configuration data before and after the migration.

[0004] Conventionally, methods have been proposed for migrating databases and converting data during migration. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2011-049695 A [Patent Document 2] JP 2015-222465 A [Patent Document 3] JP 2015-153344 A Summary of the Invention [Problem to be solved by the invention]

[0006] In the conventional method, in order to confirm whether the data has been correctly transferred, the equivalence of the database before and after the transfer is confirmed by checking whether the element values ​​of the data table match.

[0007] However, in the migration of network devices, the setting logic and setting grammar for realizing the same functions in the source network device and the destination network device are different, so that equivalence cannot be determined by simply matching elements.

[0008] In addition, when a telecommunications carrier performs configuration migration of network devices, the conversion time is long due to the huge amount of configuration and complex configuration conversion logic, and there is a possibility that route switching may not be completed during the nighttime hours when services are quiet. Therefore, there has been a demand for a method that can efficiently execute the equivalence of configuration data between the source network device and the destination network device.

[0009] The present invention has been made in consideration of the above, and aims to provide a management system, management method, and management program that can efficiently check whether configuration data between network devices has been transferred successfully. [Means for solving the problem]

[0010] In order to solve the above-mentioned problems and achieve the object, the management system of the present invention is a management system that manages migration from a source network device to a destination network device, and is characterized in having a conversion device having a first extraction unit that extracts setting contents for each network function as first summary information from first setting data that sets the operation of the source network device, and a conversion unit that converts the system of the first setting data that sets the operation of the source network device into second setting data that conforms to the system of the setting data of the destination network device and applies the second setting data to the destination network device, and a confirmation device having a judgment unit that judges whether the migration of the first setting data to the destination network device has been performed normally based on the first summary information and the third setting data applied to the destination network device. Effect of the Invention

[0011] According to the present invention, it is possible to efficiently check whether or not configuration data between network devices has been transferred normally. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram illustrating an example of a configuration of a management system according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of the first summary information. [Diagram 3] FIG. 3 is a diagram showing an example of a determination result output by the confirmation device. [Figure 4] FIG. 4 is a block diagram illustrating an example of a configuration of the conversion device illustrated in FIG. [Diagram 5] FIG. 5 is a diagram illustrating an example of a data configuration of the system data table. [Figure 6] FIG. 6 is a diagram illustrating an example of a data configuration of the system data table. [Figure 7] FIG. 7 is a diagram illustrating an example of a data configuration of the system data table. [Figure 8] FIG. 8 is a diagram for explaining the processing of the conversion device and the verification device. [Figure 9] FIG. 9 is a block diagram illustrating an example of the configuration of the confirmation device illustrated in FIG. [Figure 10] FIG. 10 is a sequence diagram illustrating an example of a processing procedure of the management processing according to the embodiment. [Figure 11] FIG. 11 is a sequence diagram illustrating an example of a procedure of the confirmation process according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of a computer that realizes the conversion device and the confirmation device by executing a program. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an embodiment of a management system, a management method, and a management program according to the present application will be described in detail with reference to the drawings. Note that the management system, the management method, and the management program according to the present application are not limited to the embodiment.

[0014] [Embodiment Mode] First, an embodiment will be described. In the embodiment, a management system that manages the migration of a configuration from a source network (NW) device to a destination NW device will be described.

[0015] In the embodiment, a case will be described where it is confirmed whether or not the configuration data has been normally transferred from the source network device to the destination network device. The configuration data is setting data for setting the operation of the network device, and has a structure in which multiple linked setting information (parameters) are arranged in a nested manner. The different configuration data systems mean that the combinations of linked parameters and the nesting relationships are different.

[0016] [Management system configuration] A 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.

[0017] 1, a management system 100 according to the embodiment manages the migration of configuration data between a source network device 10 and a destination network device 20. The management system 100 includes a conversion device 30 and a confirmation device 40.

[0018] The conversion device 30 is provided between the source NW device 10 and the destination NW device 20. The conversion device 30 converts the system of the config data C1 (first setting data) of the source NW device 10 into config data Ct (second setting data) that conforms to the system of the config data of the destination NW device 20. The conversion device 30 applies the converted config data Ct to the destination NW device 20.

[0019] The conversion device 30 extracts setting contents for each network function from the configuration data C1 as first summary information, and outputs it to the confirmation device 40. Fig. 2 is a diagram showing an example of the first summary information F1. As shown in Fig. 2, the first summary information F1 describes various setting contents for each network function extracted from the configuration data C1, such as the loop-up address of the device, the IP addresses used for each service, and the number of VLANs (vlans) set.

[0020] In addition, when the configuration data systems are different between the source NW device 10 and the destination NW device 20, the conversion device 30 uses a parameter sheet that can associate setting contents for each network function to extract first summary information from the configuration data C1 and convert the configuration data C1 to configuration data Ct.

[0021] The confirmation device 40 confirms that the handover of setting information is normally performed between the source NW device 10 and the destination NW device 20. The confirmation device 40 receives as input the config data C2 (third setting data) applied to the destination NW device 20 and the first summary information output by the conversion device 30. The confirmation device 40 extracts setting contents for each network function from the config data C2 as second summary information.

[0022] The second summary information is the same as the first summary information F1, and describes various setting contents for network functions extracted from the configuration data C2.

[0023] The confirmation device 40 judges whether the migration of the configuration data C1 to the destination NW device 20 is performed normally based on the first summary information F1 and the second summary information. The confirmation device 40 compares the contents of the first summary information F1 and the second summary information item by item and judges whether they match. If the first summary information F1 and the second summary information match, the confirmation device 40 judges that the migration of the configuration data C1 to the destination NW device 20 is performed normally. On the other hand, if the first summary information F1 and the second summary information do not match, the confirmation device 40 judges that the migration of the configuration data C1 to the destination NW device 20 is not performed normally.

[0024] Then, the confirmation device 40 notifies the judgment result, for example, to a management server of the management system 100. Fig. 3 is a diagram showing an example of the judgment result output by the confirmation device 40. As shown in Fig. 3, in the judgment result E1, a judgment result (OK or NG) is recorded for each item, and, for example, the judgment results of all items are recorded at the end.

[0025] In addition, when the configuration data systems are different between the source network device 10 and the destination network device 20, the confirmation device 40 uses a system data table in the same format as the system data table used by the conversion device 30 to extract the second summary information from the configuration data C2 and compare the configuration data C1 with the configuration data C2.

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

[0027] 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 (e.g., the source NW device 10, the destination NW device 20, and the confirmation device 40) via electric communication lines such as a LAN (Local Area Network) or the Internet.

[0028] The storage unit 32 is a storage device such as a hard disk drive (HDD) or a solid state drive (SSD). The storage unit 32 may be a semiconductor memory in which data can be rewritten, such as a random access memory (RAM), a flash memory, or a non-volatile static random access memory (NVSRAM). The storage unit 32 stores an operating system (OS) and various programs executed by the conversion device 30. Furthermore, the storage unit 32 stores various information used in the execution of the programs.

[0029] The storage unit 32 stores a parameter sheet 321, a system data table 322 (first system data table), pre-conversion configuration data 323, first summary information 324, and post-conversion configuration data 325. The storage unit 32 also stores information on each format of the configuration data of each NW device.

[0030] The parameter sheet 321 is used when there is a difference in the required configuration setting contents between the source NW device 10 and the destination NW device 20 and the difference is to be resolved. For example, a difference may exist when the destination NW device 20 has a unique PKG (package) that does not exist in the source NW device 10, and the communication address of the unique PKG needs to be set to enable the unique PKG. In such a case, the conversion device 30 fills in the information required for operation by recording the communication address of the unique PKG of the destination NW device 20 in the parameter sheet 321.

[0031] The system data table 322 has a format corresponding to each network function. FIGS. 5 to 7 are diagrams showing an example of the data configuration of the system data table. In the system data table T1 of FIG. 5, the setting contents can be associated with each service item provided to the user for each user. In the system data table T1, cells corresponding to items including the presence or absence of an Internet Service Provider (ISP (Service Provider)) and items including the presence or absence of DHCP (Dynamic Host Configuration Protocol) are provided for each user. In addition, the system data table T2 of FIG. 6 can associate addresses and the like according to the functions provided to the user. In addition, the system data table T3 of FIG. 7 can associate security contents with each security policy.

[0032] The pre-conversion configuration data 323 is, for example, configuration data (for example, configuration data C1) of the source NW device 10. The first summary information 324 is, for example, first summary information F1, which is information extracted from the configuration data C1 by an extraction unit 331 (described later). The post-conversion configuration data 325 is, for example, configuration data (for example, configuration data Ct) that is applied to the destination NW device 20 and that is converted by a conversion unit 332 (described later).

[0033] The control unit 33 controls the entire conversion device 30. The control unit 33 is, for example, an electronic circuit such as a central processing unit (CPU) or a micro processing unit (MPU), or an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The control unit 33 also has an internal memory for storing programs defining 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 the operation of various programs. The control unit 33 has an extraction unit 331 (first extraction unit) and a conversion unit 332.

[0034] The extraction unit 331 extracts setting contents (e.g., parameters) for each network function as first summary information from the configuration data C1. The extraction unit 331 extracts, as first summary information from the configuration data C1, user information of a user who receives a predetermined service via the source NW device 10, unique information of the source NW device 10, and / or the number of networks and connection destinations set in the source NW device.

[0035] The extraction unit 331 extracts the setting contents for each network function from the configuration data C1, and writes the extracted setting contents in the corresponding cells of the system data table 322 in the format corresponding to each network function. FIG. 8 is a diagram for explaining the processing of the conversion device 30 and the confirmation device 40.

[0036] 8, for example, the extraction unit 331 writes the ISP setting contents D1-1 for the "interface USER1.1002" from the configuration data C1 into each cell W1-1 corresponding to this setting contents in the system data table T1 (see FIG. 5) (arrow Y1-1). Also, the extraction unit 331 writes the setting contents D1-2 for the function "viewing channel list" provided to the user from the configuration data C1 into each cell W1-2 corresponding to this setting contents in the system data table T2 (see FIG. 6) (arrow Y2-1).

[0037] In this way, the extraction unit 331 extracts each setting content associated with each network function from the configuration data C1 and writes it in the corresponding cells of the system data tables T1 to T3, thereby creating system data tables T1-1, T1-2, and T1-3 in which the setting content of the configuration data C1 is written for each network function. The extraction unit 331 uses these system data tables T1-1, T1-2, and T1-3 as the first summary information 324 as they are, or uses information that summarizes user information of a user who receives a predetermined service via the source NW device 10, unique information of the source NW device 10, and / or the number of settings of networks and connection destinations in the source NW device as the first summary information based on the system data tables T1-1, T1-2, and T1-3. The extraction unit 331 outputs the first summary information 324 to the confirmation device 40.

[0038] The conversion unit 332 converts the system of the configuration data C1 into configuration data Ct that conforms to the system of the setting data of the destination network device, and applies the configuration data Ct to the destination network device 20.

[0039] When the configuration data systems differ between the source network device 10 and the destination network device 20, the conversion unit 332 generates configuration data Ct by arranging the setting contents written in each cell of the system data tables T1-1, T1-2, and T1-3 according to the system of the configuration data applied to the destination network device 20.

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

[0041] The communication unit 41 is a communication interface that transmits and receives 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 migration destination NW device 20, the conversion device 30) via electric communication lines such as a LAN or the Internet.

[0042] 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. Furthermore, the storage unit 42 stores various information used in the execution of the programs.

[0043] The memory unit 42 stores a parameter sheet 321, a system data table 322, first summary information 324 (e.g., system data tables T1-1, T1-2, T1-3), post-application configuration data 421 (e.g., configuration data C2) applied to the destination NW device 20, second summary information 422 created by an extraction unit 431 (described later), and a judgment result 423 by a judgment unit 433 (e.g., judgment result E1).

[0044] 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 defining 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 the operation of various programs. The control unit 43 has an extraction unit 431 (second extraction unit), a collation unit 432, and a determination unit 433.

[0045] The extraction unit 431 extracts setting contents for each network function as second summary information from the configuration data C2. The extraction unit 431 extracts user information of a user who receives a predetermined service via the destination NW device 20, unique information of the destination NW device 20, and / or the number of settings of networks and connection destinations in the destination NW device 20 as second summary information from the configuration data C2.

[0046] The extraction unit 431 extracts setting contents for each network function from the configuration data C2, and writes the extracted setting contents in the corresponding cells of the architecture data table 322 in a format corresponding to each network function. The confirmation device 40 uses the architecture data table 322 (second architecture data table) in the same format as the architecture data table 322 used by the conversion device 30.

[0047] 8, for example, the extraction unit 431 writes the ISP setting contents D2-1 for "interface port-subsc 1.1002" from the configuration data C2 into each cell W2-1 corresponding to this setting contents in the system data table T1 (see FIG. 5) (arrow Y2-1). Also, the extraction unit 431 writes the setting contents D2-2 for the function "Ipv6 access list multicast" provided to the user from the configuration data C2 into each cell W2-2 corresponding to this setting contents in the system data table T2 (see FIG. 6) (arrow Y2-2).

[0048] In this way, the extraction unit 431 extracts each setting content associated with each network function from the configuration data C2 and writes it in the corresponding cells of the system data tables T1 to T3, thereby creating system data tables T2-1, T2-2, and T2-3 in which the setting content of the configuration data C2 is written for each network function. The extraction unit 431 sets these system data tables T2-1, T2-2, and T2-3 as second summary information 422 as they are, or sets user information of a user who receives a predetermined service via the source NW device 10, unique information of the source NW device 10, and / or information summarizing the number of settings of networks and connection destinations in the source NW device as second summary information based on the system data tables T2-1, T2-2, and T2-3.

[0049] The collation unit 432 collates the first summary information 324 with the second summary information 422. As shown in Fig. 8, the architecture data tables T1-1, T1-2, and T1-3, which are the first summary information 324, and the architecture data tables T2-1, T2-2, and T2-3, which are the second summary information 422, are all architecture data tables in the same format, and the setting contents are described in each cell for each NW function. Therefore, the collation unit 432 collates the setting contents for each NW function by comparing the description contents of the cells at the same positions in the architecture data tables T1-1, T1-2, and T1-3 and the architecture data tables T2-1, T2-2, and T2-3 ((1) in Fig. 8).

[0050] For example, the collation unit 432 collates the setting contents described in cell W1-1 of the structure data table T1-1 with the setting contents described in cell W2-1 of the structure data table T2-1 ((2) in FIG. 8). The collation unit 432 also collates the setting contents described in cell W1-2 of the structure data table T1-2 with the setting contents described in cell W2-2 of the structure data table T2-2 ((3) in FIG. 8). Similarly, the collation unit 432 collates the setting contents of cells at the same position in the structure data tables T1-3 and T2-3 ((4) in FIG. 8). The collation unit 432 outputs the collation result to the determination unit 433.

[0051] The determination unit 433 determines, based on the first summary information 324 and the second summary information 422, whether or not the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally.

[0052] If the first summary information 324 and the second summary information 422 match based on the result of the comparison by the comparison unit 432, the determination unit 433 determines that the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally.

[0053] Specifically, when the contents of the system data tables T1-1, T1-2, and T1-3 that are the first summary information 324 match with the contents of the system data tables T2-1, T2-2, and T2-3 that are the second summary information 422, the determination unit 433 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 433 determines that the migration results of all items are "OK", as shown in the determination result E1 in FIG.

[0054] On the other hand, if the first summary information 324 and the second summary information 422 do not match, the determining unit 433 determines that the migration of the configuration data C1 to the migration destination NW device 20 has not been performed normally.

[0055] For example, when the setting contents described in cell W1-2 of system data table T1-1 and cell W2-2 of system data table T2-2 among system data tables T1-1, T1-2, T1-3 and system data tables T2-1, T2-2, T2-3 do not match, the determination unit 433 determines that the server identification number and address in the video viewing function of the configuration data C1 have not been successfully migrated to the migration destination NW device 20. In this case, the determination unit 433 determines the result of the determination regarding the migration of the server identification number and address in the video viewing function to be "NG".

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

[0057] 10, when migrating a configuration from a source NW device 10 to a destination NW device 20, first, the conversion device 30 receives pre-conversion configuration data C1 from the source NW device 10 (step S1). The conversion device 30 extracts setting contents for each network function from the configuration data C1 as first summary information (step S2).

[0058] The conversion device 30 converts the configuration data C1 into configuration data Ct that conforms to the configuration data system applied to the destination NW device 20 (step S3). Then, the conversion device 30 transmits the converted configuration data Ct to the destination NW device 20 (step S4) and applies the configuration data Ct to the destination NW device 20 (step S5). The conversion device 30 transmits the first summary information to the confirmation device 40 (step S6).

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

[0060] 11, 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 received the first summary information transmitted from the conversion device 30.

[0061] The confirmation device 40 extracts the setting contents for each network function as second summary information from the configuration data C2 (step S12). The confirmation device 40 compares the first summary information with the second summary information (step S13) and determines whether the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally (step S14).

[0062] [Effects of the embodiment] Thus, in the embodiment, the conversion device 30 extracts setting contents for each network function as first summary information from the configuration data C1 of the source NW device 10. Then, in the embodiment, the confirmation device 40 extracts setting contents for each network function as second summary information from the configuration data C2 applied to the destination NW device 20. In the embodiment, the confirmation device 40 determines whether the migration of the configuration data C1 to the destination NW device 20 has been performed normally based on the first summary information and the second summary information.

[0063] In this way, the confirmation device 40 judges whether the migration of the configuration data C1 to the migration destination NW device 20 has been performed normally by comparing the setting contents of the configuration data C1 and C2 on a network function basis. Since the configuration data C1 and the configuration data C2 are data for setting the operation of the NW devices, the confirmation device 40 can properly execute equivalence judgment between the configuration data C1 and the configuration data C2 by collating the setting contents for realizing the NW functions. Also, in the embodiment, it is not necessary to perform a full row comparison between the configuration data C1 and the configuration data C2, so that it is possible to efficiently execute whether the migration of the configuration data between the NW devices has been performed normally as compared to the case where a full row comparison is performed.

[0064] In this manner, in the embodiment, since the normality check of the configuration migration can be efficiently and appropriately executed, the normality check process of the configuration migration can be accelerated. Also, in the management system 100, the processing load of the normality check of the configuration migration can be reduced compared to the conventional method due to the improved efficiency of the normality check of the configuration migration.

[0065] The confirmation device 40 may compare the configuration data C2 applied to the destination NW device 20 with the first summary information 324 to determine whether the migration of the configuration data C1 to the destination NW device 20 has been performed normally. If the first summary information 324 matches the setting contents of the configuration data C2, the confirmation device 40 determines that the migration of the configuration data C1 to the destination NW device 20 has been performed normally. If the first summary information 324 does not match the setting contents of the configuration data C2, the confirmation device 40 determines that the migration of the configuration data C1 to the destination NW device 20 has not been performed normally. If the confirmation device 40 compares the first summary information 324 with the setting contents of the configuration data C2, it is not necessary to create the second summary information 422.

[0066] [System configuration of the embodiment] Each component of the conversion device 30 and the confirmation device 40 is a functional concept, and does not necessarily have 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 and the confirmation device 40 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.

[0067] Further, each process performed in the conversion device 30 and the confirmation device 40 may be realized, in whole or in part, by a CPU, a GPU (Graphics Processing Unit), and a program analyzed and executed by the CPU and the GPU. Further, each process performed in the conversion device 30 and the confirmation device 40 may be realized as hardware using wired logic.

[0068] 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 by a known method. In addition, the process procedures, control procedures, specific names, and information including various data and parameters described above and shown in the drawings can be changed as appropriate unless otherwise specified.

[0069] [program] 12 is a diagram showing an example of a computer in which a program is executed to realize the conversion device 30 and the verification device 40. 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.

[0070] 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 an 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.

[0071] 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 in 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).

[0072] 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 out program module 1093 or program data 1094 stored in memory 1010 or hard disk drive 1090 into RAM 1012 as necessary, and executes the program.

[0073] Note that the program module 1093 and the program data 1094 are not limited to being stored in the hard disk drive 1090, but may 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 the program data 1094 may be stored in another computer connected via a network (such as a local area network (LAN) or wide area network (WAN)). The program module 1093 and the program data 1094 may then be read by the CPU 1020 from the other computer via the network interface 1070.

[0074] Although the embodiment of the invention made by the present inventor has been described above, the present invention is not limited by the description and drawings that form a part of the disclosure of the present invention according to the present embodiment. In other words, other embodiments, examples, operation techniques, etc. made by those skilled in the art based on the present embodiment are all included in the scope of the present invention. [Explanation of symbols]

[0075] 10 Source Network Equipment 20 Destination Network Equipment 30 Conversion Device 31,41 Communications Department 32,42 Storage part 33,43 Control section 40 Verification device 100 Management Systems 331,431 Extraction part 332 Conversion unit 432 Collation Department 433 Judgment section

Claims

1. A management system for managing migration from a source network device to a destination network device, comprising: a first extracting unit that extracts setting contents for each network function as first summary information from first setting data that configures an operation of the migration source network device; a conversion unit that converts a system of first setting data that configures an operation of the source network device into second setting data that conforms to a system of setting data of the destination network device, and applies the second setting data to the destination network device; A conversion device having a determination unit that determines whether or not the migration of the first setting data to the migration destination network device has been performed normally, based on the first summary information and the third setting data applied to the migration destination network device; A verification device having A management system comprising:

2. The management system described in claim 1, characterized in that the first extraction unit extracts from the first setting data, as the first summary information, user information of a user who receives a specified service via the source network device, unique information of the source network device, and / or the number of network and connection destination settings in the source network device.

3. 3. The management system according to claim 1, wherein the determination unit determines that the migration of the first setting data to the destination network device is performed normally when the first summary information matches the setting contents of the third setting data, and determines that the migration of the first setting data to the destination network device is not performed normally when the first summary information does not match the setting contents of the third setting data.

4. The verification device includes: a second extraction unit that extracts, as second summary information from the third setting data, user information of a user who receives a predetermined service via the destination network device, specific information of the destination network device, and / or the number of settings of networks and connection destinations in the destination network device; 4. The management system according to claim 3, wherein the determination unit determines that the migration of the first setting data to the destination network device is performed normally when the first summary information and the second summary information match, and determines that the migration of the first setting data to the destination network device is not performed normally when the first summary information and the second summary information do not match.

5. the first extraction unit extracts setting contents for each of the network functions from the first setting data, and writes the extracted setting contents in corresponding cells of a first system data table in a format corresponding to each of the network functions; the second extraction unit extracts setting contents for each of the network functions from the third setting data, and writes the extracted setting contents in corresponding cells of a second architecture data table having the same format as the first architecture data table; The management system described in claim 4, characterized in that the determination unit determines whether the migration of the first setting data to the destination network device is being performed normally based on the contents of each cell of the first system data table and the contents of each cell of the second system data table.

6. A management method executed by a management system that has a conversion device and a confirmation device and manages migration from a source network device to a destination network device, comprising: extracting, by the conversion device, setting contents for each network function from first setting data that sets an operation of the migration source network device, as first summary information; a step of converting, by the conversion device, a first setting data system for configuring an operation of the source network device into second setting data conforming to a setting data system of the destination network device, and applying the second setting data to the destination network device; a step of determining, by the confirmation device, whether or not the migration of the first setting data to the migration destination network device has been performed normally based on the first summary information and the third setting data applied to the migration destination network device; A management method comprising the steps of:

7. A management program for causing a computer to execute the method, The computer as a conversion device extracting setting contents for each network function as first summary information from first setting data that sets the operation of the migration source network device; converting a first setting data system for setting an operation of the source network device into second setting data conforming to a setting data system of a destination network device, and applying the second setting data to the destination network device; Run the command, The computer as a verification device determining whether or not the migration of the first setting data to the destination network device has been performed normally based on the first summary information and the third setting data applied to the destination network device; A management program for causing the user to execute the above steps.

Images