Managing a distributed directory database

• US 7,120,690 B1
• Filed: 09/27/2001
• Issued: 10/10/2006
• Est. Priority Date: 09/27/2001
• Status: Expired due to Term

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Krishnan, Sriram, Bauer, Andreas L., Lazar, Gregory W.
• Primary Examiner(s): Wiley, David
• Assistant Examiner(s): SHIN, KYUNG H
• Application Number:
  US09/965,430
• Time in Patent Office: 1,839 Days
• Field of Search: 709/223, 709/225, 709/239, 709/220, 707/200
• US Class Current: 709/225
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

In a computer network having a plurality of computer nodes, a directory database (DDB) distributed throughout the network in each of the nodes, the contents of the DDB being maintained consistent or replicated throughout the network in a manner to avoid a single point of failure through the use of one of its nodes having been appointed as master node. The master node has a privileged status as compared to the other nodes. The master node updates each DDB in each node in its network or domain configuration when the configuration changes, such as when a node fails, a network link fails and/or a node is added or removed. A node can be added to or removed from the configuration through the master node or through a non master node. A node can fail under different circumstances in which it may or may not know which node is its master node. A master node can fail and be replaced or can be replaced for other reasons. A global administrator is a privileged user compared to other computer network users who has authority to replace or appoint a master node and to configure a domain, and who performs these and other functions by way of computer terminal screen dialogs offered by a graphical user interface (GUI) associated with the computer network. Replication service includes pinging by the master node of its failed or potentially failed nodes, and participating nodes in the configuration use repetitive polling of their master node to aid it in its pursuit of DDB consistency across the configuration.

Claims

1. In a computer network having a plurality of nodes for interacting with computer network information including both computer data and domain configuration status, a system for managing said plurality of nodes comprising:

means for establishing a DDB in each of said nodes;

means for controlling contents of each said DDB to be identical to contents of every other said DDB and in a manner to avoid a single point of failure;

wherein said contents controlling means further comprises;

means for maintaining the most current of said domain configuration status in said DDB in said each of said nodes;

means for selecting one of said plurality of nodes as a master node;

means for subordinating all other of said plurality of nodes to said master node in a configuration defined by said master node and said all other of said plurality of nodes; and

,

wherein said master node includes means for responding to a change to said domain configuration status in a manner to maintain said contents of said each said DDB identical to said contents of said every other said DDB.

2. The system of claim 1 and wherein:

said each of said nodes has a unique IP address; and

,

said DDB establishing means further comprises;

means for associating each said unique IP address with its respective node to provide an IP-address-respective-node association;

means for combining said association for said each of said nodes into a network IP association; and

,

means for distributing said network IP association to said DDB in said each of said nodes.

3. The system of claim 1 and wherein said interacting includes receiving, storing, modifying, and transmitting.

4. The system of claim 1 and wherein said controlling means further comprises:

means for replacing said master node with another node if said master node fails.

5. The system of claim 4 and wherein said master node replacing means includes means for replacing said master node with another node selected from said configuration.

6. The system of claim 1 and wherein said change to said domain configuration status is selected from the group of changes consisting of:

adding a first node to said configuration;

deleting a second node from said configuration;

a third node failing in said configuration; and

, a network link failing between a fourth node in said configuration and said master node.

7. The system of claim 6 and wherein said computer network is a client-server network having a graphical user interface and wherein said selecting means further comprises:

means, utilizing said graphical user interface, for invoking a select master dialog by which said user can select said one of said plurality of nodes.

8. The system of claim 4 and wherein said computer network is a client-server network having a graphical user interface and wherein said replacing means further comprises:

means, utilizing said graphical user interface, for invoking a select master dialog by which said user can select said another node.

9. The system of claim 6 and wherein said responding means further comprises:

first means for handling said third node failing under conditions in which said master node is known to said third node; and

,

second means for handling said third node failing under conditions in which said master node is unknown to said third node.

10. The system of claim 9 and wherein said first means further comprises:

means for establishing version numbers to identify versions of said DDB in each of said plurality of nodes;

