Methods, devices, and systems for allocating IP address

Patent metadata

Field	Value
Publication number	US-9100303-B2
Application number	US-201113993225-A
Country	US
Kind code	B2
Filing date	Nov 30, 2011
Priority date	Dec 13, 2010
Publication date	Aug 4, 2015
Grant date	Aug 4, 2015

Abstract

The embodiments of the present disclosure provide a method, a device and a network system for allocating an IP address. The allocating method comprises: allocating a first IP address to a first server; allocating a second IP address to a client connected to the first server; monitoring the client allocated with the second IP address; allocating a third IP address to the first server when a monitoring result indicates that an IP address conflict exists between the first IP address and a current IP address of a second server; wherein the second server is connected to the client allocated with the second IP address. The method may reallocate the IP address automatically when a subnet conflict occurs.

First claim

What is claimed is:

1. A method of allocating an Internet Protocol IP address, comprising:
allocating a first IP address to a first server;
allocating a second IP address to a client connected to the first server;
monitoring the client allocated with the second IP address;
allocating a third IP address to the first server when a monitoring result indicates that an IP address conflict exists between the first IP address and a current IP address of a second server;
wherein the second server is connected to the client allocated with the second IP address.

2. The method according to claim 1 , wherein the IP address conflict existing between the first IP address and the current IP address of the second server comprises: the first IP address and the current IP address of the second server are identical, and a connection message of the client is not received during a preset time period.

3. The method according to claim 1 , wherein before allocating the second IP address to the client connected to the first server, the method further comprises: detecting physical access of the client; and
after allocating the second IP address to the client connected to the first server, the method further comprises: initiating the monitoring of the client.

4. The method according to claim 1 , wherein the monitoring result indicating that an IP address conflict exists between the first IP address and the current IP address of the second server comprises: receiving a message from the client as a subnet conflict message, the subnet conflict message indicating that a subnet conflict exists between a subnet in which the first server is located and a subnet in which the second server is located.

5. The method according to claim 1 , wherein the IP address conflict existing between the first IP address and the current IP address of the second server further comprises: maintaining the monitoring after a connection message of the client is received during a preset time period;
receiving a message from the client as a subnet conflict message, the subnet conflict message indicating that a subnet conflict exists between a subnet in which the first server is located and a subnet in which the second server is located.

6. The method according to claim 1 , wherein allocating the first IP address to the first server and/or allocating the third IP address to the first server are/is random allocation.

7. The method according to claim 6 , wherein the random allocation comprises:
allocating an IP address segment randomly, and allocating an IP address in the IP address segment to the first server.

8. The method according to claim 1 , further comprising: obtaining an IP address segment manifest; and
avoiding addresses in the IP address segment manifest, when the first IP address and/or the third IP address are/is allocated to the first server.

9. The method according to claim 8 , further comprising:
adding the current IP address and a subnet mask of the second server to the IP address segment manifest, when the monitoring result indicates that the subnet conflict exists between the first IP address and the current IP address of the second server.

10. A server of allocating an Internet Protocol IP address, comprising:
a sever address allocation module configured to allocate a first IP address to a first server;
a client address allocation module configured to allocate a second IP address to a client connected to the server;
a monitoring module configured to monitor the client, and notify the server address allocation module of allocating a third IP address to the server when a monitoring result indicates that a subnet conflict exists between the first IP address of the server and a current IP address of a second server;
wherein the second server is connected to the client and is different from the server.

11. The server according to claim 10 , wherein the monitoring module is further configured to deduce the result indicating that the IP address conflict exists between the first IP address and the current IP address of the second server, when the monitoring module does not receive a connection message of the client during a preset time period; and deduce a monitoring result indicating that a subnet conflict exists between the first IP address of the server and the current IP address of the second server, according to the result of IP address conflict.

12. The server according to claim 11 , wherein the monitoring module is further configured to maintain the monitoring after the connection message of the client is not received during the preset time period; and deduce the monitoring result indicating that the subnet conflict exists between the first IP address of the server and the current IP address of the second server, when the monitoring module receives a subnet conflict message from the client, the subnet conflict message indicating that the subnet conflict exists between the first IP address of the server and the current IP address of the second server.

13. The server according to claim 10 , wherein the monitoring result indicating that the subnet conflict exists between the first IP address of the server and the current IP address of the second server comprises: receiving a message from the client as a subnet conflict message, the subnet conflict message indicating that the subnet conflict exists between a subnet in which the server is located and a subnet in which the second server is located.

14. The server according to claim 10 , further comprising: a detection module configured to notify the client address allocation module, after a physical connection is established between the client and the server;
the client address allocation module is further configured to notify the monitoring module of initiating the monitoring of the client, after the second IP address is allocated to the client.

15. The server according to claim 10 , wherein the server address allocation module is further configured to allocate the first IP address and/or the third IP address randomly.

16. The server according to claim 10 , further comprising a storage module configured to store an IP address segment manifest;
the server address allocation module is further configured to obtain the IP address segment manifest from the storage module, and avoid an IP address range contained in the IP address segment manifest when the first IP address and/or the third IP address are/is allocated.

17. The server according to claim 16 , further comprising: an IP address segment addition module configured to save the current IP address and a subnet mask of the second server in the IP address segment manifest, when the monitoring result of the monitoring module is received; wherein the monitoring result is that the subnet conflict exists between the first IP address of the server and the current IP address of the second server.

18. A network system comprising a first server and a client, wherein
the first sever is configured to allocate a first Internet Protocol IP address to itself, and allocate a second IP address to the client, the client being connected to the first server at this point;
the first server is further configured to monitor the client, and allocate a third IP address to itself when a monitoring result indicates that a subnet conflict exists between the first IP address of the server and a current IP address of a second server;
wherein the second server is connected to the client and is different from the first server.

19. The system according to claim 18 , wherein the client is configure

Assignees

• Li Bin
• Wang Sheng
• Xu Chao
• Beijing Lenovo Software Ltd
• Lenovo Beijing Ltd

Inventors

• Li Bin
• Wang Sheng
• Xu Chao

Classifications

• H04L61/5046 Primary

  Resolving address allocation conflicts; Testing of addresses (testing when self-assigning an address H04L61/5092) · CPC title

• H04L61/2046

  Electricity · mapped topic

• H04L43/0823 Primary

  Errors, e.g. transmission errors · CPC title

• H04L61/2015

  Electricity · mapped topic

• H04L61/5014

  using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP] · CPC title