Method, system, and article of manufacture for network management

• US 20040111505A1
• Filed: 12/10/2002
• Published: 06/10/2004
• Est. Priority Date: 12/10/2002
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Lecoq, Robert J., Callahan, Tony L., Maslowski, Daniel J.
• Application Number:
  US10/315,794
• Publication Number:
  US 20040111505A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0859 by keeping history of different configuration generations or by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/0866 Checking the configuration
• 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/55 Push-based network services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Provided are a method, system and article of manufacture for network management. Information is discovered on at least one client of a plurality of clients managed by a server. The discovered information is compared to rules related to the management of the plurality of clients, wherein the rules are for examining prior operational history and current operation of the at least one client. Based on the comparison, an update is recognized to be applied to the at least one client, wherein the update includes an executable that can be automatically installed on the at least one client. The update is pushed to the at least one client, wherein the discovering, comparing, recognizing and pushing are controlled by the server.

Claims

1. A method for network management comprising:

discovering information on at least one client of a plurality of clients managed by a server;

comparing the discovered information to rules related to the management of the plurality of clients, wherein the rules are for examining prior operational history and current operation of the at least one client;

based on the comparison, recognizing an update to be applied to the at least one client, wherein the update includes an executable that can be automatically installed on the at least one client; and

pushing the update to the at least one client, wherein the discovering, comparing, recognizing and pushing are controlled by the server.

2. The method of claim 1, wherein the discovering is performed by a discovery application on the server, wherein the discovering further comprises:

determining a unique name of the at least one client;

determining an operating system of the at least one client; and

determining a participation in a dynamic licensing scheme of the at least one client.

3. The method of claim 1, wherein the comparing and recognizing is performed by an analysis application on the server, and wherein the rules related to the management of the plurality of clients include rules related to versioning requirements of software, rules related to network environment, rules related to billing, rules related to analysis of logs, and rules related to licensing requirements.

4. The method of claim 1, wherein the server includes an user interface application, the method further comprising:

prior to pushing, displaying a message via the user interface application on a screen of the at least one client, wherein the message is transmitted in hypertext, text file format or electronic mail to the at least one client, and wherein the message requests permission from the at least one client for pushing the update.

5. The method of claim 1, further comprising:

prior to pushing the update, receiving the update at the server from a master server, wherein the master server is a computational device to which a plurality of servers are securely connected.

6. The method of claim 1, further comprising:

based on the comparison, determining that the at least one client cannot be managed by the server;

sending a notification to an user of the at least one client and the administrator of the server of the determination that the at least one client cannot be managed by the server; and

sending a suggested modification that would allow the at least one client to be managed by the server to the user of the at least one client.

7. The method of claim 1, wherein the discovering, comparing, recognizing, and pushing are performed by a server side application on the server, wherein the server side application comprises of:

a discovery application for performing discovery functions related to the plurality of clients;

an analysis application for performing validity checks with respect to the rules for the plurality of clients; and

an user interface application to control a display of information on the plurality of clients;

8. The method of claim 1, wherein the server is connected to a storage area network, and wherein the plurality of clients include hosts and storage devices.

9. A method for aggregating transactions comprising:

receiving at a server data on a plurality of transactions performed by clients managed to the server;

verifying that the plurality of transactions conform to rules maintained at the server, wherein the rules are for examining prior operational history and current operation of the clients;

aggregating at the server the data on the plurality of transactions; and

sending the data on the plurality of transactions to a master server coupled to the server, wherein the master server is a computational device coupled to a plurality of servers.

10. The method of claim 9, further comprising:

generating an invoice based on the aggregated data on the plurality of transactions; and

displaying the data on the plurality of transactions to an administrator connected to the server.

11. The method of claim 9, wherein the master server has master server side applications that corresponds to server side applications on the server, the method further comprising:

storing the data on the plurality of transactions at the master server; and

displaying the data on the plurality of transactions to an administrator connected to the master server.

12. The method of claim 9, wherein the data on the plurality of transactions include billing information related to the plurality of clients, and a billing application on the server performs the aggregating, wherein the billing application on the server sends the data to a master billing application on the at least one server.

13. A method for updating devices, comprising:

receiving an update at a management server from a master server connected to the management server, wherein a plurality of management servers are connected to the master server;

determining at the management server at least one client that requires the update, wherein the one management server manages a plurality of clients including the at least one client, wherein the management server includes rules for examining prior operational history and current operation of the at least one client, and wherein the update including code is necessary for satisfying the rules; and

