JP2008276604A - Internet storage name service method, internet storage name service server device and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To uniquely identify a computer terminal when there are several computer terminals having the same identifier in a network (WAN). <P>SOLUTION: This Internet storage name service method includes: retrieving an iSNSDB based on the network (NW) entity ID of a device attribute registration request message, and retrieving the iSCSIDB based on the NW entity index corresponding to the NW entity ID when the NW entity ID of the message matches the NW entity ID of the iSNSDB, and deciding whether or not the iSCSI name of the ISCSI node index corresponding to the iSCSI node index associated with the acquired NW entity index matches the iSCSI name of the message. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an Internet storage name service method, an Internet storage name service server apparatus, and a program, and in particular, an IP- that connects a plurality of computer terminals (hosts) to a plurality of storage apparatuses (devices) via an IP (Internet Protocol) network. The present invention relates to an iSNS method, an iSNS server device, and a program in an iSNS (Internet Storage Name Service) technology for centrally managing connection settings between computer terminals and storage devices in a SAN (Storage Area Network).

In recent years, with the spread of IP-SAN, the number of hosts and devices connected to IP-SAN has increased dramatically. Management of connection destination settings, specifically, which host is connected to which device The task of setting each host or device to do so has become very complicated. ISNS has been put to practical use as a technical standard for centrally managing the connection destination settings on a server and reducing this work addition (see Non-Patent Document 1, for example).
Internet Engineering Task Force, Request For Comments 4171, Internet Storage Name Service (iSNS)

  Until now, the above-mentioned IP-SAN technology has been mainly used in a local area network (LAN), and iSNS is also mainly assumed to be used in a LAN as well. However, with the spread of broadband networks such as FTTH (Fiber-To-The-Home), it has become realistic to use IP-SAN technology on public wide area networks (WAN). Assuming use in such a WAN, the following problems exist in the iSNS standard defined in Non-Patent Document 1 and the existing products in which iSNS is implemented.

  With the use in a LAN that has been assumed in the past, it can be expected that all setting items of the host and device on which the iSNS client is executed are enshrined so as not to hinder the operation of the iSNS server. In this operation, it is highly possible that the iSNS server operator cannot change the network address and host name of the host and device. For example, when the iSNS service is provided by a storage service provider (SSP) and the host exists in the user facility receiving the service provision of the SSP, the SSP is the IP address of the host in the user facility. The host name cannot be changed. The iSNS client installed on the host may generate a host identifier from these pieces of information and send it to the iSNS server, and identifier collision may occur between users. In the standard iSNS protocol, these identifiers are expected to be unique, and an iSNS service cannot be provided to hosts using duplicate identifiers.

  In the example of FIG. 13, the iSNS client A101 and the iSNS client B102 communicate with the iSNS server via the NAT device A111 and the NAT device B112, respectively. In such a situation, there is a possibility that the IP addresses used by the iSNS client A101 and the iSNS client B102 overlap. When iSNS client A101 and iSNS client B102 use IP addresses as network entity IDs, after iSNS client A101 registers this network entity ID with iSNS server 10, iSNS client B102 registers with the same network entity ID. When it is performed, it is determined that another iSNS client is going to change the content that the iSNS client A101 first registered, and registration by the iSNS client B102 is rejected.

  The present invention has been made in view of the above points, and when there are a plurality of computer terminals having the same identifier in the network (WAN), the computer terminal can be managed by centrally managing connection settings of the computer terminal and the storage device. It is an object of the present invention to provide an iSNS method, an iSNS server device, and a program that can uniquely identify a client.

  In order to solve the above-described problem, the ISSNS server apparatus according to the present invention is an iSNS object in which duplication of identification is likely to occur when information sent from an iSNS client is collated with information existing in an iSNS database. In the case of collation, it is confirmed whether or not the identifiers of the associated iSCSI nodes are the same. As shown in FIG. 13, in a situation where iSNS clients existing in a plurality of independent networks are accommodated by one iSNS server device, an identifier of an iSCSI (Internet Small Computer System Interface) node allocated to each host and device. Can be expected to be managed in a form that maintains uniqueness by the administrator of the iSNS server device. Utilizing this fact, the network entity that is the highest level object in the iSNS object hierarchy that represents each iSNS client in the iSNS database is going to be registered in the iSCSI node registered in the lower level or in the lower level. The condition is that there is no overlap in the set of iSCSI nodes. In addition, the collation of iSNS objects other than the iSCSI node (portal) is added on condition that the highest network entity is the same.

  FIG. 1 is a diagram for explaining the principle of the present invention.

The present invention (Claim 1) establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches an iSNS database when there are a plurality of computer terminals having the same identifier in the network. An iSNS method in an iSNS server device for performing
In an iSNS server device having an iSNS database storing a network entity table and an iSCSI node table,
a registration request message receiving step (step 1) for receiving a device attribute registration request message from the iSNS client;
A first search step (step 2) for searching the iSNS database based on the network entity ID of the device attribute registration request message;
If the network entity ID of the device attribute registration request message matches the network entity ID of the network entity table of the iSNS database (step 3, Yes), based on the network entity index corresponding to the network entity ID of the network entity table Search the iSCSI node table (step 4), obtain the iSCSI node index corresponding to the network entity index, and obtain the iSCSI name of the ISCSI node index (step 4); a second search step;
It is determined whether the iSCSI name acquired in the second search step matches the iSCSI name included in the device attribute registration request message (step 6). If they match (Yes in step 6), the device attribute registration request message The iSNS database is updated with the contents (step 7). If they do not match (step 6, No), the contents of the device request message are newly registered in the iSNS database (step 8), and the database update step is performed.

The present invention (Claim 2) establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches the iSNS database when there are a plurality of computer terminals having the same identifier in the network. An iSNS method in an iSNS server device for performing
In an iSNS server device having an iSNS database storing a network entity table and a portal table,
A receiving step of receiving a device attribute registration request message for registering a new portal;
A first search step of searching the iSNS database based on the portal IP address of the device attribute registration request message and the portal TCP port;
If the portal IP address of the device attribute registration request message, the portal TCP port, the portal IP address of the portal table of the iSNS database, and the portal TCP port match, correspond to the portal IP address and portal TCP port of the portal table. A second search step for searching the network entity index from the network entity table;
A third search step of searching for a corresponding network entity index from the iSCSI node table based on the iSCSI name included in the device attribute registration request message;
It is determined whether the network entity indexes acquired in the second and third search steps match. If they match, the iSNS database is updated with the content of the device attribute registration request message. If they do not match, the device attribute registration is performed. A database update step of newly registering the content of the request message in the iSNS database.

The present invention (Claim 3) establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches an iSNS database when there are a plurality of computer terminals having the same identifier in the network. An iSNS method in an iSNS server device for performing
In an iSNS server device having an iSNS database storing a network entity table and an iSCSI node table,
a deletion request message receiving step of receiving a device deletion request message from the iSNS client;
A first search step of searching the iSNS database based on the network entity ID of the device deletion request message;
When the network entity ID of the device deletion request message matches the network entity ID of the network entity table of the iSNS database, the iSCSI node table is searched based on the network entity index corresponding to the network entity ID of the network entity table; A second search step of obtaining an iSCSI node index corresponding to the network entity index and obtaining an iSCSI name of the ISCSI node index;
It is determined whether the iSCSI name acquired in the second search step matches the iSCSI name included in the device deletion request message. If they match, information corresponding to the network entity index from the network entity table and iSCSI node table of the iSNS database. And a delete step to delete.

  FIG. 2 is a principle configuration diagram of the present invention.

The present invention (Claim 4) establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches the iSNS database when there are a plurality of computer terminals having the same identifier in the network. An iSNS server device that performs
An iSNS database 29 storing a network entity table and an iSCSI node table;
registration request message receiving means 23 for receiving a device attribute registration request message from an iSNS client;
The iSNS database 29 is searched based on the network entity ID of the device attribute registration request message, and when the network entity ID of the device attribute registration request message matches the network entity ID of the network entity table of the iSNS database 29, the network Database search means 28 for searching the iSCSI node table based on the network entity index corresponding to the network entity ID of the entity table, acquiring the iSCSI node index corresponding to the network entity index, and acquiring the iSCSI name of the ISCSI node index When,
It is determined whether the iSCSI name acquired by the database search means 28 matches the iSCSI name included in the device attribute registration request message. If they match, the iSNS database 29 is updated with the contents of the device attribute registration request message, and they do not match. A registration unit 22 for newly registering the content of the device request message in the iSNS database 29.

The present invention (Claim 5) establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches the iSNS database when there are a plurality of computer terminals having the same identifier in the network. An iSNS server device that performs
An iSNS database storing a network entity table, an iSCSI node table, and a portal table;
Receiving means for receiving a device attribute registration request message for registering a new portal;
Based on the portal IP address of the device attribute registration request message and the portal TCP port, a first search means for searching the iSNS database, the portal IP address of the device attribute registration request message, the portal TCP port, and the iSNS database A second search means for searching a network entity index corresponding to the portal IP address and the portal TCP port of the portal table from the network entity table when the portal IP address of the portal table and the portal TCP port match; Third search means for searching for a corresponding network entity index from the iSCSI node table based on the iSCSI name included in the device attribute registration request message; A database search means comprising:
It is determined whether the network entity indexes acquired by the second and third search means match. If they match, the iSNS database is updated with the contents of the device attribute registration request message. If they do not match, the device attribute registration request Database updating means for newly registering the content of the message in the iSNS database.

The present invention (Claim 6) establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches the iSNS database when there are a plurality of computer terminals having the same identifier in the network. An iSNS server device that performs
An iSNS database storing a network entity table and an iSCSI node table;
delete request message receiving means for receiving a device delete request message from an iSNS client;
The iSNS database is searched based on the network entity ID of the device deletion request message, and when the network entity ID of the device deletion request message matches the network entity ID of the network entity table of the iSNS database, the network of the network entity table Database search means for searching an iSCSI node table based on a network entity index corresponding to an entity ID, acquiring an iSCSI node index corresponding to the network entity index, and acquiring an iSCSI name of the ISCSI node index;
It is determined whether the iSCSI name acquired by the database search means matches the iSCSI name included in the device deletion request message. If they match, the information corresponding to the network entity index is deleted from the network entity table and iSCSI node table of the iSNS database. Deleting means.

  The present invention (Claim 7) is a program for causing a computer to function as the iSNS server apparatus according to Claims 4 to 6.

  As described above, according to the present invention, when there are a plurality of computer terminals having the same identifier in the network (WAN), the input network entity information included in the device attribute request message and the reference network entity included in the iSNS database By collating the information, the computer terminal can be uniquely identified.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  In the following, processing when different iSNS clients have the same network entity ID or portal IP address and portal TCP (Transmission Control Protocol) port will be described.

  FIG. 3 shows the configuration of the iSNS server in one embodiment of the present invention.

  The iSNS server 20 shown in FIG. 1 includes a device attribute registration unit 22, a TCP communication unit 23, a database search unit 28, and an iSNS database 29.

  The iSNS client C103 will be described as a terminal that transmits a device attribute registration request message including input network entity information and reference network entity information to the iSNS server 20.

[First Embodiment]
In this embodiment, a case where a new network entity is registered in the iSNS database 29 will be described.

  Hereinafter, a detailed operation when the database search unit 28 collates the input network entity information included in the device attribute registration request message transmitted from the iSNS client C103 and the reference network entity information included in the iSNS database 29 will be described.

  FIG. 4 is a flowchart of the outline of the iSNS server in the first embodiment of the invention.

  The device attribute registration unit 12 of the iSNS server 20 receives a device attribute registration request message, which is a kind of iSNS request message, from the iSNS client C103 via the TCP communication unit 23 (step 101), and the network entity ID is described therein. If the device attribute registration request message is a request to newly register a network entity corresponding to the network entity ID, or an existing network entity already registered in the iSNS database 29 It is necessary to determine whether the request is for updating information. Therefore, the device attribute registration unit 22 transmits the network entity information included in the device attribute registration request message to the database search unit 18 (step 102), and collates with the network entity information registered in the iSNS database 29 one by one. (Step 103), it is necessary to search whether the same network entity is already registered in the iSNS database 29. As a result, if the same network entity is found (step 104, Yes), the network entity information discovered by the database search unit 18 is returned to the device attribute registration unit 22 (step 105), and the device attribute registration unit 22 Then, an update process for the network entity in the iSNS database 29 is performed (step 106). On the other hand, if the same network entity is not found, the network entity information is not returned to the device attribute registration unit 22 from the database search unit 28, and the device attribute registration unit 22 acquires the content of the device attribute registration request message. (Step 107), a new network entity is newly registered in the iSNS database 29 (step 108).

  FIG. 5 shows an example of a table of the iSNS database according to the first embodiment of the present invention.

  In the figure, as an example, the iSNS client A 101 and the iSNS client B 102 have already transmitted the device attribute registration request message to the iSNS server 20 and configured the iSNS database 29 in a state where the registration to the iSNS database 29 has been completed. The registration contents of the network entity table (A), iSCSI node table (B), and portal table (C) are shown.

  The network entity table shown in FIG. 5A stores a network entity index and a network entity ID. The iSCSI node table shown in FIG. 5B stores an iSCSI node index, an iSCSI name, and a network entity index. The portal table shown in FIG. 5C stores a portal index, a portal IP address, a portal TCP port, and a network entity index (detailed in the second embodiment).

  FIG. 6 shows an example of a device attribute registration request message in the first embodiment of the present invention. The device attribute registration request message shown in the figure has an attribute name, an attribute value, and an attribute type. Examples of attribute names include iSCSI names and network entity IDs.

  Here, a case where a device attribute registration request message in which an iSNS attribute as shown in FIG. 6 is described is transmitted from the iSNS client C103 to the iSNS server 20 and transmitted to the device attribute registration unit 22 will be described.

  FIG. 7 is a flowchart of the operation when a device attribute registration request message is received according to the first embodiment of this invention.

  The device attribute registration unit 22 determines that the request is an update or new registration request regarding a network entity whose value of the network entity ID associated with the message key attribute of the device attribute registration request message is “Example-Host” (step 201). ). In order to confirm whether the input network entity already exists in the iSNS database 29, the device attribute registration unit 22 instructs the database search unit 28 to search for the network entity ID “Example-Host” (step 202). ). The database search unit 28 searches the network entity table of FIG. 5A to determine that the network entity whose network entity index value is “2” matches the network entity ID (Yes in step 203). If there is no matching network entity ID in the iSNS database 29, it is determined that the information related to the device attribute registration request message is not stored in the iSNS database 29, and is newly registered in the iSNS database 29 (step 210).

  Normally, according to the ISNS protocol standard defined in the above-mentioned Non-Patent Document 1, the input network entity is determined to be the same as the network entity with the network entity index “2” at this stage.

  However, in the present invention, thereafter, the device attribute registration unit 22 further searches the iSCSI node table of FIG. 5B for the network entity index value “2” (step 204). As the relevant iSCSI nodes, two iSCSI nodes having iSCSI node indexes “2” and “3” are searched (step 205, Yes, step 206, Yes).

  Next, it is checked whether the iSCSI names “Node_B_1” and “Node_B_2” of these two iSCSI nodes match the iSCSI names “Node_C_1” and “Node_C_2” described in the device attribute registration request message shown in FIG. (Step 207). In this example, since there is no match (step 208, No), it is determined in the present invention that the input network entity does not exist in the iSNS database 29, and a new network entity is displayed by the device registration unit 22 in FIG. (Step 210). On the other hand, if the iSCSI name associated with the network entity index of the iSCSI node table matches the iSCSI name of the device attribute registration request message, the iSNS database 29 is updated with the content of the device attribute registration request message (step 209). .

  When a new network entity is registered in the iSNS database 29, the network index “3” and the network entity ID “Example-Host” are registered in the network entity table (A) as shown in FIG. In the node table (B), an iSCSI node index “4”, an iSCSI name “Node_C_1”, a network entity index “3”, an iSCSI node index “5”, an iSCSI name “Node_C_2”, and a network entity index “3” are registered. Is done.

[Second Embodiment]
Since the configuration of the iSNS server in the present embodiment is the same as the configuration of FIG. 3, the description thereof is omitted.

  In the present embodiment, an example of requesting portal registration as a device attribute request message will be described. Hereinafter, it is referred to as a “portal registration request message”.

  The tables in the iSNS database 29 referred to in the present embodiment are the network entity table, portal table, iSCSI node table in FIG. 8, and portal registration request message in FIG.

  FIG. 10 is a flowchart of the operation when a portal registration request message is received according to the second embodiment of this invention.

  The database search unit 28 extracts the portal IP address and portal TCP port of the portal registration request message (step 301). Based on the extracted portal IP address and portal TCP port, the portal index is searched from the portal table of FIG. 8C (step 302).

  As a result of the search, portal indexes “1” and “4” are searched from the portal table (step 303, Yes). Normally, both of these portals can be regarded as the same as the portal of the portal registration request message.

  However, in the present invention, the network entity indexes “1” and “3” respectively corresponding to the portal indexes “1” and “4” acquired from the portal table are acquired from the portal table (FIG. 8C) (FIG. 8C). Step 304).

  Based on the iSCSI name included in the portal registration request message, the iSCSI node table of FIG. 8B is searched, and the iSCSI node index “5” and the network entity index “3” corresponding to the iSCSI name are searched (step) 305). When this is compared with the network entity index “1” corresponding to the portal index “1” and the network entity index “3” corresponding to the portal index “4” retrieved from the portal table of FIG. Because the latter matches the network entity index “3” corresponding to the portal index “4” (Yes in step 306), the portal with the portal index “4” is regarded as the same portal as the portal described in the portal registration request message. The portal index “4” in the portal table of FIG. 8C is updated according to the content of the portal registration request message (step 307).

  If any of the portals retrieved in step 304 does not match the corresponding network entity index retrieved in step 305 in step 306 (step 306, No), a new portal IP address is obtained. A portal having “192.168.0.1” and portal TCP port “12345” is registered together with a portal index having a new value and the network entity index retrieved in step 305 (step 308).

  As described above, according to the present invention, even when the network entity ID, the portal IP address, and the portal TCP port collide, registration to the iSNS database is possible.

[Third Embodiment]
In the present embodiment, the deletion process will be described.

  Assume that the state of the ISNS database 29 is as shown in FIG. At this time, it is assumed that the iSNS server 20 receives a device deletion request message having the attributes shown in FIG. The device deletion request message includes an attribute name, an attribute value, and an attribute type. In the example of FIG. 11, the device deletion request message requests deletion of the network entity ID “Example-Host” from the iSNS database 29. Therefore, the database search unit 28 of the iSNS server 20 selects the network entity. Search from the network entity table (FIG. 8A). As a result, the network entity indexes “2” and “3” are searched. Here, the iSNS server 20 of the present invention compares the iSCSI name “Node_B_1” described in the message shown in FIG. 11 with the set of iSCSI nodes associated with each searched network entity.

  FIG. 12 is a flowchart of the operation when a device deletion request message is received according to the third embodiment of the present invention.

  A specific comparison method is as follows.

  1) The network index “2” is searched from the network entity table (FIG. 5A) with the network entity ID “Example-Host” in the device deletion request message (step 402).

  2) The iSCSI node table (FIG. 5B) is searched with the searched network index “2”, and iSCSI nodes “Node_B_1” and “Node_B_2” with the iSCSI node indexes “2” and “3” are obtained (steps). 404).

  3) When these iSCSI names “Node_B_1” “Node_B_2” and the attribute value “Node_B_1” of “iSCSI name” which is the attribute name of the device deletion request message in FIG. 11 are collated (step 406), the iSCSI node index is “2”. (Step 407, Yes). In this case, the ISCSI node index data in the iSCSI node table is deleted.

  On the other hand, when the same processing is performed for the network entity having the iSCSI node index “3” of 2) above, the iSCSI name of the iSCSI node index “3” in FIG. 5B is “Node_B_2”, which matches. No (Step 407, No). That is, an iSCSI node with a matching iSCSI name is not searched.

  From the above result, it can be determined that the device deletion request message in FIG. 11 is a deletion request for a network entity whose network entity index value is “2”.

  In addition, the function of the iSNS server of said 1st-3rd embodiment can be constructed | assembled as a program, and it can install in the computer utilized as an iSNS server, or can distribute | circulate it via a network.

  Further, the constructed program can be stored in a portable storage medium such as a hard disk, a flexible disk, or a CD-ROM, and can be installed or distributed in a computer.

  The present invention is not limited to the above-described embodiments and examples, and various modifications and applications can be made within the scope of the claims.

  The present invention is applicable to a technique for uniquely identifying a computer in a system having a plurality of computers having the same identifier in a network that is IP-connected to a plurality of storage apparatuses.

It is a figure for demonstrating the principle of this invention. It is a principle block diagram of this invention. It is a block diagram of the iSNS server in the 1st Embodiment of this invention. It is a flowchart of operation | movement of the iSNS server in the 1st Embodiment of this invention. It is an example of the table of the iSNS database in the 1st Embodiment of this invention. It is an example of the device attribute registration request message in the 1st Embodiment of this invention. It is a flowchart of operation | movement at the time of receiving the device attribute registration request message in the 1st Embodiment of this invention. It is an example of the iSNS database in which the network entity in the 1st Embodiment of this invention was newly registered. It is an example of the portal registration request message in the 2nd Embodiment of this invention. It is a flowchart of operation | movement at the time of receiving the portal registration request message in the 2nd Embodiment of this invention. It is an example of the device deletion request message in the 3rd Embodiment of this invention. It is a flowchart of operation | movement at the time of receiving the device deletion request message in the 3rd Embodiment of this invention. It is a structural example of the conventional iSNS.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 iSNS server 11 TCP connection management part 12 Device attribute registration part 13 Device deletion part 14 State change notification registration part 15 State change notification deletion part 16 Entity state inquiry part 17 State change notification part 18 Database search part 19 iSNS database 20 iSNS server 22 Registration unit, device attribute registration unit 23 registration request message reception unit, TCP communication unit 28 database search unit, database search unit 29 iSNS database 101 iSNS client A
102 iSNS client B
103 iSNS client C
111 NAT device A
112 NAT device B

Claims (7)

iSNS (Internet Storage Name Service) client establishes TCP (Transmission Control Protocol) connection, performs iSNS communication using the TCP connection, and updates the iSNS database when there are multiple computer terminals with the same identifier in the network An iSNS method in an iSNS server device that performs a search,
In an iSNS server device having an iSNS database storing a network entity table and an iSCSI node table,
A registration request message receiving step of receiving a device attribute registration request message from the iSNS client;
A first search step of searching an iSNS database based on a network entity ID of the device attribute registration request message;
If the network entity ID of the device attribute registration request message matches the network entity ID of the network entity table of the iSNS database, the iSCSI node is based on the network entity index corresponding to the network entity ID of the network entity table. Searching a table, obtaining an iSCSI node index corresponding to the network entity index, and obtaining an iSCSI name of the ISCSI node index;
It is determined whether the iSCSI name acquired in the second search step matches the iSCSI name included in the device attribute registration request message. If they match, the iSNS database is updated with the content of the device attribute registration request message. If they do not match, a database update step for newly registering the contents of the device request message in the iSNS database;
ISNS method characterized by performing. An iSNS method in an iSNS server device that establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches an iSNS database when there are a plurality of computer terminals having the same identifier in the network. There,
In an iSNS server device having an iSNS database storing a network entity table and a portal table,
A receiving step of receiving a device attribute registration request message for registering a new portal;
A first search step of searching an iSNS database based on a portal IP address of the device attribute registration request message and a portal TCP port;
If the portal IP address and portal TCP port of the device attribute registration request message match the portal IP address and portal TCP port of the portal table of the iSNS database, the portal IP address and portal TCP port of the portal table A second search step of searching the network entity table for a network entity index corresponding to
A third search step of searching a corresponding network entity index from the iSCSI node table based on an iSCSI name included in the device attribute registration request message;
It is determined whether or not the network entity indexes acquired in the second and third search steps match, and if they match, the iSNS database is updated with the content of the device attribute registration request message. A database update step for newly registering the contents of the device attribute registration request message in the iSNS database;
ISNS method characterized by performing. An iSNS method in an iSNS server device that establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches an iSNS database when there are a plurality of computer terminals having the same identifier in the network. There,
In an iSNS server device having an iSNS database storing a network entity table and an iSCSI node table,
A deletion request message receiving step of receiving a device deletion request message from the iSNS client;
A first search step of searching an iSNS database based on a network entity ID of the device deletion request message;
If the network entity ID of the device deletion request message matches the network entity ID of the network entity table of the iSNS database, the iSCSI node table is based on the network entity index corresponding to the network entity ID of the network entity table. A second search step of obtaining an iSCSI node index corresponding to the network entity index and obtaining an iSCSI name of the ISCSI node index;
It is determined whether the iSCSI name acquired in the second search step matches the iSCSI name included in the device deletion request message. If they match, from the network entity table and the iSCSI node table of the iSNS database. A deletion step of deleting information corresponding to the network entity index;
ISNS method characterized by performing. An iSNS (Internet Storage Name Service) client establishes a TCP connection, performs iSNS communication using the TCP connection, and updates / searches an iSNS database when there are a plurality of computer terminals having the same identifier in the network A server device,
An iSNS database storing a network entity table and an iSCSI node table;
Registration request message receiving means for receiving a device attribute registration request message from the iSNS client;
The iSNS database is searched based on the network entity ID of the device attribute registration request message, and when the network entity ID of the device attribute registration request message matches the network entity ID of the network entity table of the iSNS database, Database search for searching the iSCSI node table based on the network entity index corresponding to the network entity ID of the network entity table, acquiring the iSCSI node index corresponding to the network entity index, and acquiring the iSCSI name of the ISCSI node index Means,
It is determined whether the iSCSI name acquired by the database search means matches the iSCSI name included in the device attribute registration request message. If they match, the iSNS database is updated with the content of the device attribute registration request message. If they do not match, registration means for newly registering the contents of the device request message in the iSNS database;
An iSNS server device characterized by comprising: An iSNS server device that establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches an iSNS database when there are a plurality of computer terminals having the same identifier in the network,
An iSNS database storing a network entity table, an iSCSI node table, and a portal table;
Receiving means for receiving a device attribute registration request message for registering a new portal;
First search means for searching an iSNS database based on a portal IP address and a portal TCP port of the device attribute registration request message; a portal IP address of the device attribute registration request message; a portal TCP port and the iSNS database When the portal IP address of the portal table and the portal TCP port match, the second search means for searching the network entity index corresponding to the portal IP address of the portal table and the portal TCP port from the network entity table And a corresponding network entity index is retrieved from the iSCSI node table based on the iSCSI name included in the device attribute registration request message. Database search means having third search means;
It is determined whether or not the network entity indexes acquired by the second and third search means match, and if they match, the iSNS database is updated with the content of the device attribute registration request message. Database update means for newly registering the contents of the device attribute registration request message in the iSNS database;
An iSNS server device characterized by comprising: An iSNS server device that establishes a TCP connection with an iSNS client, performs iSNS communication using the TCP connection, and updates / searches an iSNS database when there are a plurality of computer terminals having the same identifier in the network,
An iSNS database storing a network entity table and an iSCSI node table;
Delete request message receiving means for receiving a device delete request message from the iSNS client;
The iSNS database is searched based on the network entity ID of the device deletion request message, and when the network entity ID of the device deletion request message matches the network entity ID of the network entity table of the iSNS database, the network entity Database search means for searching the iSCSI node table based on a network entity index corresponding to a network entity ID of the table, acquiring an iSCSI node index corresponding to the network entity index, and acquiring an iSCSI name of the ISCSI node index; ,
It is determined whether the iSCSI name acquired by the database search means matches the iSCSI name included in the device deletion request message. If they match, the network entity table and the iSCSI node table of the iSNS database are used for the network. A deletion means for deleting information corresponding to the entity index;
An iSNS server device characterized by comprising: Computer
A program that functions as the iSNS server device according to claim 4.

Images