means, employed by each of said all other of said plurality of nodes, for continuously polling said master node at regular intervals to obtain the most current one of said version numbers of the DDB in said master node;

means employed by said master node, responsive to said polling received from said third node after recovery of said third node, for sending said most current one of said version numbers to said third node; and

means for updating the DDB in said third node if said most current one of said version numbers does not match the version number of said DDB in said third node.

11. The system of claim 10 and wherein said third node DDB updating means includes means for handshaking between said master node and said third node.

12. The system of claim 9 and wherein said conditions in which said master node is unknown to said third node include both said third node failing while it is being added to said configuration and said master node was replaced during time of failure of said third node.

13. The system of claim 12 and wherein said second means further comprises:

means, employed by said master node, for repetitively pinging said third node at predetermined intervals until said third node recovers and sends a recovery signal to said master node; and

,

said master node including means, responsive to said recovery signal, for updating the DDB in said third node as may be needed.

14. The system of claim 13 and wherein said third node DDB updating means includes means for handshaking between said master node and said third node.

15. The system of claim 6 and wherein said responding means further comprises:

means for handling said network link failing.

16. The system of claim 15 and wherein said network link failing handling means further comprises:

means for establishing version numbers to identify versions of said DDB in each of said plurality of nodes;

means, employed by each of said all other of said plurality of nodes, for continuously polling said master node at regular intervals to obtain the most current one of said version numbers of the DDB in said master node;

means employed by said master node, responsive to said polling received from said fourth node after recovery of said network link, for sending said most current one of said version numbers to said fourth node; and

,

means for updating the DDB in said fourth node if said most current one of said version numbers does not match the version number of said DDB in said fourth node.

17. The system of claim 16 and wherein said fourth node DDB updating means includes means for handshaking between said master node and said fourth node.

18. The system of claim 6 and wherein said responding means further comprises:

means for handling said adding a first node to said configuration.

19. The system of claim 18 and wherein said first node adding handling means comprises:

means for determining if said first node is being added through said master node to obtain a master-added node or through one of said all other of said plurality of nodes to obtain a portal-added node.

20. The system of claim 19 and wherein said determining means, for the condition of said master-added node, further comprises:

said master node including means for updating the DDB in said master node with the IP address of said first node and for informing said first node that the first node'"'"'s master is said master node;

said first node including means, responsive to operation of said informing means, for entering the IP address of said master node in the DDB of said first node and for acknowledging said master node; and

,

said master node including means for sending said IP address of said first node as an update to all other nodes in said configuration.

21. The system of claim 20 and wherein said IP address sending means further comprises:

means for performing a master to node handshake between said master node and said all other nodes in said configuration.

22. The system of claim 19 and wherein said determining means, for the condition of said portal-added node, further comprises:

a cache memory included in said portal node;

means for holding the IP address of said first node in said cache memory;

means for performing a node to master handshake between said first node and said master node;

said portal node including means for informing said master node of the IP address of said first node;

said master node including means for updating the DDB in said master node with the IP address of said first node and for informing said first node that the first node'"'"'s master is said master node;

said first node including means, responsive to operation of said informing means, for entering the IP address of said master node in the DDB of said first node and for acknowledging said master node; and

,

said master node including means for sending said IP address of said first node as an update to all other nodes in said configuration.

23. The system of claim 22 and wherein said IP address sending means further comprises:

means for performing a master to node handshake between said master node and said all other nodes in said configuration.

24. The system of claim 7 and wherein said responding means further comprises:

means for handling said deleting a second node from said plurality of nodes.

25. The system of claim 24 and wherein said second node deleting handling means further comprises:

means, utilizing said graphical user interface, for removing said second node from said configuration;

means for determining if said second node is removed through said master node;

means, responsive to operation of said determining means removing said second node through said master node, for;

(1) updating the DDB in said master node by removing the IP address of said second node from the DDB of said master node;

(2) informing said second node that said configuration no longer includes said second node and detaching said second node from said configuration;

(3) erasing all contents of the DDB of said second node; and

,

(4) sending an update to all remaining nodes in said configuration.