pushing the update to the at least one client from the management server.

14. The method of claim 13, wherein the master server manages the plurality of management servers, wherein the master server is connected securely to the plurality of management servers, wherein the plurality of clients comprise a storage area network, and wherein pushing the update to the at least one client does not require permission of any user of the at least one client.

15. The method of claim 13, wherein the plurality of management servers periodically update the master server with information related to the plurality of clients managed by the plurality of management servers.

16. A system for network management of a plurality of clients comprising:

a server connected to the plurality of clients and managing the plurality of clients;

means for discovering information on at least one client of the plurality of clients;

means for comparing the discovered information to rules related to the management of the plurality of clients, wherein the rules are for examining prior operational history and current operation of the at least one client;

means for recognizing an update to be applied to the at least one client based on the comparison, wherein the update includes an executable that can be automatically installed on the at least one client; and

means for pushing the update to the at least one client, wherein the discovering, comparing, recognizing and pushing are controlled by the server.

17. The system of claim 16, wherein the means for discovering includes a discovery application on the server, wherein the means for discovering further performs:

determining a unique name of the at least one client;

determining an operating system of the at least one client; and

determining a participation in a dynamic licensing scheme of the at least one client.

18. The system of claim 16, wherein the means for comparing and the means for recognizing include an analysis application on the server, and wherein the rules related to the management of the plurality of clients include rules related to versioning requirements of software, rules related to network environment, rules related to billing, rules related to analysis of logs, and rules related to licensing requirements.

19. The system of claim 16, wherein the server includes an user interface application, the system further comprising:

means for displaying a message via the user interface application on a screen of the at least one client, wherein the message is transmitted in hypertext, text file format or electronic mail to the at least one client, and wherein the message requests permission from the at least one client for pushing the update.

20. The system of claim 16, further comprising:

means for receiving the update at the server from a master server, wherein the master server is a computational device to which a plurality of servers are securely connected.

21. The system of claim 16, further comprising:

means for determining that the at least one client cannot be managed by the server;

means for sending a notification to an user of the at least one client and the administrator of the server of the determination that the at least one client cannot be managed by the server; and

means for sending a suggested modification that would allow the at least one client to be managed by the server to the user of the at least one client.

22. The system of claim 16, wherein the means for discovering, the means for comparing, the means for recognizing, and the means for pushing comprise a server side application on the server, wherein the server side application comprises of:

a discovery application for performing discovery functions related to the plurality of clients;

an analysis application for performing validity checks with respect to the rules for the plurality of clients; and

an user interface application to control a display of information on the plurality of clients;

23. The system of claim 16, wherein the server is connected to a storage area network, and wherein the plurality of clients include hosts and storage devices.

24. A system for aggregating transactions from clients comprising:

a server coupled to the clients and managing the clients;

means for receiving at the server data on a plurality of transactions performed by the clients;

means for verifying that the plurality of transactions conform to rules maintained at the server, wherein the rules are for examining prior operational history and current operation of the clients;

means for aggregating at the server the data on the plurality of transactions; and

means for sending the data on the plurality of transactions to a master server, wherein the master server is coupled to the server and to other servers.

25. The system of claim 24, further comprising:

means for generating an invoice based on the aggregated data on the plurality of transactions; and

means for displaying the data on the plurality of transactions to an administrator connected to the server.

26. The system of claim 24 wherein the master server has master server side applications that corresponds to server side applications on the server, the system further comprising:

means for storing the data on the plurality of transactions at the master server; and

means for displaying the data on the plurality of transactions to an administrator connected to the master server.

27. The system of claim 24 wherein the data on the plurality of transactions include billing information related to the plurality of clients, and a billing application on the server performs the aggregating, wherein the billing application on the server sends the data to a master billing application on the at least one server.

28. A system for updating clients, comprising:

a plurality of management servers;

a master server connected to the plurality of management servers;

means for receiving an update at a management server from the master server;

means for determining at the management server at least one client that requires the update, wherein the one management server manages a plurality of clients including the at least one client, wherein the management server includes rules for examining prior operational history and current operation of the at least one client, and wherein the update including code is necessary for satisfying the rules; and

means for pushing the update to the at least one client from the management server.

29. The system of claim 28, wherein the master server manages the plurality of management servers, wherein the master server is connected securely to the plurality of management servers, wherein the plurality of clients comprise a storage area network, and wherein pushing the update to the at least one client does not require permission of any user of the at least one client.

