DYNAMICALLY DEPLOYABLE SELF CONFIGURING DISTRIBUTED NETWORK MANAGEMENT SYSTEM

• US 20160323153A1
• Filed: 07/15/2016
• Published: 11/03/2016
• Est. Priority Date: 07/07/2005
• Status: Active Grant

• Current Assignee: ScienceLogic
• Original Assignee: ScienceLogic
• Inventors: LINK, David, CORDRAY, Christopher G., CHART, Richard, LUEBKE, Matthew, GINTER, Karl, BARTMAN, Michael
• Granted Patent: US 10,230,588 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 12/08 in hierarchically structured memory systems, e.g. virtual memory systems
• CPC Class Codes: G06F 15/173 using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
• CPC Class Codes: G06F 15/177 Initialisation or configuration control processor initialisation G06F9/4405
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/20 Network management software packages
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Systems, software, and methods for managing networks of connected electronic devices are described. In one example, network management policy and network management applications are transferred automatically upon detection and identification of a new device, protocol or application on the network. In another example, information related to at least one aspect of the network is obtained by an NMAS, and at least one applicable management policy is identified by the NMAS; and the identified policy is used to manage at least one aspect of the network'"'"'s operation.

Claims

1. A network management method comprising:

deploying an arrangement of network task managers on a network or subnetwork, said arrangement of network task managers comprising at least one specification that defines membership and/or privileges within at least one trust domain including specifying;

a first task manager software authorized to operate on a trust domain,

a first hardware computing component upon which the first task manager software is authorized to operate,

a second task manager software authorized to operate on the trust domain,

a second hardware computing component upon which the second task manager software is authorized to operate,

a first network collection software,

a third hardware computing component upon which the first network collection software is authorized to operate,

a second network collection software,

a fourth hardware computing component upon which the second network collection software is authorized to operate, and

at least one network collection specification specifying information the first and second network collection software is authorized to collect from the network,

executing said first task manager software on the specified first hardware computing component to at least in part manage the trust domain,

executing said second task manager software on the specified second hardware computing component to at least in part manage the at least one trust domain,

executing said first network collection software on the specified third hardware computing component to collect information about the network, subnetwork or host computing system(s), and

executing said second network collection software on the specified fourth hardware computing component to collect further information about the network, subnetwork or host computing system(s).

2. The method of claim 1 further including controlling said first and second network collection softwares using said first and second task manager softwares.

3. The method of claim 1 further including balancing discovery load for the at least one trust domain between the first network collection software and the second network collection software.

4. The method of claim 3 further including controlling the load balancing by at least one of the first and second task manager softwares.

5. The method of claim 3 further including controlling said load balancing using a cooperating set of the first and second task manager softwares.

6. The method of claim 5 further including using a bidding process to arbitrate said load balancing.

7. The method of claim 3 further including controlling said load balancing by assigning collection tasks to each of said first and second network collection softwares.

8. The method of claim 3 further including the first task manager software communicating with the first and second network collection softwares, performing a bidding process and assigning collection tasks to a winning master network collection software.

9. A collection of cooperative network configuration network collection softwares deployed across at least one network comprising:

a trust domain comprising;

a first network collection arrangement comprising at least a first task manager software and at least a first network collection software executing on a first hardware component on a first network segment;

a second network collection arrangement comprising at least a second task manager software and at least a second network collection software executing on a second hardware component on a second network segment;

wherein said first and second network collection softwares operate together as a distributed network collection software.

10. The collection of claim 9 wherein said first and second network collection softwares are configured to load balance collection tasks therebetween.

11. The collection of claim 9 wherein said first and second network collection softwares are configured to share discovery information therebetween.

12. The collection of claim 9 wherein said first and second network collection softwares are instantiated on non-traditional networks.

13. The collection of claim 9 wherein said first and second network collection softwares are instantiated on gateways between traditional and non-traditional networks.

14. The collection of claim 9 wherein said first and second network collection softwares are configured to share at least one dynamic application.

15. The collection of claim 9 wherein said first network collection software is configured to perform tasks previously performed by the second network collection software upon failure of the second network collection software.

16. The collection of claim 15 wherein said second network collection software regains performance of said previously performed tasks when the second network collection software recovers.

17. The collection of claim 16 wherein said second network collection software regains performance only after a delay.

18. The collection of claim 16 wherein said second network collection software selectively regains performance based at least in part on load balancing.

27. The system of claim 15 wherein said second network collection software regains performance of said previously performed tasks when the second network collection software recovers.

28. The system of claim 16 wherein said second network collection software regains performance only after a delay.

29. The system of claim 16 wherein said second network collection software selectively regains performance based at least in part on load balancing.

19. A network management system comprising:

an arrangement of network task managers for being deployed on a network or subnetwork, said arrangement of network task managers comprising at least one specification that defines membership and/or privileges within at least one trust domain specifying;

a first task manager software authorized to operate on a trust domain,

a first hardware computing component upon which the first task manager software is authorized to operate,

a second task manager software authorized to operate on the at least one trust domain,

a second hardware computing component upon which the second task manager software is authorized to operate,

a first network collection software,

a third hardware computing component upon which the first network collection software is authorized to operate,

a second network collection software,

a fourth hardware computing component upon which the second network collection software is authorized to operate, and

at least one network collection specification specifying information the first and second network collection software is authorized to collect from the network,

the specified first hardware computing component executing said first task manager software to at least in part manage the at least one trust domain,

the specified second hardware computing component executing said second task manager software to at least in part manage the at least one trust domain,

the specified third hardware computing component executing said first network collection software to collect information about the network, subnetwork or host computing system(s), and

the specified fourth hardware computing component executing said second network collection software to collect further information about the network, subnetwork or host computing system(s).

20. The system of claim 19 wherein said first and second network collection softwares are configured to be controlled using said first and second task manager softwares.

21. The system of claim 19 further including a load balancer that balances discovery load for the at least one trust domain between the first network collection software and the second network collection software.

22. The system of claim 21 wherein the load balancer is configured to control the load balancing by at least one of the first and second task manager softwares.

23. The system of claim 21 wherein the load balancer is configured to control said load balancing using a cooperating set of the first and second task manager softwares.

24. The system of claim 21 wherein the load balancer is configured to use a bidding process to arbitrate said load balancing.

25. The system of claim 21 wherein the load balancer is configured to control said load balancing by assigning collection tasks to each of said first and second network collection softwares.

26. The system of claim 21 wherein the first task manager software is configured to communicate with the first and second network collection softwares, perform a bidding process and assign collection tasks to a winning master network collection software.