26. The system of claim 25 and wherein said update sending means further comprises:

means for performing a master to node handshake between said master node and said all remaining nodes in said configuration.

27. The system of claim 24 and wherein said second node deleting handling means further comprises:

means, utilizing said graphical user interface, for removing said second node from said configuration;

means for selecting a portal-removal node other than said master node through which to remove said second node from said configuration;

a cache memory included in said portal-removal node;

means for determining if said second node is removed through said master node;

means, responsive to operation of said determining means removing said second node through said portal-removal node and not through said master node, for;

(1) storing the IP address of said second node in said cache;

(2) performing a node to master handshake between said portal-removal node and said master node;

(3) informing said master node to remove the IP address of said second node from the DDB of said master node;

(4) updating the DDB in said master node by removing the IP address of said second node from the DDB of said master node;

(5) informing said second node that said configuration no longer includes said second node and detaching said second node from said configuration;

(6) erasing all contents of the DDB of said second node; and

,

(7) sending an update to all remaining nodes in said configuration.

28. The system of claim 27 and wherein said update sending means further comprises:

means for performing a master to node handshake between said master node and said all remaining nodes in said configuration.

29. The system of claim 21 or 23 and wherein said master to node handshake performing means comprises for each one of said all other nodes in said configuration:

first deciding means for deciding if the IP address of said master node in said update matches the IP address of said master node contained in the DDB of said each one of said all other nodes in said configuration;

means, responsive to operation of said first deciding means deciding no match, for rejecting said update and logging said event;

second deciding means, responsive to operation of said first deciding means deciding a match, for deciding if the version number of the DDB in said master node before said update matches the version number of said DDB of said each one of said all other nodes in said configuration before said update;

means, responsive to operation of said second deciding means deciding no match, for accepting a completely updated DDB with updated version number from said master node; and

,

means, responsive to operation of said second deciding means deciding a match, for accepting only said update with said updated version number from said master node.

30. The system of claim 26 or 28 and wherein said master to node handshake performing means comprises for each one of said all remaining nodes in said configuration:

first deciding means for deciding if the IP address of said master node in said update matches the IP address of said master node contained in the DDB of said each one of said all remaining nodes in said configuration;

means, responsive to operation of said first deciding means deciding no match, for rejecting said update and logging said event;

second deciding means, responsive to operation of said first deciding means deciding a match, for deciding if the version number of the DDB in said master node before said update matches the version number of said DDB of said each one of said all remaining nodes in said configuration;

means, responsive to operation of said second deciding means deciding no match, for accepting a completely updated DDB with updated version number from said master node; and

,

means, responsive to operation of said second deciding means deciding a match, for accepting only said update with said updated version number from said master node.

31. A computer program product for use in a computer network having a plurality of nodes for interacting with computer network information including both computer data and domain configuration status, said computer program product including a computer usable medium having computer readable program code thereon for managing said plurality of nodes, said program code comprising:

program code for establishing a DDB in each of said nodes;

program code for controlling contents of each said DDB to be identical to contents of every other said DDB and in manner to avoid a single point of failure;

wherein said contents controlling program code further comprises;

program code for maintaining the most current of said domain configuration status in said DDB in said each of said nodes;

program code for selecting one of said plurality of nodes as a master node;

program code for subordinating all other of said plurality of nodes to said master node in a configuration defined by said master node and said all other of said plurality of nodes; and

,

wherein said master node includes program code for responding to a change to said domain configuration status in a manner to maintain said contents of said each said DDB identical to said contents of said every other said DDB.

32. The computer program product of claim 31 and wherein:

said each of said nodes has a unique IP address; and

,

said DDB establishing program code further comprises;

program code for associating each said unique IP address with its respective node to provide an IP-address-respective-node association;

program code for combining said association for said each of said nodes into a network IP association; and

,

program code for distributing said network IP association to said DDB in said each of said nodes.

33. The computer program product of claim 31 and wherein said interacting includes receiving, storing, modifying, and transmitting.

34. The computer program product of claim 31 and wherein said controlling program code further comprises:

program code for replacing said master node with another node if said master node fails.

35. The computer program product of claim 34 and wherein said master node replacing program code includes program code for replacing said master node with another node selected from said configuration.

36. The computer program product of claim 31 and wherein said change to said domain configuration status is selected from the group of changes consisting of:

adding a first node to said configuration;

deleting a second node from said configuration;

a third node failing in said configuration; and

, a network link failing between a fourth node in said configuration and said master node.

37. The computer program product of claim 36 and wherein said computer network is a client-server network having a graphical user interface and wherein said selecting program code further comprises:

program code, utilizing said graphical user interface, for invoking a select master dialog by which said user can select said one of said plurality of nodes.

38. The computer program product of claim 34 and wherein said computer network is a client-server network having a graphical user interface and wherein said replacing program code further comprises:

program code, utilizing said graphical user interface, for invoking a select master dialog by which said user can select said another node.

39. The computer program product of claim 36 and wherein said responding program code further comprises:

first program code for handling said third node failing under conditions in which said master node is known to said third node; and

,

second program code for handling said third node failing under conditions in which said master node is unknown to said third node.

40. The computer program product of claim 39 and wherein said first program code further comprises:

program code for establishing version numbers to identify versions of said DDB in each of said plurality of nodes;

program code, employed by each of said all other of said plurality of nodes, for continuously polling said master node at regular intervals to obtain the most current one of said version numbers of the DDB in said master node;

program code employed by said master node, responsive to said polling received from said third node after recovery of said third node, for sending said most current one of said version numbers to said third node; and

program code for updating the DDB in said third node if said most current one of said version numbers does not match the version number of said DDB in said third node.

41. The computer program product of claim 40 and wherein said third node DDB updating program code includes program code for handshaking between said master node and said third node.

42. The computer program product of claim 39 and wherein said conditions in which said master node is unknown to said third node include both said third node failing while it is being added to said configuration and said master node was replaced during time of failure of said third node.

43. The computer program product of claim 42 and wherein said second program code further comprises:

program code, employed by said master node, for repetitively pinging said third node at predetermined intervals until said third node recovers and sends a recovery signal to said master node; and

,

said master node including program code, responsive to said recovery signal, for updating the DDB in said third node as may be needed.

44. The computer program product of claim 43 and wherein said third node DDB updating program code includes program code for handshaking between said master node and said third node.

45. The computer program product of claim 36 and wherein said responding program code further comprises:

program code for handling said network link failing.

46. The computer program product of claim 45 and wherein said network link failing handling program code further comprises:

program code for establishing version numbers to identify versions of said DDB in each of said plurality of nodes;

program code, employed by each of said all other of said plurality of nodes, for continuously polling said master node at regular intervals to obtain the most current one of said version numbers of the DDB in said master node;

program code employed by said master node, responsive to said polling received from said fourth node after recovery of said network link, for sending said most current one of said version numbers to said fourth node; and

,

program code for updating the DDB in said fourth node if said most current one of said version numbers does not match the version number of said DDB in said fourth node.

47. The computer program product of claim 46 and wherein said fourth node DDB updating program code includes program code for handshaking between said master node and said fourth node.

48. The computer program product of claim 36 and wherein said responding program code further comprises:

program code for handling said adding a first node to said configuration.

49. The computer program product of claim 48 and wherein said first node adding handling program code comprises:

program code for determining if said first node is being added through said master node to obtain a master-added node or through one of said all other of said plurality of nodes to obtain a portal-added node.

50. The computer program product of claim 49 and wherein said determining program code, for the condition of said master-added node, further comprises:

said master node including program code for updating the DDB in said master node with the IP address of said first node and for informing said first node that the first node'"'"'s master is said master node;

said first node including program code, responsive to operation of said informing program code, for entering the IP address of said master node in the DDB of said first node and for acknowledging said master node; and

,

said master node including program code for sending said IP address of said first node as an update to all other nodes in said configuration.

51. The computer program product of claim 50 and wherein said IP address sending program code further comprises:

