Network setting management device and method

Abstract

To establish a plurality of paths in a network, and manage the usage statu of the network in a configuration in which a path is selected for each application.SOLUTION: A network setting management device includes a route management unit that manages, for each path, communication quality including a bandwidth of the path as route quality information and manages the path selected for each application as route selection information, a traffic prediction unit that predicts the traffic volume for each application, predicts a selected route for each application on the basis of the route selection information, and predicts the traffic volume for each path on the basis of the predicted traffic volume and the predicted selected route, and a setting evaluation unit that determines whether there is a path whose traffic volume exceeds the bandwidth on the basis of the traffic volume and route quality information for each path.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to techniques for managing network usage by applications. [Background technology]

[0002] Digital transformation (DX) is expanding the use of IT (Information Technology) services from a single location to multiple locations via a wide area network (WAN) and anywhere via the cloud. Accordingly, the routes used by applications are being flexibly configured using software-defined networking (SDN).

[0003] There is a demand for managing whether the use of the network by the application is appropriate (see Patent Document 1).

[0004] Patent Document 1 discloses a technology that collects information necessary for quality control, such as traffic volume, from edge routers in a corporate network, predicts future traffic trends and future operational status trends, and notifies users of the prediction results. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2003-69644 A Summary of the Invention [Problem to be solved by the invention]

[0006] However, Patent Document 1 does not take into consideration the management of network usage status in a configuration (SD-WAN) in which multiple routes are established within a WAN network using SDN technology and a route is selected for each application.

[0007] One object of the present disclosure is to provide a technique that enables management of the usage state of a network in a configuration in which multiple routes are established within a network and a route is selected for each application. [Means for solving the problem]

[0008] A network setting management device according to one aspect of the present disclosure has a processor and a storage device, and the processor executes a software program stored in the storage device, and the network setting management device has a route management unit that manages communication quality including the bandwidth of each route as route quality information and manages the route selected for each application as route selection information, which are realized by the processor executing the software program, a traffic prediction unit that predicts the traffic volume for each application, predicts the selected route for each application based on the route selection information, and predicts the traffic volume for each route based on the predicted traffic volume and the predicted selected route, and a setting evaluation unit that determines whether there is a route whose traffic volume exceeds the bandwidth based on the traffic volume for each route and the route quality information.

[0009] A network configuration management method according to one aspect of the present disclosure is a network configuration management method realized by a computer having a processor and a storage device, in which the processor reads and executes a software program stored in the storage device, and the method manages communication quality including the bandwidth of each route as route quality information, manages a route selected for each application as route selection information, predicts traffic volume for each application, predicts a selected route for each application based on the route selection information, predicts traffic volume for each route based on the predicted traffic volume and the predicted selected route, and determines whether there is a route for which the traffic volume exceeds the bandwidth based on the traffic volume for each route and the route quality information. Effect of the Invention

[0010] According to one aspect of the present disclosure, it is possible to establish multiple routes within a network and manage the usage status of the network in a configuration in which a route is selected for each application. [Brief description of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating an example of a network configuration to which a network setting management device according to an embodiment of the present invention is applied; [Diagram 2] 2 is a block diagram showing a functional configuration of the network setting management device shown in FIG. 1. [Diagram 3] 2 is a block diagram showing a hardware configuration of the network setting management device shown in FIG. 1. [Figure 4] 3 is a diagram showing an example of application information managed as an input table in a path management unit shown in FIG. 2; [Diagram 5] 3A and 3B are diagrams showing an example of route information managed as an input table in the route management unit shown in FIG. 2, where (a) is a diagram showing a traffic table for each route, (b) is a diagram showing a route quality table, and (c) is a diagram showing a quality monitoring table for each route. [Figure 6] 3 is a diagram showing an example of result policy information managed as an input table in a path management unit shown in FIG. 2; FIG. [Figure 7] 2 is a flowchart for explaining a network setting management method in the network setting management device shown in FIG. 1. [Figure 8] 3A and 3B are diagrams showing intermediate information created by the traffic prediction unit shown in FIG. 2, in which FIG. 3A shows a traffic prediction table for each application, and FIG. 3B shows a traffic prediction table for each path. [Figure 9] 3 is a flowchart for explaining details of a band determination process in a setting evaluation unit shown in FIG. 2. [Figure 10] 3 is a diagram showing a table including information indicating a path state determined by a setting evaluation unit shown in FIG. 2. FIG. [Figure 11] 3 is a flowchart for illustrating details of an alternative route determination process in a setting evaluation unit shown in FIG. 2. [Figure 12] 3 is a flowchart for explaining details of a route determination process after switching in a setting evaluation unit shown in FIG. 2; [Figure 13] 3 is a flowchart illustrating details of a route selection policy change direction search process in a setting evaluation unit illustrated in FIG. 2. [Figure 14] 3 is a diagram showing a route selection policy evaluation table created in a route selection policy change direction search process in a setting evaluation unit shown in FIG. 2; FIG. [Figure 15] 3 is a flowchart for explaining a process in which a setting evaluation unit shown in FIG. 2 determines whether or not there is an unused route among routes managed by a route management unit. [Figure 16] 3 is a diagram showing an unused route determination table created by a setting evaluation unit shown in FIG. 2; FIG. [Figure 17] 4 is a diagram showing a route status screen displayed on the display device shown in FIG. 3. FIG. [Figure 18] 18 is a diagram showing a screen displayed on a display device when a details confirmation button is pressed on the route status screen shown in FIG. 17. FIG. [Figure 19] 19 is a diagram showing a screen displayed on a display device when a details confirmation button is pressed on the route status screen shown in FIG. 18. FIG. [Figure 20] 3 is a diagram showing a screen for notifying unused routes among the routes managed by the route management unit shown in FIG. 2. FIG. [Figure 21] FIG. 13 is a diagram showing a screen displayed on the display device when an application is changed. [Figure 22] 13 is a flowchart illustrating a process for proposing a change to a route selection policy that results in an alternative route in the network configuration management device shown in FIG. 1 by presenting the number of times the policy was selected and the number of times a failure occurred among the number of times the policy was selected. [Diagram 23] FIG. 23 is a diagram showing a table created by the processing shown in FIG. 22. [Figure 24] FIG. 24 is a diagram showing a routing policy change proposal screen that reflects the contents of the output table shown in FIG. 23. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0013] FIG. 1 is a diagram showing an example of a network configuration to which a network setting management device of the present invention is applied, and shows how applications are used.

[0014] 1, the network configuration of this example is configured so that a base network 11 can be connected to a data center or other base network 12 via a WAN 13, and a route 14 established on the WAN 13 by a network device 16 between the base network 11 and the data center or other base network 12 is managed by a network setting management device 15. The network setting management device 15 may be provided for each base network, or may be provided for a specific base network and manage the routes 14 between the network devices 15 of all base networks.

[0015] In a network configuration configured in this manner, a user (not shown) within the base network 11 is a user who uses multiple applications (not shown), and to process each application, the user uses data from a data center or other base network 12 via a route 14 managed by a network setting management device 15.

[0016] FIG. 2 is a block diagram showing a functional configuration of the network setting management device 15 shown in FIG.

[0017] As shown in FIG. 2, the network setting management device 15 shown in FIG. 1 has, as its functions, a route management unit 21, a traffic prediction unit 22, and a setting evaluation unit 23.

[0018] The route management unit 21 manages the communication quality including the bandwidth of each route 14 as route quality information, and also manages the route selected for each application transmitted from within the base network 11 as route selection information.

[0019] The traffic prediction unit 22 predicts the traffic volume for each application transmitted from within the base network 11, predicts the selected route for each application based on the route selection information managed by the route management unit 21, and predicts the traffic volume for each route based on the predicted traffic volume and the predicted selected route.

[0020] The setting evaluation unit 23 determines, based on the traffic volume for each route predicted by the traffic prediction unit 22 and the route quality information managed by the route management unit 21, whether or not there is a route whose traffic volume exceeds the bandwidth.

[0021] FIG. 3 is a block diagram showing a hardware configuration of the network setting management device 15 shown in FIG.

[0022] The hardware configuration of the network setting management device 15 shown in FIG. 1 is, as shown in FIG. 3, a processor 31, a main memory 32, a memory capacity 33, a communication device 34, an input device 35, and a display device 36 connected via a bus 37.

[0023] The processor 31 executes software programs read from the storage device 33 to the main memory 32 to realize the functions shown in FIG.

[0024] The communication device 34 is for connecting to the network device 16 .

[0025] The input device 35 is for inputting information into various tables set in the storage device 33 .

[0026] The display device 36 displays and outputs the results of execution by the processor 31.

[0027] A network setting management method in the network setting management device 15 configured as above will be described below.

[0028] First, the information stored in the storage device 33 and managed as an input table by the route management unit 21 will be described.

[0029] Fig. 4 is a diagram showing an example of application information managed as an input table by the path management unit 21 shown in Fig. 2. The application information includes an application table, a traffic table for each application, a path selection policy table, and a path table for each application.

[0030] The application information managed as an application table serving as the input table 1 in the route management unit 21 shown in Fig. 2 includes source and destination IP address and port number information, as well as the communication protocol used, for each application traffic transmitted from the base network 11, as shown in Fig. 4. This information is acquired from the network device 16 shown in Fig. 1.

[0031] As shown in Fig. 4, application information managed as a traffic table for each application, which is input table 2 in route management unit 21 shown in Fig. 2, includes past usage times and actual measured values ​​of traffic volume at that time for each application traffic transmitted from base network 11. Note that these actual measured values ​​are measured and recorded by network device 16 shown in Fig. 1 at regular time intervals.

[0032] The application information managed as a route selection policy table serving as the input table 3 in the route management unit 21 shown in Fig. 2 is a route selection policy that specifies the conditions required for a route, such as the transfer time conditions and the packet loss rate conditions to be satisfied, for each application traffic transmitted from the base network 11, as shown in Fig. 4. This information is acquired from the network device 16 shown in Fig. 1.

[0033] The application information managed as a route table for each application, which becomes the input table 4 in the route management unit 21 shown in Fig. 2, is managed as route selection information, as shown in Fig. 4, for each application traffic transmitted from the base network 11, including the past usage time and the route used at that time. Note that this route is measured and recorded by the network device 16 shown in Fig. 1 at regular time intervals.

[0034] Fig. 5 is a diagram showing an example of route information managed as an input table by the route management unit 21 shown in Fig. 2. The route information includes a traffic table for each route, a route quality table, and a quality monitoring table for each route.

[0035] As shown in Fig. 5, the route information managed as a traffic table for each route, which becomes the input table 5 in the route management unit 21 shown in Fig. 2, records the past usage time and the actual measured value of the traffic volume at that time for each route 14. Note that this actual measured value is measured and recorded by the network device 16 shown in Fig. 1 at regular intervals.

[0036] The route information managed as a route quality table serving as input table 6 in route management unit 21 shown in Fig. 2 is managed as route quality information for each route 14, as shown in Fig. 5. The bandwidth and line type are determined at the time of contract. The transfer time and packet loss rate are actual measured values ​​obtained by measuring from network device 16 shown in Fig. 1 at regular intervals.

[0037] As shown in Fig. 5, the route information managed as a quality monitoring table for each route, which becomes the input table 7 in the route management unit 21 shown in Fig. 2, manages a bandwidth usage rate threshold and a packet loss rate threshold for each route 14. These thresholds are used to determine whether the traffic volume will be exceeded in the route determination described below, and are set in advance by, for example, a network administrator.

[0038] Fig. 6 is a diagram showing an example of track record policy information managed as an input table by the path management unit 21 shown in Fig. 2. The track record policy information includes a different environment policy table.

[0039] The other environment policy table, which serves as the input table 8 in the route management unit 21 shown in Figure 2, manages the past proven transfer times and packet loss rates as performance policies for application traffic sent from the base network 11 to a data center or other base network 12, as shown in Figure 6.

[0040] FIG. 7 is a flowchart for explaining a network setting management method in network setting management device 15 shown in FIG.

[0041] First, the traffic prediction unit 22 refers to the input table 2 shown in FIG. 4, and predicts the traffic volume for each application using, for example, a prediction model generated based on past history (step S101).

[0042] Next, the traffic prediction unit 22 refers to the input table 4 shown in FIG. 4 and acquires a route for each application (step S102).

[0043] Next, the traffic prediction unit 22 aggregates the traffic volume for each application predicted in step S101 for each route acquired in step S102 (step S103).

[0044] Fig. 8 is a diagram showing intermediate information created by the traffic prediction unit 22 shown in Fig. 2. The intermediate information includes a traffic prediction table for each application and a traffic prediction table for each path.

[0045] Based on the traffic volume predicted in step S101, an intermediate table 1 is created in which the traffic volume at a predetermined time is predicted for each application, as shown in FIG.

