WO2009012662A1

WO2009012662A1 - A method and system for data communication and an internet small computer systems interface controller

Info

Publication number: WO2009012662A1
Application number: PCT/CN2008/070521
Authority: WO
Inventors: Liyao Chen; Bin Xiao; Mingjun Xu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-07-20
Filing date: 2008-03-18
Publication date: 2009-01-29
Also published as: CN101076012A; CN101076012B

Abstract

A method for data communication and an Internet Small Computer Systems Interface controller are provide. The method includes: at least one mirroring iSCSI controller is preset for each iSCSI controller; the mirroring iSCSI controller detects that the mirrored iSCSI controller corresponding to the mirroring iSCSI controller is failure; then the service information of the mirrored iSCSI controller is added into the mirroring iSCSI controller; the mirroring iSCSI controller receives the register request sent by the iSCSI host to register to the mirrored iSCSI controller originally; the mirroring iSCSI controller communicates the data with the iSCSI host according to the service information.

Description

Data communication method, system and internet small computer system interface controller The application claims to be submitted to the Chinese Patent Office on July 20, 2007, the application number is 200710129984.3, and the invention name is "data communication method, system and internet small computer system interface controller" The priority of the Chinese Patent Application, the entire contents of which is incorporated herein by reference. Technical field

The present invention relates to the field of data communication technologies, and in particular, to a data communication method and system, and an interface controller for an internet small computer system.

Background technique

After entering the information age, the amount of information has surged, placing higher demands on the capacity, performance, and reliability of storage devices. For resource sharing, centralized management, and security considerations, it is often necessary to use distributed networking between hosts and storage devices. Supporting high-bandwidth, long-distance connection technologies in this networking mode is particularly important.

The Internet Small Computer Systems Interface (iSCSI) is a standard developed by the Internet Engineering Task Force (IETF) in 2003 to map SCSI data blocks into Ethernet data packets. iSCSI can be used to build an IP storage area network. In this way, iSCSI overcomes the limitations of direct-attached storage, enabling storage resources across different servers and across geographies, and expanding storage capacity without downtime.

Figure 1 shows the existing flow chart for data communication using iSCSI technology. As shown in Figure 1, the specific steps are as follows:

Step 101: The iSCSI controller runs the iSCSI target service program on the IP address of the service network port.

Step 102: The iSCSI host sends a login request message to the iSCSI controller according to the IP address and port number of the iSCSI controller configured.

Step 103: The iSCSI controller receives the login request message, performs login related processing, and completes the processing, and notifies the iSCSI host that the login is successful.

Step 104: The iSCSI host performs data communication with the iSCSI controller.

An iSCSI host can write data to an iSCSI controller or read data from an iSCSI controller.

As can be seen from the above process: The iSCSI target uses a single controller mode, that is, the iSCSI host only Can establish a connection with an iSCSI controller. When the connection link between the iSCSI host and the iSCSI controller fails or the iSCSI controller itself fails, data consistency and service continuity cannot be guaranteed, and data communication stability and Poor reliability.

Summary of the invention

Embodiments of the present invention provide a data communication method and system, and an iSCSI controller to improve reliability of data communication between an iSCSI host and an iSCSI controller.

The technical solution of the embodiment of the present invention is implemented as follows:

It should be noted that, in the embodiment of the present invention, if the iSCSI controller b is a mirrored iSCSI controller of the iSCSI controller a, the iSCSI controller a is referred to as the mirrored iSCSI controller of the iSCSI controller b.

A data communication method that pre-sets at least one mirrored iSCSI controller for each iSCSI controller, including:

The mirrored iSCSI controller detects that the mirrored iSCSI controller corresponding to the mirrored iSCSI controller is invalid;

Adding the service information of the mirrored iSCSI controller to the mirrored iSCSI controller; the mirrored iSCSI controller receives a login request sent by an iSCSI host originally logged into the mirrored iSCSI controller;

The mirrored iSCSI controller performs data communication with the iSCSI host based on the service information.

A data communication system comprising:

The iSCSI host is configured to re-initiate the login request, log in to the mirrored iSCSI controller corresponding to the mirrored iSCSI controller, and perform data with the mirrored iSCSI controller when the detected mirrored iSCSI controller fails to be logged in. Communication

Mirroring the iSCSI controller, configured to add the service information of the mirrored iSCSI controller to itself, and receive the original login to the mirrored iSCSI controller, when detecting that the mirrored iSCSI controller corresponding thereto fails The login request sent by the iSCSI host communicates with the iSCSI host originally logged into the mirrored iSCSI controller according to the service information.

An iSCSI controller that includes:

Mirror failure handling module, used to detect the mirrored iSCSI controller corresponding to itself Adding the service information of the mirrored iSCSI controller to itself;

A data processing module is configured to perform data communication with an iSCSI host that is originally logged into the mirrored iSCSI controller.

Compared with the prior art, the embodiment of the present invention sets at least one mirrored iSCSI controller for each iSCSI controller in advance, and when the mirrored iSCSI controller finds that its mirrored iSCSI controller fails, the mirrored iSCSI controller is The service information is added to itself, receives a login request sent from the iSCSI host that is logged in to the mirrored iSCSI controller, accepts the login request, and performs data communication with the iSCSI host according to the service information. Improve the reliability of data communication.

DRAWINGS

Figure 1 is a flow chart of data communication using the existing iSCSI technology;

2 is a flowchart of an iSCSI host logging in to an iSCSI controller and performing data communication according to an embodiment of the present invention;

FIG. 3 is a flowchart of data communication when a home iSCSI controller fails according to an embodiment of the present invention; FIG. 4 is a flow chart of data communication after a home iSCSI controller returns to normal according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a typical networking diagram of data communication using iSCSI technology according to an embodiment of the present invention; FIG.

6 is a schematic structural diagram of a data communication system according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a mirror failure processing module in an iSCSI controller according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a mirror recovery processing module in an iSCSI controller according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a recovery processing module in an iSCSI controller according to an embodiment of the present invention.

detailed description

In the embodiment of the present invention, for each iSCSI controller, at least one iSCSI controller is selected in advance among all other iSCSI controllers as a mirrored iSCSI controller of the iSCSI controller, for each iSCSI controller and its mirror. iSCSI controller sets different IP addresses, will iSCSI host The IP address and port number of an accessible iSCSI controller are configured on the iSCSI host and can have the same name for each iSCSI controller and its mirrored iSCSI controller; a home iSCSI control can be set for each iSCSI host The iSCSI controller maintains the association between the iSCSI host ID (eg, the initiator name) and the IP address of the home iSCSI controller.

The following iSCSI controller B is the mirrored iSCSI controller of iSCSI controller A, and iSCSI controller A is the home iSCSI controller of iSCSI host 1, and the IP address and port number of iSCSI controller B are configured on iSCSI host 1 as For example, the embodiments of the present invention are described in detail.

2 is a flowchart of an iSCSI host logging in to an iSCSI controller and performing data communication according to an embodiment of the present invention. As shown in FIG. 2, the specific steps are as follows:

Step 201: The iSCSI controller A is started, and the iSCSI target server service program is run on the IP address of all the service network ports; the iSCSI controller B is started, and the iSCSI target server service program is run on the IP address of all the service network ports.

There is at least one service network port on each iSCSI controller, and at least one IP address is configured on each service network port.

Step 202: The iSCSI host 1 establishes a temporary discovery session with the iSCSI controller B according to the IP address of its own iSCSI controller B: IPB1, and obtains the name of the iSCSI controller B through the session.

Step 203: The iSCSI host 1 sends a login request message to the iSCSI controller B, which carries the initiator name of the iSCSI host 1.

The iSCSI host 1 can be configured with an IP address of the iSCSI controller B. It can also be configured with two or more IP addresses of the iSCSI controller B. The iSCSI host 1 can be configured to initiate a login request at any of its own IP addresses. .

Step 204: The iSCSI controller B receives the login request message, and obtains the iSCSI host 1 attributed iSCSI host 1 according to the initiator name of the iSCSI host 1 carried in the message and the association between the saved initiator name and the IP address of the home iSCSI controller. IP address of the controller: IPA1.

The association between the initiator name of the iSCSI host and the IP address of the home iSCSI controller can be: An algorithm for calculating the IP address of the home iSCSI controller by using the initiator name of the iSCSI host as a parameter.

Step 205: The iSCSI controller B detects that the IP address of the IPA1 is not the IP address of the iSCSI host 1, and sends the IPA1 to the iSCSI host 1 in the redirect request message. The IP address of the iSCSI host 1 login is IPB1 used by iSCSI host 1 to initiate a login request in step 202.

Step 206: The iSCSI host 1 receives the redirect request message, and establishes a temporary discovery session with the iSCSI controller A pointed to by the IPA1 according to the IPA1 carried by the message, and obtains the name of the iSCSI controller A through the session.

Step 207: The iSCSI host 1 sends a login request message to the iSCSI controller A pointed to by the IPA1, where the message carries the initiator name of the iSCSI host 1.

Step 208: The iSCSI controller A receives the login request message, and obtains the iSCSI control of the iSCSI host 1 according to the initiator name of the iSCSI host 1 carried by the message and the association between the name of the initialized initiator and the IP address of the home iSCSI controller. IP address of device A: IPA1.

Step 209: The iSCSI controller A detects that the IP address of the iSCSI host is the IP address of the iSCSI host 1 and performs the login related processing. After the processing is completed, the iSCSI host 1 is notified that the login is successful.

The login related processing includes: processing of parameter negotiation, security authentication, and the like.

Step 210: The iSCSI host 1 performs data communication with the iSCSI controller A.

The iSCSI controller A stores the data sent from the iSCSI host 1 to the storage medium accessible to both the iSCSI controller A and the iSCSI controller B. The iSCSI host 1 can read data from the storage medium.

As shown in the process shown in Figure 2, each iSCSI host has a home iSCSI controller. When the initial login, the iSCSI host logs in to the home iSCSI controller. This ensures that all iSCSI host traffic is evenly distributed. On each iSCSI controller, load sharing between iSCSI controllers is implemented.

The following is given when the connection link between iSCSI host 1 and the home iSCSI controller, ie iSCSI controller A, fails or iSCSI controller A itself fails, ie: iSCSI controller A fails, by iSCSI controller A The mirrored iSCSI controller, iSCSI controller B, takes over the process of data communication between iSCSI controller A and the iSCSI host that was originally logged into iSCSI controller A.

FIG. 3 is a flowchart of data communication when a home iSCSI controller fails according to an embodiment of the present invention. As shown in FIG. 3, the specific steps are as follows:

Step 301: The iSCSI controller B detects that the iSCSI controller A is invalid, and adds the IP address of all service network ports of the iSCSI controller A to the service network port of the controller. The failure of iSCSI controller A in this step means that iSCSI controller A cannot communicate with the iSCSI host that logs in to itself. The failure of iSCSI controller A may be caused by the failure of some functions of iSCSI controller A, or it may be caused by the restart of iSCSI controller A. For the former, iSCSI controller A will notify iSCSI controller B in time after detecting its own failure; for the latter, iSCSI controller B will know the iSCSI controller because it has not received the handshake message from iSCSI controller A. A is invalid.

The IP address information on the service network port of each iSCSI controller is stored in the storage space accessible by the iSCSI controller and its mirrored iSCSI controller. Therefore, the iSCSI controller B can be used from both the iSCSI controller A and the iSCSI controller A. Obtain the IP address of all service network ports of iSCSI controller A in the storage space.

When the iSCSI controller A determines that it is invalid, it stops the iSCSI target service program running on the IP address of all its service network ports and deletes the IP addresses on all its service network ports.

After this step, the IP addresses of the service network ports of iSCSI controller B are: IPA1+IPA2+... and IPB1+IPB2+... , where IPA1+IPA2+... is all on the original iSCSI controller A. IP address on the service network port, IPB1+IPB2+... is the IP address of all service network ports on iSCSI controller B.

