Dynamically deployable self configuring distributed network management system and method having execution authorization based on a specification defining trust domain membership and/or privileges

• US 10,225,157 B2
• Filed: 07/14/2016
• Issued: 03/05/2019
• Est. Priority Date: 07/07/2005
• Status: Active Grant

• Current Assignee: ScienceLogic
• Original Assignee: ScienceLogic
• Inventors: Cordray, Christopher G., Chart, Richard, Link, David, Luebke, Matthew, Ginter, Karl, Bartman, Michael
• Primary Examiner(s): Bengzon, Greg C
• Application Number:
  US15/210,480
• Publication Number:
  US 20160380842A1
• Time in Patent Office: 964 Days
• 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, said arrangement of network task managers being controlled in accordance with at least one specification defining trust domain membership and/or privileges within a trust domain, the at least one specification specifying at least;

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

at least one network collection specification which describes information the at least one task manager software component is authorized to manage the collection of from the network, and

at least one hardware computing component upon which the at least one task manager software component is authorized to operate;

determining whether the at least one specification defining trust domain membership and/or privileges within a trust domain identifies task manager software present on the specified at least one hardware computing component as being authorized to operate as part of the arrangement of network task managers; and

if the determining determines the at least one specification defining trust domain membership and/or privileges within a trust domain identifies task manager software present on the specified at least one hardware computing component as being authorized to operate as part of the arrangement of network task managers, executing said task manager software component on the specified at least one hardware computing component to at least in part manage the trust domain in accordance with the at least one network collection specification, wherein the hardware computing component includes a processor, storage, network interface, and operating system software.

2. The method of claim 1, wherein the at least one specification defining trust domain membership and/or privileges within a trust domain specifies at least first and second task manager software components, defines an authorization and specifies a predetermined hardware computing component upon which the second task manager software component is authorized to operate based at least in part on the authorization, and the executing includes operating both the first and second task manager software components in accordance with the at least one specification defining trust domain membership and/or privileges within a trust domain.

3. The method of claim 2, wherein the at least one specification defining trust domain membership and/or privileges within a trust domain specifies an authorization for the first and second task manager software components to be in communication, and the executing includes communicating between the first and second task manager software components to, at least in part, cooperatively manage the trust domain.

4. The method of claim 3, wherein said cooperatively managing includes sharing management of the at least one specification defining trust domain membership and/or privileges within a trust domain.

5. The method of claim 3, wherein said cooperatively managing includes allocating management responsibility for at least a part of the at least one specification defining trust domain membership and/or privileges within a trust domain to the first task manager software component and allocating management responsibility for at least a part of the at least one specification defining trust domain membership and/or privileges within a trust domain to the second task manager software component.

6. The method of claim 5, wherein allocating includes assigning a first part of the at least one specification defining trust domain membership and/or privileges within a trust domain to the first task manager software component to manage, and assigning a second part of the at least one specification defining trust domain membership and/or privileges within a trust domain to the second task manager software component to manage.

7. The method of claim 3, further including communicating changes in the trust domain between the first task manager software component and the second task manager software component.

8. The method of claim 4, wherein the at least one specification defining trust domain membership and/or privileges within a trust domain specifies a first collection component and a second collection component.

9. The method of claim 8, wherein the at least one specification defining trust domain membership and/or privileges within a trust domain specifies that the first task manager software component manages the specified first collection component, and further specifies that the second task manager software component manages the specified second collection component.

10. The method of claim 8, wherein the first task manager software component and the second task manager software component both manage the same collection component.

11. The method of claim 1 wherein the at least one hardware computing component comprises first, second and third hardware computing components, the first hardware computing component being specified in a first specification defining trust domain membership and/or privileges within a trust domain, the second hardware computing component being specified in a second specification defining trust domain membership and/or privileges within a trust domain, the third hardware computing component being specified in both the first specification defining trust domain membership and/or privileges within a trust domain and the second trust domain specification.

12. A network management system comprising:

an arrangement of network task managers deployed on a network, said arrangement of network task managers being controlled in accordance with at least one specification defining trust domain membership and/or privileges within a trust domain specifying at least;

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

at least one network collection specification which describes information the at least one task manager software component is authorized to manage the collection of from the network, and

at least one hardware computing component upon which the at least one task manager software component is authorized to operate;

an authorizer that determines whether the at least one specification defining trust domain membership and/or privileges within a trust domain identifies task manager software present on the specified at least one hardware computing component as being authorized to operate as part of the arrangement of network task managers; and

conditioned on the authorizer determining that the at least one specification defining trust domain membership and/or privileges within a trust domain identifies task manager software present on the specified at least one hardware computing component as being authorized to operate as part of the arrangement of network task managers, the specified at least one hardware computing component executing said task manager software component to at least in part manage the trust domain in accordance with the at least one network collection specification,

wherein the hardware computing component includes a processor, storage, network interface, and operating system software.

13. The system of claim 12, wherein the at least one specification defining trust domain membership and/or privileges within a trust domain specifies at least first and second task manager software components, defines an authorization and specifies a predetermined hardware computing component upon which the second task manager software component is authorized to operate based at least in part on the authorization, and the predetermined hardware computing component operates both the first and second task manager software components in accordance with the at least one specification defining trust domain membership and/or privileges within a trust domain.

14. The system of claim 13 wherein the at least one specification defining trust domain membership and/or privileges within a trust domain specifies an authorization for the first and second task manager software components to be in communication, and the first and second task manager software components are configured to, at least in part, cooperatively manage the trust domain.

15. The system of claim 14, wherein said cooperatively managing configuration includes sharing management of the at least one specification defining trust domain membership and/or privileges within a trust domain.

16. The system of claim 14, wherein said cooperatively managing configuration includes allocation of management responsibility for at least a part of the at least one specification defining trust domain membership and/or privileges within a trust domain to the first task manager software component and allocation of management responsibility for at least a part of the at least one specification defining trust domain membership and/or privileges within a trust domain to the second task manager software component.

17. The system of claim 16, wherein the allocations includes an assignment of a first part of the at least one specification defining trust domain membership and/or privileges within a trust domain to the first task manager software component to manage, and an assignment of a second part of the at least one specification defining trust domain membership and/or privileges within a trust domain to the second task manager software component to manage.

18. The system of claim 15, wherein the first task manager software component and the second task manager software component are configured to communicate changes in the trust domain therebetween.

19. The system of claim 14, wherein the at least one specification defining trust domain membership and/or privileges within a trust domain specifies a first collection component and a second collection component.

20. The system of claim 19, wherein the at least one specification defining trust domain membership and/or privileges within a trust domain configures the first task manager software component to manage the specified first collection component, and configures the second task manager software component to manage the specified second collection component.

21. The system of claim 20, wherein the first task manager software component and the second task manager software component are both configured to manage the same collection component.

22. The system of claim 12 wherein the at least one hardware computing component comprises first, second and third hardware computing components, the first hardware computing component being specified in a first specification defining trust domain membership and/or privileges within a trust domain, the second hardware computing component being specified in a second specification defining trust domain membership and/or privileges within a trust domain, the third hardware computing component being specified in both the first specification defining trust domain membership and/or privileges within a trust domain and the second trust domain specification.