[0046] Based on the traffic volumes collected in step 103, an intermediate table 2 is created in which the traffic volumes at a given time are predicted for each path, as shown in FIG.

[0047] Next, the setting evaluation unit 23 determines whether or not there is a route whose traffic volume exceeds the bandwidth, based on the traffic volume for each route and the route quality information (step S104).

[0048] FIG. 9 is a flowchart for explaining the details of the band determination process in the setting evaluation unit 23 shown in FIG.

[0049] First, the setting evaluation unit 23 reads one path number from the input table 6 shown in FIG. 5 (step S201).

[0050] Next, the setting evaluation unit 23 obtains the bandwidth from the input table 6 for the route corresponding to the route number read in step S201, obtains the threshold value from the input table 7 shown in Figure 5, and obtains the time and traffic volume from the intermediate table 2 shown in Figure 8 (step S202).

[0051] Next, the setting evaluation unit 23 judges whether the ratio of the traffic volume to the bandwidth exceeds the bandwidth usage rate threshold value (step S203).

[0052] If the ratio of the traffic volume to the bandwidth does not exceed the bandwidth usage threshold, a False flag is set (step S204), and if the ratio of the traffic volume to the bandwidth exceeds the bandwidth usage threshold, a True flag is set (step S205).

[0053] After that, the process returns to step S201 (step S206), and this series of processes is performed for all the routes managed in the input table 6.

[0054] FIG. 10 is a diagram showing a table including information indicating the path state determined by the setting evaluation unit 23 shown in FIG.

[0055] The setting evaluation unit 23 judges the route state by the process shown in FIG. 9, and creates and manages the route state at a predetermined time for each route as an output table 1 indicated as the above-mentioned flag, as shown in FIG.

[0056] As a result, if there is a route whose traffic volume exceeds the bandwidth, the setting evaluation unit 23 identifies the application that selects that route as an application to be subject to route change (step S105), and determines whether there is an application that does not have an alternative route (step S106).

[0057] If there is no application without an alternative route, the application is notified of a route change (step S107), and if there is an application without an alternative route, a proposal is made to relax the route selection policy of the application (step S108).

[0058] FIG. 11 is a flowchart for explaining details of the alternative route determination process in the setting evaluation unit 23 shown in FIG.

[0059] First, the setting evaluation unit 23 reads one application name from the input table 1 shown in FIG. 4 (step S301).

[0060] Next, the setting evaluation unit 23 acquires a route along which the application having the application name read in step S301 is transferred from the input table 1 shown in FIG. 4 (step S302).

[0061] Next, the setting evaluation unit 23 refers to the threshold excess flag of the route acquired in step S302 from the output table 1 shown in FIG. 10 (step S303).

[0062] Then, the setting evaluation unit 23 determines whether or not there is a time when the threshold excess flag is True (step S304), and if there is no time when the threshold excess flag is True, it clears the response know-how / mitigation possible flag (step S305).

[0063] On the other hand, if there is a time when the threshold excess flag is True, the setting evaluation unit 23 performs a judgment on the route after switching (step S306).

[0064] FIG. 12 is a flowchart for explaining details of the route determination process after switching in the setting evaluation unit 23 shown in FIG.

[0065] First, the setting evaluation unit 23 reads one application name that matches the route acquired in step S302 from the input table 4 shown in FIG. 4 (step S401).

[0066] Next, the setting evaluation unit 23 acquires the maximum value of the predicted traffic of the application whose application name was read in step S401 from the intermediate table 1 shown in FIG. 8 (step S402).

[0067] Next, the setting evaluation unit 23 acquires the quality of a route candidate different from the route acquired in step S302 from the input table 6 shown in FIG. 5 (step S403).

[0068] Next, the setting evaluation unit 23 refers to the input table 3 shown in FIG. 4, and compares the remaining bandwidth of a route among the above route candidates that satisfies the transfer time condition and packet loss rate condition of the route selection policy for the application whose application name was read in step S401 with the maximum predicted traffic of the application (step S404), and determines whether or not there is a route candidate that satisfies the transfer time condition and packet loss rate condition and has a remaining bandwidth that is equal to or greater than the maximum traffic value (step S405).

[0069] If there is a route candidate that satisfies the transfer time condition and the packet loss rate condition and has a remaining bandwidth equal to or greater than the maximum traffic value, a False flag is set as the no alternative route prediction flag (step S406).