Step 302: The iSCSI controller B runs the iSCSI target service program on the newly added IP address of the service network port: IPA1+IPA2+.

Step 303: The iSCSI host 1 detects that the session connection with the iSCSI controller A is disconnected, and uses the IP address of the last successful login as the destination address. Specifically, in this embodiment, the login request message is re-initiated through IPA1. The message carries the initiator name of iSCSI host 1.

Typically, iSCSI host 1 initiates a login request based on the IP address that was used when the last login was successful.

Step 304: The iSCSI controller B receives the login request message, and obtains the iSCSI host 1 attributed iSCSI host 1 according to the initiator name of the iSCSI host 1 carried in the message and the association between the saved initiator name and the IP address of the home iSCSI controller. IP address of the controller: IPA1.

Step 305: The iSCSI controller B detects that the IP address of the iSCSI host 1 is the IP address of the iSCSI host 1 and performs the login related processing. After the processing is completed, the iSCSI host 1 is notified that the login is successful.

The login related processing mentioned in this step is the same as step 209. Step 306: The iSCSI host 1 performs data communication with the iSCSI controller B.

The iSCSI controller B stores the data sent from the iSCSI host 1 to the storage medium accessible to both the iSCSI controller B and the iSCSI controller A, from which the iSCSI host can read data.

As shown in the flow shown in Figure 3, after the iSCSI controller A that is logged in to iSCSI host 1 fails, the mirrored iSCSI controller (iSCSI controller B) of the iSCSI controller A passes through the service network port of the iSCSI controller A. The IP address is added to the service network port of the controller, and the iSCSI target server service program is run on the newly added IP address, and then the iSCSI host 1 re-initiates the login request, logs in to the mirrored iSCSI controller, and the image is mirrored. The iSCSI controller communicates data to ensure data consistency and business continuity.

After the home iSCSI controller (iSCSI controller A) of iSCSI host 1 is restored to normal, in order to ensure load sharing, iSCSI controller B disconnects the session from the iSCSI host that was originally logged into iSCSI controller A. The iSCSI host 1 logs back in to the iSCSI controller A. The data communication embodiment when the home iSCSI controller returns to normal is given below.

FIG. 4 is a flow chart of data communication after the home iSCSI controller returns to normal according to an embodiment of the present invention. As shown in FIG. 4, the specific steps are as follows:

Step 401: The iSCSI controller B detects that the iSCSI controller A is back to normal, disconnects the session connection with all the iSCSI hosts that are originally logged into the iSCSI controller A, and shuts down all the IP addresses running on the original iSCSI controller A. iSCSI target service program.

Step 402: The iSCSI controller B deletes all IP addresses of the iSCSI controller A configured on the service network port.

Step 403: The iSCSI controller A detects that it is back to normal, configures the IP address of the iSCSI controller A on all its service network ports, and runs the iSCSI target server service program on the configured IP address.

The IP address configured on each service network port of each iSCSI controller is stored in the storage space accessible by the iSCSI controller and its mirrored iSCSI controller. Therefore, iSCSI controller A can be both from itself and iSCSI controller B. Obtain the IP address configured on each service network port of iSCSI controller A in the accessible storage space.

Step 404: The iSCSI host 1 detects that the session connection with the iSCSI controller B is disconnected. The login request message is re-initiated according to IPA1, and the message carries the initiator name of iSCSI host 1. Step 405: The iSCSI controller A receives the login request message, and obtains the iSCSI host 1's iSCSI according to the initiator name of the iSCSI host 1 carried in the message and the association between the saved initiator name and the IP address of the home iSCSI controller. IP address of controller A: IPA1.

Step 406: The iSCSI controller A detects that the IP address of the iSCSI host 1 is the IP address of the iSCSI host 1 and performs the login related processing. After the processing is completed, the iSCSI host 1 is notified that the login is successful.

The login related processing mentioned in this step is the same as step 209.

Step 407: The iSCSI host 1 performs data communication with the iSCSI controller A.