30. The system of claim 28, wherein the plurality of management servers periodically update the master server with information related to the plurality of clients managed by the plurality of management servers.

31. An article of manufacture for network management, wherein the article of manufacture is capable of causing operations, the operations comprising:

discovering information on at least one client of a plurality of clients managed by a server;

comparing the discovered information to rules related to the management of the plurality of clients, wherein the rules are for examining prior operational history and current operation of the at least one client;

based on the comparison, recognizing an update to be applied to the at least one client, wherein the update includes an executable that can be automatically installed on the at least one client; and

pushing the update to the at least one client, wherein the discovering, comparing, recognizing and pushing are controlled by the server.

32. The article of manufacture of claim 31 wherein the discovering is performed by a discovery application on the server, wherein the discovering further comprises:

determining a unique name of the at least one client;

determining an operating system of the at least one client; and

determining a participation in a dynamic licensing scheme of the at least one client.

33. The article of manufacture of claim 31 wherein the comparing and recognizing is performed by an analysis application on the server, and wherein the rules related to the management of the plurality of clients include rules related to versioning requirements of software, rules related to network environment, rules related to billing, rules related to analysis of logs, and rules related to licensing requirements.

34. The article of manufacture of claim 31, wherein the server includes an user interface application, the article of manufacture further comprising:

prior to pushing, displaying a message via the user interface application on a screen of the at least one client, wherein the message is transmitted in hypertext, text file format or electronic mail to the at least one client, and wherein the message requests permission from the at least one client for pushing the update.

35. The article of manufacture of claim 31, further comprising:

prior to pushing the update, receiving the update at the server from a master server, wherein the master server is a computational device to which a plurality of servers are securely connected.

36. The article of manufacture of claim 31, further comprising:

based on the comparison, determining that the at least one client cannot be managed by the server;

sending a notification to an user of the at least one client and the administrator of the server of the determination that the at least one client cannot be managed by the server; and

sending a suggested modification that would allow the at least one client to be managed by the server to the user of the at least one client.

37. The article of manufacture of claim 31, wherein the discovering, comparing, recognizing, and pushing are performed by a server side application on the server, wherein the server side application comprises of:

a discovery application for performing discovery functions related to the plurality of clients;

an analysis application for performing validity checks with respect to the rules for the plurality of clients; and

an user interface application to control a display of information on the plurality of clients;

38. The article of manufacture of claim 31, wherein the server is connected to a storage area network, and wherein the plurality of clients include hosts and storage devices.

39. An article of manufacture for aggregating transactions, wherein the article of manufacture is capable of causing operations, the operations comprising:

receiving at a server data on a plurality of transactions performed by clients managed to the server;

verifying that the plurality of transactions conform to rules maintained at the server, wherein the rules are for examining prior operational history and current operation of the clients;

aggregating at the server the data on the plurality of transactions; and

sending the data on the plurality of transactions to a master server coupled to the server, wherein the master server is a computational device coupled to a plurality of servers.

40. The article of manufacture of claim 39, further comprising:

generating an invoice based on the aggregated data on the plurality of transactions; and

displaying the data on the plurality of transactions to an administrator connected to the server.

41. The article of manufacture of claim 39, wherein the master server has master server side applications that corresponds to server side applications on the server, the article of manufacture further comprising:

storing the data on the plurality of transactions at the master server; and

displaying the data on the plurality of transactions to an administrator connected to the master server.

42. The article of manufacture of claim 39, wherein the data on the plurality of transactions include billing information related to the plurality of clients, and a billing application on the server performs the aggregating, wherein the billing application on the server sends the data to a master billing application on the at least one server.

43. An article of manufacture for updating devices, wherein the article of manufacture is capable of causing operations, the operations comprising:

receiving an update at a management server from a master server connected to the management server, wherein a plurality of management servers are connected to the master server;

determining at the management server at least one client that requires the update, wherein the one management server manages a plurality of clients including the at least one client, wherein the management server includes rules for examining prior operational history and current operation of the at least one client, and wherein the update including code is necessary for satisfying the rules; and

pushing the update to the at least one client from the management server.

44. The article of manufacture of claim 43, wherein the master server manages the plurality of management servers, wherein the master server is connected securely to the plurality of management servers, wherein the plurality of clients comprise a storage area network, and wherein pushing the update to the at least one client does not require permission of any user of the at least one client.

45. The article of manufacture of claim 43, wherein the plurality of management servers periodically update the master server with information related to the plurality of clients managed by the plurality of management servers.