[0070] On the other hand, if there is no route candidate that satisfies the transfer time condition and the packet loss rate condition and has a remaining bandwidth equal to or greater than the maximum traffic value, a True flag is set as the no alternative route prediction flag (step S407).

[0071] The setting evaluation unit 23 repeats the process in steps S403 to S407 for each of the route candidates.

[0072] After that, the process returns to step S401 (step S408), and this series of processes is performed for all applications managed in the input table 4.

[0073] In the above example, the presence or absence of an alternative route is determined using the maximum value of the predicted traffic of the application whose application name was read in step S401, but other methods are also possible. For example, the variance of the predicted traffic of the application whose application name was read in step S401 may be calculated, and if the variance is equal to or less than a predetermined threshold, the maximum value of the traffic volume of the application may be compared with the remaining bandwidth of the route, and if the variance exceeds the threshold, the average value of the traffic volume of the application may be compared with the remaining bandwidth of the route.

[0074] Then, the setting evaluation unit 23 determines whether or not the True flag is set as the no alternative route prediction flag (step S307), and if the True flag is not set as the no alternative route prediction flag, proceeds to the processing in step S305 and clears the response know-how / mitigation possible flag.

[0075] On the other hand, if the True flag is set as the no alternative route prediction flag, the setting evaluation unit 23 performs a route selection policy change direction search process (step S308).

[0076] Then, the process returns to step S301 (step S309), and this series of processes is performed for all applications managed in the input table 1.

[0077] FIG. 13 is a flowchart for explaining the details of the route selection policy change direction search process in the setting evaluation unit 23 shown in FIG.

[0078] First, the setting evaluation unit 23 searches the input table 8 shown in FIG. 6 for a row of the application name read in step S301 (step S501).

[0079] Then, if there is a row with the application name read in step S301 in input table 8 shown in FIG. 6 (step S502), one of the rows is extracted (step S503).

[0080] Next, the setting evaluation unit 23 performs the post-switching route determination process shown in FIG. 12 using the transfer time and packet loss rate of the extracted row (step S504).

[0081] If the True flag is set as the no alternative path prediction flag (step S505), the process returns to step S503 (step S506), and another row for the application name read in step S301 is extracted.

[0082] On the other hand, if the no alternative route prediction flag is not set to True, the setting evaluation unit 23 sets the mitigation possible flag to True (step S507), and sets the corresponding ID value in the input table 8 to the response know-how (step S508).

[0083] FIG. 14 is a diagram showing a route selection policy evaluation table created in the route selection policy change direction search process in the setting evaluation unit 23 shown in FIG.

[0084] By the above-mentioned route selection policy change policy search process, as shown in FIG. 14, for each application traffic transmitted from the base network 11, a route selection policy evaluation table is created as output table 2 in which a no alternative route prediction flag indicating whether or not there is an alternative route, a corresponding know-how ID, and a relaxation possible flag indicating whether or not the policy can be relaxed are set for the transfer time condition and packet loss rate condition in input table 3 shown in FIG. 4.

[0085] In addition, if there is no row for the application name loaded in step S301 in the input table 8 shown in FIG. 6, or if processing has been completed for all rows of the application names loaded in step S301, the response know-how and mitigation possible flag are cleared (step S509).

[0086] In this way, the route management unit 21 further manages the requirements for the route for each application as a route selection policy, and if there is a route for which the traffic volume exceeds the bandwidth, the setting evaluation unit 23 identifies the application that selects that route based on the route selection information as an application to be subject to route change, and determines whether or not there is an alternative route that can be used as an alternative to the route selected by the application to be subject to route change without changing the route selection policy of the application to be subject to route change, based on the route selection policy, route quality information, and the predicted traffic volume for each route. This makes it possible to know whether or not the route selection policy of the application to be subject to route change should be changed.

[0087] As described above, in this embodiment, a plurality of routes are set within a network, and the usage state of the network can be managed in a configuration in which a route is selected for each application.

[0088] Here, the setting evaluation unit 23 determines whether or not there is an unused route among the routes managed by the route management unit 21, and if an unused route exists, it can also notify the route as an unused route.

[0089] FIG. 15 is a flowchart for explaining a process in which the setting evaluation unit 23 shown in FIG. 2 determines whether or not there is an unused route among the routes managed by the route management unit 21. In FIG.

