System and method for synchronizing the configuration of distributed network management applications
First Claim
1. A change management system comprising:
- an object connected to a network, wherein the object is associated with object configuration information; and
a change management server connected to the network, the change management server having a change management processor adapted to;
obtain current object configuration information;
make a determination of whether the current object configuration information is different from last known object configuration information;
in the event the current object configuration information is different from the last known object configuration information, create an object configuration file from the current object configuration information; and
update an application with the object configuration file.
8 Assignments
0 Petitions
Accused Products
Abstract
A change management system to synchronize the configuration of network management applications. Traditional network management systems are maintained by hand-entering device lists into individual network management applications with no common-ties between the different applications. Whenever a network management application is changed or upgraded, it frequently becomes necessary to insure that the upgrade is populated throughout the network in order for devices to talk to one another in an error free way. The present invention is a system and method that automates the change management process in a real-time using a two-way communications model that permits a central database to affect changes on all or some network management applications/systems in the field, while also allowing those same field systems to affect the central database thereby reducing the time required for updating and monitoring a system when device changes take place.
135 Citations
40 Claims
-
1. A change management system comprising:
-
an object connected to a network, wherein the object is associated with object configuration information; and
a change management server connected to the network, the change management server having a change management processor adapted to;
obtain current object configuration information;
make a determination of whether the current object configuration information is different from last known object configuration information;
in the event the current object configuration information is different from the last known object configuration information, create an object configuration file from the current object configuration information; and
update an application with the object configuration file. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15)
-
-
16. A change management system comprising:
-
an object connected to a network, wherein the object is associated with object configuration information;
a network application server, the network application server having an application processor adapted to operate one or more applications, wherein each application comprises software instructions for managing the object, and wherein each application makes use of the object configuration information;
a change management server connected to the network, the change management server having a change management processor adapted to;
obtain current object configuration information;
make a determination of whether the current object configuration information is different from last known object configuration information;
in the event the current object configuration information is different from the last known object configuration information, create an object configuration file from the current object configuration information;
update an application with the object configuration file; and
update a central database with the current object configuration information; and
a controller server associated with the network application server and connected to the network, the controller server having a controller processor adapted to;
receive the object configuration file;
convert the object configuration file into a format accepted by each application operated by the network application server;
update the configuration of each application with the appropriate converted configuration;
stop each application; and
restart each application. - View Dependent Claims (17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27)
-
-
28. A method for managing change on a network, the method comprising:
-
obtaining current object configuration information for an object connected to the network;
determining whether the object current configuration information is different from last known object configuration information;
in the event the current object configuration information is different from the last known object configuration information, creating an object configuration file for the object from the current object configuration information; and
updating the application with the object configuration file. - View Dependent Claims (29, 30, 31, 32, 33, 34)
-
-
35. A method for reassigning network management functions of a network monitoring application running on a network, the method comprising:
-
detecting the connectivity between a first network monitoring application and a second network monitoring application;
if the connectivity between the first network monitoring application and the second network monitoring application is lost, using the first network monitoring application to launch a backup instance of the second network monitoring application;
assigning the backup instance of the second network monitoring application the network management functions of the second network monitoring application;
detecting at the first network monitoring application restoration of the connectivity between the first network monitoring application and the second network monitoring application;
in the event connectivity between the first network monitoring application and the second network monitoring application is restored, assigning the second network monitoring application the network management functions of the backup instance of the second network monitoring application; and
shutting down the backup instance of the second network monitoring application. - View Dependent Claims (36, 37, 38, 39, 40)
-
Specification