Management device, management method, and management program
By using separate registration and output tables for flow information management, the device resolves performance issues in network monitoring by avoiding conflicts and optimizing processing loads, ensuring efficient xFlow packet output.
Patent Information
- Application Number
- JP2022581157
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-02-15
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2041-02-15
AI Technical Summary
Conventional network monitoring technologies face performance degradation due to conflicts between flow information registration/update processing and deletion processing, especially when the number of input encapsulated packets increases rapidly, leading to contention and performance drops.
The management device employs two separate flow statistical information cache tables - a registration table and an output table - to manage flow information, switching between them based on predetermined conditions to avoid conflicts and optimize processing.
This approach prevents performance degradation by eliminating conflicts between registration/update and deletion processing, reduces processing load, and maintains efficient output timing of xFlow packets.
Smart Images

Figure 0007582346000001 
Figure 0007582346000002 
Figure 0007582346000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a management device, a management method, and a management program. [Background technology]
[0002] There is xFlow technology, which samples packets and transfers statistical information calculated from header information or the header portion itself (header sample) to monitor networks and analyze traffic trends, and then tabulates and analyzes traffic. This xFlow technology adds up the statistical information in the inner header of encapsulated packets for each flow, registers it in a flow statistics cache table, monitors whether the output conditions are met for each flow, and generates and outputs xFlow packets that include the added up statistical information in the inner header for flows that meet the output conditions. [Prior art documents] [Non-patent literature]
[0003] [Non-Patent Document 1] Yuki Miyoshi et al., “Header sample format conversion method in xFlow packets”, Institute of Electronics, Information and Communication Engineers, March 2020, General Conference B-6-36. Summary of the Invention [Problem to be solved by the invention]
[0004] However, in conventional technology, the flow information registration / update process and the output flow information deletion process are performed in the same flow statistics information cache table, which causes a performance degradation problem due to contention between the flow information registration / update process and the deletion process.In particular, when the number of input encapsulated packets or encapsulated packet header samples increases rapidly, the flow information registration / update process increases accordingly, which causes an increase in contention and a significant degradation in performance.
[0005] The present invention has been made in consideration of the above, and aims to provide a management device, a management method, and a management program that can avoid performance degradation due to contention between flow information registration / update and deletion processes. [Means for solving the problem]
[0006] In order to solve the above-mentioned problems and achieve the object, the management device of the present invention is characterized by having: a memory unit that stores two tables, which are flow statistics information cache tables; a management unit that divides the two tables into a registration table and an output table and manages information including at least statistical information on the inner header of each flow, which is flow information; a management unit that performs a table change process that switches between the registration table and the output table when a specified change condition is met, and instructs the output of an xFlow packet including at least the statistical information of the inner header recorded in the output table; a registration unit that generates statistical information on the inner header from an encapsulated packet or a header sample of an encapsulated packet that has been received as input, and registers or updates the generated statistical information of the inner header in the registration table; and an output unit that receives instructions from the management unit, generates an xFlow packet for each flow based on the data in the output table, and outputs it to an output destination.
[0007] The management device according to the present invention is characterized in having: a memory unit that stores two tables, which are flow statistics information cache tables; a management unit that divides the two tables into a registration table and an output table, and manages information including at least statistical information on the inner header of each flow, which is flow information; a management unit that performs a table change process to transfer data from the registration table to the output table when a specified change condition is met, and instructs the output of xFlow packets including at least the statistical information of the inner header recorded in the output table; a registration unit that generates statistical information on the inner header from encapsulated packets or header samples of encapsulated packets that have been received as input, and registers or updates the generated statistical information of the inner header in the registration table; and an output unit that receives instructions from the management unit, generates xFlow packets for each flow based on the data in the output table, and outputs them to the output destination. Effect of the Invention
[0008] According to the present invention, it is possible to prevent performance degradation caused by contention between registration / update and deletion processes of flow information. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of a management device according to the first embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of the data configuration of Table A and Table B. As shown in FIG. [Diagram 3] FIG. 3 is a diagram illustrating a process flow in the management device. [Figure 4] FIG. 4 is a diagram illustrating the flow of processing in the management device. [Diagram 5] FIG. 5 is a diagram for explaining the format of an xFlow packet. [Figure 6] FIG. 6 is a flowchart of a procedure of the management process executed by the table management unit shown in FIG. [Figure 7]FIG. 7 is a flowchart showing the procedure of the generation and output process of an xFlow packet executed by the output unit shown in FIG. [Figure 8] FIG. 8 is a diagram for explaining conventional statistical xFlow packet generation and output processing. [Figure 9] FIG. 9 is a diagram illustrating an example of a management device according to the second embodiment. As illustrated in FIG. [Figure 10] FIG. 10 is a flowchart illustrating a procedure of the management process executed by the table management unit shown in FIG. [Figure 11] FIG. 11 is a diagram illustrating an example of a computer that realizes the management device by executing a program. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment. In addition, in the description of the drawings, the same parts are indicated by the same reference numerals.
[0011] [Embodiment 1] In the first embodiment, there are two flow statistics information cache tables, a registration table and an output table are set separately, and the registration / update process of flow information and the deletion process of output flow information are executed in different flow statistics information cache tables. Therefore, according to the first embodiment, there is no contention between the registration / update process and the deletion process of flow information, and therefore it is possible to avoid a performance degradation due to contention between the registration / update and deletion processes of flow information.
[0012] [Management device] Next, a description will be given of a management device according to the embodiment 1. Fig. 1 is a diagram illustrating an example of a management device according to the embodiment 1.
[0013] 1 receives input of sampled encapsulated packets or header information of encapsulated packets for network monitoring and traffic trend analysis, and manages statistical information of inner headers calculated from the header information and header sample data. Then, the management device 10 generates xFlow packets that include at least the statistical information of inner headers totaled for each flow, and outputs the packets to an output destination such as an analysis device.
[0014] The management device 10 is realized, for example, by loading a predetermined program into a computer or the like including a ROM (Read Only Memory), a RAM (Random Access Memory), a CPU (Central Processing Unit), etc., and the CPU executes the predetermined program. The management device 10 also has a communication interface for transmitting and receiving various information to and from other devices connected via a wired connection or a network, etc. For example, the management device 10 has a NIC (Network Interface Card) or the like, and communicates with other devices via electric communication lines such as a LAN (Local Area Network) or the Internet.
[0015] The management device 10 includes a storage unit 11, a registration unit 12, a table management unit 13 (management unit), and an output unit 14.
[0016] The memory unit 11 stores Table A and Table B, which are flow statistics information cache tables. Table A and Table B are flow statistics information cache tables with the same data structure. Table A and Table B are set as either a registration table or an output table by the table management unit 13 (described later). The registration table is a flow statistics information cache table in which at least statistical information and flow identification information regarding the inner header of each flow are registered as flow information by the registration unit 12 (described later). The output table is a flow statistics information cache table in which at least statistical information and flow identification information regarding the inner header of each flow are recorded, and which is referred to by the output unit 14 when generating an xFlow packet.
[0017] FIG. 2 is a diagram showing an example of the data configuration of Table A and Table B. As shown in FIG. 2, Table A and Table B have items of flow identification information and inner header statistical information for each sequence number. The flow identification information is predetermined packet header information of an encapsulated packet, for example, inner header information. The flow identification information may also include outer header information. The inner header and outer header, which are flow identification information, may also be hashed. The inner header statistical information is statistical information regarding the inner header for each flow having the same flow identification information, for example, the total number of packets or packet data volume for packets having the same flow identification information.
[0018] Next, a description will be given of the functions and processing of the registration unit 12, the table management unit 13, and the output unit 14. Figures 3 and 4 are diagrams illustrating the flow of processing in the management device 10.
[0019] The registration unit 12 generates statistical information on the inner header from the encapsulated packet or the header sample of the encapsulated packet that has been received, and registers or updates the generated statistical information on the inner header in the registration table. Specifically, when the registration unit 12 receives the input of the encapsulated packet or the header sample of the encapsulated packet in the registration phase ((1) in FIG. 3), the registration unit 12 acquires the header information of the encapsulated packet, separates the outer header information from the inner header information, and identifies the flow based on the flow identification information that is a part of the header information (step S1 in FIG. 3). At this time, when a packet with an xFlow header is input, the registration unit 12 removes the xFlow header and then acquires the header information. The registration unit 12 may determine the header information using, for example, the method described in Japanese Patent Application Laid-Open No. 2019-097069.
[0020] The registration unit 12 judges whether the flow identification information of the input packet is to be newly registered in the registration table or is already registered by referring to the registration table (Table A in FIG. 3), and if it is already registered, acquires statistical information of the inner header of the flow (Step S2 in FIG. 3). If it is a new registration, the registration unit 12 generates statistical information of the inner header from the packet (Step S3-1 in FIG. 3) and registers the flow information in the registration table (Table A in FIG. 3) (Step S4-1 in FIG. 3). If it is already registered, the registration unit 12 generates statistical information of the inner header from the packet, and combines it with the statistical information of the inner header of the flow acquired from the registration table (Table A in FIG. 3) in Step S2 in FIG. 3 to generate statistical information of the inner header (Step S3-2 in FIG. 3), and updates the flow information in the registration table (Table A in FIG. 3) (Step S4-2 in FIG. 3). In step S4-2 of FIG. 3, if the flow information of the flow is not registered in the registration table due to a table change process being performed after step S2 of FIG. 3, flow information including the statistical information of the inner header generated from the packet is registered in the registration table, instead of the aggregated statistical information of the inner header, as in step S4-1 of FIG. 3.
[0021] The table management unit 13 judges whether a predetermined table change condition (change condition) is satisfied. The table change condition is set based on, for example, the time when the table change process was last performed. The table change is performed, for example, at regular intervals. The table change condition may be, for example, that a predetermined time has elapsed since the time when the table change process was last performed. The table change condition may be, for example, that a predetermined time has elapsed since the time when the registration table was newly set. The table change condition may be, for example, that all information registered in the output table has been transmitted and that a predetermined time has elapsed since the time when the output table was last initialized. The table management unit 13 may apply, as the table change condition, a condition set based on the number of flows registered in the registration table. The table change condition may be, for example, that the number of flows registered in the registration table reaches a predetermined threshold.
[0022] When the table management unit 13 determines that a predetermined table change condition is satisfied ((2) in FIG. 3), it initializes table B, which is an output table, and then changes the setting of the registration table information held by the registration unit 12 from table A to table B ((5-1) in FIG. 4), and changes the setting of the output table information held by the output unit 14 from table B to table A ((5-2) in FIG. 4), thereby switching the tables referred to by the registration unit 12 and the output unit 14. In this way, every time the table change condition is satisfied, the table referred to by the registration unit 12 is switched from table A to B, or from table B to table A. Also, every time the table change condition is satisfied, the table referred to by the output unit 14 is switched from table B to A, or from table B to table A. The table management unit 13 updates the table information in which the identification information of the table corresponding to the registration table and the identification information of the table corresponding to the output table are registered. Every time the table change condition is satisfied, the table management unit 13 appropriately sets tables A and B as the registration table and the output table.
[0023] Then, the table management unit 13 updates the next table change condition determined based on the time when the table change process was last performed ((5-3) in FIG. 4), for example.
[0024] The table management unit 13 then instructs the output unit 14 to output an xFlow packet that includes at least the statistical information of the inner header ((6) in FIG. 4). The registration unit 12 registers the header information and the statistical information of the inner header in table B, which is set as a registration table, in accordance with the input of the encapsulated packet or the header sample of the encapsulated packet.
[0025] In the output phase ((7) in FIG. 4), the output unit 14 obtains flow information including statistical information in the inner header from the output table (table A) (step S11 in FIG. 4), generates an xFlow packet including the flow information (step S12 in FIG. 4), and outputs the generated xFlow packet to the destination analysis device (step S13 in FIG. 4). The output unit 14 performs the processes of steps S11 to S13 for each flow.
[0026] The output unit 14 generates an xFlow packet in a format corresponding to the processing content at the output destination of the xFlow packet. Fig. 5 is a diagram for explaining the format of an xFlow packet. As shown in Fig. 5, for example, the output unit 14 generates an xFlow packet in a format P1 having only statistical information of the inner header in accordance with the analysis device of the output destination. In addition, the management device 10 can generate an xFlow packet in a format P2 in which an inner header sample is added to the statistical information of the inner header, or in a format P3 in which an inner header sample and an outer header sample are added to the statistical information of the inner header, by storing a header sample in advance and storing a table in which the analysis device of the output destination and the flow identification information correspond to the output format.
[0027] Thus, in the management device 10, the table management unit 13 separates the two tables into a registration table and an output table, manages information including at least statistical information on the inner header of each flow, which is flow information, and when a predetermined change condition is satisfied, instructs the output of an xFlow packet including at least the statistical information of the inner header recorded in the output table. The management device 10 alternates between Table A and Table B as the registration table and the output table, and repeats the registration process in the registration table and the generation and output process of xFlow packets using the data in the output table. Therefore, the management device 10 does not time the output of xFlow packets on a flow-by-flow basis, nor does it delete flow information from the table on a flow-by-flow basis.
[0028] [Administrative processing] Next, there will be described the management processing executed by the table management unit 13. Fig. 6 is a flowchart showing the processing procedure of the management processing executed by the table management unit 13 shown in Fig. 1.
[0029] 6, at the start, the table management unit 13 initializes the registration table and the output table (step S21). The table management unit 13 determines whether the table change condition is satisfied (step S22). If the table change condition is not satisfied (step S22: No), the table management unit 13 returns to step S22 and repeats the determination process until the table change condition is satisfied.
[0030] If the table change condition is satisfied (step S22: Yes), the table management unit 13 performs a table change process (step S23). The table change process is a process of switching between the registration table and the output table after initializing the output table. Specifically, when the output table is table B and the registration table is table A, the table management unit 13 changes the setting of the registration table information held by the registration unit 12 from table A to table B, and changes the setting of the output table information held by the output unit 14 from table B to table A, thereby switching the tables referred to by the registration unit 12 and the output unit 14. At the same time, the table management unit 13 updates the information of the registration table and the output table, in this case, the information that the registration table is table B and the output table is table A. Then, the table management unit 13 updates the next table change condition determined based on the time when the table change process was last performed (step S24).
[0031] Next, the table management unit 13 instructs the output unit 14 to output the xFlow packet (step S25).Then, the table management unit 13 returns to step S22 and continues the process.
[0032] [xFlow packet generation and output processing] The following describes the process of generating and outputting xFlow packets executed by the output unit 14. Fig. 7 is a flowchart showing the procedure of the process of generating and outputting xFlow packets executed by the output unit 14 shown in Fig. 1.
[0033] As shown in Fig. 7, the output unit 14 receives an input of an instruction to output an xFlow packet from the table management unit 13 (step S31). The output unit 14 changes the output table information from Table A to Table B in accordance with an instruction to change the information in the output table received together with the output instruction from the table management unit 13. The output unit 14 then acquires flow information including statistical information in the inner header from the switched output table (step S32), and generates an xFlow packet having the flow information (step S33). The output unit 14 then outputs the generated xFlow packet to the analysis device of the output destination (step S34).
[0034] The output unit 14 judges whether or not xFlow packets have been output for all flows registered in the output table (step S35). If xFlow packets for all flows have not been output (step S35: No), the process returns to step S32 to output xFlow packets for the next flow, and continues processing. In this way, when the output unit 14 receives an output instruction, it generates an xFlow packet for each flow by adding up the statistical information in the inner header of the encapsulated packet, and outputs each xFlow packet to the analysis device that is the output destination of each flow. Then, when xFlow packets for all flows have been output (step S35: Yes), the output process of the xFlow packet ends. Note that the output unit 14 may generate and output an xFlow packet after collectively acquiring information on all flows registered in the output table.
[0035] [Advantages of the First Embodiment] Fig. 8 is a diagram explaining conventional statistical xFlow packet generation and output processing. As shown in Fig. 8, in the conventional technology, the flow information registration and update processing and the deletion processing of the output flow information are performed in the same flow statistics information cache table, which causes a problem of performance degradation due to contention between the flow information registration processing and the flow information deletion processing. In addition, in the conventional technology, the elapsed time, etc. are monitored on a per-flow basis to determine whether the output conditions are satisfied. For this reason, in the conventional technology, there is a problem that the processing load of output condition monitoring, such as timer management, increases as the number of input flows increases.
[0036] In contrast, in the first embodiment, a cache table (registration table) for registering and updating flow information and a cache table (output table) for deleting output flow information are set separately, so that no contention occurs between the registration and update process of flow information and the deletion process of flow information. Therefore, according to the present embodiment, no performance degradation occurs due to contention between the registration and update process of flow information and the deletion process of flow information.
[0037] In addition, in the first embodiment, since only the change conditions of the cache table are monitored instead of judging whether the output conditions are satisfied for each flow, the monitoring processing load can be reduced compared to the conventional technology. According to the present embodiment, the influence of a sudden increase in the processing load caused by a sudden increase in the number of input flows can be reduced.
[0038] Furthermore, according to the first embodiment, the output flow information is deleted by initializing the output table in the table change process (step S23 in FIG. 6), so the load of the flow information deletion process can be reduced compared to the conventional technology in which the output flow information is deleted for each flow.
[0039] Furthermore, in order to detect attacks, etc., it is necessary to output an xFlow packet to a downstream analysis device within a certain time after the arrival of the packet. In conventional technology, output occurs when the maximum no-communication time or maximum communication time has elapsed for each flow. In this embodiment, the time when the table change process was last performed, i.e., the time elapsed since the output table was last initialized, is included in the table change conditions. In this first embodiment, the time elapsed since the table change process was last performed is set to a time based on the maximum no-communication time or maximum communication time, thereby making it possible to properly maintain the output timing of the xFlow packet.
[0040] In the first embodiment, the case where two tables, tables A and B, are switched to a registration table and an output table has been described, but the number of tables may be two or more. For example, when three tables A, B, and C are used, the registration table is table A, the output table is table B, and table C is in an initialized state, and when a change condition is satisfied, the registration table is set to table C, the output table is set to table A, and table B is initialized. In this case, the cache memory area for the required tables increases, but when the table change condition is satisfied, a table that has been initialized in advance can be set to the registration table before initializing the output table, so that the time required to change the registration table can be shortened.
[0041] [Variations] The longer the time interval for performing the table change process, the more statistical information from the inner headers of packets of the same flow can be added together, and the total number of output xFlow packets can be reduced. However, in this case, the number of input flows also increases, and there is a possibility that the number of flows that can be registered in the registration table before the table change process is exceeded.
[0042] Therefore, the table management unit 13 may add a condition based on the number of flows registered in the registration table as a table change condition, in addition to the condition based on the time when the table change process was last performed. For example, the table change condition may include the number of flows registered in the registration table reaching a predetermined threshold.
[0043] Specifically, the management device 10 counts the number of flows registered in the registration table by the registration unit 12 (counter: k), and when k exceeds a predetermined threshold, notifies the table management unit 13 that the registration table is oversubscribed.
[0044] When the table management unit 13 receives an over-registration notification for the registration table, it sets the over-registration flag (initial value is "0") to "1." Then, the table management unit 13 performs table change processing when either of the following conditions is met: a first condition that a predetermined time has passed since the time the output table was last initialized, or a second condition that the over-registration flag is "1." In other words, the table change condition is that a predetermined time has passed since the time the registration table was newly set, or that the number of flows registered in the registration table reaches a predetermined threshold.
[0045] After the table change process, the table management unit 13 sets the value of the excess registration flag to "0" and notifies the registration unit 12 to set the counter k to "0."
[0046] According to this modified example, it is possible to change the table before the number of flows that can be registered in the registration table is exceeded, and flow information can be registered without being missed even if the number of input flows increases suddenly.
[0047] In addition, in the modified example, if the analysis device to which the xFlow packets are output has a limit on the number of xFlow packets that it can receive in a burst, a threshold for the number of registered flows is set based on the number of consecutive packets that the analysis device to which the xFlow packets are output can receive. As a result, in the second modified example, it is possible to limit the number of xFlow packets that are output by obtaining flow information from the output table with each table change, and to reduce overflow of the receiving buffer in the analysis device to which the xFlow packets are output.
[0048] [Embodiment 2] In the first embodiment, the table change process is described as switching between the tables to be set as the registration table and the output table. In the second embodiment, the table change process is described as a method of transferring data from the registration table to the output table after initializing the output table.
[0049] 9 is a diagram illustrating an example of a management device according to embodiment 2. A management device 210 illustrated in FIG. 9 has a table management section 213 instead of the table management section 13 illustrated in FIG.
[0050] The table management unit 213 determines whether a predetermined table change condition is satisfied. The table change is performed, for example, at regular time intervals. The table change condition may be, for example, that a predetermined time has elapsed since the last time the table change process was performed. The table change condition may be, for example, that a predetermined time has elapsed since the information in the registration table was transferred to the output table. The table change condition may be, for example, that all the information registered in the output table has been transmitted, and that a predetermined time has elapsed since the last time the output table was initialized. The table change condition may be, for example, that the number of flows registered in the registration table reaches a predetermined threshold. The table change condition may be, for example, that either one of the conditions is satisfied: that a predetermined time has elapsed since the information in the registration table was transferred to the output table, and that the number of flows registered in the registration table reaches a predetermined threshold.
[0051] If the table management unit 213 determines that the predetermined table change condition is satisfied, it initializes the output table, transfers the data in the registration table to the output table, and then initializes the registration table. Then, the table management unit 213 instructs the output unit 14 to output an xFlow packet that includes at least the statistical information in the inner header.
[0052] In the second embodiment, since the registration table and the output table are not switched, the registration table is fixed to, for example, table A, and the output table is fixed to, for example, table B. Therefore, in the second embodiment, the process in the first embodiment of instructing the registration unit 12 and the output unit 14 to change the setting of the reference table from the table management unit 213, and the process in the registration unit 12 and the output unit 14 of changing the setting of the registration table or the output table information are not required.
[0053] [Administrative processing] Next, a description will be given of the management processing executed by the table management unit 213. Fig. 10 is a flowchart showing the processing procedure of the management processing executed by the table management unit 213 shown in Fig. 9.
[0054] Steps S41 and S42 shown in Fig. 10 are the same processes as steps S21 and S22 shown in Fig. 6. If the table change condition is satisfied (step S42: Yes), the table management unit 213 performs a table change process (step S43). In the table change process, the data in the registration table is transferred to the output table, and then the registration table is initialized.
[0055] Table management unit 213 updates the table change condition (step S44). For example, table management unit 213 updates the next table change condition determined based on the time when the table change process was performed. If the table change condition is that a predetermined time has passed since the time when the table change process was last performed, table management unit 213 rewrites it to the time when the next table change process will be performed. Also, if the table change condition is that the number of flows registered in the registration table reaches a predetermined threshold, table management unit 213 sets the registration excess flag to the initial value "0".
[0056] Next, the table management unit 213 instructs the output unit 14 to output the xFlow packet (step S45).
[0057] [Effects of the second embodiment] In this way, in the second embodiment, as the table change process, the data in the registration table is transferred to the output table, and then the registration table is initialized, thereby achieving the same effects as in the first embodiment.
[0058] [System configuration of the embodiment] Each component of the management device 10, 210 is a conceptual function, 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 management device 10, 210 is not limited to that shown in the figure, and all or part of it can be functionally or physically distributed or integrated in any unit according to various loads, usage conditions, etc.
[0059] Further, all or any part of each process performed in the management device 10, 210 may be realized 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 management device 10 may be realized as hardware using wired logic.
[0060] 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 figures can be changed as appropriate unless otherwise specified.
[0061] [program] 11 is a diagram showing an example of a computer in which a program is executed to realize the management device 10, 210. 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.
[0062] 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.
[0063] 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, a program that defines each process of the management device 10, 210 is implemented as a program module 1093 in which code executable by the computer 1000 is written. The program module 1093 is stored, for example, in the hard disk drive 1090. For example, the program module 1093 for executing the same process as the functional configuration in the management device 10, 210 is stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced by an SSD (Solid State Drive).
[0064] 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.
[0065] 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.
[0066] 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]
[0067] 10,210 Management equipment 11 Storage section 12 Registration Department 13,213 Table Management Section 14 Output section
Claims
1. A storage unit for storing two tables, which are flow statistics information cache tables; a management unit that divides the two tables into a registration table and an output table, manages information including at least statistical information on the inner header of each flow, which is flow information, and performs table change processing to switch between the registration table and the output table when a predetermined change condition is satisfied, and instructs the output of xFlow packets including at least the statistical information on the inner header recorded in the output table; a registration unit that generates statistical information on the inner header from the received encapsulated packet or a header sample of the encapsulated packet, and registers or updates the generated statistical information on the inner header in the registration table; an output unit that receives an instruction from the management unit, generates the xFlow packet for each flow based on the data in the output table, and outputs the generated xFlow packet to an output destination; A management device comprising:
2. A storage unit for storing two tables, which are flow statistics information cache tables; a management unit that divides the two tables into a registration table and an output table, manages information including at least statistical information on the inner header of each flow, which is flow information, and performs table change processing to transfer data from the registration table to the output table when a predetermined change condition is satisfied, and instructs the output of xFlow packets including at least the statistical information of the inner header recorded in the output table; a registration unit that generates statistical information on the inner header from the received encapsulated packet or a header sample of the encapsulated packet, and registers or updates the generated statistical information on the inner header in the registration table; an output unit that receives an instruction from the management unit, generates the xFlow packet for each flow based on the data in the output table, and outputs the generated xFlow packet to an output destination; A management device comprising:
3. 3. The management device according to claim 1, wherein the change condition is set based on the time when the table change process was last performed and / or the number of flows registered in the registration table.
4. A management method executed by a management device, comprising: The management device has a storage unit that stores two tables that are flow statistics information cache tables, a step of dividing the two tables into a registration table and an output table, and managing information including at least statistical information on the inner header of each flow as flow information; generating statistical information on the inner header from the received encapsulated packet or a header sample of the encapsulated packet, and registering or updating the generated statistical information on the inner header in the registration table; performing a table change process for switching between the registration table and the output table when a predetermined change condition is satisfied, and instructing the output of an xFlow packet including at least the statistical information of the inner header recorded in the output table; receiving an instruction to output the xFlow packets, generating the xFlow packets for each flow based on the data in the output table, and outputting the xFlow packets to an output destination; A management method comprising the steps of:
5. A management method executed by a management device, comprising: The management device has a storage unit that stores two tables that are flow statistics information cache tables, a step of dividing the two tables into a registration table and an output table, and managing information including at least statistical information on the inner header of each flow as flow information; generating statistical information on the inner header from the received encapsulated packet or a header sample of the encapsulated packet, and registering or updating the generated statistical information on the inner header in the registration table; performing a table change process for transferring data from the registration table to the output table when a predetermined change condition is satisfied, and issuing an instruction to output an xFlow packet including at least the statistical information of the inner header recorded in the output table; receiving an instruction to output the xFlow packets, generating the xFlow packets for each flow based on the data in the output table, and outputting the xFlow packets to an output destination; A management method comprising the steps of:
6. A management program for causing a computer to function as the management device according to any one of claims 1 to 3.
Citation Information
Patent Citations
Method and device for virtualization of multiple data sets on same associative memory
US7281085B1
