WO2014115264A1 - Procédé de traçage, programme et appareil informatique associé - Google Patents

Procédé de traçage, programme et appareil informatique associé Download PDF

Info

Publication number
WO2014115264A1
WO2014115264A1 PCT/JP2013/051295 JP2013051295W WO2014115264A1 WO 2014115264 A1 WO2014115264 A1 WO 2014115264A1 JP 2013051295 W JP2013051295 W JP 2013051295W WO 2014115264 A1 WO2014115264 A1 WO 2014115264A1
Authority
WO
WIPO (PCT)
Prior art keywords
layer
communication
port number
pdu
trace information
Prior art date
Application number
PCT/JP2013/051295
Other languages
English (en)
Japanese (ja)
Inventor
浩二 高原
規子 笛吹
Original Assignee
富士通株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社 filed Critical 富士通株式会社
Priority to PCT/JP2013/051295 priority Critical patent/WO2014115264A1/fr
Publication of WO2014115264A1 publication Critical patent/WO2014115264A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields

Definitions

  • This technology relates to the tracing technology of communication devices.
  • Trace information may be collected to analyze communication device failures.
  • a certain patent document discloses a technique for attaching the same related identifier to related trace information. This makes it easy to specify the correspondence between instructions in a single protocol layer.
  • Another patent document discloses a technique for collecting trace information from a plurality of protocol layers and editing it in time series.
  • the upper layer is used even if the correspondence relationship of the trace information in the same layer is specified or the time-series relationship of the trace information of a plurality of layers is specified. It is difficult to grasp the relationship between the trace information and the lower layer.
  • the purpose of this technology is, in one aspect, to make it easier to identify related trace information groups.
  • a tracing method is a tracing method executed by an apparatus that performs communication between an upper layer for communication using an upper communication protocol and a lower layer for communication using a lower communication protocol, the communication processing in the upper layer Including a process of acquiring trace information related to the execution of the process, and a process of associating a connection identifier and trace information relating to a lower layer connection when executing the communication process.
  • FIG. 1 is a diagram showing an outline of an iSCSI (Internet Small Computer Computer System Interface) environment.
  • FIG. 2 is a diagram illustrating a configuration example of the host machine.
  • FIG. 3 is a diagram illustrating an example of the converted trace information.
  • FIG. 4 is a diagram illustrating an example of a configuration related to activation of the tracer.
  • FIG. 5 is a diagram showing an overview of initial settings related to SCSI (Small Computer Interface) command reception.
  • FIG. 6 is a diagram showing an overview of initial settings related to PDU (Protocol Data Unit) transmission.
  • FIG. 7 is a diagram showing an outline of the initial setting related to PDU reception.
  • FIG. 8 is a diagram showing an outline of the initial setting related to the completion notification reply.
  • FIG. 1 is a diagram showing an outline of an iSCSI (Internet Small Computer Computer System Interface) environment.
  • FIG. 2 is a diagram illustrating a configuration example of the host machine.
  • FIG. 3 is a diagram illustrating an example
  • FIG. 9 is a diagram showing an outline of the device recognition operation.
  • FIG. 10 is a diagram showing an outline of the trace operation related to SCSI command reception.
  • FIG. 11 is a diagram illustrating an example of a SCSI command recording process flow.
  • FIG. 12 is a diagram showing an outline of the trace operation related to PDU transmission.
  • FIG. 13 is a diagram illustrating an example of a PDU transmission recording process flow.
  • FIG. 14 is a diagram showing an outline of the trace operation related to PDU reception.
  • FIG. 15 is a diagram illustrating an example of a port number securing process flow.
  • FIG. 16 is a diagram illustrating an example of a PDU reception recording process flow.
  • FIG. 17 is a diagram showing an outline of the trace operation related to the completion notification reply.
  • FIG. 18 is a diagram illustrating an example of a completion notification recording process flow.
  • FIG. 19 is a diagram illustrating an example of a conversion processing flow.
  • FIG. 20 is a functional block diagram of
  • Figure 1 shows an overview of the iSCSI environment.
  • the host machine 101 is connected to the iSCSI target device 105 via the transmission path 103.
  • the iSCSI target device 105 has a disk device 107.
  • FIG. 2 shows a configuration example of the host machine 101.
  • the host machine 101 has a multi-layer software group. Specifically, the host machine 101 includes an application software 201, a SCSI layer 203, an iSCSI layer 205, a TCP (Transmission Control Protocol) layer 207, an IP (Internet Protocol) layer 209, and a driver layer in order from the upper layer to the lower layer. 211 and NIC (Network Interface Card) 213.
  • an application software 201 includes an application software 201, a SCSI layer 203, an iSCSI layer 205, a TCP (Transmission Control Protocol) layer 207, an IP (Internet Protocol) layer 209, and a driver layer in order from the upper layer to the lower layer.
  • NIC Network Interface Card
  • the host machine 101 in this embodiment further includes a tracer 215, a trace information storage unit 217, a conversion unit 219, an output unit 221 and an analysis unit 223.
  • the tracer 215 collects trace information from the iSCSI layer 205 and the driver layer 211.
  • the trace information storage unit 217 stores the collected trace information and the converted trace information.
  • the conversion unit 219 converts the collected trace information.
  • the output unit 221 outputs the collected trace information and the converted trace information.
  • the output form may be any form such as transmission, display, and printing.
  • the analysis unit 223 analyzes the converted trace information. However, in the present embodiment, description of the analysis process is omitted.
  • the SCSI layer 203 transmits a SCSI command to the iSCSI layer 205.
  • the iSCSI layer 205 returns a SCSI command completion notification to the SCSI layer 203.
  • the tracer 215 acquires trace information related to the SCSI command and trace information related to the SCSI command completion notification.
  • the tracer 215 acquires the TCP port number together with the trace information related to the SCSI command. Further, the tracer 215 acquires the TCP port number together with the trace information related to the SCSI command completion notification.
  • the iSCSI layer 205 generates a PDU and transmits it to the TCP layer 207 during execution of the SCSI command. Further, the iSCSI layer 205 receives a PDU from the TCP layer 207 during execution of the SCSI command.
  • the tracer 215 obtains trace information regarding a PDU to be transmitted (hereinafter referred to as “transmission PDU”) and trace information regarding a received PDU (hereinafter referred to as “reception PDU”).
  • the tracer 215 acquires the TCP port number together with the trace information regarding the transmission PDU. Furthermore, the tracer 215 acquires the TCP port number together with the trace information regarding the received PDU.
  • the tracer 215 acquires trace information regarding the TCP packet from the driver layer 211.
  • the tracer 215 stores the trace information in the trace information storage unit 217.
  • the tracer 215 includes trace information and a TCP port number related to a SCSI command, trace information and a TCP port number related to a SCSI command completion notification, trace information and a TCP port number related to a transmission PDU, and trace information and a TCP port number related to a reception PDU.
  • trace information related to TCP packets are stored in the trace information storage unit 217.
  • the tracer 215 causes the trace information storage unit 217 to store the time at which the above-described information is acquired.
  • the conversion unit 219 extracts, for each TCP port number, trace information about the SCSI command, trace information about the SCSI command completion notification, trace information about the transmission PDU, trace information about the received PDU, and trace information about the TCP packet, and sorts them in time order. To do.
  • the output unit 221 outputs the trace information converted by the conversion unit 219.
  • the analysis unit 223 analyzes the trace information. For example, the analysis unit 223 analyzes the trace information converted by the conversion unit 219.
  • the output unit 221 may output the analysis result obtained by the analysis unit 223.
  • Figure 3 shows an example of converted trace information.
  • This example mainly shows an example of trace information whose TCP port number is “P01”.
  • the third column shows trace information regarding the TCP packet.
  • the fourth column shows trace information related to the transmission PDU and trace information related to the reception PDU.
  • the fifth column shows trace information related to the SCSI command and trace information related to the SCSI command completion notification.
  • the trace information is shown divided into the third column to the fifth column.
  • the trace information may not be divided into columns.
  • trace information relating to the same connection can be collected on condition that the same TCP port number is used.
  • the trace information is arranged in ascending order using the acquisition time as a key.
  • the trace information related to “SCSI command 01” acquired at time “T01” and the trace information related to “completion notification of SCSI command 01” acquired at time “T10” are acquired at time “T02”.
  • FIG. 4 shows an example of the configuration related to the activation of the tracer 215.
  • the iSCSI layer 205 includes a SCSI command reception unit 401, a PDU transmission unit 403, a PDU reception unit 405, a completion notification reply unit 407, and a control unit 409.
  • the SCSI command receiving unit 401 receives a SCSI command from the SCSI layer 203.
  • the PDU transmission unit 403 transmits the PDU to the TCP layer 207.
  • the PDU receiving unit 405 receives a PDU from the TCP layer 207.
  • the completion notification reply unit 407 returns a SCSI command completion notification to the SCSI layer 203.
  • the control unit 409 controls the operation of the iSCSI layer 205.
  • the tracer 215 includes a rewriting unit 411, a securing unit 413, a SCSI command recording unit 421, a PDU transmission recording unit 423, a PDU reception recording unit 425, a completion notification recording unit 427, and a port number securing unit 429.
  • the rewriting unit 411 rewrites a part of the program that realizes the iSCSI layer 205 and a part of the program that realizes the tracer 215. With this rewriting, the tracer 215 collects trace information in accordance with the operation of the iSCSI layer 205. The operation of the rewriting unit 411 will be described later with reference to FIGS.
  • the securing unit 413 secures a storage area to be the trace information storage unit 217.
  • the SCSI command recording unit 421 records trace information related to the SCSI command received from the SCSI layer 203.
  • the PDU transmission recording unit 423 records trace information regarding the transmission PDU.
  • the PDU reception recording unit 425 records trace information regarding the received PDU.
  • the completion notification recording unit 427 records trace information related to the completion notification of the SCSI command returned to the SCSI layer 203.
  • the port number securing unit 429 secures a TCP port number.
  • the initial setting by the rewriting unit 411 will be described. Specifically, the data collection point is set by the tracer 215.
  • FIG. 5 shows an overview of the initial settings related to SCSI command reception.
  • the program 501 shows a SCSI command reception function that implements the SCSI command reception unit 401 included in the iSCSI layer 205.
  • the program 501 is an executable program before rewriting.
  • FIG. 5 shows an example of a source format program for convenience.
  • the parameter input to the SCSI command reception function is the address of the SCSI packet structure.
  • the first programmed instruction of the SCSI command reception function is referred to as a first instruction
  • the next programmed instruction is referred to as a second instruction.
  • the program 511 indicates a SCSI command recording processing routine for realizing the SCSI command recording unit 421 included in the tracer 215.
  • the program 511 is an executable program before rewriting.
  • FIG. 5 shows an example of a source format program for convenience.
  • the SCSI command recording processing routine includes, in order, an instruction code for address acquisition processing, an instruction code for command acquisition processing, an instruction code for handle acquisition processing, an instruction code for port number acquisition processing, and an instruction code for association processing. . Furthermore, two nop codes that do not involve execution are included.
  • a part of the program 501 is rewritten by the rewriting unit 411, and the SCSI command reception function is in the state shown in the program 503. Specifically, the code of the first instruction programmed in the SCSI command reception function is rewritten to a code instructing a jump to SCSI command recording.
  • the nop code on the first line is rewritten with the code of the first instruction programmed in the SCSI command reception function.
  • the nop code on the second line is rewritten with a code for instructing a jump to the second instruction programmed in the SCSI command reception function.
  • FIG. 6 shows an overview of the initial settings related to PDU transmission.
  • a program 601 shows a PDU transmission function for realizing the PDU transmission unit 403 included in the iSCSI layer 205.
  • the program 601 is an executable program before rewriting.
  • FIG. 6 shows an example of a source format program for convenience.
  • the parameters input to the PDU transmission function are a TCP connection handle and a PDU.
  • the first programmed instruction of the PDU transmission function is referred to as a first instruction, and the next programmed instruction is referred to as a second instruction.
  • the program 611 shows a PDU transmission recording processing routine for realizing the PDU transmission recording unit 423 included in the tracer 215.
  • the program 611 is an executable program before rewriting.
  • FIG. 6 shows an example of a source format program for convenience.
  • the processing routine for PDU transmission recording includes, in order, an instruction code for handle acquisition processing, an instruction code for PDU acquisition processing, an instruction code for port number acquisition processing, and an instruction code for association processing. Furthermore, two nop codes that do not involve execution are included.
  • a part of the program 601 is rewritten by the rewriting unit 411, and the PDU transmission function is in the state shown in the program 603. Specifically, the code of the first instruction programmed in the PDU transmission function is rewritten with a code instructing a jump to the PDU transmission record.
  • the nop code on the first line is rewritten with the code of the first instruction programmed in the PDU transmission function.
  • the nop code on the second line is rewritten with a code that instructs a jump to the second instruction programmed in the PDU transmission function.
  • the process jumps to the PDU transmission record shown in the program 613, and the handle acquisition process is executed. Furthermore, a PDU acquisition process is executed, a port number acquisition process is executed, and an association process is executed.
  • processing by the first instruction is executed, and the process jumps to the second instruction. Then, processing according to the second command of the PDU transmission function shown in the program 603 is executed. Details of the processing routine for PDU transmission recording will be described later with reference to FIGS.
  • FIG. 7 shows an overview of the initial settings related to PDU reception.
  • a program 701 shows a control processing routine for realizing the control unit 409 included in the iSCSI layer 205.
  • an instruction following the call of the PDU reception function is referred to as a third instruction.
  • the program 703 shows a PDU reception function for realizing the PDU reception unit 405 included in the iSCSI layer 205.
  • the program 703 is an executable program before rewriting.
  • FIG. 7 shows an example of a source format program for convenience.
  • the parameters input to the PDU reception function are the TCP connection handle and the address of the PDU storage area.
  • the first programmed instruction of the PDU reception function is referred to as a first instruction, and the next programmed instruction is referred to as a second instruction.
  • the PDU reception function includes an instruction code for standby processing and an instruction code for reception processing. Further, the PDU reception function is programmed to return to the third instruction of the program 701 by a return code.
  • the program 711 shows a port number securing processing routine for realizing the port number securing unit 429 included in the tracer 215 and a PDU receiving recording processing routine for realizing the PDU receiving recording unit 425.
  • the program 711 is an executable program before rewriting.
  • FIG. 7 shows an example of a source format program for convenience.
  • the processing routine for securing the port number includes, in order, an instruction code for handle acquisition processing, an instruction code for port number acquisition processing, and an instruction code for holding processing. Furthermore, two nop codes that do not involve execution are included.
  • the processing routine for PDU reception recording includes, in order, an instruction code for PDU acquisition processing, an instruction code for handle acquisition processing, an instruction code for port number identification processing, and an instruction code for association processing. Furthermore, one nop code without execution is included.
  • a part of the program 703 is rewritten by the rewriting unit 411, and the PDU reception function is in the state shown in the program 707.
  • the code of the first instruction programmed in the PDU reception function is rewritten with a code instructing a jump to secure the port number.
  • the return code is rewritten to a code for instructing a jump to PDU reception recording.
  • a part of the program 711 is rewritten by the rewriting unit 411, and the port number securing processing routine and the PDU reception recording processing routine are in the state shown in the program 713.
  • the nop code on the first line is rewritten with the code of the first instruction programmed in the PDU reception function.
  • the nop code on the second line is rewritten with a code for instructing a jump to the second instruction programmed in the PDU reception function.
  • the nop code is rewritten with a code for instructing a jump to the third instruction programmed in the control processing routine.
  • standby processing and reception processing included in the PDU reception function are executed.
  • the standby process the PDU is received.
  • the reception process the PDU is actually received.
  • FIG. 8 shows an overview of the initial settings relating to the completion notification reply.
  • the program 801 shows a completion notification reply function that implements the completion notice reply unit 407 included in the iSCSI layer 205.
  • the program 801 is an executable program before rewriting.
  • FIG. 8 shows an example of a source format program for convenience.
  • the parameter input to the completion notification reply function is the address of the SCSI packet structure.
  • the first programmed instruction of the completion notification reply function is referred to as a first instruction
  • the next programmed instruction is referred to as a second instruction.
  • the program 811 shows a processing routine for completion notification recording that realizes the completion notification recording unit 427 included in the tracer 215.
  • the program 811 is an executable program before rewriting.
  • FIG. 8 shows an example of a source format program for convenience.
  • the completion notification recording processing routine includes, in order, an instruction code for address acquisition processing, an instruction code for completion notification acquisition processing, an instruction code for handle acquisition processing, an instruction code for port number identification processing, and an instruction code for association processing. Yes. Furthermore, two nop codes that do not involve execution are included.
  • a part of the program 801 is rewritten by the rewriting unit 411, and the completion notification reply function is in the state shown in the program 803. Specifically, the code of the first instruction programmed in the completion notification reply function is rewritten to a code instructing a jump to the completion notification record.
  • a part of the program 811 is rewritten by the rewriting unit 411, and the processing routine for recording the completion notification is in the state shown in the program 813.
  • the nop code on the first line is rewritten to the code of the first instruction programmed in the completion notification reply function.
  • the nop code in the second line is rewritten with a code that instructs a jump to the second instruction programmed in the completion notification reply function.
  • FIG. 9 shows an outline of the device recognition operation.
  • the iSCSI setting unit 913 instructs the iSCSI layer 205 to recognize the SCSI device
  • the iSCSI layer 205 instructs the TCP layer 207 to generate a TCP connection.
  • the TCP layer 207 generates a TCP connection structure 903 in the memory area managed by the TCP layer 207.
  • the TCP connection structure 903 includes a local TCP port number 905 and a remote TCP port number 907. A different number is assigned to the local TCP port number 905 for each connection.
  • a unique number “3260” in iSCSI is set.
  • the TCP port number is an example of a connection identifier.
  • the TCP layer 207 generates a TCP connection handle 901 for specifying a TCP connection, and links the TCP connection handle 901 and the TCP connection structure 903 in a system-specific manner.
  • the TCP connection handle 901 is information for specifying a connection in the TCP layer 207.
  • TCP connection handle 901 and the TCP connection structure 903 are linked.
  • an intermediate structure that stores the address of the TCP connection structure 903 at a predetermined offset is assumed.
  • the TCP connection handle 901 uses the leading address of the intermediate structure.
  • the address of the TCP connection structure 903 is read from the address obtained by adding a predetermined offset to the TCP connection handle 901.
  • the local TCP port number 905 is read from the TCP connection structure 903.
  • another method may be sufficient as the method of making it cooperate.
  • the TCP layer 207 passes the generated TCP connection handle to the iSCSI layer 205.
  • the iSCSI layer 205 generates an iSCSI connection structure 909 in a memory area managed by the iSCSI layer 205, and stores a TCP connection handle 911 in the generated iSCSI connection structure 909. Then, the iSCSI layer 205 notifies the SCSI layer 203 that the SCSI device has been recognized. This is the end of the description of the operation for recognizing the iSCSI target device 105 as a SCSI device.
  • FIG. 10 shows an outline of the trace operation related to SCSI command reception.
  • the SCSI layer 203 passes the SCSI command to the iSCSI layer 205 and instructs the iSCSI layer 205 to prepare for transmission.
  • the iSCSI layer 205 generates a SCSI packet structure 1001 in a memory area managed by the iSCSI layer 205, and stores the contents of the SCSI command in the SCSI packet structure 1001.
  • the iSCSI layer 205 determines an iSCSI connection structure 909 to be used for this SCSI command, and stores the head address in the SCSI packet structure 1001. That is, the iSCSI packet structure 1001 points to the iSCSI connection structure 909. Then, the iSCSI layer 205 returns the address of the SCSI packet structure 1001 to the SCSI layer 203.
  • the SCSI layer 203 instructs the iSCSI layer 205 to transmit a SCSI command using the address of the SCSI packet structure 1001. This instruction corresponds to calling the SCSI command reception function shown in FIG.
  • FIG. 11 shows an example of a SCSI command recording process flow. This process corresponds to the SCSI command recording process shown in FIG.
  • the address acquisition unit 1011 acquires the address of the SCSI packet structure 1001 from the SCSI command reception unit 401 in the address acquisition process (S1101).
  • the command acquisition unit 1013 reads the SCSI command 1003 included in the SCSI packet structure 1001 in the command acquisition process (S1103).
  • the handle acquisition unit 1015 reads the start address 1005 of the iSCSI connection structure included in the SCSI packet structure 1001, and further reads the TCP connection handle 911 included in the iSCSI connection structure 909.
  • the port number acquisition unit 1017 follows the cooperation in the TCP layer 207 based on the TCP connection handle 911 and reads the local TCP port number 905.
  • the associating unit 1019 writes the trace information related to the SCSI command and the local TCP port number together with the current time in the trace information storage unit 217.
  • the SCSI command recording unit 421 executes processing according to the first command included in the SCSI command reception function (S1111).
  • the process jumps to the second instruction included in the SCSI command reception function and returns to the normal SCSI command reception function processing. This is the end of the description of the trace operation when the iSCSI command is received by the iSCSI layer 205.
  • FIG. 12 shows an outline of the trace operation related to PDU transmission.
  • the control unit 409 generates a PDU according to the SCSI command 1003. Then, the control unit 409 passes the TCP connection handle and PDU to the PDU transmission unit 403 and instructs transmission of the PDU. This instruction corresponds to calling the PDU transmission function shown in FIG.
  • FIG. 13 shows an example of a PDU transmission recording process flow. This process corresponds to the PDU transmission recording process shown in FIG.
  • the handle acquisition unit 1015 acquires a TCP connection handle from the PDU transmission unit 403 in the handle acquisition process (S1301).
  • the PDU acquisition unit 1211 acquires the PDU to be transmitted from the PDU transmission unit 403 in the PDU acquisition process (S1303).
  • the port number acquisition unit 1017 follows the cooperation in the TCP layer 207 based on the TCP connection handle 901 and reads the local TCP port number 905 in the port number acquisition process (S1305).
  • the associating unit 1019 writes the trace information regarding the PDU to be transmitted and the local side TCP port number in association with the current time, in the trace information storage unit 217.
  • the PDU transmission recording unit 423 executes processing according to the first command included in the PDU transmission function (S1309).
  • the process jumps to the second instruction included in the PDU transmission function, and returns to the normal PDU transmission function processing. Then, the PDU transmission unit 403 transmits a TCP connection handle and PDU to the TCP layer 207. This is the end of the description of the trace operation when the iSCSI layer 205 transmits a PDU to the TCP layer 207.
  • FIG. 14 shows an outline of the trace operation related to PDU reception.
  • the control unit 409 passes the TCP connection handle and the address of the PDU storage area 1401 to the PDU reception unit 405 and instructs reception of the PDU. This instruction corresponds to calling the PDU reception function shown in FIG.
  • the port number securing unit 429 starts the port number securing process.
  • the local TCP port number 1415 corresponding to the TCP connection handle 901 is secured before actually receiving the PDU.
  • FIG. 15 shows an example of a port number securing process flow. This process corresponds to the port number securing process shown in FIG.
  • the handle acquisition unit 1015 acquires a TCP connection handle from the PDU reception unit 405 in the handle acquisition process (S1501).
  • the port number acquisition unit 1411 follows the cooperation in the TCP layer 207 based on the TCP connection handle 901 and reads the local TCP port number 905 in the port number acquisition process (S1503).
  • the port number securing unit 429 stores the TCP connection handle 1417 and the local TCP port number 1415 in the storage unit 1413 in association with each other in the holding process (S1505). A plurality of pairs of the TCP connection handle 1417 and the local side TCP port number 1415 may be held.
  • the port number securing unit 429 executes processing according to the first command included in the PDU reception function (S1507).
  • the process jumps to the second command included in the PDU reception function and returns to the normal PDU reception function processing.
  • the PDU receiving unit 405 performs standby processing.
  • the PDU reception unit 405 calls the reception function of the TCP layer 207.
  • the PDU receiving unit 405 passes the TCP connection handle to the TCP layer 207 and waits for the reception of the PDU.
  • the PDU reception unit 405 receives data from the TCP layer 207 by reception processing.
  • the PDU receiving unit 405 generates a PDU from the received data, and stores the generated PDU in the PDU storage area 1401.
  • FIG. 16 shows an example of a PDU reception recording process flow. This process corresponds to the PDU reception recording process shown in FIG.
  • the PDU acquisition unit 1211 acquires the received PDU from the PDU reception unit 405 in the PDU acquisition process (S1601).
  • the handle acquisition unit 1015 acquires a TCP connection handle from the PDU reception unit 405 in the handle acquisition process (S1603).
  • the port number specifying unit 1419 specifies the local TCP port number 1415 associated with the TCP connection handle 1417 in the storage unit 1413 in the port number specifying process (S1605).
  • the associating unit 1019 writes the received trace information about the PDU and the local TCP port number 1415 together with the current time in the trace information storage unit 217.
  • FIG. 17 shows an outline of the trace operation related to the completion notification reply.
  • the control unit 409 searches for a SCSI packet structure 1001 corresponding to the generated PDU.
  • the control unit 409 generates a SCSI command completion notification based on the content of the PDU, and stores the SCSI command completion notification in the SCSI packet structure 1001.
  • the control unit 409 passes the address of the SCSI packet structure 1001 to the completion notification reply unit 407 and instructs the SCSI command completion notification to be returned. This instruction corresponds to calling the completion notification reply function shown in FIG.
  • FIG. 18 shows an example of a completion notification recording process flow. This process corresponds to the completion notification recording process shown in FIG.
  • the address acquisition unit 1011 acquires the address of the SCSI packet structure 1001 from the completion notification reply unit 407 in the address acquisition process (S1801).
  • the completion notification acquisition unit 1711 reads the SCSI command completion notification 1701 from the SCSI packet structure 1001 in the completion notification acquisition process (S1803).
  • the handle acquisition unit 1015 reads the start address 1005 of the iSCSI connection structure included in the SCSI packet structure 1001, and further reads the TCP connection handle 911 included in the iSCSI connection structure 909.
  • the port number specifying unit 1713 specifies the local TCP port number 1415 associated with the TCP connection handle 1417 in the storage unit 1413 in the port number specifying process (S1807).
  • the associating unit 1019 writes the trace information related to the SCSI command completion notification 1701 and the local TCP port number 1415 together with the current time in association with the trace information storage unit 217.
  • the completion notification recording unit 427 executes processing according to the first command included in the completion notification reply function before rewriting (S1811).
  • the process jumps to the second command included in the completion notification reply function and returns to the normal completion notification reply function processing. This is the end of the description of the trace operation when the iSCSI layer 205 returns a SCSI command completion notification.
  • FIG. 19 shows an example of the conversion processing flow.
  • the conversion unit 219 generates trace information arranged in order of time for each TCP port number as illustrated in FIG. 3 by the conversion process.
  • the conversion unit 219 identifies one unprocessed TCP port number that has not yet been converted (S1901).
  • the identified TCP port number is a key for extracting trace information.
  • the conversion unit 219 extracts trace information related to the SCSI command including the TCP port number (S1903).
  • the conversion unit 219 extracts trace information regarding the transmission PDU including the TCP port number (S1905).
  • the conversion unit 219 extracts trace information regarding the received PDU including the TCP port number (S1907).
  • the conversion unit 219 extracts trace information regarding the SCSI command completion notification 1701 including the TCP port number (S1909).
  • the conversion unit 219 extracts trace information regarding the TCP packet including the TCP port number (S1911). Then, the conversion unit 219 sorts the extracted trace information group in descending order of time (S1913). This completes the processing related to the TCP port number.
  • the conversion unit 219 determines whether there is an unprocessed TCP port number (S1915). If it is determined that there is an unprocessed TCP port number, the process returns to S1901 to continue the conversion process. If it is determined that there is no unprocessed TCP port number, the conversion process is terminated. Above, description about the conversion process by the conversion part 219 is finished.
  • an example of a multi-layer is shown in FIG. 2, but a configuration of another communication layer may be used.
  • the example in which the iSCSI layer 205 is a trace target has been described, but the trace target is not limited to the iSCSI layer 205.
  • Other protocol layers may be traced.
  • an example in which the connection of the TCP layer 207 is specified by the TCP port number is shown, but a connection in another protocol layer may be specified by another connection identifier.
  • the connection of the TCP layer 207 can be specified for the trace information of the iSCSI layer 205. This is useful for collecting the trace information group of the iSCSI layer 205 related to the same TCP connection, for example. Further, if the TCP port number is specified from the trace information of the TCP layer 207, the relationship between the trace information of the iSCSI layer 205 and the trace information of the TCP layer 207 related to the same connection can be specified.
  • the port number is acquired before the communication process in the iSCSI layer 205 is executed, it is possible to avoid a situation in which the port number cannot be acquired by closing the connection after the communication process is executed.
  • connection identification information such as a TCP connection handle
  • a TCP port number that cannot be directly identified from trace information (such as a SCSI command, transmission PDU, reception PDU, or SCSI command completion notification) can be acquired from the TCP layer 207. Become.
  • the TCP port number for specifying the TCP connection is specified from the plurality of TCP port numbers acquired before the execution of the communication process in the iSCSI layer 205, even when the TCP connection is closed after the execution of the communication process, The TCP port number can be specified reliably.
  • the TCP port number at the time of execution can be specified based on the connection specifying information such as the TCP connection handle.
  • the present technology has been described above, but the present technology is not limited to this.
  • the functional block configuration described above may not match the actual program module configuration.
  • each storage area described above is an example, and the configuration as described above is not necessarily required. Further, in the processing flow, the processing order can be changed if the processing result does not change. Further, it may be executed in parallel.
  • the host machine 101 described above is a computer device, and as shown in FIG. 20, a memory 2501, a CPU (Central Processing Unit) 2503, a hard disk drive (HDD: Hard Disk Drive) 2505, and a display device 2509.
  • a display control unit 2507 connected to the computer, a drive device 2513 for a removable disk 2511, an input device 2515, and a communication control unit 2517 for connecting to a network are connected by a bus 2519.
  • An operating system (OS: Operating System) and an application program for performing the processing in this embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503.
  • OS Operating System
  • the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 according to the processing content of the application program, and performs a predetermined operation. Further, data in the middle of processing is mainly stored in the memory 2501, but may be stored in the HDD 2505. In an embodiment of the present technology, an application program for performing the above-described processing is stored in a computer-readable removable disk 2511 and distributed, and installed from the drive device 2513 to the HDD 2505. In some cases, the HDD 2505 may be installed via a network such as the Internet and the communication control unit 2517. Such a computer apparatus realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above and programs such as the OS and application programs. .
  • the tracing method according to the present embodiment is a tracing method executed by a device that performs communication using an upper layer for communication using an upper communication protocol and a lower layer for communication using a lower communication protocol.
  • connection identifier is specified from the lower layer trace information, the relationship between the upper layer trace information and the lower layer trace information related to the same connection can be specified.
  • connection identifier may be a port number.
  • trace method may include an acquisition process for acquiring a port number before the execution of the communication process.
  • the port number may be acquired based on the connection specifying information in the lower layer.
  • connection identification information such as the connection handle in this way, the port number that cannot be identified directly from the trace information can be acquired from the lower layer.
  • connection identifier may be a port number.
  • the tracing method may include a process of acquiring a port number related to a lower layer connection and holding the acquired port number before executing the communication process.
  • the trace method may include a specifying process for specifying a port number to be associated with the trace information from among the plurality of held port numbers.
  • the port number that identifies the connection is identified from the plurality of port numbers acquired before the execution of the communication process, so even if the connection is closed after the execution of the communication process, the port number is guaranteed Can be identified.
  • the port number to be associated with the trace information may be specified based on the connection specifying information in the lower layer.
  • the port number at the time of execution can be specified based on the connection specifying information such as the connection handle.
  • the upper layer may be an iSCSI layer.
  • the lower layer may be a TCP layer.
  • the TCP port number can be associated with the iSCSI layer trace information.
  • the upper layer may be an iSCSI layer.
  • the lower layer may be a TCP layer.
  • the communication process may include at least one of a command reception process from the SCSI layer and a PDU transmission process to the TCP layer.
  • the TCP port number can be acquired even when the TCP connection is closed after the command reception process from the SCSI layer or the PDU transmission process to the TCP layer.
  • the upper layer may be an iSCSI layer.
  • the lower layer may be a TCP layer.
  • the communication process may include at least one of a PDU reception process from the TCP layer and a command completion notification return process to the SCSI layer.
  • the TCP port number can be reliably identified.
  • a program for causing a computer to carry out the processing described above such as a flexible disk, an optical disk such as a CD-ROM, a magneto-optical disk, a semiconductor memory (for example, ROM). Or a computer-readable storage medium such as a hard disk or a storage device. Note that data being processed is temporarily stored in a storage device such as a RAM.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Debugging And Monitoring (AREA)