[0090] First, the setting evaluation unit 23 reads one path number from the input table 6 shown in FIG. 5 (step S601).

[0091] Next, the setting evaluation unit 23 calculates the number of applications that use the route read in step S601 from the input table 4 shown in FIG. 5 (step S602).

[0092] If the number of applications in use is "0" (step S603), a True flag is set as an unused flag (step S604).

[0093] On the other hand, if the number of applications in use exceeds "0", a False flag is set as an unused flag (step S605).

[0094] Then, the process returns to step S601 (step S606), and this series of processes is performed for all the routes managed in the input table 6.

[0095] FIG. 16 is a diagram showing an unused route determination table created by the setting evaluation unit 23 shown in FIG.

[0096] By the series of processes shown in Figure 15, an unused route determination table is created as output table 3, as shown in Figure 16, in which an unused flag is set for each route managed by the route management unit 21, indicating whether it is unused or not.

[0097] The notification of the above-mentioned processing result will be described below. The above-mentioned processing result is displayed on the display device 36 of the network setting management device 15 shown in FIG.

[0098] FIG. 17 is a diagram showing a route status screen displayed on the display device 36 shown in FIG.

[0099] As shown in Figure 17, the setting evaluation unit 23 displays the items of the input table 6 shown in Figure 5 for each of the routes managed by the route management unit 21, and refers to the output table 1 shown in Figure 10, and highlights by shading the routes for which a True flag has been set as the threshold exceedance flag determined in the processing shown in Figure 9.

[0100] A details confirmation button 41 is displayed on the route status screen displayed on the display device 36, and by pressing the details confirmation button 41, the details of the route that has been shaded are displayed.

[0101] FIG. 18 is a diagram showing a screen displayed on the display device 36 when the details confirmation button 41 is pressed on the route status screen shown in FIG.

[0102] When the detail confirmation button 41 is pressed on the route status screen shown in Fig. 17, the setting evaluation unit 23 refers to the input table 4 shown in Fig. 4 and the intermediate table 1 shown in Fig. 8, and displays a maximum value as a maximum traffic prediction for applications that match routes that are displayed with shading on the route status screen, as shown in Fig. 18. In addition, for alternative routes, the output table 2 shown in Fig. 14 is referenced, and if a True flag is set as the no alternative route prediction flag, "none" is displayed, and if a False flag is set, "yes" is displayed. In addition, applications that do not have an alternative route are highlighted by shading.

[0103] A confirmation details button 42 is displayed on the screen displayed on the display device 36, and by pressing the confirmation details button 42, a screen is displayed that proposes changing the policy for the application that has been shaded.

[0104] FIG. 19 is a diagram showing a screen displayed on the display device 36 when the details confirmation button 42 is pressed on the route status screen shown in FIG.

[0105] When the detail confirmation button 42 is pressed on the screen shown in FIG. 18, the setting evaluation unit 23 extracts the quality and bandwidth of the route displayed on the screen shown in FIG. 17 from the input table 6 shown in FIG. 5, extracts the policy of the application displayed in a shaded manner on the screen shown in FIG. 17 from the input table 3 shown in FIG. 4, and extracts a policy that has a proven track record in other environments for the application displayed in a shaded manner on the screen shown in FIG. 17 from the input table 8 shown in FIG. 6, and displays the current transfer time and packet loss rate, and the transfer time and packet loss rate proposed to be changed in a shaded manner as a change proposal. Also, the result of searching for a route using the proposed route selection policy is displayed. At this time, if there are multiple change proposals, each of them is displayed. Also, a policy change button 43 to be pressed when changing a policy is displayed.

[0106] In this way, the route management unit 21 further manages, for each application, route selection policies that have a proven track record in other environments by the same application, and when there is no alternative route for the application that is the target of a route change, the setting evaluation unit 23 proposes changing the route selection policy of the application that is the target of a route change to one of the proven policies. This makes it possible to know whether the route selection policy of the application that is the target of a route change should be changed.

[0107] Furthermore, in such a configuration, when there is no alternative route for the application targeted for route change, the setting evaluation unit 23 proposes changing the route selection policy of the application targeted for route change to a route selection policy that is included in the proven policy and that produces an alternative route to replace the selected route of the application targeted for route change. This proposes changing to a proven route selection policy for the application targeted for route change for which there is no alternative route under the current route selection policy, and by changing to a proven route selection policy, it becomes possible to safely suppress the traffic volume from exceeding the bandwidth.

