JP2009048530A - Internet scsi connection control system, and internet scsi connection control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an iSCSI (Internet SCSI) connection control system carrying out central control of an iSCSI connection. <P>SOLUTION: A data control system 8 receives and stores load distribution device NW information of a load distribution device 1 and iSCSI target device NW information of an iSCSI target device 61. An iSNS server 7 receives a profile of the iSCSI target device 61, and registers it in the data control system 8. The iSCSI server 7 creates a discovery domain, and registers it in the data control system 8. The data control system 8 generates a connection table record on registration of the discovery domain. The data control system 8 updates a connection table T11 in the load distribution device 1 on the basis of the generated connection table record. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a device connection control technique in an iSCSI (Internet SCSI) technique.

  iSCSI (Internet SCSI) technology (that is, one of IP (Internet Protocol) storage technologies), or a collection of multiple hard disk drives, or a disk array device that controls multiple hard disk drives with a dedicated control unit Storage devices that are used have been put into practical use.

  Fiber channel (FC), InfiniBand, SCSI (Small Computer Systems Interface), and the like are known as interface technologies for connecting a storage device and a host device (for example, server, PC (Personal Computer)).

  The SCSI interface is excellent as an application for economically connecting short distances and is already widely used. In the SCSI interface, a function corresponding to a client is called an initiator, and a function corresponding to a server is called a target, and a SCSI command (CDB: Command Descriptor Block) is exchanged between the initiator and the target. The iSCSI (Internet SCSI) technology was standardized in 2004 by IETF (The Internet Engineering Task Force) as an upper protocol of TCP / IP (Transmission Control Protocol / Internet Protocol) which is a network protocol (for example, non-patent document 1). reference).

  At present, the iSCSI technology is used for a line quality of gigabit or higher, particularly in a main line within a data center, between data centers, and a large-scale LAN (Local Area Network) system. However, there is no example in which the iSCSI technology is applied as a service on a consumer access line (for example, a broadband line) between a terminal and a server or between a terminal and a terminal. On the other hand, the spread and speeding up of FTTH (Fiber To The Home) line is underway in Japan, and a service using 100BASE-TX as a user interface has already been put into practical use. Gigabit is also expected.

  Here, a network connection management technique related to a storage network such as iSCSI will be described below.

  Server load balancing technology (SLB) is a processing technology that distributes traffic to a site to multiple servers using devices on the network. The site on the IP network is as if it is a single server from the end user. It seems to be operated in.

  There are two types of SLBs: flat-based (MAT (based on Media Access Control (MAC) Address Translation)) architecture and NAT (Network Address Translation) -based architecture (for example, see Non-Patent Document 2) due to differences in IP address configuration. It has been. In particular, the former flat base architecture is frequently used in applications where importance is placed on throughput because traffic from a server to an end user does not pass through an SLB.

  A device that implements SLB (hereinafter referred to as an SLB device) creates and manages a connection table therein for session management between client servers. The connection table is mapping information between the IP address of the client and the MAC address of the server, and the creation of the connection table is positioned at the heart of SLB capabilities.

  In many SLB apparatuses, a round robin method, a method based on the number of connection connections, a method based on a server response speed and a server CPU usage rate, and the like are used as a connection table update algorithm. However, recently, an SLB apparatus equipped with a function of fixedly distributing sessions from the same IP address to a specific server in order to cope with a use such as shopping on a Web site (that is, a procedure from product selection to payment). Has appeared.

  iSNS (Internet Storage Name Service) technology is dedicated to Internet standard storage that provides functions such as detection and configuration management of the above iSCSI devices and iFCP (Internet Fiber Channel Protocol) devices on TCP / IP networks. Name service (name resolution) standard, which was established in September 2005 as RFC (Request for Comments) 4171 (see, for example, Non-Patent Document 3).

  The iSNS server manages the profile of each device (for example, an IP address or an iSCSI name defined by RFC3721 (for example, see Non-Patent Document 4)) through an iSNS client function installed in the management device. In addition, the iSNS server realizes mutual life management between the iSNS server and the iSNS client, management of a discovery domain that defines an access relationship between devices, and sharing of a profile within the same domain. In particular, since an IP address list of a domain-affiliated device can be acquired by sharing a profile in the domain, this is applied to an access control list (ACL) and dynamic L3 (Layer 3) for access from each device. ) Can be controlled.

  Here, a flat-base (MAT-based) load distribution method for which technology has already been established will be described based on the network configuration of FIG.

  Load balancing device (Load Balancer) 1 for performing MAT-based load balancing, to which clients (clients) 31 and 32 in FIG. 3 and L2 (Layer 2) control device (L2 switch) 2 as a network relay device are connected, server ( server) 41 and 42 are connected to the network 100.

  The load balancer 1 has a connection table T11, and uses the L2 control device 2 to transfer a packet to a transfer destination based on the connection table T11. The connection table record stored in the connection table T11 in FIG. 3 is automatically created in the load balancer 1.

  For example, a packet addressed to a virtual IP (VIP) address transmitted from the client 31 (for example, IP address: 192.168.1.10) via the network 100 is transmitted to the L2 connected to the load balancer 1. The control device 2 transfers the data to the server 41 based on the connection table T11 (M101).

  More specifically, the packet addressed to the virtual IP address transmitted from the client 31 in which “192.168.1.10” is set as the IP address (the destination address is “192.168.0.200”, the transmission source The packet whose address is set to “192.168.1.10” is transmitted by the L2 control device 2 connected to the load balancer 1 in which “192.168.0.200” is set to the VIP address. When the original address is “192.168.1.10”, the MAC address is set based on the connection table T11 described so that the destination address is transferred to “00: 00: 00: 00: BB”. The data is transferred to the server 41 in which “00: 00: 00: 00: BB” is set (M101).

  Then, a reply packet from the server 41 is transmitted from the server 41 to the client 31 (M102).

Note that messages M101 ′ and M102 ′ are transmitted to the client 32 as well.
J. et al. Satran, K.M. Meth, C.I. Sapuntzakis, M .; Chadalapaka, E .; Zeinder, Request for Comments: 3720 “Internet Small Computer Systems Interface (iSCSI)”, [online], Apr 2004 (April 2004), The Internet Society, URL, July 2007 : Http: // www. ietf. org / rfc / rfc3720. txt>. Tony Burke, written by Naokishima Kosho, “Server Load Balancing Technology”, O'Reilly Japan, December 2001, p27-34. J. et al. Tseng, K.M. Gibbons, F.M. Travosino, C.I. Du Laney, J.A. Souza, Request for Comments: 4171 “Internet Storage Name Services (iSNS)”, [online], Sep 2005 (September 2005), The Internet Society, [URL search on July 24, 2007] http: // www. ietf. org / rfc / rfc4171. txt>. M.M. Bakke, J .; Hafner, J. et al. Hufferd, K.M. Voruganti, M.C. Krueger, Request for Comments: 3721 “Internet Small Computer System Interface (iSCSI) Naming and Discovery”, [online], April 2004 (April 2004), The Int. Internet <URL: http: // www. ietf. org / rfc / rfc3721. txt>.

  In a system that uses the above-described iSNS server to realize a connection between a file server having an iSCSI initiator function and a storage (iSCSI target) device, the storage access information (IP address and port number) once obtained from the iSNS server is the second or later. There is a known security problem that can be reused without going through an iSNS server.

  The iSNS server has a mechanism for dynamically realizing IP filtering by sharing an access control list (ACL) within a common domain. However, not all iSNS support devices implement ACL control. Absent.

  In addition, the operation mode in which security control is shared by each iSCSI target device is extremely complicated, and there is a problem that an invalid load due to unauthorized access occurs.

  The present invention has been made based on the above-described problem, and provides an iSCSI connection management system and an iSCSI connection management method for centrally managing iSCSI connections in a service configuration that provides an unspecified number of iSCSI target devices. There is to do.

  In order to solve the above-mentioned problem, the invention according to claim 1 comprises an Internet storage name service server, a data management system, a load distribution device having a connection table and connected to a network relay device, and an IP network is connected from the iSCSI initiator. The iSCSI storage management system performs connection control so that a packet transmitted via the connection table is transferred to an iSCSI target device based on the connection table, wherein the Internet storage name service server includes the iSCSI target device. The iSCSI target device profile including the virtual IP address, the TCP port number for iSCSI access, and the iSCSI name is received, and the profile of the iSCSI target device is managed by the data management. Receiving the iSCSI initiator profile including an IP address and iSCSI name assigned to the network interface of the iSCSI initiator, and registering and managing the iSCSI initiator profile in the data management system And a means for creating a discovery domain including the iSCSI name of the iSCSI initiator and the iSCSI name of the iSCSI target device and registering it in the data management system, wherein the data management system has an IP address of the load balancer And means for receiving and storing the load balancer NW information having the virtual IP address, storing and storing the load balancer NW information, the iSCSI name of the iSCSI target device and the iSCSI target. When the iSCSI target device NW information having the MAC address of the network interface provided in the device is received, the iSCSI target device NW information is stored and stored, and when the discovery domain is registered, the iSCSI initiator Means for generating a connection table record including an IP address and a MAC address of the iSCSI target device, and a connection table in the load balancer indicated by the IP address of the load balancer based on the generated connection table record , And when the iSCSI initiator profile, the iSCSI target device profile, or the discovery domain is deleted, the deleted profile is updated. And a means for deleting a connection table record in a load balancer corresponding to a file or a discovery domain.

  The invention according to claim 2 comprises an Internet storage name service server, a data management system, a load distribution device having a connection table and connected to a network relay device, and a packet transmitted from an iSCSI initiator via an IP network An iSCSI connection management method used in a system that performs connection control so as to transfer to an iSCSI target device that is a transfer destination based on a connection table, wherein the data management system includes an IP address and a virtual IP address of the load balancer And receiving and storing the load balancer NW information, and the data management system includes the iSCSI name of the iSCSI target device and the iSCSI target device provided with the iSCSI target device. Receiving the iSCSI target device NW information having the MAC address of the network interface, storing and storing the iSCSI target device NW information, and the Internet storage name service server including the virtual IP address of the iSCSI target device, iSCSI access Receiving a profile of the iSCSI target device including a TCP port number and an iSCSI name for registering and managing the profile of the iSCSI target device in the data management system, and the Internet storage name service server comprising the iSCSI initiator Receiving the iSCSI initiator profile including the IP address and iSCSI name assigned to the network interface of Registering and managing the profile of the CSI initiator in the data management system; and the Internet storage name service server creates a discovery domain including the iSCSI name of the iSCSI initiator and the iSCSI name of the iSCSI target device, and the data management system And a step of generating a connection table record including an IP address of the iSCSI initiator and a MAC address of the iSCSI target device when the discovery domain is registered, and The data management system has a connection in the load balancer indicated by the IP address of the load balancer based on the generated connection table record. A step of updating the table, and a load balancer corresponding to the deleted profile or the discovery domain when one of the iSCSI initiator profile, the iSCSI target device profile, or the discovery domain is deleted And a step of deleting the connection table record in the inside.

  According to the first and second aspects of the present invention, the iSCSI connection control can be centrally managed.

  As described above, according to the first and second aspects of the present invention, the complexity of operations related to iSCSI connection control in a system including an iSCSI initiator and an iSCSI target device can be eliminated, and the operability of the system can be improved.

  This can contribute to the storage network technology field.

  Below, the operation | movement outline | summary of the iSCSI connection management system in this embodiment is demonstrated.

  First, an iSNS server manages in order to centrally control access between an iSCSI initiator (iSCSI initiator device) having a registration function to an iSNS server and an alive signal transmission function and an iSCSI target device (collectively referred to as an iSCSI device). Additional information regarding the load balancer and the iSCSI target device (for example, the actual IP address of the load balancer and the MAC address of the iSCSI target device) is registered in the database in which the profile information of the iSCSI device is stored.

  On the database in which network information including the above-mentioned additional information and network information related to iSCSI is registered, the discovery domain setting from the iSNS server is hooked (for example, by the trigger function), and the connection table record of the iSCSI initiator and the iSCSI target device. (For example, using a stored procedure created and registered in advance).

  By reflecting the created connection table record in the connection table managed by the load balancer, the connection between the iSCSI initiator and the iSCSI target device can be established.

  On the other hand, when the registration of either the iSCSI initiator or the iSCSI target device is deleted, the connection table record is deleted by hooking on the database and reflected in the connection table on the load balancer.

  By the operation of the iSCSI connection management system described above, the iSCSI session is established between the iSCSI initiator and the iSCSI target device only when the iSCSI initiator and the iSCSI target device are both registered in the iSNS server and the discovery domain is set on the iSNS server. Thus, centralized access control on the load balancer can be realized.

  Further, in the operation of the iSCSI connection management system described above, the purpose of use of the load distribution device is greatly different, and the load distribution device is used as a device for controlling IP packet redirection rather than a load distribution function.

  Hereinafter, an iSCSI connection management system according to an embodiment of the present invention will be described in more detail with reference to the drawings.

  A network configuration relating to the iSCSI connection management system in the present embodiment will be described with reference to FIG. The network configuration shown in FIG. 1 includes an iSCSI initiator 51, 52, a load balancer 1 to which an L2 controller 2 is connected, an iSCSI target device (iSCSI target) 61, 62, an iSNS server 7, and a database 8. 100. In the network configuration, it can be said that the iSCSI connection management system includes the L2 control device 2, the load distribution device 1, the iSNS server 7, and the database 8.

  The load distribution apparatus 1 has a connection table T11 as in FIG. That is, the load distribution apparatus 1 may include a connection table management unit (not shown) that implicitly manages the connection table T11 by performing processing such as registration or deletion of the connection table record. .

  The network configuration in FIG. 1 is obtained by newly adding an iSNS server 7 and a database 8 for storing management data of the server to the network configuration in FIG.

  The iSNS server 7 registers the iSNS registration information transmitted from the iSCSI initiator and the iSCSI target device and the discovery domain based on them in the database 8. For example, the iSNS server 7 is obtained by installing an iSNS server program in a computer or server having a control unit such as a CPU (Central Processing Unit) and a storage unit such as a memory and a hard disk.

  The database 8 includes a general DBMS (Database Management System) having a trigger function and a stored procedure function, and database data managed by the DBMS, and an iSCSI connection set or registered from the iSNS server 7. It is a database that stores and manages necessary information. For example, the database 8 is obtained by installing a DBMS program and database data managed by the DBMS in a computer or server having a control unit such as a CPU (Central Processing Unit) and a storage unit such as a memory and a hard disk. In the present embodiment, the DBMS as described above is adopted, but any data management system that has a function equivalent to the trigger function or the stored procedure function and manages data may be used.

  The database 8 has a function and authority to access the connection table in the load balancer and update the table record.

  The database 8 has a function of hooking information update from the iSNS server 7 (for example, hooking with a trigger function) and performing a predetermined process (for example, a stored procedure for performing the predetermined process).

  The iSNS server 7 and the database 8 may be installed in the same computer with software that realizes each of them.

  The iSCSI connection management system according to the present embodiment realizes centralized connection control in the load balancer by dynamically creating a connection table for the connection relationship between the client and the server. The device configuration of FIG. 1 replaces the client-server in the device configuration of FIG. 3 with an iSCSI initiator-iSCSI target device.

  A procedure for realizing the iSCSI connection via the load balancer between the iSCSI initiator and the iSCSI target in this embodiment will be described with reference to FIG.

  First, load balancer NW (Network) information of the load balancer 1 is registered (manually entered) in the database 8 (M201: database registration of load balancer NW information). For example, the network administrator registers the load balancer NW information through a terminal or a network provided in advance. That is, the database 8 stores and stores the received load balancer NW information.

  The load balancer NW information to be input is a record having a combination of the IP address (real IP address) of the load balancer 1 and the virtual IP address (for example, load balancer NW information as shown in the table below). When managing a plurality of load balancers, a plurality of records are registered.

  Next, the iSCSI target device NW information of the iSCSI target device 61 (or 62) is registered (manually entered) in the database 8 (M202: database registration of iSCSI target device NW information). That is, the database 8 stores and stores the received iSCSI target device NW information. For example, the network administrator registers the iSCSI target device NW information via a terminal or a network provided in advance. It is assumed that records of all iSCSI target devices that establish a session via the load balancer 1 registered in the database 8 are registered.

  The iSCSI target device NW information to be input is a record having a combination of a unique iSCSI name set for each iSCSI target device and the MAC address of the network interface of the device (for example, an iSCSI target device NW as shown in the table below). information). In the table below, the iSCSI name is not described in the iqn format. The iSCSI name in the table below is “iSCSI_name_target”.

  Next, the iSCSI target device 61 (or 62) profile (for example, the profile shown in the table below), which is iSNS registration information, is registered to the iSNS server 7 by the iSNS client function of the iSCSI target device 61 (or 62). (M203 (or M203 ′): iSCSI target device profile iSNS server registration). The iSNS server 7 registers and manages the received profile in the database 8. The iSCSI name in the table below is “iSCSI_name_target”.

  Normally, the IP address registered by the iSNS client function uses the IP address assigned to the network interface, but for the operation from the load balancer 1 which is a flat base load balancer, the IP address is assigned to the loopback interface of the iSCSI target device. The virtual IP address of the load balancer is applied as the IP address.

  The profile to be registered is a record including a combination of a TCP port number for iSCSI access and an iSCSI name unique to the device in addition to a virtual IP address.

  Further, in FIG. 1, ESI (Entity Status Inquiry) and SCN (State Change Notification) defined by iSNS are unreachable from the load balancer 1 to the iSCSI target devices 61 and 62. Therefore, since the iSCSI target devices 61 and 62 applicable to the iSCSI connection management system are devices that can send an alive signal to the iSNS server 7, together with the profile, “ESI (Alive) = yes”, “SCN = The information “no” is transmitted to the iSNS server 7.

  Next, the iSCSI initiator 51 (or 52) profile (for example, the profile shown in the table below), which is the iSNS registration information, is registered in the iSNS server 7 by the iSNS client function of the iSCSI initiator 51 (or 52) ( M204 (or M204 ′): iSNS server registration of iSCSI initiator profile). The iSNS server 7 registers the received profile in the database 8. In the table below, the iSCSI name is “iSCSI_name_initiator”.

  The profile registered by the client function is a record including a combination of an IP address assigned to a network interface and an iSCSI name unique to the iSCSI initiator 51 (or 52).

  Further, since the iSCSI initiator 51 (or 52) is required to manage life and death from the iSNS server 7, it is assumed to have an ESI processing function (or an Alive signal transmission function to the iSNS server 7). In FIG. 1, information “ESI (Alive) = yes” is transmitted to the iSNS server 7 together with the profile.

  Next, as an operation on the iSNS server 7, a discovery domain between the iSCSI initiator and the iSCSI target device is set and registered in the database 8 (M205: discovery domain setting on the iSNS server).

  A portion surrounded by a broken line in FIG. 1 indicates an operation for incorporating the iSCSI initiator 51 and the iSCSI target 61 into a common discovery domain DD1 (for example, discovery domain DD1 as shown in the table below). As a result of this operation, the iSCSI initiator 51 can access the profile of the iSCSI target device 61 (for example, the profile indicated by the symbol D3 in Table 3 and FIG. 2).

  In the table below, the iSCSI name “iSCSI_name_initiator” is combined with the discovery domain identifier “DD1” for identifying the discovery domain, and further, the iSCSI name “iSCSI_name_target” and the discovery domain identifier “DD1” are combined to provide the iSCSI name “iSCSI_name_initiator”. And the iSCSI name “iSCSI_name_target” are grouped to represent the discovery domain DD1.

  A data relationship as shown in FIG. 2 is formed in the database 8 by registration or processing relating to the messaging M201 to M205 described above. Here, the data relationship of the data stored in the database 8 will be described with reference to FIG.

  The load balancer NW information D1 is composed of the IP address d2 and the virtual IP address d1 of the load balancer 1.

  The iSCSI target device NW information D2 includes a unique iSCSI name d3 set for each iSCSI target device and a MAC address d5 of the network interface of the device.

  The profile D3 of the iSCSI target device is composed of a virtual IP address d1 of the load balancer, a TCP port number d4 of the iSCSI target device, and an iSCSI name d3 unique to the iSCSI target device.

  The iSCSI initiator profile D4 includes an assigned IP address d7 and an iSCSI name d6 unique to the iSCSI initiator.

  The discovery domain D5 between the iSCSI initiator and the iSCSI target device has the iSCSI name d6 of the iSCSI initiator and the iSCSI name d3 of the iSCSI target device.

  The connection table d8 is updated based on the connection table record generated from the IP address d7 of the iSCSI initiator and the MAC address d5 of the iSCSI target device.

  Next, when the discovery domain is set by the processing related to the messaging M205 (for example, by hooking an event indicating that the discovery domain is registered in the database 8), the database 8 sets the IP address of the iSCSI initiator 51. A connection table record including a combination of the address and the MAC address of the iSCSI target device 61 is generated (M206: creation of connection table record).

  Then, the database 8 reflects the connection table record generated by the processing related to the messaging M206 in the connection table T11 in the load balancer 1 (that is, the load balancer indicated by the real IP address in Table 1) (M207: (Reflect the created connection table record to the load balancer). For example, based on the generated connection table record, the connection table T11 in the load balancer 1 is updated using a stored procedure stored in the database 8.

  As described above, the procedure for realizing the iSCSI connection via the load balancer between the iSCSI initiator and the iSCSI target along the messaging M201 to M207 has been described.

  Next, a procedure for releasing the iSCSI connection via the load balancer between the iSCSI initiator and the iSCSI target will be described.

  When either the iSNS registration information (profile) of the iSCSI initiator or the iSNS registration information (profile) of the iSCSI target device (and the iSCSI target device NW information) is deleted from the database 8 (or has been deleted) When a corresponding event occurs), or when a discovery domain is deleted (when an event according to deletion occurs), the database 8 hooks these events and deletes the event The connection table record of the connection table T11 corresponding to the profile or discovery domain that has been set is deleted.

  In the iSCSI connection management system of the present embodiment, the above-described iSCSI connection procedure (processing related to the messaging M201 to M207) and the iSCSI connection release procedure are used as means for each corresponding device (for example, means in a computer program). As). The series of messaging may be considered as an iSCSI connection management method (procedure) in the iSCSI connection management system of this embodiment.

  As described above, this embodiment enables centralized management of iSCSI connection control (session control) by the iSNS server.

  With the widespread use of broadband lines such as FTTH lines, it is becoming possible to deploy WAN (Wide-Area Network) based on iSCSI technology that has been used in high-speed IP environments. However, since the iSCSI technology originally emphasizes convenience in a closed area, security strength against hacking between the file server and the storage device is weak.

  In this embodiment, in an iSCSI storage resource providing type ASP (Application Service Provider) service using iSNS, an iSCSI connection can be made only between an iSCSI initiator and an iSCSI target device registered in an iSNS server by a predetermined procedure. Environment can be provided.

  That is, since session control of the iSCSI initiator and the iSCSI target device can be centrally controlled by the iSNS server, it is possible to contribute to the reduction of complicated operations that conventionally required management for each iSCSI target device.

  Although the embodiments of the present invention have been described above, the present invention is not limited to the described embodiments, and various modifications can be made within the scope described in each claim.

  For example, as a modification of the network configuration of the present embodiment, a Web server may be added, and the load balancer NW information and the iSCSI target device NW information may be registered in the database via the Web server.

The network block diagram regarding the iSCSI connection management system in this embodiment. The data related figure in the iSCSI connection management system in this embodiment. The network block diagram of a general flat base (MAT base) load distribution system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Load distribution apparatus 2 ... L2 control apparatus 7 ... iSNS server 8 ... Database 31, 32 ... Client 41, 42 ... Server 51, 52 ... iSCSI initiator 61, 62 ... iSCSI target apparatus 100 ... Network T11, d8 ... Connection table D1 ... load balancer NW information D2 ... iSCSI target device NW information D3 ... iSCSI target device profile D4 ... iSCSI initiator profile D5, DD1 ... discovery domain d1 ... load balancer virtual IP address d2 ... load balancer IP address d3 ... Unique iSCSI name set for each iSCSI target device d4 ... TCP port number of iSCSI target device d5 ... Network interface of iSCSI target device MAC address d6 ... iSCSI name specific to iSCSI initiator d7 ... IP address assigned to iSCSI initiator

Claims (2)

Internet storage name service server, data management system, load balancer with connection table and connected network relay device
An iSCSI connection management system that performs connection control to transfer a packet transmitted from an iSCSI initiator via an IP network to an iSCSI target device that is a transfer destination based on the connection table,
The Internet storage name service server is
Means for receiving a profile of the iSCSI target device including a virtual IP address of the iSCSI target device, a TCP port number for iSCSI access, and an iSCSI name, and registering and managing the profile of the iSCSI target device in the data management system; ,
Means for receiving a profile of the iSCSI initiator including an IP address and an iSCSI name assigned to the network interface of the iSCSI initiator, and registering and managing the profile of the iSCSI initiator in the data management system;
Means for creating a discovery domain including the iSCSI name of the iSCSI initiator and the iSCSI name of the iSCSI target device and registering it in the data management system;
With
The data management system is
Means for receiving load balancer NW information having an IP address and a virtual IP address of the load balancer, and storing and storing the load balancer NW information;
Means for receiving iSCSI target device NW information having an iSCSI iSCSI name of the iSCSI target device and a MAC address of a network interface provided in the iSCSI target device, and storing and storing the iSCSI target device NW information;
Means for generating a connection table record including an IP address of the iSCSI initiator and a MAC address of the iSCSI target device when a discovery domain is registered;
Means for updating the connection table in the load balancer indicated by the IP address of the load balancer based on the generated connection table record;
When one of the iSCSI initiator profile, the iSCSI target device profile, and the discovery domain is deleted, a connection table record in the load balancer corresponding to the deleted profile or the discovery domain is displayed. Means to delete,
Comprising
An iSCSI connection management system characterized by the above. Internet storage name service server, data management system, load balancer with connection table and connected network relay device
An iSCSI connection management method for use in a system that performs connection control to transfer a packet transmitted from an iSCSI initiator via an IP network to an iSCSI target device that is a transfer destination based on the connection table,
The data management system receiving load balancer NW information having an IP address and a virtual IP address of the load balancer, and storing and storing the load balancer NW information;
The data management system receives the iSCSI target device NW information having the iSCSI iSCSI name of the iSCSI target device and the MAC address of the network interface provided in the iSCSI target device, and stores and stores the iSCSI target device NW information. Steps,
The Internet storage name service server receives a profile of the iSCSI target device including the virtual IP address of the iSCSI target device, a TCP port number for iSCSI access, and an iSCSI name, and manages the profile of the iSCSI target device as the data management Registering and managing in the system;
The Internet storage name service server receives the iSCSI initiator profile including the IP address and iSCSI name assigned to the network interface of the iSCSI initiator, and registers and manages the iSCSI initiator profile in the data management system. When,
The Internet storage name service server creating a discovery domain including the iSCSI name of the iSCSI initiator and the iSCSI name of the iSCSI target device, and registering it in the data management system;
The data management system generating a connection table record including an IP address of the iSCSI initiator and a MAC address of the iSCSI target device when the discovery domain is registered;
Updating the connection table in the load balancer indicated by the IP address of the load balancer based on the generated connection table record;
When one of the iSCSI initiator profile, the iSCSI target device profile, and the discovery domain is deleted, a connection table record in the load balancer corresponding to the deleted profile or the discovery domain is displayed. A step to delete,
An iSCSI connection management method comprising the steps of:

Images