Method for tracking configuration changes in networks of computer systems through historical monitoring of configuration status of devices on the network.

• US 6,282,175 B1
• Filed: 04/23/1998
• Issued: 08/28/2001
• Est. Priority Date: 04/23/1998
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Steele, Douglas William, Bryant, Craig William, Goin, Todd M., Moos, Thomas J.
• Primary Examiner(s): Jung, Min
• Application Number:
  US09/065,263
• Time in Patent Office: 1,223 Days
• Field of Search: 370/254, 370/255, 370/256, 370/257, 370/258, 709/223, 709/224
• US Class Current: 370/254
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 11/2289 by configuration test
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3051 Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs verification or detection of system hardware configuration G06F11/2247
• CPC Class Codes: G06F 11/327 Alarm or error message display
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/835 Timestamp
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: H04L 41/0253 using browsers or web-pages for accessing management information
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• 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/0869 Validating the configuration within one network element
• CPC Class Codes: H04L 43/045 for graphical visualisation of monitoring data
• CPC Class Codes: H04L 43/067 using time frame reporting
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/106 using time related information in packets, e.g. by adding timestamps

Abstract

A tracking system that uses a revision control system and configuration status gathering to historically track and store configuration changes in computers and interconnect devices to aid in managing and troubleshooting networks of computer systems. Configuration data is gathered from devices on the network selected for monitoring on a periodic basis. The data collected each collection cycle is stored in a data storehouse on a computer within the network, called the remote support node. The data storehouse is comprised of a revision control system and data base. The data is accessed by computers on the network having web browsers. The user selects a first and second collection time, and any changes in configuration of any monitored devices in the network occurring between these two collection times is displayed in the browser window. By changing the collection times, configuration changes from different collection cycles may be viewed.

Claims

1. A computerized method for tracking configuration changes within a computer system comprising the steps of:

(a) collecting a first snapshot of a data item having a unique identifier at a first predetermined time, from a first monitored device on a computer system network, and setting a first time stamp indicating when said first snapshot was collected;

(b) storing said first snapshot of said data item and said first time stamp in a remote support node connected to said first monitored device through a first network connection within said computer system network;

(c) collecting a second snapshot of said data item having said unique identifier at a second predetermined time, from said first monitored device on said computer system network, and setting a second time stamp indicating when said second snapshot was collected;

(d) comparing said stored first snapshot of said data item to said collected second snapshot of said data item;

(e) when step (d) determines that said collected second snapshot of said data item has at least one difference from said stored first snapshot of said data item, performing step (f) and not step (g), and when step (d) determines that there is no difference, performing step (g) and not step (f);

(f) storing all differences identified in step (d) and said second time stamp in said remote support node as a most recently stored snapshot of said data item;

(g) discarding said second snapshot and said second time stamp, wherein said stored first snapshot is a most recently stored snapshot of said data item; and

(h) displaying said all differences stored in step (f) between said second snapshot and said first snapshot, or displaying an indication that said no difference was determined between said second snapshot and said first snapshot, on a graphics display in said remote support node.

2. A computerized method for tracking configuration changes within a computer system according to claim 1 wherein step (b) further comprises step (b1), and step (f) further comprises step (f1):

(b1) storing said first snapshot and said first time stamp of said data item in a data storehouse within said remote support node; and

(f1) storing said all differences identified in step (d) and said second time stamp in said data storehouse within said remote support node.

3. A computerized method for tracking configuration changes within a computer system according to claim 1 further comprising the steps of:

(i) collecting an additional snapshot of said data item having said unique identifier at an additional predetermined time, from said first monitored device on said computer system network, and setting an additional time stamp indicating when said additional snapshot was collected;

(j) comparing said additional snapshot of said data item to said most recently stored snapshot of said data item;

(k) repeating steps (e), (f), (g), and (h) for said additional snapshot and said most recently stored snapshot of said data item; and

(l) repeating steps (i), (j), and (k) for a plurality of additional snapshots of said data item having said unique identifier, at a plurality of additional predetermined times, from said first monitored device on said computer system network.

4. A computerized method for tracking configuration changes within a computer system according to claim 3 further comprising the step of:

(m) repeating steps (a) through (l) for a plurality of data items of said first monitored device on said computer system network, wherein each of said plurality of data items has a different unique identifier.

5. A computerized method for tracking configuration changes within a computer system according to claim 4 further comprising the step of:

(n) repeating steps (a) through (m) for each of a plurality of additional monitored devices on said computer system network.

6. A computerized method for tracking configuration changes within a computer system according to claim 3 wherein step (a) further comprises step (a0) performed before step (a), step (c) further comprises step (c0) performed before step (c), step (i) further comprises step (i0) performed before step (i), and step (l) further comprises step (l) performed before step (l):

(a0) setting said first predetermined time for collecting said first snapshot of said data item within schedule software located within said remote support node;

(c0) setting said second predetermined time for collecting said second snapshot of said data item within said schedule software located within said remote support node;

(i0) setting said additional predetermined time for collecting said additional snapshot of said data item within said schedule software located within said remote support node; and

(l0) setting said plurality of additional predetermined times for collecting said plurality of additional snapshots of said data item within said schedule software located within said remote support node.

7. A computerized method for tracking configuration changes within a computer system according to claim 6 wherein step (a0) further comprises the steps of:

(a0a) invoking said schedule software at said first predetermined time

(a0b) passing a collection root identifier from said schedule software to pebble software located within said remote support node, wherein said collection root identifier defines a list of data items;

(a0c) invoking, with said schedule software, a collector portion of said pebble software;

(a0d) accessing, with said collector portion of said pebble software, a data storehouse within said remote support node, wherein said collection root identifier is used to get said list of data items;

(a0e) accessing, with said collector portion of said pebble software, said data storehouse within said remote support node, wherein collection method information is gathered for collecting said snapshots of each of said data items in said list of data items from said first monitored device, and from a plurality of additional monitored devices, said collection method information comprising commands for collecting each of said data items in said list, attributes of each of said data items when said attributes are associated with each of said data items in said list, a most recently stored signature of each of said data items in said list, and from which of said first monitored device and said plurality of additional monitored devices each of said data items in said list is to be collected; and

(a0f) grouping said collection method information gathered in step (a0e) by said first monitored device and by each of said plurality of additional monitored devices.

8. A computerized method for tracking configuration changes within a computer system according to claim 7 wherein said first monitored device on said computer system network is a first monitored interconnect device.

9. A computerized method for tracking configuration changes within a computer system according to claim 8 wherein step (a) further comprises the steps of:

(a1) invoking, through said collector portion of said pebble software, a collection script for collecting said first snapshot of said data item from said first monitored interconnect device;

(a2) invoking, through said collection script, a first command from said grouped collection method information gathered in step (a0e) and grouped in step (a0f) for said first monitored interconnect device, to collect said first snapshot of said data item from said first monitored interconnect device;

(a3) determining if said first command to collect said first snapshot of said data item was successfully executed;

(a4) when step (a3) determines that said first command was successfully executed, performing steps (a5) through (a9) and not steps (a10) through (a12), and when step (a3) determines that said first command was not successfully executed, performing steps (a10) through (a12) and not steps (a5) through (a9);

(a5) creating a first signature for said data item;

(a6) capturing a first output from said executed first command, any first attributes, said first signature, and said first time stamp;

(a7) returning said captured first output, said captured any first attributes, said captured first signature, and said captured first time stamp to said remote support node for storing in a memory within said remote support node;

(a8) transferring, from said memory within said remote support node, said stored first output, said stored any first attributes, and said stored first time stamp for storage in a revision control system in said data storehouse within said remote support node, wherein said stored first output, said stored any first attributes, and said stored first time stamp constitute said first snapshot;

(a9) transferring, from said memory within said remote support node, said stored first signature, said stored first time stamp, and a first change event indicator for storage in a data base in said data storehouse within said remote support node;

(a10) generating a first error message, and capturing said first error message and said first time stamp;

(a11) returning said captured first error message and said captured first time stamp to said remote support node; and

(a12) storing said captured first error message and said captured first time stamp in a log file in a data base in said data storehouse within said remote support node.

10. A computerized method for tracking configuration changes within a computer system according to claim 8 wherein step (c) further comprises the steps of:

(c1) invoking, through said collector portion of said pebble software, said collection script for collecting said second snapshot of said data item from said first monitored interconnect device;

(c2) invoking, through said collection script, a first command from said grouped collection method information gathered in step (a0e) and grouped in step (a0f) for said first monitored interconnect device, to collect said second snapshot of said data item from said first monitored interconnect device;

(c3) determining if said first command to collect said second snapshot of said data item was successfully executed;

(c4) when step (c3) determines that said first command was successfully executed, performing steps (c5) through (c12) and not steps (c13) through (c15), and when step (c3) determines that said first command was not successfully executed, performing steps (c13) through (c15) and not steps (c5) through (c12);

(c5) creating a second signature for said data item;

(c6) capturing a second output from said executed first command, any second attributes, said second signature, and said second time stamp;

(c7) returning said captured second output, said captured any second attributes, said captured second signature, and said captured second time stamp to said remote support node for storing in a memory within said remote support node;

(c8) comparing, within said remote support node, said second signature of said data item with said most recently stored signature of said data item from step (a0e);

(c9) when step (c8) determines that said second signature is different from said most recently stored signature of said data item, performing steps (c10) and (c11) and not step (c12), and when step (c10) determines that said second signature is not different, performing step (c12) and not steps (c10) and (c11);

(c10) transferring, from said memory within said remote support node, said stored second output, said stored any second attributes, and said stored first time stamp for storage in a revision control system in said data storehouse within said remote support node, wherein said stored second output, said stored any second attributes, and said stored second time stamp constitute said second snapshot;

(c11) transferring, from said memory within said remote support node, said stored second signature, said stored second time stamp, and a second change event indicator for storage in a data base in said data storehouse within said remote support node;

(c12) discarding said captured second output, said captured any second attributes, said captured second signature, and said captured second time stamp;

(c13) generating a second error message, and capturing said second error message and said second time stamp;

(c14) returning said captured second error message and said captured second time stamp to said remote support node; and

(c15) storing said captured second error message and said captured second time stamp in a log file in a data base in said data storehouse within said remote support node.

11. A computerized method for tracking configuration changes within a computer system according to claim 8 wherein step (i) further comprises the steps of:

(i1) invoking, through said collector portion of said pebble software, said collection script for collecting said second additional snapshot of said data item from said first monitored interconnect device;

(i2) invoking, through said collection script, a first command from said grouped collection method information gathered in step (a0e) and grouped in step (a0f) for said first monitored interconnect device, to collect said additional snapshot of said data item from said first monitored interconnect device;

(i3) determining if said first command to collect said additional snapshot of said data item was successfully executed;

(i4) when step (i3) determines that said first command was successfully executed, performing steps (i5) through (i12) and not steps (i13) through (i15), and when step (i3) determines that said first command was not successfully executed, performing steps (i13) through (i15) and not steps (i5) through (i12);

(i5) creating an additional signature for said data item;

(i6) capturing an additional output from said executed first command, any additional attributes, said additional signature, and said additional time stamp;

(i7) returning said captured additional output, said captured any additional attributes, said captured additional signature, and said captured additional time stamp to said remote support node for storing in a memory within said remote support node;

(i8) comparing, within said remote support node, said additional signature of said data item with said most recently stored signature of said data item from step (a0e);

(i9) when step (i8) determines that said additional signature is different from said most recently stored signature of said data item, performing steps (i10) and (i11) and not step (i12), and when step (i10) determines that said additional signature is not different, performing step (i12) and not steps (i10) and (i11);

