JP2015170140A - Communication device and data management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To obtain information on failure right before occurrence of the failure from a communication device when the failure has occurred in the communication device.SOLUTION: A communication device includes: a first memory into which data is written per prescribed quantity and which does not require power supply to retain the data; an MRAM into which data is written per quantity less than prescribed quantity and which does not require power supply to retain the data; and a second memory which requires power supply to retain data. The communication device stores data which has been processed by the communication device in the second memory, stores data which has been processed by the communication device and should be stored to analyze an event that has occurred in the communication device in the MRAM, moves data stored in the MRAM to the first memory per prescribed quantity, and stores data to be stored in the MRAM in the first memory if the communication device has started after the communication device had stopped due to occurrence of an event in the communication device.

Description

  The present invention relates to a communication device.

  When a failure or failure occurs in various information processing devices such as general-purpose computers, servers, or transmission devices, the device information immediately before the failure or failure occurs is acquired from the information processing device for investigation and countermeasures. There is a need. Conventionally, apparatus information is stored in a storage device while the information processing apparatus is operating, and apparatus information is acquired from the storage device when a failure or the like occurs.

  Conventionally, techniques for holding various device information generated in an information processing device have been proposed. For example, means for storing a recording start address for starting recording in a recording area for recording processing history information has been proposed (see, for example, Patent Document 1).

  In the log management system, means for outputting an operation history as a log in accordance with the operation of software has been proposed (see, for example, Patent Document 2).

JP 2013-228789 A JP 2012-242872 A

  When the information processing apparatus stores apparatus information in a volatile storage device, the contents of the volatile storage device may be lost when the information processing apparatus is restarted. For this reason, when a failure or failure occurs in the information processing device and it is restarted, the contents of the volatile storage device are lost, the device information at the time of failure or failure is unknown, and the cause investigation is hindered. there were.

  According to an exemplary embodiment of the present invention, a communication device is a processor that processes data, and data is written for each predetermined amount, and does not require supply of power to hold the data. A first memory, an MRAM in which data is written every smaller amount than the predetermined amount, and does not require a power supply for holding the data, and a power supply for holding the data A second memory that is required, and the data processed in the communication device is stored in the second memory, is the data processed in the communication device, and is generated in the communication device The data to be stored to analyze the event is stored in the MRAM, the data stored in the MRAM is moved to the first memory by the predetermined amount, and the communication is performed. After the event occurs the communication device is stopped in the device, when the communication device is activated, the data stored in the MRAM, stored in the first memory.

  According to an embodiment of the present invention, when a failure occurs in the communication device, information on the failure immediately before the failure can be acquired from the communication device.

  Problems, configurations, and effects other than those described above will be clarified by the following description of embodiments.

