SYSTEMS AND METHODS FOR IIP ADDRESS SHARING ACROSS CORES IN A MULTI-CORE SYSTEM

• US 20140143394A1
• Filed: 11/15/2013
• Published: 05/22/2014
• Est. Priority Date: 08/05/2010
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Ramachandra, Pratap, Choudhary, Akshat, Kumar, Arkesh, Agarwal, Mugdah
• Granted Patent: US 8,856,369 B2
• Time in Patent Office: Days
• US Class Current: 709/222
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 61/50 Address allocation
• CPC Class Codes: H04L 63/166 at the transport layer

Abstract

In a multi-core system, multiple packet engines across corresponding cores may be working concurrently processing data packets from data flows of SSL VPN sessions. For example, a first core may establish a SSL VPN session with a client. Any one of the other cores, such as a second core, may received packets related to the session owned by the first core. Embodiments of the systems and method described below provide management of IIP addresses for the multi-core/multi-packet engine approach to providing SSL VPN service. In some embodiments, the approach to managing IIP addresses is to have one packet engine on a core act as a master or controller of the IIPs for the remaining packet engines and cores. The packet engines/cores use a protocol for communications regarding IIP management.

Claims

1. A method for managing intranet internet protocol addresses via a device comprising a plurality of cores, the method comprising:

(a) establishing, on a device comprising a plurality of cores, a controller for managing intranet internet protocol (IIP) addresses assigned to sessions of users;

(b) receiving, by a controller, from a first core a request for an IIP address for a session of a user;

(c) determining, by the controller that an IIP address is not available to assign to the session;

(d) communicating, by the controller to a second core, a second request to identify one or more existing IIP addresses allocated to the user; and

(e) transferring, by the controller, from the one or more existing IIP addresses to the session of the request an existing IIP address allocated to the user.

2. The method of claim 1, wherein step (a) further comprises establishing the controller on one of the first core or the second core of the plurality of cores.

3. The method of claim 1, wherein step (a) further comprising selecting one core of the plurality of cores as the core to establish the controller and communicating the selection to each of the others cores of the plurality of cores.

4. The method of claim 1, wherein step (b) further comprises transmitting, by the first core, the request for the IIP address responsive to the client requesting to establish the session via the device.

5. The method of claim 1, wherein step (c) further comprises determining, by the controller, that the IIP addresses available to the user have been allocated.

6. The method of claim 1, wherein step (d) further comprises determining, by the controller, that the second core is an owner of the session.

7. The method of claim 1, wherein step (d) further comprises receiving, by the controller from the second core, the one or more existing IIP addresses allocated to the user and corresponding session information.

8. The method of claim 1, wherein step (e) further comprises receiving, by the controller, a third request to transfer login of an existing session of the user to the session of the request, the second request comprising information about the client, the user, the session and the IIP address.

9. The method of claim 1, wherein step (e) further comprises transmitting, by the first core, a third request to the client to transfer login of an existing session of the user to the session of the request.

10. The method of claim 1, further comprises communicating, by the controller, to the plurality of cores, the transfer of the allocation of the IIP address to the session.

11. A system for managing intranet internet protocol addresses via a device comprising a plurality of cores, the system comprising:

a device comprising a plurality of cores;

a controller established on the device and configured to manage intranet internet protocol (IIP) addresses assigned to sessions of users;

wherein the controller is configured to receive from a first core a request for an IIP address for a session of a user, determine that an IIP address is not available to assign to the session and communicate to a second core, a second request to identify one or more existing IIP addresses allocated to the user; and

wherein the controller is configured to transfer from the one or more existing IIP addresses to the session of the request an existing IIP address allocated to the user.

12. The system of claim 11, wherein the controller is established on one of the first core or the second core of the plurality of cores.

13. The system of claim 11, wherein the device is configured to select one core of the plurality of cores as the core to establish the controller and the selected core is configured to communicate the selection to each of the others cores of the plurality of cores.

14. The system of claim 11, wherein the first core is further configured to communicate the request for the IIP address responsive to the client requesting to establish the session via the device.

15. The system of claim 11, wherein the controller is further configured to determine that the IIP addresses available to the user have been allocated.

16. The system of claim 11, wherein the controller is further configured to determine that the second core is an owner of the session.

17. The system of claim 11, wherein the controller is further configured to receive from the second core, the one or more existing IIP addresses allocated to the user and corresponding session information.

18. The system of claim 11, wherein the controller is further configured to receive a third request to transfer login from an existing session of the user to the session of the request, the second request comprising information about the client, the user, the session and the IIP address.

19. The system of claim 11, wherein the first core is further configured to communicate a third request to the client to transfer login from an existing session of the user to the session of the request.

20. The system of claim 11, wherein the controller is further configured to communicate to the plurality of cores the transfer of the allocation of the IIP address to the session.