(i10) transferring, from said memory within said remote support node, said stored additional output, said stored any additional attributes, and said stored additional time stamp for storage in a revision control system in said data storehouse within said remote support node, wherein said stored additional output, said stored any additional attributes, and said stored additional time stamp constitute said additional snapshot;

(i11) transferring, from said memory within said remote support node, said stored additional signature, said stored additional time stamp, and an additional change event indicator for storage in a data base in said data storehouse within said remote support node;

(i12) discarding said captured additional output, said captured any additional attributes, said captured additional signature, and said captured additional time stamp;

(i13) generating an additional error message, and capturing said additional error message and said additional time stamp;

(i14) returning said captured additional error message and said captured additional time stamp to said remote support node; and

(i15) storing said additional error message and said additional time stamp in a log file in a data base in said data storehouse within said remote support node.

12. A computerized method for tracking configuration changes within a computer system according to claim 11 wherein step (l) further comprises the steps of:

(l1) repeating steps (i1) through (i15) for each of said plurality of additional snapshots at each of said plurality of additional predetermined times.

13. A computerized method for tracking configuration changes within a computer system according to claim 7 wherein said first monitored device on said computer system network is a first monitored computer.

14. A computerized method for tracking configuration changes within a computer system according to claim 13 wherein step (a) further comprises the steps of:

(a1) launching, through said collector portion of said pebble software, remote execution of collecting said grouped collection method information for said first monitored computer by passing said grouped collection method information for said first monitored computer to said first monitored computer;

(a2) invoking, through said collector portion of said pebble software, client collection software installed on said first monitored computer to collect said first snapshot of said data item;

(a3) invoking, through said client collection software, a first command from said grouped collection method information passed to said first monitored computer in step (a1) to collect said data item from said first monitored computer;

(a4) determining if said first command to collect said data item was successfully executed;

(a5) when step (a4) determines that said first command was successfully executed, performing steps (a6) through (a10) and not steps (a11) through (a13), and when step (a4) determines that said first command was not successfully executed, performing steps (a11) through (a13), and not steps (a6) through (a10);

(a6) creating a first signature for said data item;

(a7) storing a first output from said executed first command, any first attributes, said first signature, and said first time stamp in a first monitored computer memory;

(a8) returning said stored first output, said stored any first attributes, said stored first signature, and said stored first time stamp, from said first monitored computer memory, to said remote support node for storing in a memory within said remote support node;

(a9) transferring, from said memory in said remote support node, said stored first output, said stored any first attributes, and said stored first time stamp for storage in a revision control system in said data storehouse within said remote support node, wherein said stored first output, said stored any first attributes, and said stored first time stamp constitute said first snapshot;

(a10) transferring, from said memory in said remote support node, said stored first signature, said stored first time stamp, and a first change event indicator for storage in a data base in said data storehouse within said remote support node;

(a11) generating a first error message, and storing said first error message and said first time stamp in a first monitored computer memory;

(a12) returning said stored first error message and said stored first time stamp from said first monitored computer memory to said remote support node; and

(a13) storing said stored first error message and said stored first time stamp in a log file in a data base in said data storehouse within said remote support node.

15. A computerized method for tracking configuration changes within a computer system according to claim 13 wherein step (c) further comprises the steps of:

(c1) launching, through said collector portion of said pebble software, remote execution of collecting said grouped collection method information for said first monitored computer by passing said grouped collection method information for said first monitored computer to said first monitored computer;

(c2) invoking, through said collector portion of said pebble software, client collection software installed on said first monitored computer to collect said second snapshot of said data item;

(c3) invoking, through said client collection software, a first command from said grouped collection method information passed to said first monitored computer in step (c1) to collect said data item from said first monitored computer;

(c4) determining if said first command to collect said data item was successfully executed;

(c5) when step (c4) determines that said first command was successfully executed, performing steps (c6) through (c10) and not step (c11), and when step (c4) determines that said first command was not successfully executed, performing step (c11) and not steps (c6) through (c10);

(c6) creating a second signature for said data item;

(c7) comparing said second signature of said data item with said most recently stored signature of said data item from step (a0e);

(c8) when step (c7) determines that said second signature is different from said most recently stored signature of said data item, performing step (c9) and not step (c10), and when step (c7) determines that said second signature is not different, performing step (c10) and not step (c9);

(c9) storing differences from a second output from said executed first command, any second attributes, said second signature, and said second time stamp in a first monitored computer memory;

(c10) discarding a second output from said executed first command, any second attributes, said second signature, and said second time stamp;

(c11) generating a second error message, and storing said second error message and said second time stamp in a first monitored computer memory;

(c12) returning said stored differences from said second output from said executed first command, said stored any second attributes, said stored second signature, and said stored second time stamp, from said first monitored computer memory, to said remote support node for storing in a memory within said remote support node;

(c13) returning said stored second error message and said stored second time stamp, from said first monitored computer memory, to said remote support node for storing in said memory within said remote support node;

(c14) transferring, from said memory in said remote support node, said stored differences from said second output, said stored any second attributes, and said stored second time stamp for storage in a revision control system in said data storehouse within said remote support node, wherein said stored differences from said second output, said stored any second attributes, and said stored second time stamp constitute said second snapshot;

(c15) transferring, from said memory in said remote support node, said stored first signature, said stored second time stamp, and a second change event indicator for storage in a data base in said data storehouse within said remote support node; and

(c16) transferring, from said memory in said remote support node, said stored second error message and said stored second time stamp for storage in a log file in said data base in said data storehouse within said remote support node.

16. A computerized method for tracking configuration changes within a computer system according to claim 13 wherein step (i) further comprises the steps of:

(i1) launching, through said collector portion of said pebble software, remote execution of collecting said grouped collection method information for said first monitored computer by passing said grouped collection method information for said first monitored computer to said first monitored computer;

(i2) invoking, through said collector portion of said pebble software, client collection software installed on said first monitored computer to collect said additional snapshot of said data item;

(i3) invoking, through said client collection software, a first command from said grouped collection method information passed to said first monitored computer in step (i1) to collect said data item from said first monitored computer;

(i4) determining if said first command to collect said data item was successfully executed;

(i5) when step (i4) determines that said first command was successfully executed, performing steps (i6) through (i10) and not step (i11), and when step (i4) determines that said first command was not successfully executed, performing step (i11) and not steps (i6) through (i10);

(i6) creating an additional signature for said data item;

(i7) comparing said additional signature of said data item with said most recently stored signature of said data item from step (a0e);

(i8) when step (i7) determines that said second signature is different from said most recently stored signature of said data item, performing step (i9) and not step (i10), and when step (i7) determines that said second signature is not different, performing step (i10) and not step (i9);

(i9) storing differences from an additional output from said executed first command, any additional attributes, said additional signature, and said additional time stamp in a first monitored computer memory;

(i10) discarding, an additional output from said executed first command, any additional attributes, said additional signature, and said additional time stamp;

(i11) generating an additional error message, and storing said additional error message and said additional time stamp in a first monitored computer memory;

(i12) returning said stored differences from an additional output from said executed first command, said stored any additional attributes, said stored additional signature, and said stored additional time stamp, from said first monitored computer memory, to said remote support node for storing in a memory within said remote support node;

(i13) returning said stored additional error message and said stored additional time stamp, from said first monitored computer memory, to said remote support node for storing in said memory within said remote support node;

(i14) transferring, from said memory in said remote support node, said stored differences from said additional output, said stored any additional attributes, and said stored additional time stamp for storage in a revision control system in said data storehouse within said remote support node, wherein said stored differences from said additional output, said stored any additional attributes, and said stored additional time stamp constitute said additional snapshot;

(i15) transferring, from said memory in said remote support node, said stored additional signature, said stored additional time stamp, and an additional change event indicator for storage in a data base in said data storehouse within said remote support node; and