It is a block diagram which shows the computer of a present Example. It is explanatory drawing which shows the log definition table of a present Example. It is explanatory drawing which shows the log classification table of a present Example. It is explanatory drawing which shows the transfer management table of a present Example. It is a flowchart which shows the process of the apparatus control module of a present Example. It is a flowchart which shows the process of the apparatus control module and event recording part of a present Example. It is a flowchart which shows the process of the packet recording part of a present Example. It is a flowchart which shows the process of the log recording part of a present Example. It is a flowchart which shows the process of the starting process part of a present Example.

  Below, the computer which is the information processing apparatus of this invention is demonstrated.

  FIG. 1 is a block diagram showing a computer 100 of this embodiment.

  The computer 100 of this embodiment is a computer having the functions of a general-purpose computer, a server, or a communication device, and includes a processor. The computer 100 of this embodiment is a communication device having a communication function for transferring packets.

  The computer 100 is connected to the network 150 or another computer 100. The computer 100 is connected to the input / output device 160.

  The input / output device 160 receives input from the user and displays the processing result in the computer 100 to the user. The input / output device 160 may include any device such as a display, a printer, a tablet terminal, a keyboard, and a mouse.

  The computer 100 illustrated in FIG. 1 includes a control unit 110, a transfer unit 130, and at least one interface unit 140 (140a to 140c).

  The interface unit 140 is a network interface that transmits a packet to the network 150 and further receives a packet from the network 150. The interface unit 140 is connected to the network 150 (150a, 150b) or another computer 100. The packet received by the interface unit 140 is transferred to the transfer unit 130.

  When the computer 100 does not have a function of transferring a packet, the interface unit 140 may be connected to the device control module 111 of the control unit 110.

  The transfer unit 130 is a processing unit that transfers a packet received from the interface unit 140 to the interface unit 140 or the control unit 110 according to the destination of the packet. The transfer unit 130 includes a processor and a memory.

  When the received packet is a packet destined for a device other than its own device, the transfer unit 130 of this embodiment copies the packet. Then, the transfer unit 130 transmits the copied packet to the device control module 111 of the control unit 110.

  The control unit 110 is a processing unit for managing data processed in the computer 100. The control unit 110 includes a processor and a memory. The control unit 110 includes a device control module 111 and a logging module 112 as processing units. In addition, the control unit 110 includes an auxiliary storage device 113, a DRAM 114, and a nonvolatile memory 115 as storage devices.

  The device control module 111 collects logs related to hardware and software included in the computer 100. Specifically, the device control module 111 monitors a system log output from hardware, an application log output from software, and the like corresponding to a predetermined condition while the computer 100 is operating. To collect. The collected log is sent to the event recording unit 116 of the logging module 112.

  Here, the predetermined condition is for designating a log necessary for analyzing an event such as a failure occurring in hardware and software. The device control module 111 may hold a condition specified by the user via the input / output device 160 as a predetermined condition for collecting logs. Further, the predetermined condition may be specified by, for example, the type of event indicated by the log or the content of the message.

  Further, the device control module 111 collects the packets transferred from the transfer unit 130. Then, the device control module 111 transmits the collected packets to the packet recording unit 117 of the logging module 112.

  Further, the apparatus control module 111 instructs the logging module 112 to execute processing at the time of startup of the computer 100.

  The logging module 112 includes a module that stores data in the storage device of the control unit 110 and moves data in the storage device. The logging module 112 includes an event recording unit 116, a packet recording unit 117, a log recording unit 118, and an activation processing unit 119. The logging module 112 includes a log definition table 125, a log classification table 126, and a packet definition table 127.

  The auxiliary storage device 113 is, for example, a non-volatile memory such as a flash memory or a hard disk, and is a storage device that can hold data without being supplied with power. Each processing unit of the control unit 110 can write data to the auxiliary storage device 113 for each predetermined data amount.

  Generally, when the amount of the predetermined data is large, the access speed is slow. That is, when the amount of data that can be written at a time is large, the speed at which data is stored in the auxiliary storage device 113 is slow.

  The DRAM 114 is configured by a volatile memory. In this embodiment, the DRAM 114 may be a volatile memory other than a DRAM (Dynamic Random Access Memory). The DRAM 114 of this embodiment may be any volatile memory as long as it is a volatile memory that requires power to hold data. The DRAM 114 has a higher access speed than the auxiliary storage device 113.

  The non-volatile memory 115 is configured by a non-volatile memory such as an MRAM (Magnetic Resistive Random Access Memory). Each processing unit of the control unit 110 can write data in the nonvolatile memory 115 for each data amount smaller than that of the auxiliary storage device 113.

  For this reason, the non-volatile memory 115 has a higher access speed (specifically, a speed for storing data) than the auxiliary storage device 113 and may be used as a buffer in processing.

  The nonvolatile memory 115 according to the present embodiment is any memory as long as the nonvolatile memory 115 does not require a power source to hold data and can write data for each smaller data amount than the auxiliary storage device 113. May be.

  The event recording unit 116 stores the log input from the device control module 111 in the nonvolatile memory 115 based on the log definition table 125. The packet recording unit 117 stores the packet input from the device control module 111 in the nonvolatile memory 115 based on the packet definition table 127. The activation processing unit 119 moves the data stored in the nonvolatile memory 115 after the failure of the computer 100 to the auxiliary storage device 113.

  The log definition table 125 indicates the storage destination in the nonvolatile memory 115 of the log input from the device control module 111. The log classification table 126 indicates the importance of the log.

  The packet definition table 127 shows the storage destination of the packet in the nonvolatile memory 115. Specifically, the packet definition table 127 indicates packet storage destinations according to the packet destination, transmission source, type, message, or the like.

  The nonvolatile memory 115 includes a long-term storage area 121 (121a, 121b) and a short-term storage area 122 (122a, 122b). The long-term storage area 121 stores data that needs to be stored for a long time, and the short-term storage area 122 stores data that does not need to be stored for a long time.

  The long-term storage area 121 of this embodiment is a storage area that is less frequently overwritten when the capacity of data stored in the long-term storage area 121 reaches the upper limit of the area. In addition, the short-term storage area 122 according to the present embodiment is a storage area that is frequently overwritten when the capacity of data stored in the short-term storage area 122 reaches the upper limit value of the area.

  An area larger than the short-term storage area 122 may be allocated to the long-term storage area 121 in order to reduce the frequency of overwriting. In addition, each processing unit of the control unit 110 records the date and time when the data is stored in the nonvolatile memory 115 in the nonvolatile memory 115, and restricts the data stored in the long-term storage area 121 from being overwritten for a predetermined period. Good.

  The long-term storage area 121a and the short-term storage area 122a shown in FIG. 1 are storage areas for storing logs. Also, the long-term storage area 121b and the short-term storage area 122b shown in FIG. 1 are storage areas for storing packets.

  Further, the nonvolatile memory 115 has a transfer management table 120 (120a, 120b). The transfer management table 120 indicates whether or not the data stored in the storage area of the nonvolatile memory 115 has been transferred to the auxiliary storage device 113.

  The transfer management table 120a corresponds to the long-term storage area 121a and the short-term storage area 122a, and the transfer management table 120b corresponds to the long-term storage area 121b and the short-term storage area 122b.

  The long-term storage area 121b and the short-term storage area 122b are areas for storing only the data immediately before and after the occurrence of the failure when the failure occurs in the computer 100, that is, include the time when the failure occurs. This is an area for storing data processed by the computer 100 during a predetermined period (first period). The long-term storage area 121b and the short-term storage area 122b in the present embodiment are areas for storing packets received via the interface unit 140.

  The long-term storage area 121a and the short-term storage area 122a are areas for storing data that needs to be stored for a predetermined period (second period), and store data that needs to be transferred to the auxiliary storage device 113. It is an area to do. The long-term storage area 121a and the short-term storage area 122a in the present embodiment are areas for storing event logs.

  Here, the first period is a period sufficiently shorter than the second period. This is because data that may occur in a large amount in a certain period needs to be saved for the data processed immediately before and after the failure occurs, but on the other hand, the data stored in the auxiliary storage device 113 or the like This is because the use capacity of the device may be compressed. For this reason, data that may occur in large quantities in a certain period is stored in the long-term storage area 121b and the short-term storage area 122b in the present embodiment.

  The nonvolatile memory 115 according to the present embodiment has a long-term storage area 121, a short-term storage area 122, and the like according to a period in which data needs to be stored. It can be controlled optimally. The device control module 111 and the logging module 112 may be physical devices each including a processor and a memory, or may be logical processing units implemented by programs. When the device control module 111 and the logging module 112 are logical processing units, a program for mounting the device control module 111 and the logging module 112 may be developed in the DRAM 114.

  FIG. 2 is an explanatory diagram illustrating the log definition table 125 according to this embodiment.

  The log definition table 125 indicates a storage location for storing a log received by the event recording unit 116. The log definition table 125 includes a log code 1251, date and time 1252, log details 1253, and nonvolatile memory storage destination 1254.

  The log code 1251 indicates a number included in the log. The date and time 1252 indicates the occurrence date and time of the event included in the log. The log details 1253 indicate the contents of events included in the log.

  The non-volatile memory storage location 1254 indicates the storage location of the non-volatile memory 115 that stores a log including the log code 1251, the date and time 1252, and the log details 1253. For example, when the nonvolatile memory storage destination 1254 of the entry corresponding to the received log indicates “long-term storage area”, the event recording unit 116 stores the log in the DRAM 114 and the long-term storage area 121 a of the nonvolatile memory 115. Store.

  For example, when the nonvolatile memory storage location 1254 indicates “not applicable”, the event recording unit 116 stores the log only in the DRAM 114.

  FIG. 3 is an explanatory diagram showing the log classification table 126 of the present embodiment.

  The log classification table 126 shown in FIG. 3 shows a log code 1261 and a log code definition 1262. The log code 1261 corresponds to the log code 1251 of the log definition table 125.

  The log code definition 1262 indicates the meaning of the log code. The log code 1261 shown in FIG. 3 indicates that the smaller the number is, the longer the log needs to be stored. Also, in the log classification table 126 of this embodiment, log codes of important logs and log codes of unimportant logs are designated in advance.

  The device control module 111 may display the log classification table 126 on the input / output device 160 and allow the user to specify the correspondence between the log code and the storage destination, and may update the log definition table 125 according to this specification. .

  The device control module 111 may display the log classification table 126 on the input / output device 160 and allow the user to input a log code of a log that does not need to be stored in the nonvolatile memory 115. Then, the apparatus control module 111 may cause the event recording unit 116 to hold the input log code.

  FIG. 4 is an explanatory diagram showing the transfer management table 120 of this embodiment.

  The transfer management table 120 indicates a storage location of data stored in the nonvolatile memory 115 and is a table for managing data in the nonvolatile memory 115. The transfer management table 120 includes a recording device 1201, an address 1202, a length 1203, and a transfer status 1204.

  The recording device 1201 indicates an area of the nonvolatile memory 115. Specifically, the recording device 1201 indicates whether it is a long-term storage area 121 or a short-term storage area 122.

  An address 1202 and a length 1203 indicate an area of data stored as one data in the nonvolatile memory 115. One data is specifically an event log or a packet.

  The address 1202 indicates the start point of the address of the area where one piece of data is stored. The length 1203 indicates the length from the start point indicated by the address 1202 (that is, the amount of data).

  In this embodiment, the transfer management table 120 indicates an area in which one piece of data is stored by an address 1202 and a length 1203, but the area is defined by the start address and end address of the area in which one piece of data is stored. May be shown.

  The transfer state 1204 indicates whether or not the data in the area indicated by the address 1202 and the length 1203 has already been stored in the auxiliary storage device 113.

  FIG. 5 is a flowchart showing the processing of the device control module 111 of this embodiment.

  The apparatus control module 111 activates the activation processing unit 119 when the activation process of the computer 100 is started, and instructs to move data from the nonvolatile memory 115 to the auxiliary storage device 113 (601). In the process of step 601, the data stored in the nonvolatile memory 115 is stored in the auxiliary storage device 113 so that the information at the time of the failure can be acquired even when the data in the DRAM 114 is erased due to a failure or the like. To be executed. The processing of the activation processing unit 119 in step 601 corresponds to the processing shown in FIG.

  After step 601, the device control module 111 monitors a log (stored in the DRAM 114) output by hardware and software and determines whether an event has occurred (602).

  If it is determined in step 602 that an event has occurred, the device control module 111 executes processing relating to the event that has occurred (603). Here, the process related to the event that has occurred is a process that is determined in advance as a response to the event when the event has occurred. For example, a notification of a warning via the input / output device 160, a restart of software, or the like It is.

  After step 603 or during execution of step 603, the device control module 111 acquires a log of the event that has occurred from the DRAM 114, and transmits the acquired log to the event recording unit 116. When receiving the event log, the event recording unit 116 stores the event log in the nonvolatile memory 115 by executing the process shown in FIG. 6 (604).

  If it is not determined in step 602 that an event has occurred, the device control module 111 determines whether a packet has been received from the transfer unit 130 (605). If no packet is received from the transfer unit 130, the apparatus control module 111 returns to step 602.

  If it is determined in step 605 that a packet has been received from the transfer unit 130, the apparatus control module 111 executes processing related to the received packet (606). Here, the process related to the received packet is a process determined in advance according to the content of the received packet, for example, a process of calculating a traffic amount of a predetermined type of packet according to the content of the received packet.

  After step 606 or during execution of step 606, the device control module 111 transmits the received packet to the packet recording unit 117. When the packet recording unit 117 receives the packet, the packet recording unit 117 stores the packet in the nonvolatile memory 115 by the process shown in FIG. 7 (607).

  After step 604 or step 607, the apparatus control module 111 returns to step 602.

  FIG. 6 is a flowchart illustrating processing of the apparatus control module 111 and the event recording unit 116 according to this embodiment.

  The device control module 111 collects the hardware and software logs of the computer 100 and transfers the collected logs to the event recording unit 116 (301). For example, when the device control module 111 detects that an event has occurred in the hardware, the device control module 111 collects a log of the event.

  When an event occurs in the hardware and software of the computer 100, the hardware and software functions store a log indicating the event in the DRAM 114.

  After step 301, the event recording unit 116 searches the log definition table 311 according to the content of the received log. Then, the event recording unit 116 specifies the nonvolatile memory storage destination 1254 of the entry of the log definition table 311 corresponding to the received log.

  When the value of the acquired nonvolatile memory storage location 1254 is “not applicable” or when there is no entry corresponding to the received log in the log definition table 311, the event recording unit 116 stores the log in the nonvolatile memory 115. Since it is not necessary to store, the process of FIG. 6 is terminated.

  When the acquired nonvolatile memory storage location 1254 indicates “long-term storage area”, the event recording unit 116 stores the log in the long-term storage area 121a of the nonvolatile memory 115 (331). Here, the event recording unit 116 adds a new entry to the transfer management table 120a, and stores information related to the log stored in the long-term storage area 121a in the new entry.

  Specifically, in step 331, the event recording unit 116 stores a value indicating “long-term storage area” in the recording device 1201 of the new entry in the transfer management table 120a, and logs the address 1202 and the length 1203. Stores a value indicating the stored area. Then, a value indicating non-transfer is stored in the transfer state 1204.

  If the acquired value of the nonvolatile memory storage location 1254 is “short-term storage area”, the event recording unit 116 determines whether the received log is important based on the log classification table 126 (321) ).

  For example, when the log classification table 126 has previously designated a log code of 2 or less as an important log and the log code of the received log is 1, the event recording unit 116 indicates that the received log is important. Therefore, it is determined that the data needs to be stored in the nonvolatile memory 115. Then, the event recording unit 116 stores the received log in the short-term storage area 122a of the nonvolatile memory 115 (332).

  If the received log is a log code designated in advance as an unimportant log, the event recording unit 116 ends the process of FIG. 6 without storing the received log in the nonvolatile memory 115.

  In step 332, the event recording unit 116 adds a new entry to the transfer management table 120a, and stores information related to the log stored in the short-term storage area 122a in the new entry. Specifically, in step 332, the event recording unit 116 stores a value indicating “short-term storage area” in the recording device 1201 of the new entry in the transfer management table 120 a, and logs the address 1202 and length 1203. Stores a value indicating the stored area. Then, a value indicating non-transfer is stored in the transfer state 1204.

  By the process of FIG. 6, the event recording unit 116 can store the received log in the long-term storage area 121a or the short-term storage area 122a of the nonvolatile memory 115 according to the contents of the log.

  FIG. 7 is a flowchart showing the processing of the packet recording unit 117 of this embodiment.

  When the interface unit 140 receives a packet, the transfer unit 130 transfers the packet according to the destination of the received packet, while copying the received packet, and transfers the copied packet to the device control module 111. The device control module 111 transmits the packet received from the transfer unit 130 to the packet recording unit 117 (201).

  After step 201, the packet recording unit 117 refers to the received packet and determines whether the destination of the packet is the computer 100 itself (addressed to itself) (211). In this embodiment, a packet addressed to the computer 100 itself is highly likely to cause a failure of the computer 100. Therefore, when the destination of the packet is the computer 100 itself, the packet recording unit 117 stores the received packet in the long-term storage area 121b of the nonvolatile memory 115 (231).

  Here, the packet recording unit 117 adds a new entry to the transfer management table 120b, and stores information on the packet stored in the long-term storage area 121b in the new entry. Specifically, in step 231, the packet recording unit 117 stores a value indicating “long-term storage area” in the recording device 1201 of the new entry in the transfer management table 120b, and stores the packet in the address 1202 and the length 1203. Stores a value indicating the stored area. Then, a value indicating non-transfer is stored in the transfer state 1204.

  If the destination of the received packet is not the computer 100 itself, the packet recording unit 117 refers to the packet definition table 127 and determines the storage destination of the received packet (221). Specifically, in step 221, the packet recording unit 117 refers to the header portion and the data portion of the received packet, and based on the destination, transmission source, type, etc. of the received packet and the packet definition table 127. Thus, it is determined whether the storage destination of the received packet is the long-term storage area 121b or the short-term storage area 122b.

  In step 221, when the storage destination of the received packet is the long-term storage area 121b, the packet recording unit 117 executes step 231 and stores the received packet in the long-term storage area 121b.

  In step 221, when the storage destination of the received packet is the short-term storage area 122b, the packet recording unit 117 stores the received packet in the short-term storage area 122b (232).

  Here, the packet recording unit 117 adds a new entry to the transfer management table 120b, and stores information on the packet stored in the short-term storage area 122b in the new entry. Specifically, in step 232, the packet recording unit 117 stores a value indicating “short-term storage area” in the recording device 1201 of the new entry in the transfer management table 120b, and stores the packet in the address 1202 and the length 1203. Stores a value indicating the stored area. Then, a value indicating non-transfer is stored in the transfer state 1204.

  After step 231 or step 232, the packet recording unit 117 ends the process shown in FIG.

  FIG. 8 is a flowchart showing the processing of the log recording unit 118 of this embodiment.

  While the computer 100 is operating, the log recording unit 118 transfers data from the area of the nonvolatile memory 115 in which the event log is stored to the auxiliary storage device 113 by the process shown in FIG. In this embodiment, the event log is data that is preferably stored for a certain period of time, and the packet is data that is preferably stored only when a failure or the like occurs. This is because it is determined in advance.

  However, if it is determined that a packet received via the interface unit 140 is also desirably stored for a certain period, the log recording unit 118 performs the processing of FIG. 8 in the transfer management table 120b, the long-term storage area 121b, and the short-term storage area. It is executed at 122b.

  The log recording unit 118 acquires data from the nonvolatile memory 115 based on the transfer management table 120a (361). Specifically, the log recording unit 118 acquires data from the area indicated by the address 1202 and the length 1203 of the entry whose transfer status 1204 of the transfer management table 120a indicates untransferred.

  The log recording unit 118 may acquire data from the nonvolatile memory 115 each time the transfer management table 120a is updated. Further, the log recording unit 118 may acquire data from the nonvolatile memory 115 by periodically referring to the transfer management table 120a. In step 361, the log recording unit 118 may acquire data preferentially from the area of the address 1202 and length 1203 of the entry indicating that the recording device 1201 indicates the long-term storage area 121a.

  Then, the log recording unit 118 determines whether or not a predetermined amount has been acquired from the nonvolatile memory 115 (362). Here, the predetermined amount in step 362 is an amount writable in the auxiliary storage device 113 and is a value uniquely determined by the auxiliary storage device 113.

  If the amount that can be written to the auxiliary storage device 113 is large, there is a possibility that data cannot be written to the auxiliary storage device 113 for a long period of time. If a failure occurs during a period in which data cannot be written, the DRAM 114 also has the auxiliary storage device 113. There is a possibility that data that is not written to may be generated.

  It should be noted that data can be written into the nonvolatile memory 115 of this embodiment for each amount smaller than the predetermined amount in step 362.

  In step 362, when the acquired data is less than the predetermined amount, the log recording unit 118 returns to step 361. Specifically, the log recording unit 118 acquires new data, and repeats step 361 until the total value of the acquired data and the amount of newly acquired data reaches a predetermined amount.

  When the predetermined amount of data is acquired in step 362, the log recording unit 118 stores the acquired data in the auxiliary storage device 113 (363). After storing the data in step 363, the log recording unit 118 notifies the event recording unit 116 of the data stored in the auxiliary storage device 113 (364). This notification indicates the address 1202 and length 1203 in the nonvolatile memory 115 of the data stored in the auxiliary storage device 113 in step 363.

  When the event recording unit 116 receives the notification from the log recording unit 118, the event recording unit 116 updates the transfer status 1204 of the address 1202 and the length 1203 indicated by the notification to a value indicating that transfer has been completed (365).

  Note that the logging module 112 may transfer the data stored in the DRAM 114 to the auxiliary storage device 113 in the same manner as the processing shown in FIG. In this case, the transfer management table 120 is not updated. By storing data from the DRAM 114 to the auxiliary storage device 113, data processed in the computer 100 can be stored for a long period of time.

  FIG. 9 is a flowchart showing the processing of the activation processing unit 119 of the present embodiment.

  When the activation process of the computer 100 is started, the apparatus control module 111 activates the activation processing unit 119 (501).

  The activation processing unit 119 first determines whether or not the computer 100 has ended normally (511) when the computer 100 has ended (or stopped) last time. The activation processing unit 119 refers to a system log or the like output by the hardware of the computer 100, and determines whether or not the computer 100 has ended normally.

  In step 511, when it is determined that the computer 100 has ended normally when the computer 100 ended last time, the activation processing unit 119 terminates the processing illustrated in FIG. 9, and the computer 100 performs the activation processing of the computer 100. continue.

  In step 511, when it is determined that the computer 100 has not ended normally when the computer 100 ended last time, the activation processing unit 119 stores the data stored in the non-volatile memory 115 into the auxiliary storage device 113. Transfer data is extracted based on the transfer management tables 120a and 120b. Then, the activation processing unit 119 stores the extracted data in the auxiliary storage device 113 (521).

  Here, the activation processing unit 119 also stores the data (packets) stored in the long-term storage area 121 b and the short-term storage area 122 b of the nonvolatile memory 115 in the auxiliary storage device 113. Therefore, the activation processing unit 119 can also store in the auxiliary storage device 113 packets received immediately before and after the occurrence of a failure or the like.

  In step 521, the activation processing unit 119 causes the event recording unit 116 and the packet recording unit 117 to update the transfer status 1204 of the transfer management tables 120a and 120b after storing the data in the auxiliary storage device 113. Specifically, the activation processing unit 119 updates the transfer state 1204 with a value indicating that transfer has been completed.

  After step 521, the activation processing unit 119 outputs to the input / output device 160 that the computer 100 has ended abnormally and that the data of the nonvolatile memory 115 has been stored in the auxiliary storage device 113 as failure information ( 541). The activation processing unit 119 may transmit information to be output to the input / output device 160 via the device control module 111.

  In step 541, the activation processing unit 119 may transmit the content of data stored in the auxiliary storage device 113 in step 521 or a list to the input / output device 160. The input / output device 160 may display data immediately before and immediately after the occurrence of a failure or the like in the computer 100 based on the transmitted data.

  As a result, the user can detect that there is a failure in the computer 100, and can acquire data for analyzing the failure from the input / output device 160.

  After step 541, the activation processing unit 119 ends the process illustrated in FIG. 9, and the computer 100 continues the activation process of the computer 100.

  When the computer 100 is stopped and restarted due to a failure or failure or the like, and the data is lost from the DRAM 114 even though the data in the DRAM 114 is not transferred to the auxiliary storage device 113, the processing shown in FIG. By executing, the data immediately before and after the occurrence of the failure or the like is stored in the auxiliary storage device 113. Thus, when a failure occurs in the computer 100, information on the failure immediately before the failure can be acquired from the computer 100.

  In addition, this invention is not limited to an above-described Example, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files for realizing each function is stored in a recording device such as a memory, a hard disk, or an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD. Can do.

  Further, the control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

100 Computer 110 Control Unit 111 Device Control Module 112 Logging Module 113 Auxiliary Storage Device 114 DRAM
115 Non-volatile memory 116 Event recording unit 117 Packet recording unit 118 Log recording unit 119 Start processing unit 120 Transfer management table 121 Long-term storage area 122 Short-term storage area 130 Transfer unit 140 Interface unit 150 Network 160 I / O device

Claims (12)

A communication device,
A processor for processing the data;
A first memory in which data is written for each predetermined amount and does not require supply of power to hold the data;
An MRAM in which data is written for each smaller amount than the predetermined amount and does not require the supply of power to hold the data;
A second memory that requires supply of power to hold the data,
Storing data processed in the communication device in the second memory;
Data that is processed in the communication device and that is to be stored to analyze an event that has occurred in the communication device is stored in the MRAM,
Moving the data stored in the MRAM to the first memory by the predetermined amount;
When the communication apparatus is started after the event occurs and the communication apparatus is stopped, the data stored in the MRAM is stored in the first memory. . The communication device according to claim 1,
The MRAM is
A first storage area for storing data processed in a first period including a time when an event occurs in the communication device;
A second storage area for storing data to be stored for a second period longer than the first period,
The communication device
Storing the new data in the first storage area by overwriting the old data with new data when stored in the first storage area;
After the communication apparatus is activated, data stored in the second storage area is stored in the first memory. The communication device according to claim 2,
Has a network interface,
A communication apparatus that stores a packet received via the network interface in the first storage area. The communication device according to claim 2,
The data processed in the communication device includes an event log indicating at least the content of an event that has occurred in the communication device,
The communication device
Holding definition information for determining whether the event log is the data to be stored;
From the data processed in the communication device, based on the definition information, extract an event log to be stored in order to analyze an event occurring in the communication device,
The extracted event log is stored in the second storage area. The communication device according to claim 2,
Holding management information indicating whether data stored in the MRAM is stored in the first memory;
When the data stored in the MRAM is stored in the first memory, the management information is updated,
When the communication device is started after an event occurs in the communication device and the communication device is stopped, data obtained by extracting data based on the management information from the data stored in the MRAM is stored in the first memory. A communication device characterized by storing. The communication device according to claim 1,
Has an output interface,
When an event occurs in the communication device and the communication device is stopped, the communication device is activated, and when data stored in the MRAM is stored in the first memory, the data is stored in the first memory. A notification indicating the above is output from the output interface. A data management method by a communication device,
The communication device
A processor for processing the data;
A first memory in which data is written for each predetermined amount and does not require supply of power to hold the data;
An MRAM in which data is written for each smaller amount than the predetermined amount and does not require the supply of power to hold the data;
A second memory that requires supply of power to hold the data,
The method
A procedure in which the processor stores data processed in the communication device in the second memory;
A procedure for storing, in the MRAM, data that is processed by the processor and is to be stored in order to analyze an event that has occurred in the communication device;
A procedure for the processor to move data stored in the MRAM to the first memory by the predetermined amount;
The processor stores the data stored in the MRAM in the first memory when the communication device is started after the event occurs in the communication device and the communication device is stopped; A data management method comprising: The data management method according to claim 7, comprising:
The MRAM is
A first storage area for storing data processed in a first period including a time when an event occurs in the communication device;
A second storage area for storing data to be stored for a second period longer than the first period,
The method
The processor stores the new data in the first storage area by overwriting the old data with new data when stored in the first storage area; and
A data management method comprising: a step of storing data stored in the second storage area in the first memory after the communication device is activated by the processor. The data management method according to claim 8, comprising:
The communication device has a network interface;
The method includes a procedure in which the processor stores a packet received via the network interface in the first storage area. The data management method according to claim 8, comprising:
The data processed in the communication device includes an event log indicating at least the content of an event that has occurred in the communication device,
The communication device holds definition information for determining whether or not the event log is the data to be stored,
The method
A procedure for the processor to extract an event log to be stored in order to analyze an event that has occurred in the communication device based on the definition information from data processed in the communication device;
And a procedure for the processor to store the extracted event log in the second storage area. The data management method according to claim 8, comprising:
The communication device holds management information indicating whether data stored in the MRAM is stored in the first memory;
The method
A procedure for updating the management information when the processor stores data stored in the MRAM in the first memory;
When the communication device is activated after an event occurs in the communication device and the communication device is stopped, the processor extracts data obtained by extracting data based on the management information from data stored in the MRAM. And a procedure for storing the data in one memory. The data management method according to claim 7, comprising:
The communication device has an output interface;
When the communication device is started after an event occurs in the communication device and the communication device is stopped, the procedure for storing the data stored in the MRAM in the first memory is as follows. A data management method comprising a step of outputting from the output interface a notification indicating that data has been stored in the memory.

Images