In the embodiment shown in FIG. 2 to FIG. 4, the iSCSI controller B is a mirrored iSCSI controller of the iSCSI controller A. In practical applications, the iSCSI controller A can also be set as the iSCSI controller B. The mirrored iSCSI controller, at this time, iSCSI controller A and iSCSI controller B can be referred to as the peer iSCSI controller.

In addition, in the embodiment shown in Figures 2 through 4, iSCSI Controller A has only one mirrored iSCSI controller: iSCSI Controller B. In practical applications, each iSCSI controller can also have two or more mirrored iSCSI controllers. Each iSCSI controller mirrors the data sent by the iSCSI host to all its mirrored iSCSI controllers. When the iSCSI controller fails, a mirrored iSCSI controller can be selected in the working mirrored iSCSI controller to replace the iSCSI controller with the iSCSI host originally logged into the iSCSI controller for data communication, and the selected mirror iSCSI is selected. The controller can be the least loaded of all mirrored iSCSI controllers. For example, if there are multiple mirrored iSCSI controllers, you can arbitrate to determine which mirrored iSCSI controller takes over the failed iSCSI controller.

According to the embodiment shown in FIG. 2 to FIG. 4, FIG. 5 shows a typical networking diagram of data storage using the iSCSI technology provided by the embodiment of the present invention. As shown in FIG. 5, the controller A and the controller B controller are shown.

The iSCSI target server running the image on N, iSCSI host 1, iSCSI host 2 iSCSI host m is established with iSCSI controller through wide i or network (WAN, Wide Area Network) or local area network (LAN, Local Area Network) Conversation. Only one session is established between the iSCSI host and the iSCSI target (including the mirrored iSCSI controller and the mirrored iSCSI controller). As shown in Figure 5, for iSCSI host 1, the session of iSCSI host 1 is established under iSCSI control. A or iSCSI controller B, iSCSI host 1 sees the same name, so iSCSI host 1 will not I learned that the iSCSI controller has changed.

FIG. 6 is a schematic diagram showing the structure of a data storage system according to an embodiment of the present invention. As shown in FIG. 6, the method mainly includes: an iSCSI host and an iSCSI controller, where:

iSCSI host: At startup, according to the IP address of the iSCSI controller configured to obtain the name of the iSCSI controller pointed to by the IP address, send a login request carrying the initiator name of the iSCSI host to the iSCSI controller pointed to by the IP address. The message, if receiving the redirect request message carrying the IP address sent by the iSCSI controller, obtains the name of the iSCSI controller pointed to by the IP address carried in the redirect request message, and points to the IP address carried in the redirect request message. The iSCSI controller sends a login request message, receives a login success notification sent by the iSCSI controller pointed by the IP address carried by the redirect request message, and performs data communication with the iSCSI controller pointed to by the IP address carried by the redirect request message. When the session connection with the iSCSI controller is disconnected, the login request message is re-initiated, for example, the login request message may be re-initiated according to the IP address successfully used by the last login.

As shown in FIG. 6, the iSCSI controller mainly includes: a login processing module 61, a mirror failure processing module 62, a mirror recovery processing module 63, and a data processing module 64, wherein:

The login processing module 61 receives the login request message sent by the iSCSI host, and calculates the home iSCSI of the iSCSI host according to the initiator name of the iSCSI host carried in the message and the association between the name of the initiator and the IP address of the home iSCSI controller. If the IP address of the controller is the IP address of the iSCSI host, the login process is performed. The processing is complete, and the iSCSI host is notified that the login is successful. Otherwise, the calculated IP address is carried in the redirect request message. iSCSI host.

The image failure processing module 62 detects that the mirrored iSCSI controller of the controller fails, adds the IP address of the service network port of the mirrored iSCSI controller to the IP address of the controller, and runs the iSCSI target on the IP address. Service program.

The mirror recovery processing module 63 detects that the mirrored iSCSI controller of the controller is restored to normal, disconnects the session between the controller and the iSCSI host that is originally logged into the mirrored iSCSI controller, and stops at the controller. The iSCSI target service program on the IP address of the mirrored iSCSI controller on the service network port, and delete the IP address on the service network port of the controller.