(i16) transferring, from said memory in said remote support node, said stored additional error message and said stored additional time stamp for storage in a log file in a data base in said data storehouse within said remote support node.

17. A computerized method for tracking configuration changes within a computer system according to claim 16 wherein step (l) further comprises the steps of:

(l1) repeating steps (i1) through (i16) for each said plurality of additional snapshots at each of said plurality of additional predetermined times.

18. A computerized method for tracking configuration changes within a computer system according to claim 1 wherein step (h) further comprises the steps of:

(h1) loading web browser software on a browser computer, wherein said browser computer is connected to said remote support node through a second network connection;

(h2) requesting, through said web browser software, a universal resource locator for said computerized method for tracking configuration changes;

(h3) establishing a connection between said browser computer and said remote support node through said second network connection;

(h4) finding, within said remote support node, a html page associated with said universal resource locator requested in step (h2) for said computerized method for tracking configuration changes;

(h5) returning said html page for said computerized method for tracking configuration changes to said browser computer through said connection; and

(h6) displaying said html page for said computerized method for tracking configuration changes on a screen display on said browser computer wherein said all differences stored in step (f) are displayed within said html page on said screen display.

19. A computerized method for tracking configuration changes within a computer system according to claim 18 wherein step (h6) further comprises the steps of:

(h6a) displaying said html page on said screen display as a tracking tree frame and a data display frame;

(h6b) receiving click input on a hyperlink in said html page;

(h6c) requesting a universal resource locator for said hyperlink in said html page through said web browser software and said connection to said remote support node;

(h6d) finding, within said remote support node, a html page for said hyperlink requested in step (h6c);

(h6e) returning said html page for said hyperlink to said browser computer through said connection; and

(h6f) displaying said html page for said hyperlink in said data display frame in said screen display.

20. A computerized method for tracking configuration changes within a computer system according to claim 19 wherein step (h6a) further comprises the steps of:

(h6a1) displaying in said tracking tree frame at least one tab, wherein receiving click input on said at least one tab accesses a function of said computerized method for tracking configuration changes; and

(h6a2) displaying within each of said at least one tab at least one available action button, wherein receiving click input on said at least one available action button will execute a specific action within said function of said computerized method for tracking configuration changes.

21. A computerized method for tracking configuration changes within a computer system according to claim 20 wherein step (h6a1) further comprises the steps of:

(h6a1a) receiving click input on said at least one tab, wherein said function accessed is a tracking function;

(h6a1b) displaying in said tracking tree frame as part of said tracking function a tracking tree, wherein said tracking tree is a an expandable index of said data items;

(h6a1c) receiving click input on a data item name in said tracking tree which has a change indicator associated with a data item icon corresponding to said data item name; and

(h6a1d) displaying in said data display frame a time frame, a changes within time frame, and a collection history, wherein said time frame shows a first collection time and a second collection time during which said data item was changed, said changes within time frame shows said at least one difference of said data item that occurred between said first collection time and said second collection time, and said collection history shows a date and a time that said data item was changed.

22. A computerized method for tracking configuration changes within a computer system according to claim 20 wherein step (h6a2) further comprises the steps of:

(h6a2a) receiving click input on said at least one available action button wherein said at least one available action button is a change time frame available action button;

(h6a2b) entering a new first collection time and a new second collection time;

(h6a2c) requesting a script associated with said change time frame available action button through said web browser software and said connection to said remote support node;

(h6a2d) loading said script requested in step (h6a2c) within pebble software within said remote support node;

(h6a2e) communicating with hat daemon software to get permission to run said script;

(h6a2f) running said script and accessing a data storehouse within said remote support node to obtain said at least one difference of said data item;

(h6a2g) formatting said at least one difference of said data item into a html formatted page;

(h6a2h) returning said html formatted page for said at least one difference of said data item to said browser computer through said connection; and

(h6a2i) displaying said html formatted page for said at least one difference of said data item in said data display frame in said screen display.