Method and apparatus for providing scalability and fault tolerance in a distributed network
View Patent ↗A method and apparatus for providing scalability and fault tolerance to a distributed network. According to one embodiment of the invention, a network management system comprises a set of one or more element management servers. One of the plurality of element management servers is designated as a master server. The master server determines which of the plurality of element management servers are to manage each of a set of one or more network elements. In one embodiment, peered and federated services are used within the network management system to provide scalability and fault tolerance.
1. A network management system comprising:
a plurality of element management servers to manage a set of one or more network elements, one of said plurality of element management servers to be designated as the master server, said master server to,
determine which of said plurality of element management servers to manage each of said set of one or more network elements,
detect a failure of one or more of said plurality of element management servers, and
manage the failure by determining which of said non-failed plurality of element management servers are to manage each of said set of one or more network elements; and
a peered service resident on each of said plurality of element management servers to handle a request from a client, wherein the peered service on one of the element management servers can forward the request to the peered service on another element management server.
2. The network management system of claim 1 where each of said plurality of element management server includes:
a federated service, said federated service to access data stored in a element management server memory, said element management server memory includes data to describe each of said set of network elements to be managed by each of said plurality of element management servers.
3. The network management system of claim 2 where said federated service to access nodal alarm data in said element management server memory.
4. The network management system of claim 2 where said federated service to provide data to a data store.
5. The network management system of claim 2 where said federated service to provide event log data to a data store.
6. The network management system of claim 1 where said plurality of element management servers to determine with a bully algorithm which of said plurality of element management servers is designated as said master server.
7. The network management system of claim 6 where said peered service resident on said plurality of element management servers to access a database to handle said request.
8. The network management system of claim 1 where said peered service resident on said plurality of element management servers to access event log data in said database.
9. The network management system of claim 8 where said peered service resident on said plurality of element management servers to calculate a circuit route to handle said request.
10. The network management system of claim 1 where said client to randomly select one of said plurality of element management servers to handle said request.
11. The network management system of claim 1 where said client to randomly access a peered service on said plurality of element management servers.
12. The network management system of claim 1 where said client to generate a view of said of network elements and said plurality of element management servers from data stored in a database.
13. The network management system of claim 1 where said client to randomly access a federated service on said Plurality of element management servers.
14. The network management system of claim 1 where said client to generate a view of said set of network elements and said plurality of element management servers from data stored in said element management server memory.
15. A machine-readable medium that provides instructions, which when executed by a set of one or more processors, cause said set of processors to perform operations comprising:
pooling a plurality of element management servers, said plurality of element management servers to manage a set of network elements;
designating a master server from said plurality of element management servers, said master server to,
determine which of said plurality of element management servers to manage each of said set of network elements,
detect a failure of one or more of said plurality of element management servers, and
manage the failure by determining which of said non-failed plurality of element management servers are to manage each of said set of network elements; and
receiving a request from a client, said request to be handled by a peered service resident on each of said plurality of element management servers, wherein the peered service on one of the element management servers can forward the request to the peered service on another element management server.
16. The machine-readable medium of claim 15 further comprising:
receiving a request for data stored in element management server memory, said request to be handled by a federated service, said federated service to access said data stored in element management server memory, said data to describe each of said set of network elements to be managed by said plurality of element management servers.
17. The machine-readable medium of claim 16 where said federated service to access nodal alarm data in said element management server memory.
18. The machine-readable medium of claim 16 where said federated service to provide data to a data store.
19. The machine-readable medium of claim 16 where said federated service to provide event log data to a data store.
20. The machine-readable medium of claim 15 where said plurality of element management servers to determine with of said plurality of element management servers is designated as said master server.
21. The machine-readable medium of claim 20 where said plurality of element management servers to determine with a bully algorithm which of said plurality of element management servers is designated as said master server.
22. The machine-readable medium of claim 15 where said peered service resident on said plurality of element management servers to access a database to handle said request.
23. The machine-readable medium of claim 15 where said peered service resident on said plurality of element management servers to access event log data in said database.
24. The machine-readable medium of claim 15 where said client to randomly select one of said plurality of element management servers to handle said request.
25. The machine-readable medium of claim 15 where said client to randomly access a peered service on said plurality of element management servers.
26. The machine-readable medium of claim 15 where said client to generate a view of said of network elements and said plurality of element management servers from data stored in a database.
27. The machine-readable medium of claim 15 where said client to randomly access a federated service on said plurality of element management servers.
28. The machine-readable medium of claim 15 where said client to generate a view of said set of network elements and said plurality of element management servers from data stored in said element management server memory.