Resolving multiple master node conflict in a DDB

Electrical computers and digital processing systems: multicomput – Computer network managing – Computer network monitoring

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C709S223000

Reexamination Certificate

active

09964977

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 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. A global administrator is a privileged user compared to other computer network users who has authority to replace or select 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. Only one master node per domain is permitted and if the password-protected global administrator's security is breached, other users may select other master nodes for the same network resulting in master to master conflict. In the case of multiple master nodes attempting to be master for the same nodes in the same network at the same time, this conflict is resolved in one embodiment of the present invention by allowing the most recently selected purported master node to be the actual master node. This resolution is obtained in a manner that avoids a single point of failure. After resolution of this conflict the result is communicated by the prevailing master node to all nodes in the network. This resolution takes into account a global network with varying time zones, and further takes into account the remote possibility of a simultaneous appointment of two masters.

REFERENCES:
patent: 5289176 (1994-02-01), Novakovich et al.
patent: 5313465 (1994-05-01), Perlman et al.
patent: 5511188 (1996-04-01), Pascucci et al.
patent: 5608903 (1997-03-01), Prasad et al.
patent: 5708812 (1998-01-01), Van Dyke et al.
patent: 5768519 (1998-06-01), Swift et al.
patent: 5805072 (1998-09-01), Kakemizu
patent: 5805785 (1998-09-01), Dias et al.
patent: 5805786 (1998-09-01), Badovinatz et al.
patent: 5844900 (1998-12-01), Hong et al.
patent: 5968121 (1999-10-01), Logan et al.
patent: 5974429 (1999-10-01), Strub et al.
patent: 5987011 (1999-11-01), Toh
patent: 6061600 (2000-05-01), Ying
patent: 6081898 (2000-06-01), Miller et al.
patent: 6092214 (2000-07-01), Quoc et al.
patent: 6115713 (2000-09-01), Pascucci et al.
patent: 6181689 (2001-01-01), Choung et al.
patent: 6199169 (2001-03-01), Voth
patent: 6243826 (2001-06-01), Quoc et al.
patent: 6292905 (2001-09-01), Wallach et al.
patent: 6295541 (2001-09-01), Bodnar et al.
patent: 6324571 (2001-11-01), Hacherl
patent: 6363416 (2002-03-01), Naeimi et al.
patent: 6381627 (2002-04-01), Kwan et al.
patent: 6450298 (2002-09-01), Koura et al.
patent: 6466608 (2002-10-01), Hong et al.
patent: 6611860 (2003-08-01), Ying
patent: 6636982 (2003-10-01), Rowlands
patent: 6665730 (2003-12-01), Michelson et al.
patent: 6680903 (2004-01-01), Moriguchi et al.
patent: 6691173 (2004-02-01), Morris et al.
patent: 6732202 (2004-05-01), Ying
patent: 6751634 (2004-06-01), Judd
patent: 6751719 (2004-06-01), Peloquin et al.
patent: 6823429 (2004-11-01), Olnowich
patent: 6829487 (2004-12-01), Eiden et al.
patent: 6877043 (2005-04-01), Mallory et al.
patent: 6915309 (2005-07-01), Conley et al.
patent: 6941350 (2005-09-01), Frazier et al.
patent: 7054910 (2006-05-01), Nordin et al.
patent: 7120690 (2006-10-01), Krishnan et al.
patent: 2002/0044549 (2002-04-01), Johansson et al.
patent: 2002/0080807 (2002-06-01), Lind
patent: 2003/0149735 (2003-08-01), Stark et al.
patent: 2005/0055418 (2005-03-01), Blanc et al.
patent: 2005/0063313 (2005-03-01), Nanavati et al.
patent: 2005/0102704 (2005-05-01), Prokupets et al.
patent: 2005/0114401 (2005-05-01), Conkel
patent: 2005/0163133 (2005-07-01), Hopkins
patent: 2005/0182942 (2005-08-01), Calin
patent: 2007/0081535 (2007-04-01), Li

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Resolving multiple master node conflict in a DDB does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Resolving multiple master node conflict in a DDB, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Resolving multiple master node conflict in a DDB will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-3785883

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.