program code for performing a master to node handshake between said master node and said all other nodes in said configuration.

52. The computer program product of claim 49 and wherein said determining program code, for the condition of said portal-added node, further comprises:

a cache memory included in said portal node;

program code for holding the IP address of said first node in said cache memory;

program code for performing a node to master handshake between said first node and said master node;

said portal node including program code for informing said master node of the IP address of said first node;

said master node including program code for updating the DDB in said master node with the IP address of said first node and for informing said first node that the first node'"'"'s master is said master node;

said first node including program code, responsive to operation of said informing program code, for entering the IP address of said master node in the DDB of said first node and for acknowledging said master node; and

,

said master node including program code for sending said IP address of said first node as an update to all other nodes in said configuration.

53. The computer program product of claim 52 and wherein said IP address sending program code further comprises:

program code for performing a master to node handshake between said master node and said all other nodes in said configuration.

54. The computer program product of claim 37 and wherein said responding program code further comprises:

program code for handling said deleting a second node from said plurality of nodes.

55. The computer program product of claim 54 and wherein said second node deleting handling program code further comprises:

program code, utilizing said graphical user interface, for removing said second node from said configuration;

program code for determining if said second node is removed through said master node;

program code, responsive to operation of said determining program code removing said second node through said master node, for;

(1) updating the DDB in said master node by removing the IP address of said second node from the DDB of said master node;

(2) informing said second node that said configuration no longer includes said second node and detaching said second node from said configuration;

(3) erasing all contents of the DDB of said second node; and

,

(4) sending an update to all remaining nodes in said configuration.

56. The computer program product of claim 55 and wherein said update sending program code further comprises:

program code for performing a master to node handshake between said master node and said all remaining nodes in said configuration.

57. The computer program product of claim 54 and wherein said second node deleting handling program code further comprises:

program code, utilizing said graphical user interface, for removing said second node from said configuration;

program code for selecting a portal-removal node other than said master node through which to remove said second node from said configuration;

a cache memory included in said portal-removal node;

program code for determining if said second node is removed through said master node;

program code, responsive to operation of said determining program code removing said second node through said portal-removal node and not through said master node, for;

(1) storing the IP address of said second node in said cache;

(2) performing a node to master handshake between said portal-removal node and said master node;

(3) informing said master node to remove the IP address of said second node from the DDB of said master node;

(4) updating the DDB in said master node by removing the IP address of said second node from the DDB of said master node;

(5) informing said second node that said configuration no longer includes said second node and detaching said second node from said configuration;

(6) erasing all contents of the DDB of said second node; and

,

(7) sending an update to all remaining nodes in said configuration.

58. The computer program product of claim 57 and wherein said update sending program code further comprises:

program code for performing a master to node handshake between said master node and said all remaining nodes in said configuration.

59. The computer program product of claim 51 or 53 and wherein said master to node handshake performing program code comprises for each one of said all other nodes in said configuration:

first deciding program code for deciding if the IP address of said master node in said update matches the IP address of said master node contained in the DDB of said each one of said all other nodes in said configuration;

program code, responsive to operation of said first deciding program code deciding no match, for rejecting said update and logging said event;

second deciding program code, responsive to operation of said first deciding program code deciding a match, for deciding if the version number of the DDB in said master node before said update matches the version number of said DDB of said each one of said all other nodes in said configuration before said update;

program code, responsive to operation of said second deciding program code deciding no match, for accepting a completely updated DDB with updated version number from said master node; and

,

program code, responsive to operation of said second deciding program code deciding a match, for accepting only said update with said updated version number from said master node.

60. The computer program product of claim 56 or 58 and wherein said master to node handshake performing program code comprises for each one of said all remaining nodes in said configuration:

first deciding program code for deciding if the IP address of said master node in said update matches the IP address of said master node contained in the DDB of said each one of said all remaining nodes in said configuration;

program code, responsive to operation of said first deciding program code deciding no match, for rejecting said update and logging said event;

second deciding program code, responsive to operation of said first deciding program code deciding a match, for deciding if the version number of the DDB in said master node before said update matches the version number of said DDB of said each one of said all remaining nodes in said configuration;