[0108] FIG. 20 is a diagram showing a screen for notifying unused routes among the routes managed by the route management unit 21 shown in FIG.

[0109] As described above, it is determined whether each of the routes managed by the route management unit 21 is unused or not, so the setting evaluation unit 23 refers to the output table 3 shown in FIG. 16, and displays on the display device 36 the bandwidth, bandwidth type, transfer time, and loss rate for routes for which a True flag is set as the unused flag.

[0110] In this way, when an unused route exists among the routes managed by the route management unit 21, the setting evaluation unit 23 notifies the route as an unused route. This makes it possible to select an unused route and to effectively utilize routes.

[0111] FIG. 21 is a diagram showing a screen displayed on the display device 36 when the application is changed.

[0112] The setting evaluation unit 23 compares the route of each application traffic transmitted from the base network 11 with the route shown in the input table 4 shown in Fig. 4, and if there is an application whose route has been changed, extracts the quality and bandwidth of the corresponding route from the input table 6 shown in Fig. 5 and displays them as route information, as shown in Fig. 21. The setting evaluation unit 23 also extracts applications of the same route from the input table 4 shown in Fig. 4, extracts the maximum value of the predicted traffic of the application from the intermediate table 1 shown in Fig. 8, combines them, and displays them.

[0113] (Other embodiments) In the above-described embodiment, it is also conceivable that for a route selection policy that results in an alternative route, the number of times it was selected and the number of times a failure occurred among the number of times it was selected are presented to suggest a change.

[0114] FIG. 22 is a flowchart illustrating a process for proposing a change in a route selection policy that results in an alternative route in network setting management device 15 shown in FIG. 1 by presenting the number of times the policy was selected and the number of times a failure occurred among the number of times the policy was selected.

[0115] First, the setting evaluation unit 23 reads one path number from the input table 6 shown in FIG. 5 (step S701).

[0116] Next, the setting evaluation unit 23 refers to the input table 4 shown in FIG. 5, and extracts the application that was used at the latest time for each path (step S702).

[0117] Next, the setting evaluation unit 23 refers to the input table 4 shown in FIG. 5 and determines whether or not the application extracted in step S702 has the same route as the previous time (step S703).

[0118] If the route for the application extracted in step S702 was not the same as the previous route, an external error log is referenced to determine whether or not a failure occurred on the previous route (step S704).

[0119] If a fault has occurred on the previous route, the number of troubles on that route is incremented by one (step S705).

[0120] In addition, the number of times that the route has been selected is incremented by one (step S706).

[0121] Next, the process returns to step S702 (step S707), and the processes of steps S702 to S706 are performed for each application.

[0122] If the application extracted in step S702 is on the same route as the previous time, the processes in steps S704 and S705 are not performed. Also, if no failure has occurred on the previous route, the process in step S705 is not performed.

[0123] Then, the process returns to step S701 (step S708), and this series of processes is performed for all the routes managed in the input table 6.

[0124] FIG. 23 is a diagram showing the table created by the process shown in FIG.

[0125] As shown in FIG. 23, the process shown in FIG. 22 creates an output table 4 in which the number of times the route was selected and the number of times a problem occurred are added to the input table 8 shown in FIG. 6.

[0126] The output table 4 thus created is managed by the route management unit 21. As a result, the route management unit 21 manages the number of times that the performance policy based on the input table 8 shown in Fig. 6 was selected and the number of times that a failure occurred during the selection.

[0127] FIG. 24 is a diagram showing a routing policy change proposal screen that reflects the contents of the output table 4 shown in FIG.

[0128] When reflecting the contents of the output table 4 shown in FIG. 23, the setting evaluation unit 23 extracts the quality and bandwidth of the route displayed on the screen shown in FIG. 17 from the input table 6 shown in FIG. 5, extracts the policy of the application displayed in a shaded manner on the screen shown in FIG. 17 from the input table 3 shown in FIG. 4, and extracts the policy of the corresponding application from the output table 4 shown in FIG. 23, and displays the current transfer time and packet loss rate, the transfer time and packet loss rate proposed to be changed, the number of selections, and the number of past troubles in a shaded manner as change proposals. Also, the result of searching for a route using the proposed route selection policy is displayed. At this time, if there are multiple change proposals, each of them is displayed. Also, a policy change button 44 to be pressed when changing the policy is displayed.