The data processing module 64 receives the original iSCSI controller that is logged into the controller. The data sent from the iSCSI host is saved to the cache (Cache).

As shown in FIG. 7, the image failure processing module 62 mainly includes: a mirror failure detection module 621 and an IP address adding module 622, where:

The mirror failure detection module 621 detects that the mirrored iSCSI controller of the controller fails, and sends a mirror failure indication to the IP address adding module 622.

The IP address adding module 622 receives the mirroring invalidation indication sent by the mirroring failure detecting module 621, adds the IP address of the mirrored iSCSI controller of the controller to the service network port of the controller, and runs iSCSI on each IP address. Target server service program.

As shown in FIG. 8, the image recovery processing module 63 mainly includes: a image recovery detection module 631, a session connection disconnection module 632, and an IP address deletion module 633, where:

The image recovery detection module 631 is configured to send a mirror recovery indication to the session connection disconnection module 632 and the IP address deletion module 633 after detecting that the mirrored iSCSI controller of the controller is restored.

The session connection disconnection module 632 is configured to disconnect the session between the controller and all iSCSIs on the mirrored iSCSI controller that is originally logged into the controller after receiving the image recovery indication sent by the image recovery detection module 631. connection.

The IP address deletion module 633 is configured to stop the iSCSI target service program on the IP address of the mirrored iSCSI controller of the service network port of the controller after receiving the image recovery indication sent by the image recovery detection module 631, and Delete the IP address of the mirrored iSCSI controller configured on the service network port of the controller.

In addition, the iSCSI controller in the embodiment of the present invention may further include: a failure processing module and a recovery processing module, where:

The local failure processing module is used to stop all the service network ports of the user when determining that the controller is invalid.

The iSCSI target server running on the IP address and delete the IP address on all its service network ports.

When the local recovery processing module detects that the controller is recovering from failure, configure an IP address on all service network ports of the controller and run the iSCSI target service program on the IP address of the service network port of the controller.

As shown in FIG. 9, the local recovery processing module mainly includes: a local recovery detection module 651 and an IP address configuration module 652, wherein: The local recovery detection module 651 is configured to send a failure recovery indication to the IP address configuration module 652 upon detecting that the controller is recovering from failure.

The IP address configuration module 652 is configured to configure an IP address on all service network ports of the controller after receiving the failure recovery indication sent by the recovery detection module 651, and run the iSCSI target service program on each IP address.

It can be seen from the above embodiment that when the iSCSI controller fails, the mirrored iSCSI controller of the iSCSI controller adds the IP address of the service network port of the iSCSI controller to its own service network port, and at each IP address. The iSCSI target server service program runs on the address, and then the iSCSI host logs in to the mirrored iSCSI controller to perform data communication with the mirrored iSCSI controller, achieving data consistency and service continuity, and improving data communication reliability. And stability. Also, load sharing is achieved by setting up a home iSCSI controller for each iSCSI host. In addition, the iSCSI controller and the mirrored iSCSI controller use the same name, making the iSCSI controller switching process transparent to the user.

The above is only the embodiment of the process and method of the present invention, and is not intended to limit the present invention. Any modifications, equivalents, improvements, etc. made within the spirit and principles of the present invention should be included in the present invention. Within the scope of protection.

Claims

Rights request

A data communication method, characterized in that at least one mirrored iSCSI controller is provided in advance for each Internet small computer system interface iSCSI controller, the method comprising:

2. The method according to claim 1, wherein the method further comprises: presetting that each iSCSI host belongs to one of the mirrored iSCSI controllers;

The mirrored iSCSI controller further includes: before detecting that the mirrored iSCSI controller corresponding to the mirrored iSCSI controller fails:

The iSCSI host logs into the mirrored iSCSI controller to which it belongs and performs data communication with the home mirrored iSCSI controller.

The method according to claim 2, wherein the method further comprises: the mirrored iSCSI controller detects that it is invalid, and stops running the iSCSI target server program on the IP address of all its service network ports. .

The method of claim 3, wherein the method further comprises: the mirrored iSCSI controller detects that it has recovered from failure, and configures an IP address on all of its service network ports, and Run the iSCSI Target Service program on the IP address.