program code, responsive to operation of said second deciding program code deciding no match, for accepting a completely updated DDB with updated version number from said master node; and

,

program code, responsive to operation of said second deciding program code deciding a match, for accepting only said update with said updated version number from said master node.

61. In a computer network having a plurality of nodes for interacting with computer network information including both computer data and domain configuration status, a method for managing said plurality of nodes comprising:

establishing a DDB in each of said nodes;

controlling contents of each said DDB to be identical to contents of every other said DDB and in a manner to avoid a single point of failure;

wherein said contents controlling further comprises;

maintaining the most current of said domain configuration status in said DDB in said each of said nodes;

selecting one of said plurality of nodes as a master node;

subordinating all other of said plurality of nodes to said master node in a configuration defined by said master node and said all other of said plurality of nodes; and

,

said master node responding to a change to said domain configuration status in a manner to maintain said contents of said each said DDB identical to said contents of said every other said DDB.

62. The method of claim 61 and wherein:

said each of said nodes has a unique IP address; and

,

said DDB establishing further comprises;

associating each said unique IP address with its respective node to provide an IP-address-respective-node association;

combining said association for said each of said nodes into a network IP association; and

,

distributing said network IP association to said DDB in said each of said nodes.

63. The method of claim 62 and wherein said interacting includes receiving, storing, modifying, and transmitting.

64. The method of claim 62 and wherein said controlling further comprises:

replacing said master node with another node if said master node fails.

65. The method of claim 64 and wherein said master node replacing includes replacing said master node with another node selected from said configuration.

66. The method of claim 62 and wherein said change to said domain configuration status is selected from the group of changes consisting of:

adding a first node to said configuration;

deleting a second node from said configuration;

a third node failing in said configuration; and

, a network link failing between a fourth node in said configuration and said master node.

67. The method of claim 66 and wherein said computer network is a client-server network having a graphical user interface and wherein said selecting further comprises:

utilizing said graphical user interface to invoke a select master dialog by which said user can select said one of said plurality of nodes.

68. The method of claim 64 and wherein said computer network is a client-server network having a graphical user interface and wherein said replacing further comprises:

utilizing said graphical user interface to invoke a select master dialog by which said user can select said another node.

69. The method of claim 66 and wherein said responding further comprises:

first handling said third node failing under conditions in which said master node is known to said third node; and

,

second handling said third node failing under conditions in which said master node is unknown to said third node.

70. The method of claim 69 and wherein said first handling further comprises:

establishing version numbers to identify versions of said DDB in each of said plurality of nodes;

each of said all other of said plurality of nodes continuously polling said master node at regular intervals to obtain the most current one of said version numbers of the DDB in said master node;

said master node, responsive to said polling received from said third node after recovery of said third node, sending said most current one of said version numbers to said third node; and

updating the DDB in said third node if said most current one of said version numbers does not match the version number of said DDB in said third node.

71. The method of claim 70 and wherein said third node DDB updating includes handshaking between said master node and said third node.

72. The method of claim 69 and wherein said conditions under which said master node is unknown to said third node include both said third node failing while being added to said configuration and said master node being replaced during time of failure of said third node.

73. The method of claim 72 and wherein said second handling further comprises:

said master node repetitively pinging said third node at predetermined intervals until said third node recovers and sends a recovery signal to said master node; and

,

said master node, responsive to said recovery signal, updating the DDB in said third node as may be needed.

74. The method of claim 73 and wherein said third node DDB updating includes handshaking between said master node and said third node.

75. The method of claim 66 and wherein said responding further comprises:

handling said network link failing.

76. The method of claim 75 and wherein said network link failing handling further comprises:

establishing version numbers to identify versions of said DDB in each of said plurality of nodes;

each of said all other of said plurality of nodes continuously polling said master node at regular intervals to obtain the most current one of said version numbers of the DDB in said master node;

said master node, responsive to said polling received from said fourth node after recovery of said network link, sending said most current one of said version numbers to said fourth node; and

,

updating the DDB in said fourth node if said most current one of said version numbers does not match the version number of said DDB in said fourth node.

77. The method of claim 76 and wherein said fourth node DDB updating includes handshaking between said master node and said fourth node.

78. The method of claim 66 and wherein said responding further comprises:

handling said adding a first node to said configuration.

79. The method of claim 78 and wherein said first node adding handling comprises:

determining if said first node is being added through said master node to obtain a master-added node or through one of said all other of said plurality of nodes to obtain a portal-added node.

80. The method of claim 79 and wherein said determining, for the condition of said master-added node, further comprises:

said master node updating the DDB in said master node with the IP address of said first node and informing said first node that the first node'"'"'s master is said master node;

said first node, responsive to said informing, entering the IP address of said master node in the DDB of said first node and acknowledging said master node; and

,

said master node sending said IP address of said first node as an update to all other nodes in said configuration.

81. The method of claim 80 and wherein said IP address sending further comprises:

performing a master to node handshake between said master node and said all other nodes in said configuration.

82. The method of claim 79 for the condition of said portal-added node, and wherein said portal-added node includes a cache memory, said determining further comprising:

holding the IP address of said first node in said cache memory;

performing a node to master handshake between said first node and said master node;

said portal node informing said master node of the IP address of said first node;

said master node updating the DDB in said master node with the IP address of said first node and informing said first node that the first node'"'"'s master is said master node;

said first node, responsive to said informing, entering the IP address of said master node in the DDB of said first node and acknowledging said master node; and

,

said master node sending said IP address of said first node as an update to all other nodes in said configuration.

83. The method of claim 82 and wherein said IP address sending further comprises:

performing a master to node handshake between said master node and said all other nodes in said configuration.

84. The method of claim 67 and wherein said responding further comprises:

handling said deleting a second node from said plurality of nodes.

85. The method of claim 84 and wherein said second node deleting handling further comprises:

utilizing said graphical user interface to remove said second node from said configuration;

determining if said second node is removed through said master node;

said determining, responsive to said utilizing removing said second node through said master node, for;

(1) updating the DDB in said master node by removing the IP address of said second node from the DDB of said master node;

(2) informing said second node that said configuration no longer includes said second node and detaching said second node from said configuration;

(3) erasing all contents of the DDB of said second node; and

,

(4) sending an update to all remaining nodes in said configuration.

86. The method of claim 85 and wherein said update sending further comprises:

performing a master to node handshake between said master node and said all remaining nodes in said configuration.

87. The method of claim 84 and wherein said second node deleting handling further comprises:

utilizing said graphical user interface to remove said second node from said configuration;

selecting a portal-removal node other than said master node through which to remove said second node from said configuration;

establishing a cache memory in said portal-removal node;

determining if said second node is removed through said master node;

said determining, responsive to said utilizing removing said second node through said portal-removal node and not through said master node;

(1) storing the IP address of said second node in said cache;

(2) performing a node to master handshake between said portal-removal node and said master node;

(3) informing said master node to remove the IP address of said second node from the DDB of said master node;

(4) updating the DDB in said master node by removing the IP address of said second node from the DDB of said master node;

(5) informing said second node that said configuration no longer includes said second node and detaching said second node from said configuration;

(6) erasing all contents of the DDB of said second node; and

,

(7) sending an update to all remaining nodes in said configuration.

88. The method of claim 87 and wherein said update sending further comprises:

performing a master to node handshake between said master node and said all remaining nodes in said configuration.

89. The method of claim 81, 83, 86, or 88 and wherein said master to node handshake performing comprises for each one of said all other nodes in said configuration:

deciding if the IP address of said master node in said update matches the IP address of said master node contained in the DDB of said each one of said all other nodes in said configuration;

if no IP address match, rejecting said update and logging said event;

if an IP address match, deciding if the version number of the DDB in said master node before said update matches the version number in the DDB of said each one of said all other nodes in said configuration before said update;

if no version number match, accepting a completely updated DDB with updated version number from said master node; and

,

if a version number match, accepting only said update with said updated version number from said master node.