Systems and methods for IIP address sharing across cores in a multi-core system
First Claim
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.
9 Assignments
0 Petitions
Accused Products
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.
-
Citations
20 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
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. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification