IP Library Granted Patent US 9,900,211
Granted Patent B1
US 9,900,211 · App. 14/503,664 · Granted Feb 20, 2018

Systems and methods for network management

Inventor: Roman Mach (Bothell, WA)
Assignee: Crimson Corporation
H04L41/0806H04L41/12H04L67/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,900,211
App. No.
14/503,664
Granted
Feb 20, 2018
Kind
B1
Abstract

A method for managing nodes is disclosed. The method includes testing a management script on a management server for managing at least one node. The method also includes receiving administrator validation to distribute the management script. The method further includes sending the validated management script to one or more management servers on one or more networks.

Claims (21)

1. A method for managing nodes, comprising: sending, from an administrative compute device, a management script to a management server configured to manage at least one node such that the management server, in response to receiving the management script, executes the management script in a test mode and generates test results based on an output of the management script, the management server being operated by a tenant from a plurality of tenants each operating a different set of management servers connected to the administrative compute device; receiving the test results from the management server; receiving tenant authorization to distribute the management script to a set of tenants from the plurality of tenants, the tenant authorization representing a determination by the tenant that the test results meet a first criterion; receiving administrator validation to distribute a validated management script based on the management script to the set of tenants from the plurality of tenants, the administrator validation representing a determination by an administrator of the administrative compute device that the test results meet a second criterion; and sending, in response to receiving the authorization and the validation, the validated management script to one or more management servers on one or more networks, the one or more management servers operated by the set of tenants from the plurality of tenants.

2. The method of claim 1 , wherein the management script includes instructions to: retrieve at least one identifier of an unmanaged node; retrieve at least one core parameter of the unmanaged node; retrieve at least one configuration of the unmanaged node; and apply the at least one configuration to one or more nodes other than the unmanaged node managed by the management server.

3. The method of claim 1 , wherein the management script is defined by a user associated with the tenant using in a browser-based interface.

4. The method of claim 1 , wherein the validated management script is validated using in a browser-based interface.

5. The method of claim 1 , wherein the management server is in a network including an unmanaged node, the method further comprising: sending a signal indicating an Internet Protocol address for the unmanaged node in the network to the management server.

6. The method of claim 1 , wherein the tenant is a customer and the sending the validated management script to the one or more management servers includes sending the validated management script to one or more management servers associated with the customer.

7. The method of claim 1 , wherein the sending the validated management script to the one or more management servers causes the one or more management servers, in response to receiving the validated management script, to discover and configure; one or more unmanaged nodes based on a signature cache of including an Internet Protocol address of the one or more unmanaged nodes.

8. The method of claim 1 , wherein the sending the validated management script to the one or more management servers causes the one or more management servers, in response to receiving the validated management script, to discover and configure one or more unmanaged nodes independent of a firmware version installed on the one or more unmanaged nodes.

9. An administrative compute device comprising: a processor; a memory in electronic communication with the processor; and instructions stored in the memory, the instructions being executable to: identify a node in a network including a management server configured to manage at least one node in the network, the node being an unmanaged node that has not been configured by the management server; send a management script to the management server such that the management server, in response to receiving the management script, tests the management script to generate test results indicating the management server being operated by a tenant from a plurality of tenants each operating a different set of management servers connected to the administrative compute device; receive the test results from the management server; receive tenant authorization to distribute the management script to a set of tenants from the plurality of tenants, the tenant authorization representing a determination by the tenant that the test results meet a first criterion; receive administrator validation to distribute a validated management script based on the management script to the set of tenants from the plurality of tenants, the administrator validation representing a determination by an administrator of the administrative compute device that the test results meet a second criterion; and send, in response to receiving the authorization and the validation, the management script to one or more management servers on one or more networks, the one or more management servers operated by the set of tenants from the plurality of tenants.

10. The administrative compute device of claim 9 , wherein the management script includes instructions to: retrieve at least one identifier of the node; retrieve at least one core parameter of the node; retrieve at least one configuration of the node; and apply the configuration to one or more nodes other than the node managed by the management server.

11. The compute device of claim 9 , wherein the management script is defined by a user associated with the tenant using in a browser-based interface.

12. The administrative compute device of claim 9 , wherein the management script is validated using in a browser-based interface.

13. The administrative compute device of claim 9 , wherein the instructions are further executable to: send a signal indicating an Internet Protocol address for the node in the network to the management server, the instructions executable to send the management script to the management server including, instructions executable to send the management script to the management server such that the management server, in response to receiving the management script, processes the management script in a test mode to discover and configure the node.

14. The administrative compute device of claim 9 , wherein the tenant is a customer and the one or more management servers to which the management script is sent include one or more management servers associated with the customer.

15. The administrative compute device of claim 9 , wherein the tenant is a customer, and the instructions are further executable to: send, in response to the customer requesting a plurality of management scripts, a list identifying the plurality of management scripts to the customer such that the customer can add, remove or reorder one or more of the plurality of management scripts in the list; and send, after the customer adds, removes, or reorders the one or more of the management scripts in the list, one or more management scripts remaining in the list to one or more management servers associated with the customer.