Abstract

Le procédé de traçage présenté est exécuté par un appareil de communication qui utilise une couche supérieure pour communiquer en utilisant un protocole de communication supérieur et une couche inférieure pour communiquer en utilisant un protocole de communication inférieur. Le procédé de traçage comprend : un processus conçu pour acquérir des informations de traçage relatives à l'exécution d'un processus de communication de couche supérieure; et un processus conçu pour associer un identificateur de connexion en fonction d'une connexion de couche inférieure lors de l'exécution du processus de communication, et les informations de traçage. Une connexion de couche inférieure peut être spécifiée pour les informations de traçage de couche supérieure, ce qui simplifie la spécification de groupes d'informations de traçage apparentés.
PCT/JP2013/051295 2013-01-23 2013-01-23 Procédé de traçage, programme et appareil informatique associé WO2014115264A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2013/051295 WO2014115264A1 (fr) 2013-01-23 2013-01-23 Procédé de traçage, programme et appareil informatique associé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2013/051295 WO2014115264A1 (fr) 2013-01-23 2013-01-23 Procédé de traçage, programme et appareil informatique associé

Publications (1)

Publication Number Publication Date
WO2014115264A1 true WO2014115264A1 (fr) 2014-07-31

Family

ID=51227081

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/051295 WO2014115264A1 (fr) 2013-01-23 2013-01-23 Procédé de traçage, programme et appareil informatique associé

Country Status (1)

Country Link
WO (1) WO2014115264A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01274545A (ja) * 1988-04-27 1989-11-02 Nippon Telegr & Teleph Corp <Ntt> マルチ・レイヤ・トレーサ
JPH05314040A (ja) * 1992-05-14 1993-11-26 Hitachi Ltd トレース方式
JPH0678021A (ja) * 1992-05-21 1994-03-18 Nec Corp トランスポートプロトコルマシン実装方式

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01274545A (ja) * 1988-04-27 1989-11-02 Nippon Telegr & Teleph Corp <Ntt> マルチ・レイヤ・トレーサ
JPH05314040A (ja) * 1992-05-14 1993-11-26 Hitachi Ltd トレース方式
JPH0678021A (ja) * 1992-05-21 1994-03-18 Nec Corp トランスポートプロトコルマシン実装方式

Similar Documents

Publication Publication Date Title
US8744668B2 (en) Automotive diagnostic server
US6263444B1 (en) Network unauthorized access analysis method, network unauthorized access analysis apparatus utilizing the method, and computer-readable recording medium having network unauthorized access analysis program recorded thereon
CN101699360B (zh) 用于数控机床的远程诊断方法及系统
CN102438173A (zh) 一种远程控制机顶盒的方法及系统
JP2016111646A (ja) 車両データのリモート収集システム
CN105978979A (zh) 一种linux车载系统异常诊断系统及其诊断方法
CN110595799A (zh) 一种无人驾驶汽车的测试方法、装置、设备及储存介质
CN102426548B (zh) 嵌入式系统的调试方法、调试器和调试系统
Leno et al. Robidium: automated synthesis of robotic process automation scripts from UI logs
CN104899070B (zh) 设备命令行的实现方法、系统与装置
CN113591422B (zh) 芯片验证中测试案例流程信息的生成系统及应用
CN109962823B (zh) 一种网络应用场景的自动化测试系统及方法
CN106789205A (zh) 机群命令运行方法及系统
WO2014115264A1 (fr) Procédé de traçage, programme et appareil informatique associé
CN112235296B (zh) 一种医学影像数据采集方法、系统及电子设备和存储介质
KR101795895B1 (ko) 연동 검증 시스템 및 이를 사용한 연동 검증 방법
US8458669B2 (en) Automated test system
WO2012139329A1 (fr) Procédé et dispositif de mise à niveau s&#39;appuyant sur un modèle de tâche, et système de mise à niveau par lots
JP4257364B2 (ja) 通信エラー情報出力プログラム、通信エラー情報出力方法および通信エラー情報出力装置
CN107330173B (zh) 集成电路后端设计自动化系统
CN112905437A (zh) 一种测试用例的方法、装置及存储介质
KR101982308B1 (ko) 프로토콜 모델 생성 장치 및 모델링 방법
CN106571957B (zh) 一种mvb动态配置方法及装置
JP6097054B2 (ja) 制御システム及び制御方法
CN109165513A (zh) 系统配置信息的巡检方法、装置和服务器

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13872517

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13872517

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP