Assign tunnel tag identifying virtual local area network tunnel

• US 10,581,638 B2
• Filed: 04/18/2018
• Issued: 03/03/2020
• Est. Priority Date: 04/18/2018
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Kandasamy, Mohanraj, Swamy, Kumar Puta
• Primary Examiner(s): Pancholi, Rina C
• Application Number:
  US15/956,281
• Publication Number:
  US 20190327113A1
• Time in Patent Office: 685 Days
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4645 Details on frame tagging routing of packets H04L45/00; support for virtual LAN H04L49/354
• CPC Class Codes: H04L 41/0627 by acting on the notification or alarm source
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 61/103 across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/086 using security domains
• CPC Class Codes: H04W 24/04 Arrangements for maintaining operational condition
• CPC Class Codes: H04W 48/16 Discovering, processing access restriction or access information
• CPC Class Codes: H04W 76/11 Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/12 Setup of transport tunnels
• CPC Class Codes: H04W 76/18 Management of setup rejection or failure
• CPC Class Codes: H04W 76/19 Connection re-establishment
• CPC Class Codes: H04W 84/12 WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/08 Access point devices

Abstract

An access point, comprising: a processing resource; and a memory resource storing machine-readable instructions to cause the processing resource to: assign a first tunnel tag to a first DHCP profile of a client device, the first tunnel tag identifying a primary VLAN tunnel to a first network controller of a first data center; assign a second tunnel tag to a second DHCP profile of the client device, the second tunnel tag identifying a secondary VLAN tunnel to a second network controller of a second data center; determine whether the primary VLAN tunnel to the first network controller is inactive based on a number of detected access failures; and connect the client device to the secondary VLAN tunnel in response to determining that the primary VLAN tunnel is inactive.

Claims

1. An access point, comprising:

a processing resource; and

a memory resource storing machine-readable instructions to cause the processing resource to;

assign a first tunnel tag to a first dynamic host configuration protocol (DHCP) profile of a client device, the first tunnel tag identifying a primary virtual local area network (VLAN) tunnel to a first network controller of a first data center;

assign a second tunnel tag to a second DHCP profile of the client device, the second tunnel tag identifying a secondary VLAN tunnel to a second network controller of a second data center;

determine whether the primary VLAN tunnel to the first network controller is inactive based on a threshold number of detected access failures;

connect the client device to the secondary VLAN tunnel in response to determining that the primary VLAN tunnel is inactive;

receive, from the client device, an address resolution protocol (ARP) request; and

transmit, to the client device, an internet protocol (IP) address of the secondary VLAN tunnel in response to the ARP request.

2. The access point of claim 1, wherein the processing resource, when connecting the client device to the secondary VLAN tunnel, is further to:

broadcast a service set identifier (SSID) to the client device.

3. The access point of claim 1, wherein the processing resource, when connecting the client device to the secondary VLAN tunnel, is further to:

engage in a bid process with the second network controller of the second data center; and

obtain a subnet from the second network controller of the second data center.

4. The access point of claim 1, wherein the processing resource, when connecting the client device to the secondary VLAN tunnel, is further to:

receive a DHCP request from the client device; and

provide a DHCP acknowledgement to the client device.

5. The access point of claim 1, wherein the secondary VLAN tunnel provides access to a distributed VLAN.

6. The access point of claim 1, wherein the client device is wirelessly connected to the access point using a pre-shared key (PSK) based service set identifier (SSID).

7. An access point, comprising:

a processing resource; and

a memory resource storing machine-readable instructions to cause the processing resource to;

assign a first tunnel tag to a first dynamic host configuration protocol (DHCP) profile of a client device, the first tunnel tag identifying a primary virtual local area network (VLAN) tunnel to a first network controller of a first data center;

assign a second tunnel tag to a second DHCP profile of the client device, the second tunnel tag identifying a secondary VLAN tunnel to a second network controller of a second data center;

determine whether the primary VLAN tunnel to the first network controller is inactive;

terminate broadcasting a service set identifier (SSID) to the client device for a predetermined time period to cause the client device to be disconnected from the primary VLAN tunnel;

connect the client device to the secondary VLAN tunnel in response to the primary VLAN tunnel being inactive,

receive, from the client device, an address resolution protocol (ARP) request and

transmit, to the client device, an internet protocol (IP) address of the secondary VLAN tunnel in response to the ARP request.

8. The access point of claim 7, wherein the processing resource, when connecting the client device to the secondary VLAN tunnel, is further to:

broadcast the SSID to the client device.

9. The access point of claim 7, wherein the processing resource, when determining whether the primary VLAN tunnel is inactive, is further to:

determine whether the primary VLAN tunnel is inactive based on a number of detected access failures.

10. The access point of claim 7, wherein the processing resource, when connecting the client device to the secondary VLAN tunnel, is further to:

receive a DHCP request from the client device; and

forward the DHCP request to the second network controller.

11. The access point of claim 10, wherein the processing resource, when connecting the client device to the secondary VLAN tunnel, is further to:

receive a DHCP acknowledgment from the second network controller; and

provide the DHCP acknowledgement to the client device.

12. The access point of claim 7, wherein the secondary VLAN tunnel provides access to a centralized VLAN.

13. A system, comprising:

an access point;

a first network controller of a first data center, the first network controller being connected to the access point; and

a second network controller of a second data center, the second network controller being connected to the access point, wherein the system is to;

assign a first tunnel tag to a first dynamic host configuration protocol (DHCP) profile of a client device, the first tunnel tag identifying a primary virtual local area network (VLAN) tunnel to the first network controller;

assign a second tunnel tag to a second DHCP profile of the client device, the second tunnel tag identifying a secondary VLAN tunnel to the second network controller;

determine whether the primary VLAN tunnel to the first network controller is inactive based on a number of detected access failures;

engage the access point in a bid process with the second network controller of the second data center;

connect the client device to the secondary VLAN tunnel in response to determining that the primary VLAN tunnel is inactive;

provide the access point with a subnet from the second network controller of the second data center;

receive, from the client device, an address resolution protocol (ARP) request; and

provide, to the client device, an internet protocol (IP) address associated with the secondary VLAN tunnel in response to the ARP request.

14. The system of claim 13, wherein the system, when connecting the client device to the secondary VLAN tunnel, is further to:

broadcast a service set identifier (SSID) to the client device.

15. The system of claim 13, wherein Virtual Private Network (VPN) redundancy for the client device is provided by connecting the client device to one of the primary VLAN tunnel and the secondary VLAN tunnel.

16. The system of claim 13, wherein the client device is wirelessly connected to the access point using a pre-shared key (PSK) based service set identifier (SSID).

17. The system of claim 13, wherein the first DHCP profile and the second DHCP profile belong to a network layer.