Method to control dynamic host configuration protocol pool exhaustion in dynamic network environments

• US 9,866,522 B2
• Filed: 07/29/2014
• Issued: 01/09/2018
• Est. Priority Date: 07/29/2014
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Aruba Networks Incorporated (Hewlett-Packard Enterprise Company)
• Inventors: Chatterjee, Avignan, Ganapathy Achari, Rajesh Kumar, Jayarajan, Srinivasan, Nagaraja, Harsha, Nair, Anoop Kumaran, Ramachandran, Venkatesh, Theogaraj, Isaac, Venkatanaranappa, Venkatraju
• Primary Examiner(s): Miah, Razu A
• Application Number:
  US14/445,312
• Publication Number:
  US 20160036770A1
• Time in Patent Office: 1,260 Days
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 61/5053 Lease time; Renewal aspects
• CPC Class Codes: H04L 61/5061 Pools of addresses
• CPC Class Codes: H04L 67/01 Protocols

Abstract

The present disclosure discloses a method and a network device for controlling DHCP pool exhaustion in dynamic network environments. Specifically, a network device determines that a client device is assigned an Internet Protocol (IP) address by a DHCP server. The network device detects that the client device is disconnected from a network associated with the IP address, for example, by receiving a de-association message from the client device; determining that a session or an entry corresponding to the client device has timed out; determining that the client device has failed to respond to one or more messages transmitted to the client device; determining that the client device has connected to another network different than said network; etc. In response, the network device then generates a DHCP release message on behalf of the client device, and transmits the DHCP release message to the DHCP server.

Claims

1. A non-transitory computer readable medium storing instructions executable by a hardware processor to:

determine that a client device is assigned an Internet Protocol (IP) address by a Dynamic Host Configuration Protocol (DHCP) server;

share user entries and DHCP server information among a plurality of network controllers that are in a Virtual Local Area Network (VLAN);

detect that the client device is disconnected from a first network controller among the plurality of network controllers, based in part on the shared user entries, DHCP server information, and a determination that none of the plurality of network controllers detects a connection with the client device, wherein the first network controller is associated with the IP address; and

responsive to the detection that the client device is disconnected from the first network controller;

generate a DHCP release message on behalf of the client device; and

transmit the DHCP release message to the DHCP server.

2. The medium of claim 1, wherein the instructions to determine that the client device is assigned the IP address by the DHCP server comprise instructions executable by the processor to snoop a message between the DHCP server and the client device.

3. The medium of claim 1, wherein the instructions to detect that the client device is disconnected from the first network controller comprise instructions executable by the processor to receive a de-association message from the client device.

4. The medium of claim 1, wherein the instructions to detect that the client device is disconnected from the first network controller comprise instructions executable by the processor to determine that a session or an entry corresponding to the client device has timed out.

5. The medium of claim 1, wherein the instructions to detect that the client device is disconnected from the first network controller comprise instructions executable by the processor to determine that the client device has failed to respond to one or more messages transmitted to the client device.

6. The medium of claim 1, wherein the instructions to detect that the client device is disconnected from the first network controller comprise instructions executable by the processor to determine that the client device has connected to a second network controller among the plurality of network controllers.

7. The medium of claim 1, wherein the instructions to generate generating the DHCP release message on behalf of the client device comprise instructions executable by the processor to identify a source of the DHCP release message as the client device.

8. The medium of claim 1, wherein the instructions to perform the generate and transmit operations are further responsive to a determination that a DHCP lease associated with the IP address has not expired.

9. The medium of claim 1, wherein the instructions to perform the generate and transmit operations are further responsive to a determination that a DHCP release message has not been transmitted by the client device.

10. The medium of claim 1, wherein the instructions to detect that the client device is disconnected from the first network controller comprise instructions executable by the processor to:

send an address resolution protocol request to the client device; and

determine the client device is no longer associated with the first network controller when a response is not received from the client device in receipt of the address resolution protocol request.

11. A network device, comprising:

a hardware processor to execute instructions to;

determine that a client device is assigned an Internet Protocol (IP) address by a Dynamic Host Configuration Protocol (DHCP) server;

share user entries and DHCP server information among a plurality of network controllers that are in a Virtual Local Area Network (VLAN);

detect that the client device is disconnected from a first network controller among the plurality of network controllers, based in part on the shared user entries, DHCP server information, and a determination that none of the plurality of network controllers detects a connection with the client device, wherein the first network controller is associated with the IP address; and

responsive to the detection that the client device is disconnected from the first network controller;

generate a DHCP release message on behalf of the client device; and

generate the DHCP release message to the DHCP server.

12. The network device of claim 11, wherein the instructions to determine that the client device is assigned the IP address by the DHCP server comprise instructions executable by the processor to snoop a message between the DHCP server and the client device.

13. The network device of claim 11, wherein the instructions to detect that the client device is disconnected from the first network controller comprise instructions executable by the processor to receive a de-association message from the client device.

14. The network device of claim 11, wherein the instructions to detect that the client device is disconnected from the first network controller comprise instructions executable by the processor to determine that a session or an entry corresponding to the client device has timed out.

15. The network device of claim 11, wherein the instructions to detect that the client device is disconnected from the first network controller comprise instructions executable by the processor to determine that the client device has failed to respond to one or more messages transmitted to the client device.

16. The network device of claim 11, wherein the instructions to detect that the client device is disconnected from the first network controller comprise instructions executable by the processor to determine that the client device has connected to a second network controller among the plurality of network controllers.

17. The network device of claim 11, wherein the instructions to generate the DHCP release message on behalf of the client device comprise instructions executable by the processor to identify a source of the DHCP release message as the client device.

18. The network device of claim 11, wherein the instructions to perform the generate and transmit operations are further responsive to a determination that a DHCP lease associated with the IP address has not expired.

19. The network device of claim 11, wherein the instructions to perform the generate and transmit operations are further responsive to a determination that a DHCP release message has not been transmitted by the client device.