[0129] In this way, when there is no alternative route for the application to be changed, the setting evaluation unit 23 proposes a change to the route selection policy of the application to be changed by presenting the number of times the policy was selected and the number of times a failure occurred among the number of times the policy was selected for the route selection policy that is included in the proven policy and has an alternative route to substitute for the selected route of the application to be changed. This makes it possible to safely prevent the traffic volume from exceeding the bandwidth by checking the number of times a proven route selection policy was selected and the number of times a failure occurred among the number of times the policy was selected.

[0130] The above-described embodiments of the present invention are merely illustrative examples of the present invention, and are not intended to limit the scope of the present invention to these embodiments. Those skilled in the art can implement the present invention in various other forms without departing from the scope of the present invention. [Explanation of symbols]

[0131] 11...base network, 12...data center or other base network, 13...WAN, 14...route, 15...network setting management device, 16...network device, 21...route management unit, 22...traffic prediction unit, 23...setting evaluation unit, 31...processor, 32...main memory, 33...storage device, 34...communication device, 35...input device, 36...display device, 37...bus

Claims

1. A network configuration management device having a processor and a storage device, the processor executing a software program stored in the storage device, The processor executes the software program, a route management unit that manages communication quality including the bandwidth of each route as route quality information, manages a route selected for each application as route selection information, further manages requirements for the route for each application as a route selection policy, and further manages a route selection policy that has a proven track record in other environments by the same application for each application as a track record policy; a traffic prediction unit that predicts a traffic volume for each of the applications, predicts a selected route for each of the applications based on the route selection information, and predicts a traffic volume for each of the routes based on the predicted traffic volume and the predicted selected route; a setting evaluation unit that determines whether or not there is a route whose traffic volume exceeds a bandwidth based on the traffic volume for each route and the route quality information, and if there is a route whose traffic volume exceeds a bandwidth, identifies an application that selects the route based on the route selection information as an application that is a target for route change, and determines whether or not there is an alternative route that can be used as an alternative to the route selected by the application that is a target for route change without changing the route selection policy of the application that is a target for route change based on the route selection policy, the route quality information, and the predicted traffic volume for each route, and when there is no alternative route for the application that is a target for route change, proposes changing the route selection policy of the application that is a target for route change to one of the performance policies; A network configuration management device having the above configuration.

2. the setting evaluation unit, when there is no alternative route for the application to be subject to route change, proposes changing the route selection policy of the application to be subject to route change to a route selection policy that is included in the performance policy and that generates an alternative route that is an alternative to the selected route of the application to be subject to route change.

2. The network configuration management device according to claim 1.

3. The path management unit further manages, for the performance policy, the number of times the performance policy has been selected and the number of times a failure has occurred among the number of times the performance policy has been selected; when there is no alternative route for the application to be changed, the setting evaluation unit proposes a change to a route selection policy for the application to be changed, the route selection policy being included in the performance policy and producing an alternative route to be an alternative to the selected route for the application to be changed, by presenting the number of times the policy was selected and the number of times a failure occurred among the number of times the policy was selected; The network configuration management device according to claim 2.

4. A network configuration management method implemented by a computer having a processor and a storage device, the computer reading and executing a software program stored in the storage device by the processor, comprising: managing, for each route, communication quality including the bandwidth of the route as route quality information, managing a route selected for each application as route selection information, managing requirements for the route for each application as a route selection policy, and managing, for each application, a route selection policy that has a proven track record in other environments by the same application as a track record policy; predicting a traffic volume for each of the applications, predicting a selected route for each of the applications based on the route selection information, and predicting a traffic volume for each of the routes based on the predicted traffic volume and the predicted selected route; determining whether or not there is a route whose traffic volume exceeds a bandwidth based on the traffic volume for each route and the route quality information; If there is a route where the traffic volume exceeds the bandwidth, an application that selects the route is identified as an application to be changed based on the route selection information; determining whether or not there is an alternative route that can be used as an alternative to the selected route of the application to be route-changed without changing the route selection policy of the application to be route-changed, based on the route selection policy, the route quality information, and the predicted traffic volume for each route; When there is no alternative route for the application to be route-changed, it is proposed to change the route selection policy of the application to be route-changed to one of the performance policies. How to manage your network settings.

Images