16. The administrative compute device of claim 9 , wherein the sending of the management script to the one or more management servers causes the one or more management servers, in response to receiving the management script, to discover and configure one or more unmanaged nodes based on a signature cache of the one or more unmanaged nodes.

17. The administrative compute device of claim 9 , wherein the sending of the management script to the one or more management servers causes the one or more management servers, in response to receiving the management script, to discover and configure one or more unmanaged nodes based on a signature cache including an Internet Protocol address of the one or more unmanaged nodes.

18. The administrative compute device of claim 9 , wherein the sending of the management script to the one or more management servers causes the one or more management servers, in response to receiving the management script, to discover and configure the one or more unmanaged nodes independent of a firmware version installed on the one or more unmanaged nodes.

19. The method of claim 1 , wherein the sending of the validated management script to the one or more management servers causes the one or more management servers, in response to receiving, the validated management script, to discover and configure one or more unmanaged nodes such that the one or more unmanaged nodes become managed nodes.

20. The method of claim 1 , wherein the validated management script includes a modification made by the administrator of the administrative compute device to the management script.

21. The method of claim 1 , wherein the validated management script is the management script.

Assignments (20)
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY 14633493 WHICH WAS ENTERED INCORRECTLY AS 14633793 PREVIOUSLY RECORDED ON REEL 71176 FRAME 315. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST LIEN NEWCO SECURITY AGREEMENT. Recorded Nov 10, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 073818/0515 →
FIRST LIEN NEWCO SECURITY AGREEMENT Recorded May 5, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0315 →
SECURITY INTEREST Recorded May 2, 2025
From: IVANTI, INC.
To: ALTER DOMUS (US) LLC
Reel/Frame 071164/0482 →
NOTICE OF SUCCESSION OF AGENCY FOR SECURITY INTEREST AT REEL/FRAME 054665/0873 Recorded Apr 29, 2025
From: BANK OF AMERICA, N.A., AS RESIGNING AGENT
To: ALTER DOMUS (US) LLC, AS SUCCESSOR AGENT
Reel/Frame 071123/0386 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; IVANTI, INC.; MOBILEIRON, INC.; IVANTI US LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 054665/0062 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; INVANTI, INC.; MOBILEIRON, INC.; INVANTI US LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 054665/0873 →
RELEASE OF SECURITY INTEREST : RECORDED AT REEL/FRAME - 41052/0762 Recorded Dec 1, 2020
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: CRIMSON CORPORATION
Reel/Frame 054560/0857 →
RELEASE OF SECURITY INTEREST : RECORDED AT REEL/FRAME - 41459/0387 Recorded Dec 1, 2020
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: CRIMSON CORPORATION
Reel/Frame 054637/0161 →
MERGER Recorded Apr 19, 2018
From: CRIMSON CORPORATION
To: IVANTI, INC.
Reel/Frame 045983/0075 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL/FRAME NO. 35993/0423 Recorded Jan 23, 2017
From: JEFFERIES FINANCE LLC
To: CRIMSON CORPORATION; LANDESK SOFTWARE, INC.
Reel/Frame 041462/0634 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL/FRAME NO. 35994/0864 Recorded Jan 23, 2017
From: JEFFERIES FINANCE LLC
To: CRIMSON CORPORATION; LANDESK SOFTWARE, INC.
Reel/Frame 041462/0642 →
RELEASE OF SECOND LIEN SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 40183/0506 Recorded Jan 23, 2017
From: JEFFERIES FINANCE LLC
To: CRIMSON CORPORATION
Reel/Frame 041463/0457 →
RELEASE OF FIRST LIEN SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 40182/0345 Recorded Jan 23, 2017
From: JEFFERIES FINANCE LLC
To: CRIMSON CORPORATION
Reel/Frame 041463/0581 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jan 20, 2017
From: CRIMSON CORPORATION
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 041459/0387 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Jan 20, 2017
From: CRIMSON CORPORATION
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 041052/0762 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Sep 29, 2016
From: CRIMSON CORPORATION
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 040183/0506 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Sep 29, 2016
From: CRIMSON CORPORATION
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 040182/0345 →
SECURITY INTEREST Recorded Jul 1, 2015
From: LANDESK SOFTWARE, INC.; CRIMSON CORPORATION
To: JEFFERIES FINANCE LLC
Reel/Frame 035993/0423 →
SECURITY INTEREST Recorded Jul 1, 2015
From: LANDESK SOFTWARE, INC.; CRIMSON CORPORATION
To: JEFFERIES FINANCE LLC
Reel/Frame 035994/0864 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 15, 2014
From: MACH, ROMAN
To: CRIMSON CORPORATION
Reel/Frame 033952/0884 →