JP2003143176A - Method for managing group of network resource - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method for dispersedly managing DHCP (dynamic host configuration protocol) servers for managing the set information of equipment to be connected to a network in each specific group and managing the set information of equipment to be connected in each specific group. SOLUTION: Group ID for recognizing a specific group is registered in each of DHCP clients and DHCP servers, each DHCP client adds the group ID to a new option field of a DHCP message and transmits the DHCP message and resource information including an IP address specific for the group specified by the group ID is registered in a DHCP server. The DHCP server extracts the group ID from the new option field of the received DHCP message, determines whether the extracted group ID is matched with the registered group ID or not, and when matched, sends the resource information specific for the group.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network resource group management method, and more particularly to an IP (Internet).
The present invention relates to a method for centrally managing network resources such as an IP address in a network device that uses et protocol).

[0002]

2. Description of the Related Art Conventionally, as a method for dynamically obtaining an IP address, DHCP (Dynamic Host Con) is used.
(figure protocol). In this protocol, since the client acquires the IP address, it is directed to the DHCP server <DHCPDISCO
Broadcast transmission of VER>. <DHCPDI
The DHCP server that received the SCOVER> is
Address (Server's IP Address)
And returns <DHCPOFFER> to the client side. The client receiving <DHCPOFFER> determines one DHCP server receiving the IP address from the received <DHCPOFFER>,
Insert the IP address of the determined server <DHCPR
EQUEST> is broadcasted to the DHCP server. If the IP address can be loaned, the DHCP server sends <DHCPACK> to the client to lend the IP address. In this way, the client dynamically obtains the IP address.

By the way, when a plurality of devices exist on the same LAN, all the clients connected to the broadcast domain need to centrally manage all necessary various information. However, in the conventional standard DHCP IP address distribution method, when a client requests lending an IP address, there is no mechanism for mutual selection and identification between the client and the server, and for a client that establishes and manages multiple DHCP servers. It is not possible to select the management server for each model group.

As another conventional technique, in the network system and the DHCP server selection method described in Japanese Patent Laid-Open No. 11-154978, the DHCP
A reference address is provided in the address area of the IP address owned by the P server, the difference between the IP address requested by the client and the reference address is calculated, and the DHCP server is selected. As a result, it is possible to operate multiple DHCP servers to distribute the load on the clients,
After all, each client belongs to a certain group, and various information required for each group cannot be centrally managed.

[0005]

In recent years, not only computers such as workstations and personal computers (hereinafter referred to as PCs) but also various consumer appliances have come to be used as terminals connected to Ethernet (registered trademark). It was The current network management requires setting for each device connected to the network, and there is a problem in that managing the network resources required by these devices with one DHCP server imposes a heavy burden on the network administrator. .

[0006] Therefore, the present invention has been made in view of the above problems in the prior art, and an object of the present invention is to provide a method for managing setting information of devices connected to a network for each specific group. To do. Another object of the present invention is to provide a method for decentralized management of a DHCP server that manages setting information of devices connected to each specific group.

[0007]

In order to achieve the above object, an invention according to claim 1 is a network resource group management method, which comprises a DHCP client and a DHCP.
A group ID for recognizing a specific group is registered in each of the P servers, and the DHCP client is caused to add the group ID to a new option field of a DHCP message to be transmitted, and to the DHCP server,
DHC received by registering resource information including an IP address unique to the group specified by the group ID
The group ID is extracted from the new option field of the P message to determine whether it is the same as the registered group ID. If they are the same, the resource information peculiar to the group is transmitted.

According to the first aspect of the present invention, even if there is only one DHCP server according to the first aspect or there are a plurality of DHCP servers having different group IDs, the clients belonging to a specific group Resource information including a specific IP address can be provided.

According to a second aspect of the present invention, in the network resource group management method according to the first aspect, the DH
The CP client extracts the group ID from the new option field of the DHCP response message from the DHCP server, determines whether the group ID is the same as the registered group ID, and determines a plurality of DHs having the same group ID.
It is characterized in that a message requesting provision of resource information is sent to one of the CP servers.

According to the second aspect of the present invention, even in an environment in which a plurality of DHCP servers according to the first aspect and normal DHCP servers coexist, D belonging to a specific group
Resource information including a specific IP address can be provided only to the DHCP client, and a normal DH can be provided to the DHCP client that does not belong to a specific group.
Resource information including an IP address can be provided from the CP server.

According to a third aspect of the present invention, in the network resource group management method according to the first aspect, the DH
The CP client extracts the group ID from the new option field of the DHCP response message from the DHCP server and determines whether it is the same as the registered group ID, and if there is no DHCP server having the same group ID, , A message for requesting provision of resource information is sent in response to a normal DHCP response message from a DHCP server.

According to the third aspect of the present invention, there is no DHCP server belonging to a specific group, and a normal DHC
When only the P server exists, the resource information including the IP address can be provided from the normal DHCP server.

According to a fourth aspect of the present invention, in the network resource group management method according to the first, second or third aspect, a plurality of group IDs are registered in the DHCP server, and a new option field of a received DHCP message is selected. The group ID is extracted, and it is determined whether the group ID is the same as any of the plurality of group IDs. If the group ID is the same as any of the plurality of group IDs, resource information specific to the group Is transmitted.

According to the invention described in claim 4, when there is one or a plurality of DHCP servers described in the claim, each client belonging to a plurality of specific groups includes a specific IP address. Resource information can be provided.

According to a fifth aspect of the present invention, there is provided a DHCP client, a means for registering a group ID for recognizing a specific group, and a means for adding the group ID to a new option field of a DHCP message and transmitting it. It is characterized by having and.

By combining the DHCP client according to claim 5 and the DHCP server according to claim 8, when there is one DHCP server according to this claim, or when there are a plurality of DHCP servers having different group IDs. However, it is possible to provide the resource information including the specific IP address to the clients belonging to the specific group.

The invention according to claim 6 is the D according to claim 5.
HCP client, D from DHCP server
The registered group ID is obtained by extracting the group ID from the new option field of the HCP response message.
And a means for sending a message requesting provision of resource information to one DHCP server among a plurality of DHCP servers having the same group ID. .

A DHCP client according to claim 6, a plurality of DHCP servers according to claim 8, and normal DHCP
Even in an environment in which servers are mixed, resource information including a specific IP address can be provided only to DHCP clients that belong to a specific group, and normal DHCP can be provided to DHCP clients that do not belong to a specific group. Resource information including an IP address can be provided from the server.

The invention according to claim 7 is the D according to claim 5.
HCP client, D from DHCP server
The registered group ID is obtained by extracting the group ID from the new option field of the HCP response message.
And a DHCP server having the same group ID does not exist.
Means for sending a message requesting provision of resource information in response to a DHCP response message from the HPC server.

According to the DHCP client described in claim 7, when there is no DHCP server belonging to a specific group and only a normal DHCP server exists, resource information including an IP address is sent from the normal DHCP server. Can be provided.

The invention according to claim 8 is a DHCP server, which is a group ID for recognizing a specific group.
Registering the resource information including the IP address specific to the group identified by the group ID, extracting the group ID from the new option field of the received DHCP message, and registering the registered group ID. Means for determining whether they are the same, the extracted group ID and the registered group I
When D is the same, means for sending the resource information peculiar to the group is provided.

A DHCP server according to claim 8 and claim 5.
By combining the described DHCP clients, resource information including a specific IP address for a client belonging to a specific group even if there is only one DHCP server or if there are multiple DHCP servers having different group IDs. Can be provided.

The invention according to claim 9 is the D according to claim 8.
An DHCP server, wherein the DHCP server can register a plurality of group IDs and receives the received DHCP.
Group I from New Options field of message
D is retrieved and the group ID is the group I
The group ID is determined by determining whether it is the same as any of D.
Is the same as any of the plurality of group IDs, the resource information peculiar to the group is transmitted.

A DHCP server according to claim 9 and claim 5.
By combining the DHCP clients described in the claims, when there is one or a plurality of DHCP servers described in the claim, resource information including a specific IP address is provided to the clients belonging to a plurality of specific groups. can do.

[0025]

BEST MODE FOR CARRYING OUT THE INVENTION Next, a specific example of an embodiment of a network resource group management method according to the present invention will be described with reference to the drawings.

FIG. 1 shows the overall configuration of a network system to which the network resource group management method according to the present invention is applied. This network system is a DHC.
P server (hereinafter simply referred to as “server”) 110 and D
HCP clients (hereinafter, simply referred to as “clients”) 101 to 105 are connected by a LAN 112, and a server 111 and clients 106 to 109 are L.
It is connected by AN113. In addition, LAN11
2 and the LAN 113 are connected via a bridge (or router) 114.

In order to automatically acquire and distribute the IP address, a message of the format shown in FIG. 2 is transmitted and received between the client and the server. Each client connected to this network first sends a DHC to the server.
Send PDISCOVER. DHCPDISCOV
The server that receives the ER determines the corresponding IP address from a predetermined address area that has been assigned in advance, and sends DHCPOFFER to the client. When the client receives DHCPOFFER, it requests an IP address.
Send the EST. If the server that has received the IP address can distribute the IP address, the server sends DHCPACK to the client and transits to the BOUND state.

Here, the server 110 basically includes not only the clients 101 to 105 but also the client 106.
To 109, the server 110 can distribute the IP address to the clients 101 to 105.
It is also possible to distribute the IP address to.
Therefore, it is up to the client to select which server. Therefore, the network administrator must register various information required by each device in all of the plurality of servers 110 and 111. Therefore, the present embodiment is configured so that each client belonging to a specific group can centrally manage various information of the group.

Next, the overall operation of this embodiment will be described in detail with reference to the sequence diagrams of FIGS.

First, in step 301 of FIG. 3, on the client side, the client sets PRODUCT
_GROUP is determined whether it belongs, PRODUCT
If the client belongs to _GROUP, in steps 302 and 304, a new "PRODUU" in the option field (201 in FIG. 2) of the DHCP message is sent.
A group ID (here, "PRODUCT_GROUP") indicating a specific group in the "CT_TYPE" field.
), To assemble DHCPDDISCOVER, and in step 305, DHCPDISCOVE
Send R.

On the other hand, in the case of a client which does not belong to PRODUCT_GROUP, in step 303, DHPDDISCOVER is assembled, and in step 3
At 05, DHPDDISCOVER is transmitted.

Next, as shown in FIG.
In step 402, the server that has received the DHPDDISCOVER message determines whether or not the PRODUCT_TYPE mode is set, and then the PRODUCT_T
If the YPE mode is set, step 40
In 3, it is determined whether or not "PRODUCT_GROUP" is inserted in the "PRODUCT_TYPE" field.

If "PRODUCT_GROUP" is inserted in the "PRODUCT_TYPE" field, the DHCP is executed in step 404.
Assemble the OFFER, and in step 407, DH
"PRODUCT_GROUP" is inserted in the "PRODUCT_TYPE" field of CPOFFER, and DHCPOFFER is transmitted in step 408.

On the other hand, in step 403, "PRO
In the DUCT_TYPE field, "PRODUCT
If “_GROUP” is not detected, then in step 405, the DHCPPDISCOVER is discarded.

Further, in step 402, PROD
If it is determined that the UCT_TYPE mode is not set, in step 406, DHCPOFF is set.
Assemble ER, and in step 408, DHCPO
Send FFER.

Further, in FIG. 5, on the client side, DHCPOFFER is received in step 501, and in step 502, “PRODUCT_G” is received.
It is determined whether or not the domain belongs to "ROUP", and "PRO
In the case of a domain belonging to “DUCT_GROUP”,
In step 503, “PRODUCT_TYP
It is determined whether or not "PRODUCT_GROUP" is detected in the "E" field, and if it is detected, the DHCPDREQUEST is assembled in step 504, and the "PRODUCT_T" in step 507.
In the "YPE" field, "PRODUCT_GROU"
P ”is inserted, and in step 508, a desired IP address is inserted in the RequestedIP address part in the option field, and in step 509, D
Send HCP REQUEST.

On the other hand, in step 503, "PRO
In the DUCT_TYPE field, "PRODUCT
If “_GROUP” is not detected, DHCPOFFER is discarded in step 505.

Further, in step 502, "PRO
If it is not a domain belonging to “DUCT_GROUP”, in step 506, DHPDPDREQ
Assemble the UEST, insert a desired IP address into the RequestedIP address part in the option field in step 508, and send DHCPREQUEST in step 509.

That is, in FIG. 5, the clients belonging to a particular group receive the DHCPOFFER
In the "PRODUCT_TYPE" field of
When "ODUCT_GROUP" is found, DHCPREQUEST is preferentially transmitted to the server. If the received DHCPOFFER's PRODUCT_T
In the "YPE" field, "PRODUCT_GROUP"
If the message owning "P" cannot be found, one of the collected DHCPOFFER is selected and DHCPREQUEST is transmitted to the server.
At this time as well, the "PRODUU" of DHCPOFFER
In the "CT_TYPE" field, "PRODUCT_G
When "ROUP" is detected, "PRODUCT_T
In the "YPE" field, "PRODUCT_GROU"
P ”is inserted.

Next, as shown in FIG. 6, DHCPREQ
The server receiving the UEST sends DHCPACK to the client if the IP address can be loaned, and B
Transition to the OUND (lease) state (step 601 to
609).

In FIG. 7, "PRODUCT_GRO
It is assumed that there are a mixture of PRODUCT_TYPE mode servers that recognize "UP" and standard servers. In steps 701 and 702, PRODUCT_GRO
A client belonging to UP sends a DHCPD to the server.
When ISCOVER is transmitted, steps 704 and 70
In 6, the standard server operates according to the DHCP specifications and performs a series of exchanges regarding lending of IP addresses.

At this time, the received DHCPDISCOV
PRO in the PRODUCT_TYPE field of the ER
DH if DUCT_GROUP is inserted
When sending COFFER, the PRODUCT_T
Insert PRODUCT_GROUP in the YPE field. On the other hand, the server in the PRODUCT_TYPE mode uses the option field “PRODUCT_TYPE
When it is confirmed that "PRODUCT_GROUP" is inserted in the "E" field, DHPDDISCO
Analyze VER, assemble DHCPOFFER and send.

In step 705, the client waits for a certain period of time to collect DHCPOFFER, and then D
When receiving the HCPOFFER, the received DHCPDPI
PRODUC in the option field of SCOVER
Check the T_TYPE field, steps 706, 7
At 07, one server is selected from among those in which the group ID indicating the group to which the client itself belongs is inserted, and DHCPREQUEST is assembled and transmitted.

In steps 708 and 710, the server sends DHCPACK if the IP address can be loaned.
To enter the BOUND (lease) state. As a result, P that recognizes "PRODUCT_GROUP"
A server in ROOT_TYPE mode is
I only for clients that belong to CT_GROUP
Allows P address lending.

In FIG. 8, PRODUCT_TYPE
Mode servers exist, each of which has a "PRODUCT_G
"ROUP", "ANOTHER_PRODUCT_GR
It is assumed that "OUP" is recognized. First, step 80
1 and 802, a client belonging to PRODUCT_GROUP sends a DHCPPDISCO to the server.
Send VER. The server that recognizes "PRODUCT_GROUP" performs a series of exchanges in steps 804 to 809, but "ANOTHER_PR"
A server recognizing "ODUCT_GROUP" has "ANOTHER_PRODUCT_GR" in the "PRODUCT_TYPE" field of the option field.
Since a group ID different from "UP" is inserted,
In step 803, the DHCPPDISCOVER is discarded and DHCPOFFER is not sent to the client. This makes it possible to select the IP address lending depending on which group the client belongs to in the PRODUCT_TYPE mode server.

In FIG. 9, "PRODUCT_GRO
It is assumed that the PRODUCT_TYPE mode servers that recognize "UP" and standard servers are mixed. First, in steps 901 and 902, the standard client sends DHPDDISCOVER to the server. The standard server exchanges according to the DHCP specification in steps 903 to 908.
The server in the UCT_TYPE mode does not insert the option field “PRODUCT_GROUP”, and therefore, in step 904, the DHCPPDISC is performed.
Discard OVER and do not send DHCPOFFER.
As a result, the server in the PRODUCT_TYPE mode can selectively refuse the lending of the IP address to the standard client.

In FIG. 10, it is assumed that only standard servers exist. In steps 1001 and 1002, the client belonging to PRODUCT_GROUP sends DHPDDISCOVER to the server. The server receiving the DHCPDISCOVER,
Since this is a conventional standard server, steps 1003 and 10
In 04, the operation is performed according to the normal DHCP specification, and DHCPOFFER is transmitted to the client. Here, in order to collect DHCPOFFER, a certain time is waited. Then, in steps 1006 and 1007, one server is selected from the collected DHCPOFFERs and DHCPREQUEST is transmitted. Hereinafter, in steps 1008 and 1009, normal DH is performed.
It operates according to the specifications of the CP and performs a series of exchanges of IP address lending. As a result, PRODUCT_G
Even if the server to which the client belonging to the ROW applies for the IP address loan has only a standard server, the IP address can be loaned.

In this way, PRODUCT_TYPE
On a LAN where E-mode servers and standard servers are mixed and clients belonging to various groups exist, various information can be centrally managed for each group.
Also, from these, it can be seen that even if the standard server exists in the same broadcast domain, it operates without problems according to the normal DHCP specifications.

Next, another embodiment of the present invention will be described with reference to FIG. In the figure, PROD
The server in UCT_TYPE mode is "PRODUCT_
GROUP "and" ANOTHER_PRODUCT_G
It is extended so that a plurality of groups can be recognized, such as "ROUP". First, in steps 1101 and 1102, a client belonging to PRODUCT_GROUP and ANOTHER_PRODUCT_GROUP
Clients belonging to the group apply for IP address lending, so DHPDDISCOVER is PRODUCT_TY
Send to PE mode server. At that time, DHC
In the PRODUCT_TYPE field of PDISCOVER, each has a specific group ID "PR".
OUTPUT_GROUP "and" ANOTHER_
"PRODUCT_GROUP".

"PRODUCT_GROUP" and "ANOTHER" which have received the respective DHCPPDISCOVER
A server in the PRODUCT_TYPE mode that recognizes both "_PRODUCT_GROUP" and "PRODUCT_GROUP" has "PRODUCT_GROUP" and "ANOTTHE" in the PRODUCT_TYPE field in the option field.
R_PRODUCT_GROUP ”for each DHCPD
Since it was found in ISCOVER, in steps 1103 and 1104, DHCPO is performed for both parties.
Send FFER. At that time, "PRODUCT_GROUP" and "ANOTHER_" indicating each group
"PRODUCT_GROUP" is inserted and transmitted. In this way, by making the server recognize the group IDs indicating a plurality of specific groups, it is possible to manage various information of those groups by one server.

[0051]

As described above, according to the present invention,
A group management method of network resources capable of managing setting information of devices connected to a network for each specific group can be provided. It is also possible to provide a network resource group management method capable of distributed management of DHCP servers that manage the setting information of the devices to be connected for each specific group.

[Brief description of drawings]

FIG. 1 is a diagram showing an example of the overall configuration of a network system used in a network resource group management method according to the present invention.

FIG. 2 is a diagram showing a format of a message exchanged between a server and a client in the network resource group management method according to the present invention.

FIG. 3 shows a DH from a client to a server in FIG.
It is a flowchart figure of operation | movement when assembling and transmitting CPDISCOVER.

FIG. 4 is a diagram showing the DH from the server to the client in FIG.
It is a flowchart figure of operation | movement when assembling and transmitting CPOFFER.

FIG. 5: In FIG. 1, DH from client to server
It is a flowchart figure of operation | movement when assembling and transmitting CPREQUEST.

FIG. 6 is a diagram showing the DH from the server to the client in FIG.
It is a flowchart figure of operation | movement when assembling and transmitting CPACK (or DHPNAK).

FIG. 7 is a sequence diagram when a client belonging to PRODUCT_GROUP exchanges DHCP messages when there is a PRODUCT_TYPE mode server that recognizes PRODUCT_GROUP and a standard server in the network resource group management method according to the present invention. Is.

FIG. 8 is a network resource group management method according to the present invention, in which a PRODUCT_TYPE mode server that recognizes PRODUCT_GROUP and an AN.
FIG. 9 is a sequence diagram when a client belonging to PRODUCT_GROUP exchanges a DHCP message when there is a PRODUCT_TYPE mode server that recognizes OTHER_PRODUCT_GROUP.

FIG. 9 is a diagram illustrating a network resource group management method according to the present invention. When a PRODUCT_TYPE-mode server that recognizes PRODUCT_GROUP and a standard server exist, a client requesting IP address lending by a normal communication exchanges a DHCP message. It is a sequence diagram when doing.

FIG. 10 is a sequence diagram when a client belonging to PRODUCT_GROUP exchanges a DHCP message when only standard servers exist on the network in the network resource group management method according to the present invention.

FIG. 11 is a diagram showing a network resource group management method according to the present invention, wherein PRODUCT_GROUP and AN are used.
When there is a server in PRODUCT_TYPE mode that recognizes OTHER_PRODUCT_GROUP, PRODUCT_GROUP and ANOTHE
It is a sequence diagram when each client belonging to R_PRODUCT_GROUP exchanges a DHCP message.

[Explanation of symbols]

101-109 clients 110 servers 111 server 112 LAN 113 LAN 114 bridge / router 115 Bridge / Router

Claims (9)

[Claims] 1. A group I for identifying a specific group to each of a DHCP client and a DHCP server.
D is registered, and the group ID is DH to the DHCP client.
The resource information including the IP address unique to the group specified by the group ID is registered in the DHCP server in addition to the new option field, and the group ID is registered from the new option field of the received DHCP message. Is taken out to judge whether it is the same as the registered group ID, and if it is the same, the resource information peculiar to the group is sent out. 2. The DHCP client is a DHCP client.
The group ID is extracted from the new option field of the DHCP response message from the server, it is determined whether the group ID is the same as the registered group ID, and one of the plurality of DHCP servers having the same group ID is used as the DHCP server.
2. The network resource group management method according to claim 1, wherein a message requesting provision of resource information is sent to the P server. 3. The DHCP client is a DHCP client.
The group ID is extracted from the new option field of the DHCP response message from the server, and it is determined whether or not it is the same as the registered group ID. If there is no DHCP server having the same group ID, the normal DHCP server 2. The network resource group management method according to claim 1, wherein a message requesting provision of resource information is transmitted in response to a DHCP response message from the server. 4. A plurality of group IDs are registered in the DHCP server, a group ID is extracted from a new option field of a received DHCP message, and it is determined whether the group ID is the same as any of the plurality of group IDs. 4. The method according to claim 1, 2 or 3, wherein when the group ID is the same as any of the plurality of group IDs, resource information specific to the group is transmitted. . 5. A DHCP client comprising: means for registering a group ID for recognizing a specific group; and means for adding the group ID to a new option field of a DHCP message and transmitting it. 6. A means for extracting a group ID from a new option field of a DHCP response message from the DHCP server and determining whether or not the group ID is the same as the registered group ID, and a plurality of DHCP servers having the same group ID. 6. The DHCP client according to claim 5, further comprising means for sending a message requesting provision of resource information to one of the DHCP servers. 7. A means for extracting a group ID from a new option field of a DHCP response message from the DHCP server to determine whether or not the group ID is the same as the registered group ID, and a DHCP server having the same group ID does not exist. In this case, the device further comprises means for sending a message requesting provision of resource information in response to a normal DHCP response message from the DHCP server.
The DHCP client described. 8. A means for registering a group ID for recognizing a specific group, a means for registering resource information including an IP address unique to the group specified by the group ID, and a new DHCP message received. A means for extracting the group ID from the option field to determine whether it is the same as the registered group ID, and, if the extracted group ID and the registered group ID are the same, And a means for transmitting resource information. 9. The DHCP server can register a plurality of group IDs, retrieves the group ID from a new option field of a received DHCP message, and determines whether the group ID is the same as any of the plurality of group IDs. 9. The DHCP server according to claim 8, wherein if the group ID is the same as any of the plurality of group IDs, the resource information unique to the group is transmitted.