The method according to claim 3 or 4, wherein the method further comprises: the iSCSI host detecting disconnection of data communication with the mirrored iSCSI controller, re-initiating a login request, logging in Data communication with the iSCSI controller is performed on the iSCSI controller.

6. The method of claim 1, wherein the adding the service information of the mirrored iSCSI controller to the mirrored iSCSI controller comprises: adding an IP address of the mirrored iSCSI controller to the Mirror the iSCSI controller's service network port and add it to each IP address. Run the iSCSI target server.

The method according to claim 6, wherein the method further comprises: the mirrored iSCSI controller detecting that the mirrored iSCSI controller is restored to normal; the mirroring iSCSI controller is disconnected from the original login The data communication between the iSCSI host of the mirrored iSCSI controller is stopped, and the iSCSI target service program running on the IP address of the mirrored iSCSI controller of the service network port is stopped, and the service port on the service network port is deleted. The IP address of the mirrored iSCSI controller.

8. The method of claim 1, wherein the method further comprises: pre-setting the same name for the iSCSI controller and its corresponding mirrored iSCSI controller.

9. A data communication system, comprising:

Mirroring the iSCSI controller, configured to add the service information of the mirrored iSCSI controller to itself, and receive the original login to the mirrored iSCSI controller, when detecting that the mirrored iSCSI controller corresponding thereto fails The login request sent by the iSCSI host performs data communication with the iSCSI host originally logged into the mirrored iSCSI controller according to the service information.

10. An iSCSI controller, comprising:

a mirror failure processing module, configured to add the service information of the mirrored iSCSI controller to itself when detecting that the mirrored iSCSI controller corresponding to itself fails;

The iSCSI controller according to claim 10, wherein the mirror failure processing module comprises:

a mirror failure detection module, configured to send a mirror failure indication when detecting that the mirrored iSCSI controller corresponding to itself fails;

The IP address adding module is configured to receive the mirroring invalidation indication sent by the mirroring failure detecting module, add the IP address of the mirrored iSCSI controller to the service network port of the controller, and run the iSCSI target on each IP address. Service program.

The iSCSI controller of claim 10, wherein the iSCSI controller further comprises:

a mirror recovery processing module, configured to: when detecting that the mirrored iSCSI controller returns to normal, disconnect a data communication connection with an iSCSI host that is originally logged into the mirrored iSCSI controller, and delete the iSCSI control The service information of the mirrored iSCSI controller on the device.

The iSCSI controller of claim 12, wherein the image restoration processing module comprises:

a mirror recovery detection module, configured to send a mirror recovery indication to the session connection disconnection module and the IP address deletion module when detecting that the mirrored iSCSI controller returns to normal;

a session connection disconnecting module, configured to: after receiving the image recovery indication, disconnect a data communication connection between the iSCSI controller and all iSCSI hosts originally logged into the mirrored iSCSI controller;

The IP address deletion module is configured to: after receiving the image recovery indication, stop the iSCSI target service program on the IP address of the mirrored iSCSI controller of the service network port of the iSCSI controller, and delete the Indicates the IP address of the mirrored iSCSI controller configured on the service network port of the iSCSI controller.

The iSCSI controller according to claim 10, wherein the iSCSI controller further comprises:

The failure processing module is configured to stop the iSCSI target service program running on the IP address of all the service network ports of the iSCSI controller when the controller fails, and delete the IP addresses on all service network ports.

The iSCSI controller according to claim 10 or 14, wherein the iSCSI controller further comprises:

The local recovery processing module is configured to configure service information on the iSCSI controller after detecting that the iSCSI controller is restored to normal by failure.

The iSCSI controller according to claim 15, wherein the local recovery processing module comprises:

The local recovery detection module is configured to send a failure recovery indication after detecting that the iSCSI controller recovers from failure; The IP address configuration module is configured to receive the failure recovery indication sent by the recovery detection module, configure an IP address on all service network ports of the iSCSI controller, and run an iSCSI target service program on each IP address.