US6564216B2 - Server manager - Google Patents
- ️Tue May 13 2003
US6564216B2 - Server manager - Google Patents
Server manager Download PDFInfo
-
Publication number
- US6564216B2 US6564216B2 US09/182,949 US18294998A US6564216B2 US 6564216 B2 US6564216 B2 US 6564216B2 US 18294998 A US18294998 A US 18294998A US 6564216 B2 US6564216 B2 US 6564216B2 Authority
- US
- United States Prior art keywords
- server
- network protocol
- server manager
- protocol address
- database Prior art date
- 1998-10-29 Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5076—Update or notification mechanisms, e.g. DynDNS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
Definitions
- the present invention relates to the field information networking and more specifically to transmitting configuration information between a central database and one or more servers in a network.
- FIG. 1 illustrates an overall diagram of a conventional Transmission Control Protocol (TCP)/Internet Protocol (IP) network 101 including one or more Domain Name Service (DNS) servers 102 A-N, one or more Dynamic Host Configuration Protocol (DHCP) servers 103 A-N and a central database 104 .
- TCP Transmission Control Protocol
- IP Internet Protocol
- DNS Domain Name Service
- DHCP Dynamic Host Configuration Protocol
- the one or more DNS servers 102 A-N and DHCP servers 103 A-N on the network transmit requests for configuration information and send configuration updates to the central database 104 .
- the central database 104 either transmits the requested configuration information back to each server or it stores the configuration updates received from each server.
- DHCP simplified the management and assignment of IP addresses to clients by eliminating the need for the network administrator to manually configure the network.
- DCHP when a client requests an IP address in order to communicate over the network, a DHCP server answers the request by providing network configuration information that was obtained from a database and dynamically assigning an IP address to the client.
- Each DHCP server manages a range of client addresses and can pick any address from that range as long as it is not being used by a another client managed by that DHCP server. Since the address is dynamically assigned, the client can have a different IP address each time it logs on to the network.
- a DHCP server also supports static IP address that have been assigned to one particular client on the network. Based on the configuration information received from the database, the DHCP server can automatically assign a specific IP address to a specific client.
- DNS also simplified the management of networks by translating domain names into IP addresses. Since the DNS server contains a list of domain names and their associated IP addresses, a host or client can be located through by its domain name rather than its IP address. Any given domain name could be associated with more than one IP address and any IP address could be associated with more than one domain name.
- a DNS server updates the domain name and IP address associations by periodically polling a central database containing configuration information for the network. When a new client is assigned an IP address by a DHCP server, the new configuration information is stored in the central database. Each DNS servers on the network poll the central database for configuration changes. If a new IP address was assigned to a client managed by a DNS server, the DNS server updates the domain name with the new IP address or updates the IP address with the new domain name. 2
- a server manager acts as an interface between the one or more servers and the central database.
- the server manager also synchronizes requests for configuration information and configuration updates from the one or more servers and transmits the requests and updates to the central database through a single communication channel.
- the server manager receives the configuration information from the central database and sends the information to the servers that issued the requests.
- the server manager also transmits the configuration updates from the one or more servers to the central database.
- the server manager polls the central database for any changes in configuration made to the network. If the server manager finds any changes stored in the central database, it transmits the changes to the appropriate servers.
- the server manager also processes multiple requests at one time and queues up any further requests based on the priority of the work requested or the order in which they were received.
- FIGS. 1A-1B are an overall diagram of a conventional TCP/IP network.
- FIG. 2 is an overall diagram of a TCP/IP network as may implement the present invention.
- FIG. 3 is a flow diagram illustrating the steps for a server to server manager login process as may be utilized by an embodiment of the present invention.
- FIG. 4 is a flow diagram illustrating a method for communicating configuration information from the central database to a DHCP server through the server manager as may be utilized by an embodiment of the present invention.
- FIG. 5 is a flow diagram illustrating a method for communicating configuration updates from the central database to a DNS server as may be utilized by an embodiment of the present invention.
- FIG. 6 is a flow diagram illustrating a method for retrieving any configuration changes in the network from the delta-logging facility in the central database and transmitting them to the servers on the network as may be utilized by an embodiment of the present invention.
- FIG. 7 is a flow diagram illustrating a method for determining the operational status of the DNS and DHCP servers on the network and transmitting the status information to the NMS as may be utilized by an embodiment of the present invention.
- FIG. 8 is a flow diagram illustrating a method for authenticating a user and binding the user to the IP address dynamically assigned to it by a DHCP server as may be utilized by an embodiment of the present invention.
- reference numerals in all of the accompanying drawings typically are in the form “drawing number” followed by two digits, xx; for example, reference numerals on FIG. 1 may be numbered 1xx; on FIG. 3, reference numerals may be numbered 3xx.
- FIG. 2 illustrates a TCP/IP network configured in accordance with the methods and apparatus discussed herein.
- the network can contain a plurality of servers that must access the central database in order to obtain configuration information.
- a server manager can be introduced. The server manager would communicate directly with the plurality of servers and the central database and transmit any requests from the servers to the central database. Therefore, the central database only would need to communicate with the server manager. As will be discussed, this reduces the number of requests which must be managed by the central database.
- IP addressing is integrated with DNS and DHCP management. All configuration changes, whether made statically, dynamically or at remote locations, are registered in the central database and automatically distributed to the appropriate servers. Also, DHCP redundancy guarantees that a DHCP server is always serving a given range of client addresses. Primary and backup DHCP servers serve the same address range which ensures that DHCP clients in the range can always acquire an IP address. Internet Service Providers (ISP) can benefit from the present invention because management of IP address space is simplified.
- ISP Internet Service Providers
- DHCP servers can act as both DHCP and Bootstrap Protocol (BootP) servers which enables ISPs to integrate the static allocation of IP addresses to cable modems through BootP with the dynamic allocation of IP addresses to end users through DHCP.
- the present invention also will be of great importance in such applications as Voice/Fax Over IP and Policy-Enabled Networking where a user needs an authenticated address to access network services.
- the network includes a server manager 201 , one or more DNS servers 202 A-N, one or more DHCP servers 203 A-N, a central database 204 , a NMS 205 , one or more clients 208 , a Lightweight Directory Access Protocol (LDAP) server 209 and a LDAP database 210 .
- the one or more DNS servers 202 A-N and DHCP servers 203 A-N are coupled in communication with the server manager 201 through individual communication channels.
- the server manager 201 is coupled in communication with the central database 204 over a single communication channel 206 and the NMS 205 over a single communication channel 207 .
- the LDAP server 209 is coupled in communication with the server manager 201 over a single communication channel 211 .
- the LDAP server 209 can communicate directly with the central database 204 .
- the central database 204 may be any number of conventional databases. In the described embodiment, either a Sybase 7.3 or 8.0, available from Sybase, Inc. of Emeryville, Calif. or Oracle 11.x database, available from Oracle Corporation of Redwood Shores, Calif., is utilized to store network configuration information.
- the configuration information may include DNS and DHCP parameters, other server parameters, IP addresses, domain names, the operational status of servers that have successfully logged in to the network and the like.
- the central database 204 is relational and stores changes in configuration made to the network. Because the central database 204 is relational, it can log any configuration changes in a separate area. For purposes of this disclosure, the section of the central database 204 that contains the log of changes in configuration will be referred to as the delta-logging facility.
- the server manager 201 can restore the central database 204 to a previously known state. For example, if the central database becomes corrupted, the server manager can search the delta logging facility for the configuration information of a previously known uncorrupted state.
- the one or more DNS servers 202 A-N are Berkeley Internet Name Domain (BIND) 4.9.5 DNS servers, BIND 8.1.1 DNS servers or the like. These servers 202 A-N communicate with the central database 204 through the server manager 201 . Each DNS server is coupled to the server manager 201 through a TCP link. The TCP links from the servers 202 A-N to the server manager 201 enable dynamic DNS updates and dynamic DNS reconfiguration.
- the one or more DHCP servers 203 A-N are based on the BootP. These servers 203 A-N also communicate with the server manager 201 through a TCP link and update the central database 204 with changes in DHCP configuration.
- the ability of the DHCP servers to update the central database with configuration changes enables incremental synchronization of DNS and DHCP services.
- the servers that can be linked to the server manager are not limited to DNS and DHCP servers.
- a similar configuration could be used to support Remote Access Dial In User Services (RADIUS), Policy and future servers through the use of protocol server plug-in technology.
- RADIUS Remote Access Dial In User Services
- the server manager 201 , DNS 202 A-N and DHCP 203 A-N servers described in the embodiment may, for example, run on the operating systems and hardware platforms given in Table 1.
- the DNS servers 202 A-N and DHCP servers 203 A-N must first login with the server manager 201 . If the login process is successful, the servers 202 A-N, 203 A-N must set their server id in able to issue command and requests to the server manager 201 for processing.
- the following sections describe how the servers 202 A-N, 203 A-N complete the login process and how they communicate with the server manager 201 . It should be appreciated that the methods described can be performed in other ways without departure from the scope of the present invention.
- FIG. 3 provides a flow diagram illustrating steps utilized in the described embodiment for a server to server manager login process.
- the login process is not unique to one type of server and can be used by any server attempting to establish a communication channel with the server manger 201 .
- the one or more DNS servers 202 A-N and DHCP servers 203 A-N establish a TCP link to the server manager 201 , step 301 .
- each server 202 A-N, 203 A-N issues a login request by providing a userid and a password to the server manager 201 , step 302 .
- the password for each server 202 A-N, 203 A-N is only known by each individual server and the server manager 201 .
- the server manager 201 validates the userid and password by using MD 5 , which is described in detail in Rivest, R., “The MD5 Message-Digest Algorithm,” Networking Group Request For Comments (RFC) 1331, April 1992, to compute a digest value, step 303 . If the password is correct, the server, for example a DNS server 202 A, is logged in to the server manager 201 , step 305 . If the password is incorrect, the login fails and the server manager 201 drops the TCP link, step 304 . In order to retry the login sequence, the server 202 A must reinitiate a TCP link to the server manager 201 and start the login process from the beginning, step 301 .
- each DNS server 202 A-N and DHCP server 203 A-N After logging in with the server manager 201 , each DNS server 202 A-N and DHCP server 203 A-N must set their server-id, step 306 . Each server-id is checked against all of the DNS and DHCP servers already coupled in communication with the server manager 201 , step 307 . If the server-id is the same as a server-id for a server already on the network, the TCP link for the requesting server will be dropped, step 308 . If the server-id is unique to that server, the login process is complete, step 309 .
- the servers can issue requests for configuration information from the central database 204 or send updated configuration information to the central database 204 .
- the server manager 201 synchronizes all of the requests and updates from the servers and transmits them to the central database 204 .
- the server manager 201 monitors all the DNS servers 202 A-N and DHCP servers 203 A-N on the network from a single point and acts as a single pipeline to the central database 204 .
- the DHCP server 203 A determines if it can send configuration information to the requesting client 208 . If the DHCP server 203 A can give an IP address and configuration information to the client 208 , it sends host configuration information and an IP address to the client 208 . The DHCP server 203 A automatically registers the new domain name, the IP address and the host configuration information with the central database 204 through the server manager 201 . The DNS server 202 A detects the new IP address through the server manager and updates its DNS information.
- the DHCP server 203 A When the lease expires or the client 208 leaves the network and releases the IP address, the DHCP server 203 A notifies the central database 204 of the change through the server manager 201 .
- the IP address is available for reassignment by the DHCP server 203 A to a new client. Therefore, the server manager 201 eliminates the need for the individual DNS servers 202 A-N and DHCP servers 203 A-N to establish direct communication channels with the central database by providing access to the central database 204 through one communication channel 206 . (more????)
- the described embodiment utilizes plug-in technology in order to allow support for current as well as future generation servers.
- the DHCP server plug-in has three functions: (1) Provides configuration information to the DHCP servers linked to the network; (2) Informs the DHCP servers of any relevant changes in the central database; and (3) Transacts the DHCP hosts into the central database.
- FIG. 4 provides a flow diagram which is useful for describing a method of the described embodiment for transmitting configuration information from the central database 204 to a DHCP server 203 A.
- the server manger 201 receives a request for configuration information from a DHCP server 203 A, step 401 , it checks to see if the server-id is zero, step 402 . If the server-id is zero, the message is ignored, step 403 . 6 Otherwise, the server manager 201 initiates a process to retrieve configuration information from the central database 204 .
- the server manager 201 first receives information, such as range and host lists, from the DHCP server 203 A, step 404 .
- the server manager 201 then requests the configuration information from the central database 204 based on the lists provided by the DHCP server 203 A and the lists it created, step 407 .
- the central database 204 transmits configuration information requested by the server manager 201 , step 408 , and this information is sent to the DHCP server 203 A requesting the configuration information, step 409 .
- the configuration information can consist of (1) the global options for the network, which is sent to the requesting server and the backup server serving the same address ranges, if DHCP redundancy is supported, (2) the network options for each network contained in the network list that was created by the server manager, (3) the subnet options for each subnet contained in the subnet list, (4) the range options for each range contained in the range list and (5) the host options for each host contained in the host list.
- a benefit of processing all requests for configuration information from the central database 204 by the DHCP servers 203 A-N in the server manager 201 is that the load on the central database 204 is reduced.
- the server manager 204 eliminates the active link between every DHCP server 203 A-N that needs configuration information from the central database 204 .
- the server manager 201 also notifies each DHCP server 203 A-N of any changes to the central database 201 .
- the server manager 201 polls the delta-logging facility in the central database 204 for configuration changes made to the network that would effect the DHCP servers 203 A-N coupled in communication with the server manager 201 .
- the interval in between polling can be either a default value or a value set by a user such as the network administrator. In the described embodiment, the interval between each time the server manager 201 polls the central database 204 for configuration changes is 60 seconds.
- FIG. 5 provides a flow diagram which illustrates a method of the described embodiment for retrieving any changes in configuration made to the network from the delta-logging facility in the central database 204 and transmitting them to the DHCP 203 A-N servers coupled in communication with the server manager 201 .
- the server manager 201 queries the delta-logging facility in the central database 204 , step 501 , to determine if there were any configuration changes, step 502 . If there were changes in configuration, the server manager 201 issues a request to the central database 204 for the global range information, the network information, the global client pool and each client pool and client pool entry managed by the DHCP servers 203 A-N, step 503 .
- the server manager 201 retrieves the appropriate information, step 504 and distributes it to the appropriate DHCP 203 A-N servers. 9 If the server manager 201 finds no changes or has completed distributing the changes to the DHCP server 203 A-N, it waits the set interval of time and polls the delta-logging facility again for changes, step 501 .
- a benefit of only allowing the server manger 201 to pool the delta-logging facility for changes in configuration is that the load on the network is reduced. The reduced load and reduced amount of traffic to the database increases the overall performance of the network because the server manager 201 automatically determines which DHCP servers 203 A-N are effected by the changes. This eliminates update requests from DHCP servers that are not affected by the configuration changes made to the network.
- the server manager 201 also processes host commit requests from DHCP servers 203 A-N. 10
- the server manager 201 In order to add host information to the central database 204 , the server manager 201 must determine if the domain name is available, unavailable, moving from another host or being updated.
- the server manager 201 Upon receiving a request from a DHCP server 203 A to add a host, the server manager 201 first checks if the domain is a Canonical Name (CNAME) or primary name. If the domain is a CNAME, it fails validation and the server manager 201 notifies the DHCP server 203 A that the domain is unavailable. 11 If the domain does not exist in the central database 204 , the label 12 may be assigned to the host and the server manager 201 notifies the DHCP server 203 A that the domain is available.
- CNAME Canonical Name
- the label may be assigned to the requesting host and the server manager notifies the DHCP server 203 A that the domain is available. If the host in the central database 204 is static, the label can't be used and the server manager 201 notifies the DHCP server 203 A that the domain is unavailable. If the IP addresses match, the label is updated and the server manager 201 notifies the DHCP server 203 A that the domain has been updated. If the IP addresses do not match, the label is moved to the requesting host and the server manager 201 notifies the DHCP server 203 A that the domain has been moved.
- the server manager 201 notifies the DHCP server 203 A that the domain is unavailable. If the server manager 201 determines that the domain name is available, the server manager adds the new host to the network by (1) setting the host IP address; (2) assigning a client-id to the host; (3) setting the hardware address; (4) setting the DHCP server-id; (5) assigning a lease expire time; and (7) determining a domain name. 13 The server manager 201 will then validate all of the above information. If the validation fails, the server manager 201 notifies the DHCP server 203 A that the host commit failed, otherwise the server manager 201 notifies the DHCP server 203 A that the host has been committed and transmits the host information to the central database 204 .
- the DNS server's plug-in has two functions: (1) Provides format configuration information to the both the BIND 4.9.5 DNS servers and the BIND 8.1.1 DNS servers; and (2) Informs them of the relevant changes in the central database.
- FIG. 6 provides a flow diagram which is useful for describing a method of the described embodiment for communicating configuration updates from the central database 201 to a DNS server 202 A. 14
- the server manager 201 receives a configuration update message from a DNS server 202 A, step 601 , it checks to see if the server id is valid, step 602 . If the server-id is NULL, the message is ignored, step 603 .
- the server manager 201 receives the primary and secondary zones managed by the DNS server 202 A, step 604 .
- the server manager 201 then issues a configuration update request for each zone managed by the DNS server 202 A to the central database 204 , step 605 .
- the central database 204 transmits the configuration information for each zone to the sever manager 201 , step 606 .
- the server manager 201 then transmits the updated configuration information to the DNS server, step 607 .
- the server manger 201 For each primary forward zone, the server manger 201 sends the Start of Authority (SOA) record, name servers of the zone, the A record, 15 RR record, option record, CNAME record and the glue record with the subzones to the DNS server 202 A. 16 For each primary reverse zone, the server manager 201 sends the SOA record, name servers of the zone, the PTR record for each subdomain of the zone and the glue record with the subzones to the DNS server 202 A. For each secondary zone, the server manager 201 sends that zone transfer list to the DNS server 202 A. Finally, the server manager 201 sends information about the root server on the network to the DNS server 202 A. 17
- SOA Start of Authority
- the server manager 201 also polls the delta-logging facility in the central database 204 periodically to determine if there were any changes in configuration made to the network that would effect the DNS servers 202 A-N.
- the process of polling the delta-logging facility in the central database 204 for the DNS servers 202 A-N is similar to the process previously described in FIG. 5 for the DHCP servers 203 A-N.
- the server manager 201 requests the primary and secondary zone information, the primary forward and reverse zone information, the subzone information for each subzone not managed by a DNS server and the subdomain of one of the primary zones managed by the DNS server. Once the server manager 201 retrieves this information, it transmits the relevant information to the appropriate DNS servers 203 A-N.
- This method has a similar benefit, as described above in the DHCP section, in that DNS servers that are not effected by the configuration changes will not be polling the central database 204 for changes since the only server manager 201 is coupled in communication with the central database 204 .
- the server manager 201 can process multiple requests or commands at the same time. However, the number of requests or updates that the server manager 201 can process at the same time is determined by the machine that it is running on. Therefore, the server manager 201 , as used by the described embodiment, prioritizes what it processes based on the type of work requested.
- the server manager 201 services the requests and updates in the following order: (1) get configuration requests from the DCHP servers; (2) polling the central database for any configuration changes in the network; (3) configuration update requests from the DNS servers; and (4) removing leases for IP addresses when they expire. 19 Prioritizing based on the type of work requested is not the only method available for the server manager 201 to process information. It could also process the information based on a first-in first-out method. For example, the first request or packet of information received by the server manager 201 would be processed first and the last request or packet of information received by the server would be processed last.
- the server manager 201 also has the ability to actively manage the DNS 202 A to 202 N and DHCP 203 A-N servers and report their operational status to the NMS 205 .
- the NMS 205 communicates with an agent, the server manager 201 , to keep track of the network statistics and resources. Network administrators can use the NMS 205 to view the real-time operating status of the DNS 202 A-N and DHCP 203 A-N servers that are linked with the server manager 201 .
- the NMS 205 could be a graphical user interface (GUI) running on a powerful computer such as a workstation.
- GUI graphical user interface
- the server manager 201 polls the servers every 40 seconds to determine if the server is still running or if it has stopped, step 701 . 20 The server generates an alarm or warning to indicate its operating status and communicates the message to the server manager 201 , step 702 .
- the message could contain information such as a key word to trigger the correct plug-in, the severity of the alarm, the specific server-id, and an alarm code to indicate the problem.
- the server manager 201 queues up the reports from the servers along with any other requests that it receives and attaches a database time stamp to each one.
- the server manager 201 then communicates the alarms to the central database 204 and to the NMS 205 , step 703 .
- the alarms are sent to the NMS 205 through a Simple Network Management Protocol (SNMP) trap.
- the traps could contain information such as setting the server status to up when the server successfully establishes a TCP link with the server manager 201 , setting the server status to down when the TCP link between the server and the server manager is dropped and setting the server status to failed login when the server successfully establishes a TCP link with the server manager 201 but tried an invalid login.
- the advantage to using the server manager 201 for active server management is that the server manager 201 can detect when a server has crashed. In some embodiments, multiple servers are running on the same hardware. If the hardware is still running but one of the servers has crashed, the server manager 201 can detect the change through the TCP link which will be dropped if the server crashes. When the TCP link is started or dropped, the server manager 201 generates an exception, such as the described SNMP traps, to the NMS 205 . Therefore, the network administrator is able to determine if a server has gone down if the hardware is still operational.
- FIG. 8 provides a flow diagram which illustrates a method of the described embodiment for authenticating a user and binding the user to their current address.
- a client 208 requests an IP address from the DHCP server 203 N on the network, step 801 .
- the DHCP server 203 N dynamically assigns the client 208 an IP address before it has been authenticated, step 802 .
- the client 208 then issues a registration request with the binding server 209 and communicates its userid, password and the IP address it just obtained from the DHCP server 203 N to the binding server 209 , step 803 .
- the method of communication used by the client in the described embodiment is the Hyper Text Transfer Protocol (HTTP) but alternative methods can be used.
- HTTP Hyper Text Transfer Protocol
- the client does not provide itself with a userid or password.
- two examples of methods for the client to obtain its userid and password are to have the user go to a World Wide Web (WWW) page or download a Java applet to obtain information from a PC or workstation which could modify the operating system to automatically provide it.
- the binding server 209 then authenticates the userid, password and IP address through an LDAP request to the LDAP database 210 , step 804 .
- the LDAP request searches the LDAP database 210 for the userid, password and the possible IP addresses that the DHCP server 203 N could assign, step 805 .
- the LDAP database 210 is organized in a tree hierarchy. For example, the root of an Internet address is at the top and the common name associated with the user is at the bottom.
- the LDAP database 210 is accessible through an open, standards based protocol such as TCP. If the information is found in the LDAP database 210 , it notifies the binding server 209 that the user credentials were verified by returning the authenticated credentials, step 807 . 22
- the binding server 209 then sends the authenticated credentials to be stored in the central database 204 , step 808 .
- the binding server 209 communicates with the server manager 201 over a single channel 211 to store the credentials in the central database 204 .
- the binding server 209 could also communicate directly or through some other device with the central database 204 in order to store the authenticated credentials.
- the present invention as utilized in the described embodiment authenticates the actual userid/password and address combination.
- Applications such as Voice/Fax over IP and Video Conferencing can benefit from the present invention because routing and bandwidth considerations are based on source and destination addresses. Therefore, deciding which users can access the network services requires authenticated addresses.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A method and apparatus for managing IP addressing in a network and effectively synchronizing communication between a central database and one or more servers (such as DNS and DHCP).
Description
1. Field of the Invention
The present invention relates to the field information networking and more specifically to transmitting configuration information between a central database and one or more servers in a network.
2. Description of the Related Art
In a typical network, a server directly communicates with the central database in order to obtain configuration information. FIG. 1 illustrates an overall diagram of a conventional Transmission Control Protocol (TCP)/Internet Protocol (IP)
network101 including one or more Domain Name Service (DNS)
servers102A-N, one or more Dynamic Host Configuration Protocol (DHCP)
servers103A-N and a
central database104. Typically, the one or
more DNS servers102A-N and
DHCP servers103A-N on the network transmit requests for configuration information and send configuration updates to the
central database104. The
central database104 either transmits the requested configuration information back to each server or it stores the configuration updates received from each server.
In the past, organizations relied on paper based methods of managing IP addresses in a network. DHCP simplified the management and assignment of IP addresses to clients by eliminating the need for the network administrator to manually configure the network. With DCHP, when a client requests an IP address in order to communicate over the network, a DHCP server answers the request by providing network configuration information that was obtained from a database and dynamically assigning an IP address to the client. Each DHCP server manages a range of client addresses and can pick any address from that range as long as it is not being used by a another client managed by that DHCP server. Since the address is dynamically assigned, the client can have a different IP address each time it logs on to the network. Along with the ability to dynamically assign IP addresses, a DHCP server also supports static IP address that have been assigned to one particular client on the network. Based on the configuration information received from the database, the DHCP server can automatically assign a specific IP address to a specific client.1
DNS also simplified the management of networks by translating domain names into IP addresses. Since the DNS server contains a list of domain names and their associated IP addresses, a host or client can be located through by its domain name rather than its IP address. Any given domain name could be associated with more than one IP address and any IP address could be associated with more than one domain name. A DNS server updates the domain name and IP address associations by periodically polling a central database containing configuration information for the network. When a new client is assigned an IP address by a DHCP server, the new configuration information is stored in the central database. Each DNS servers on the network poll the central database for configuration changes. If a new IP address was assigned to a client managed by a DNS server, the DNS server updates the domain name with the new IP address or updates the IP address with the new domain name.2
In mid-to large-scale networks, a significant number of transmissions between the
central database104 and the
DNS servers102A-N and
DHCP servers103A-N occur. Each
DNS server102A-N and DHCP
server103A-N must individually contact the
central database104 to obtain any configuration changes made to the network that were stored in the
central database104. If there are a large number of
DNS servers102A-N and
DHCP servers103A-N, for example 100, on the network, a bandwidth issue is created at the
central database104.
Therefore, it would be useful to provide an improved means of communicating between a database and one or more servers.
SUMMARY OF THE INVENTIONA method and apparatus for managing IP addressing in a network and effectively synchronizing communication between a central database and one or more servers (such as DNS and DHCP) is described. In one embodiment, a server manager acts as an interface between the one or more servers and the central database. The server manager also synchronizes requests for configuration information and configuration updates from the one or more servers and transmits the requests and updates to the central database through a single communication channel. The server manager then receives the configuration information from the central database and sends the information to the servers that issued the requests. The server manager also transmits the configuration updates from the one or more servers to the central database. Periodically, the server manager polls the central database for any changes in configuration made to the network. If the server manager finds any changes stored in the central database, it transmits the changes to the appropriate servers. The server manager also processes multiple requests at one time and queues up any further requests based on the priority of the work requested or the order in which they were received.
BRIEF DESCRIPTION OF THE DRAWINGSFIGS. 1A-1B are an overall diagram of a conventional TCP/IP network.
FIG. 2 is an overall diagram of a TCP/IP network as may implement the present invention.
FIG. 3 is a flow diagram illustrating the steps for a server to server manager login process as may be utilized by an embodiment of the present invention.
FIG. 4 is a flow diagram illustrating a method for communicating configuration information from the central database to a DHCP server through the server manager as may be utilized by an embodiment of the present invention.
FIG. 5 is a flow diagram illustrating a method for communicating configuration updates from the central database to a DNS server as may be utilized by an embodiment of the present invention.
FIG. 6 is a flow diagram illustrating a method for retrieving any configuration changes in the network from the delta-logging facility in the central database and transmitting them to the servers on the network as may be utilized by an embodiment of the present invention.
FIG. 7 is a flow diagram illustrating a method for determining the operational status of the DNS and DHCP servers on the network and transmitting the status information to the NMS as may be utilized by an embodiment of the present invention.
FIG. 8 is a flow diagram illustrating a method for authenticating a user and binding the user to the IP address dynamically assigned to it by a DHCP server as may be utilized by an embodiment of the present invention.
For ease of reference, it might be pointed out that reference numerals in all of the accompanying drawings typically are in the form “drawing number” followed by two digits, xx; for example, reference numerals on FIG. 1 may be numbered 1xx; on FIG. 3, reference numerals may be numbered 3xx.
DETAILED DESCRIPTION OF AN EMBODIMENT OF THE PRESENT INVENTIONFIG. 2 illustrates a TCP/IP network configured in accordance with the methods and apparatus discussed herein. Although described with reference to certain specific embodiments, those skilled in the art will recognize that the present invention may be practiced without some or all of these details and further, the present invention may be utilized in alternative networks. In one embodiment, the network can contain a plurality of servers that must access the central database in order to obtain configuration information. In order to reduce the number communication channels going to the central database, a server manager can be introduced. The server manager would communicate directly with the plurality of servers and the central database and transmit any requests from the servers to the central database. Therefore, the central database only would need to communicate with the server manager. As will be discussed, this reduces the number of requests which must be managed by the central database. In another embodiment of the invention, dynamic DNS updates are possible and IP addressing is integrated with DNS and DHCP management. All configuration changes, whether made statically, dynamically or at remote locations, are registered in the central database and automatically distributed to the appropriate servers. Also, DHCP redundancy guarantees that a DHCP server is always serving a given range of client addresses. Primary and backup DHCP servers serve the same address range which ensures that DHCP clients in the range can always acquire an IP address. Internet Service Providers (ISP) can benefit from the present invention because management of IP address space is simplified. DHCP servers can act as both DHCP and Bootstrap Protocol (BootP) servers which enables ISPs to integrate the static allocation of IP addresses to cable modems through BootP with the dynamic allocation of IP addresses to end users through DHCP. The present invention also will be of great importance in such applications as Voice/Fax Over IP and Policy-Enabled Networking where a user needs an authenticated address to access network services.
In the described embodiment, the network includes a
server manager201, one or
more DNS servers202A-N, one or
more DHCP servers203A-N, a
central database204, a NMS 205, one or
more clients208, a Lightweight Directory Access Protocol (LDAP)
server209 and a LDAP
database210. The one or
more DNS servers202A-N and
DHCP servers203A-N are coupled in communication with the
server manager201 through individual communication channels. The
server manager201 is coupled in communication with the
central database204 over a
single communication channel206 and the
NMS205 over a
single communication channel207. The
LDAP server209 is coupled in communication with the
server manager201 over a
single communication channel211. However, in alternative networks, the
LDAP server209 can communicate directly with the
central database204.
The
central database204 may be any number of conventional databases. In the described embodiment, either a Sybase 7.3 or 8.0, available from Sybase, Inc. of Emeryville, Calif. or Oracle 11.x database, available from Oracle Corporation of Redwood Shores, Calif., is utilized to store network configuration information. The configuration information may include DNS and DHCP parameters, other server parameters, IP addresses, domain names, the operational status of servers that have successfully logged in to the network and the like. In the described embodiment, the
central database204 is relational and stores changes in configuration made to the network. Because the
central database204 is relational, it can log any configuration changes in a separate area. For purposes of this disclosure, the section of the
central database204 that contains the log of changes in configuration will be referred to as the delta-logging facility. Since changes in configuration in the network are stored in the delta-logging facility, audit records can be kept accurately and the
server manager201 can restore the
central database204 to a previously known state. For example, if the central database becomes corrupted, the server manager can search the delta logging facility for the configuration information of a previously known uncorrupted state.
In the described embodiment, the one or
more DNS servers202A-N are Berkeley Internet Name Domain (BIND) 4.9.5 DNS servers, BIND 8.1.1 DNS servers or the like. These
servers202A-N communicate with the
central database204 through the
server manager201. Each DNS server is coupled to the
server manager201 through a TCP link. The TCP links from the
servers202A-N to the
server manager201 enable dynamic DNS updates and dynamic DNS reconfiguration. In the described embodiment, the one or
more DHCP servers203A-N are based on the BootP. These
servers203A-N also communicate with the
server manager201 through a TCP link and update the
central database204 with changes in DHCP configuration.3 The ability of the DHCP servers to update the central database with configuration changes enables incremental synchronization of DNS and DHCP services. The servers that can be linked to the server manager are not limited to DNS and DHCP servers. For example, a similar configuration could be used to support Remote Access Dial In User Services (RADIUS), Policy and future servers through the use of protocol server plug-in technology.
The
server manager201,
DNS202A-N and
DHCP203A-N servers described in the embodiment may, for example, run on the operating systems and hardware platforms given in Table 1.
| TABLE 1 | ||
| Operating System | Minimum Processor | Minimum Memory |
| Solaris 2.5, 2.6 | Sun Sparc 20 | 64 Mb |
| HP - UX 10.x | Hewlett Packard 600 | 64 Mb |
| Windows NT 4.0 | Pentium 166 | 64 Mb |
In the described embodiment, the
DNS servers202A-N and
DHCP servers203A-N must first login with the
server manager201. If the login process is successful, the
servers202A-N, 203A-N must set their server id in able to issue command and requests to the
server manager201 for processing. The following sections describe how the
servers202A-N, 203A-N complete the login process and how they communicate with the
server manager201. It should be appreciated that the methods described can be performed in other ways without departure from the scope of the present invention.
FIG. 3 provides a flow diagram illustrating steps utilized in the described embodiment for a server to server manager login process. The login process is not unique to one type of server and can be used by any server attempting to establish a communication channel with the
server manger201. First, the one or
more DNS servers202A-N and
DHCP servers203A-N establish a TCP link to the
server manager201,
step301. Next, each
server202A-N, 203A-N issues a login request by providing a userid and a password to the
server manager201,
step302. The password for each
server202A-N, 203A-N is only known by each individual server and the
server manager201.4 The
server manager201 validates the userid and password by using MD5, which is described in detail in Rivest, R., “The MD5 Message-Digest Algorithm,” Networking Group Request For Comments (RFC) 1331, April 1992, to compute a digest value,
step303. If the password is correct, the server, for example a
DNS server202A, is logged in to the
server manager201,
step305. If the password is incorrect, the login fails and the
server manager201 drops the TCP link,
step304. In order to retry the login sequence, the
server202A must reinitiate a TCP link to the
server manager201 and start the login process from the beginning,
step301.
After logging in with the
server manager201, each
DNS server202A-N and
DHCP server203A-N must set their server-id,
step306. Each server-id is checked against all of the DNS and DHCP servers already coupled in communication with the
server manager201,
step307. If the server-id is the same as a server-id for a server already on the network, the TCP link for the requesting server will be dropped,
step308. If the server-id is unique to that server, the login process is complete,
step309.
Once the
DNS servers202A-N and
DHCP servers203A-N establish a link with the
server manager201, the servers can issue requests for configuration information from the
central database204 or send updated configuration information to the
central database204. The
server manager201 synchronizes all of the requests and updates from the servers and transmits them to the
central database204. The
server manager201 monitors all the
DNS servers202A-N and
DHCP servers203A-N on the network from a single point and acts as a single pipeline to the
central database204. For example, when a
new client208 sends a request for an IP address to a
DHCP server203A, the
DHCP server203A determines if it can send configuration information to the requesting
client208. If the
DHCP server203A can give an IP address and configuration information to the
client208, it sends host configuration information and an IP address to the
client208. The
DHCP server203A automatically registers the new domain name, the IP address and the host configuration information with the
central database204 through the
server manager201. The
DNS server202A detects the new IP address through the server manager and updates its DNS information. When the lease expires or the
client208 leaves the network and releases the IP address, the
DHCP server203A notifies the
central database204 of the change through the
server manager201. The IP address is available for reassignment by the
DHCP server203A to a new client. Therefore, the
server manager201 eliminates the need for the
individual DNS servers202A-N and
DHCP servers203A-N to establish direct communication channels with the central database by providing access to the
central database204 through one
communication channel206. (more????)
Advantageously, the described embodiment utilizes plug-in technology in order to allow support for current as well as future generation servers. The DHCP server plug-in has three functions: (1) Provides configuration information to the DHCP servers linked to the network; (2) Informs the DHCP servers of any relevant changes in the central database; and (3) Transacts the DHCP hosts into the central database.
FIG. 4 provides a flow diagram which is useful for describing a method of the described embodiment for transmitting configuration information from the
central database204 to a
DHCP server203A.5 When the
server manger201 receives a request for configuration information from a
DHCP server203A,
step401, it checks to see if the server-id is zero,
step402. If the server-id is zero, the message is ignored,
step403.6 Otherwise, the
server manager201 initiates a process to retrieve configuration information from the
central database204. The
server manager201 first receives information, such as range and host lists, from the
DHCP server203A,
step404. It then builds a subnet list associated with the
DHCP server203A based on the range and host lists,
step405. Finally, it builds a network list associated with the
DHCP server203A based on the subnet list,
step406. The
server manager201 then requests the configuration information from the
central database204 based on the lists provided by the
DHCP server203A and the lists it created,
step407. The
central database204 transmits configuration information requested by the
server manager201,
step408, and this information is sent to the
DHCP server203A requesting the configuration information,
step409. In one embodiment, the configuration information can consist of (1) the global options for the network, which is sent to the requesting server and the backup server serving the same address ranges, if DHCP redundancy is supported, (2) the network options for each network contained in the network list that was created by the server manager, (3) the subnet options for each subnet contained in the subnet list, (4) the range options for each range contained in the range list and (5) the host options for each host contained in the host list.7 A benefit of processing all requests for configuration information from the
central database204 by the
DHCP servers203A-N in the
server manager201 is that the load on the
central database204 is reduced. The
server manager204 eliminates the active link between every
DHCP server203A-N that needs configuration information from the
central database204.
The
server manager201 also notifies each
DHCP server203A-N of any changes to the
central database201. Once the
DHCP servers203A-N have logged in with the
server manager201, the
server manager201 polls the delta-logging facility in the
central database204 for configuration changes made to the network that would effect the
DHCP servers203A-N coupled in communication with the
server manager201. The interval in between polling can be either a default value or a value set by a user such as the network administrator. In the described embodiment, the interval between each time the
server manager201 polls the
central database204 for configuration changes is 60 seconds. FIG. 5 provides a flow diagram which illustrates a method of the described embodiment for retrieving any changes in configuration made to the network from the delta-logging facility in the
central database204 and transmitting them to the
DHCP203A-N servers coupled in communication with the
server manager201. Once at least one of the
DHCP servers203A-N is communicating with the
server manager201, the
server manager201 queries the delta-logging facility in the
central database204,
step501, to determine if there were any configuration changes,
step502. If there were changes in configuration, the
server manager201 issues a request to the
central database204 for the global range information, the network information, the global client pool and each client pool and client pool entry managed by the
DHCP servers203A-N,
step503.8 Depending on what configuration changes occurred in the network, the
server manager201 retrieves the appropriate information,
step504 and distributes it to the
appropriate DHCP203A-N servers.9 If the
server manager201 finds no changes or has completed distributing the changes to the
DHCP server203A-N, it waits the set interval of time and polls the delta-logging facility again for changes,
step501. A benefit of only allowing the
server manger201 to pool the delta-logging facility for changes in configuration is that the load on the network is reduced. The reduced load and reduced amount of traffic to the database increases the overall performance of the network because the
server manager201 automatically determines which
DHCP servers203A-N are effected by the changes. This eliminates update requests from DHCP servers that are not affected by the configuration changes made to the network.
The
server manager201 also processes host commit requests from
DHCP servers203A-N.10 In order to add host information to the
central database204, the
server manager201 must determine if the domain name is available, unavailable, moving from another host or being updated. Upon receiving a request from a
DHCP server203A to add a host, the
server manager201 first checks if the domain is a Canonical Name (CNAME) or primary name. If the domain is a CNAME, it fails validation and the
server manager201 notifies the
DHCP server203A that the domain is unavailable.11 If the domain does not exist in the
central database204, the label12 may be assigned to the host and the
server manager201 notifies the
DHCP server203A that the domain is available. If the client-id of the host requesting the label is the same as the client-id of the host in the
central database204 that owns the label, the label may be assigned to the requesting host and the server manager notifies the
DHCP server203A that the domain is available. If the host in the
central database204 is static, the label can't be used and the
server manager201 notifies the
DHCP server203A that the domain is unavailable. If the IP addresses match, the label is updated and the
server manager201 notifies the
DHCP server203A that the domain has been updated. If the IP addresses do not match, the label is moved to the requesting host and the
server manager201 notifies the
DHCP server203A that the domain has been moved. If the client-id of the host requesting the label is not the same as the client-id of the host in the central database that owns the label, the label is in use and may not be assigned to the host. The
server manager201 notifies the
DHCP server203A that the domain is unavailable. If the
server manager201 determines that the domain name is available, the server manager adds the new host to the network by (1) setting the host IP address; (2) assigning a client-id to the host; (3) setting the hardware address; (4) setting the DHCP server-id; (5) assigning a lease expire time; and (7) determining a domain name.13 The
server manager201 will then validate all of the above information. If the validation fails, the
server manager201 notifies the
DHCP server203A that the host commit failed, otherwise the
server manager201 notifies the
DHCP server203A that the host has been committed and transmits the host information to the
central database204.
The DNS server's plug-in has two functions: (1) Provides format configuration information to the both the BIND 4.9.5 DNS servers and the BIND 8.1.1 DNS servers; and (2) Informs them of the relevant changes in the central database. FIG. 6 provides a flow diagram which is useful for describing a method of the described embodiment for communicating configuration updates from the
central database201 to a
DNS server202A.14 When the
server manager201 receives a configuration update message from a
DNS server202A,
step601, it checks to see if the server id is valid,
step602. If the server-id is NULL, the message is ignored,
step603. However, if the server id is a valid domain name and the version number is valid, the
server manager201 receives the primary and secondary zones managed by the
DNS server202A, step 604. The
server manager201 then issues a configuration update request for each zone managed by the
DNS server202A to the
central database204, step 605. The
central database204 transmits the configuration information for each zone to the sever
manager201,
step606. The
server manager201 then transmits the updated configuration information to the DNS server,
step607. For each primary forward zone, the
server manger201 sends the Start of Authority (SOA) record, name servers of the zone, the A record,15 RR record, option record, CNAME record and the glue record with the subzones to the
DNS server202A.16 For each primary reverse zone, the
server manager201 sends the SOA record, name servers of the zone, the PTR record for each subdomain of the zone and the glue record with the subzones to the
DNS server202A. For each secondary zone, the
server manager201 sends that zone transfer list to the
DNS server202A. Finally, the
server manager201 sends information about the root server on the network to the
DNS server202A.17
The
server manager201 also polls the delta-logging facility in the
central database204 periodically to determine if there were any changes in configuration made to the network that would effect the
DNS servers202A-N. The process of polling the delta-logging facility in the
central database204 for the
DNS servers202A-N is similar to the process previously described in FIG. 5 for the
DHCP servers203A-N. However, the
server manager201 requests the primary and secondary zone information, the primary forward and reverse zone information, the subzone information for each subzone not managed by a DNS server and the subdomain of one of the primary zones managed by the DNS server. Once the
server manager201 retrieves this information, it transmits the relevant information to the
appropriate DNS servers203A-N.18 This method has a similar benefit, as described above in the DHCP section, in that DNS servers that are not effected by the configuration changes will not be polling the
central database204 for changes since the
only server manager201 is coupled in communication with the
central database204.
The
server manager201 can process multiple requests or commands at the same time. However, the number of requests or updates that the
server manager201 can process at the same time is determined by the machine that it is running on. Therefore, the
server manager201, as used by the described embodiment, prioritizes what it processes based on the type of work requested. The
server manager201 services the requests and updates in the following order: (1) get configuration requests from the DCHP servers; (2) polling the central database for any configuration changes in the network; (3) configuration update requests from the DNS servers; and (4) removing leases for IP addresses when they expire.19 Prioritizing based on the type of work requested is not the only method available for the
server manager201 to process information. It could also process the information based on a first-in first-out method. For example, the first request or packet of information received by the
server manager201 would be processed first and the last request or packet of information received by the server would be processed last.
The
server manager201 also has the ability to actively manage the
DNS202A to 202N and
DHCP203A-N servers and report their operational status to the
NMS205. In the described embodiment, the
NMS205 communicates with an agent, the
server manager201, to keep track of the network statistics and resources. Network administrators can use the
NMS205 to view the real-time operating status of the
DNS202A-N and
DHCP203A-N servers that are linked with the
server manager201. In one embodiment, the
NMS205 could be a graphical user interface (GUI) running on a powerful computer such as a workstation. FIG. 7 provides a flow diagram which illustrates a method of the described embodiment for determining the operational status of the
DNS202A-N and
DHCP203A-N servers on the network and transmitting the status information to the
NMS205. The
server manager201 polls the servers every 40 seconds to determine if the server is still running or if it has stopped, step 701.20 The server generates an alarm or warning to indicate its operating status and communicates the message to the
server manager201,
step702. The message could contain information such as a key word to trigger the correct plug-in, the severity of the alarm, the specific server-id, and an alarm code to indicate the problem. The
server manager201 queues up the reports from the servers along with any other requests that it receives and attaches a database time stamp to each one. The
server manager201 then communicates the alarms to the
central database204 and to the
NMS205,
step703.21 The alarms are sent to the
NMS205 through a Simple Network Management Protocol (SNMP) trap. The traps could contain information such as setting the server status to up when the server successfully establishes a TCP link with the
server manager201, setting the server status to down when the TCP link between the server and the server manager is dropped and setting the server status to failed login when the server successfully establishes a TCP link with the
server manager201 but tried an invalid login. These traps can then be viewed from the GUI by the network administrator. The advantage to using the
server manager201 for active server management is that the
server manager201 can detect when a server has crashed. In some embodiments, multiple servers are running on the same hardware. If the hardware is still running but one of the servers has crashed, the
server manager201 can detect the change through the TCP link which will be dropped if the server crashes. When the TCP link is started or dropped, the
server manager201 generates an exception, such as the described SNMP traps, to the
NMS205. Therefore, the network administrator is able to determine if a server has gone down if the hardware is still operational.
The present invention also allows a user to be authenticated and binds the user to the IP address that was given to it by the DHCP server on the network. FIG. 8 provides a flow diagram which illustrates a method of the described embodiment for authenticating a user and binding the user to their current address. First a
client208 requests an IP address from the DHCP server 203N on the network,
step801. The DHCP server 203N dynamically assigns the
client208 an IP address before it has been authenticated,
step802. The
client208 then issues a registration request with the
binding server209 and communicates its userid, password and the IP address it just obtained from the DHCP server 203N to the
binding server209,
step803. The method of communication used by the client in the described embodiment is the Hyper Text Transfer Protocol (HTTP) but alternative methods can be used. Currently the client does not provide itself with a userid or password. However, two examples of methods for the client to obtain its userid and password are to have the user go to a World Wide Web (WWW) page or download a Java applet to obtain information from a PC or workstation which could modify the operating system to automatically provide it. The binding
server209 then authenticates the userid, password and IP address through an LDAP request to the
LDAP database210, step 804. The LDAP request searches the
LDAP database210 for the userid, password and the possible IP addresses that the DHCP server 203N could assign,
step805. The
LDAP database210 is organized in a tree hierarchy. For example, the root of an Internet address is at the top and the common name associated with the user is at the bottom. The
LDAP database210 is accessible through an open, standards based protocol such as TCP. If the information is found in the
LDAP database210, it notifies the
binding server209 that the user credentials were verified by returning the authenticated credentials,
step807.22 The binding
server209 then sends the authenticated credentials to be stored in the
central database204,
step808. In the described embodiment, the binding
server209 communicates with the
server manager201 over a
single channel211 to store the credentials in the
central database204. However, the binding
server209 could also communicate directly or through some other device with the
central database204 in order to store the authenticated credentials.
The present invention as utilized in the described embodiment authenticates the actual userid/password and address combination. Applications such as Voice/Fax over IP and Video Conferencing can benefit from the present invention because routing and bandwidth considerations are based on source and destination addresses. Therefore, deciding which users can access the network services requires authenticated addresses.
Thus, method and apparatus for transmitting configuration between a central database and one or more servers through a server manager on a network has been described. Although the present invention has been described with specific reference to a number of details of the preferred embodiment and with reference to FIGS. 1 through 8, it will be apparent to those skilled in the art that a number of modifications and various variations may be employed without departure from the scope and spirit of the present invention.
Claims (14)
1. A server manager configured to receive a plurality of requests for network protocol address information from one or more network protocol address management servers to prioritized said plurality of requests, and to access the requested network protocol address information from a database based on said priority, and configured to automatically and periodically poll the database for updates to said network protocol address information, and to transmit said updates to at least one of said network protocol address management servers.
2. The server manager as recited by
claim 1further configured to synchronize all communication to and from the one or more network protocol address management servers and act as a single pipeline to the database.
3. The server manager as recited by
claim 1further configured to receive updated information from the one or more network protocol management servers and communicate the updated information to the database.
4. The server manager as recited by
claim 1further configured to processes multiple requests at one time and queue up any further requests based on priority.
5. A server manager configured to periodically poll for updates of network protocol address information from a database, and to communicate said updates to one or more network protocol address servers requiring said updates, and in between consecutive polling for updates, to transmit network protocol address information to a requesting network protocol address server.
6. The server manager as recited by
claim 5wherein the server manager enables dynamic updates and dynamic reconfiguration of the one or more network protocol management servers.
7. The server manager as recited by
claim 5wherein the server manager enables incremental synchronization of the one or more network protocol address management servers through updates of changes in network protocol address information.
8. A method of communicating information between a database and one or more network protocol address management servers through a server manager comprising:
receiving at the server manager a plurality of requests for network protocol address information stored in the database and updates thereof from the one or more network protocol address management servers;
prioritizing said plurality of requests for the network protocol address information;
communicating by the server manager the requests for the network protocol address information stored in the database and the updates thereof from the one or more network protocol address management servers to the database based on said priority;
automatically and periodically polling said database for updates to said network protocol address information;
receiving at the server manager the requested information and the updates from the database; and
transmitting by the server manager the requested information to the requesting one or more network protocol address management servers and transmitting the updates to one or more network protocol address management servers is affected by said updates.
9. A widely-distributed IP network comprising
a database accessible by one or more DNS and DHCP servers; and
a server manager:
to receive requests for network protocol address information stored in said database from said one or more DNS and DHCP servers;
prioritize said requests for said network protocol address information;
access the requested network protocol address information from said database based on said priority; and
automatically and periodically poll said database for updates to said database.
10. The widely-distributed IP network as recited by
claim 9wherein the server manager monitors and controls the database and the one or more DNS and DHCP servers.
11. The widely-distributed IP network as recited by
claim 9wherein the server manager controls the database and the DNS and DHCP servers in dynamic configuration of the IP addresses.
12. A server manager:
to receive requests for network protocol address information stored in said database from the one or more DNS and DHCP servers;
prioritize said requests for said network protocol address information;
access the requested network protocol address information from said database based on said priority; and
automatically and periodically poll said database for updates to said database.
13. The server manager as recited by
claim 12further configured to monitor and control the one or more DNS and DHCP servers.
14. The server manager as recited by
claim 12further configured to manage IP services in dynamic configuration of IP addresses.
Priority Applications (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US09/182,949 US6564216B2 (en) | 1998-10-29 | 1998-10-29 | Server manager |
| PCT/IB1999/001873 WO2000026806A2 (en) | 1998-10-29 | 1999-10-29 | Server manager |
| CA002348490A CA2348490A1 (en) | 1998-10-29 | 1999-10-29 | Server manager |
| EP99954307A EP1145498A2 (en) | 1998-10-29 | 1999-10-29 | Server manager |
| AU10713/00A AU1071300A (en) | 1998-10-29 | 1999-10-29 | Server manager |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US09/182,949 US6564216B2 (en) | 1998-10-29 | 1998-10-29 | Server manager |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| US20020052876A1 US20020052876A1 (en) | 2002-05-02 |
| US6564216B2 true US6564216B2 (en) | 2003-05-13 |
Family
ID=22670749
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US09/182,949 Expired - Lifetime US6564216B2 (en) | 1998-10-29 | 1998-10-29 | Server manager |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US6564216B2 (en) |
| EP (1) | EP1145498A2 (en) |
| AU (1) | AU1071300A (en) |
| CA (1) | CA2348490A1 (en) |
| WO (1) | WO2000026806A2 (en) |
Cited By (80)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20010027453A1 (en) * | 2000-03-29 | 2001-10-04 | Akio Suto | Distributed data processing system and method of processing data in distributed data processing system |
| US20020016858A1 (en) * | 2000-06-29 | 2002-02-07 | Sunao Sawada | Communication apparatus for routing or discarding a packet sent from a user terminal |
| US20020069272A1 (en) * | 2000-05-05 | 2002-06-06 | Kim Steven D. | System and method for managing server configurations |
| US20020107984A1 (en) * | 2001-02-08 | 2002-08-08 | International Business Machines Corporation | Combining network management information with application information on a computer network |
| US20020107955A1 (en) * | 2001-02-08 | 2002-08-08 | International Business Machines Corporation | Protocol data unit prioritization in a data processing network |
| US20020107949A1 (en) * | 2001-02-08 | 2002-08-08 | International Business Machines Corporation | Polling for and transfer of protocol data units in a data processing network |
| US20020147611A1 (en) * | 2000-05-22 | 2002-10-10 | Greene William S. | Method and system for realizing a rendezvous service in a management operations center implemented in a global ecosystem of interrelated services |
| US20020173984A1 (en) * | 2000-05-22 | 2002-11-21 | Robertson James A. | Method and system for implementing improved containers in a global ecosystem of interrelated services |
| US20030033379A1 (en) * | 2001-07-20 | 2003-02-13 | Lemur Networks | Intelligent central directory for soft configuration of IP services |
| US20030061509A1 (en) * | 2001-09-27 | 2003-03-27 | Fisher Lee Adam | Token-based authentication for network connection |
| US20030074394A1 (en) * | 2001-10-16 | 2003-04-17 | Kave Eshghi | Effectively and efficiently updating content files among duplicate content servers |
| US20030101359A1 (en) * | 2001-11-29 | 2003-05-29 | International Business Machines Corporation | System and method for controlling invalid password attempts |
| US20030147421A1 (en) * | 2002-02-06 | 2003-08-07 | Gutknecht Gary Robert | Method and apparatus for dynamic host configuration protocol lease time determination |
| US20030182447A1 (en) * | 2001-05-31 | 2003-09-25 | Schilling Frank T. | Generic top-level domain re-routing system |
| US20040034705A1 (en) * | 2002-08-13 | 2004-02-19 | Mihai Focsaneanu | Connecting devices in a data network |
| US6704778B1 (en) * | 1999-09-01 | 2004-03-09 | International Business Machines Corporation | Method and apparatus for maintaining consistency among large numbers of similarly configured information handling servers |
| US6711593B1 (en) * | 2000-06-26 | 2004-03-23 | Camstar Systems, Inc. | System and method for live update of a manufacturing system |
| US20040148318A1 (en) * | 2003-01-24 | 2004-07-29 | Taylor Don H. | Staged publication and management of dynamic webpages |
| US6785706B1 (en) * | 1999-09-01 | 2004-08-31 | International Business Machines Corporation | Method and apparatus for simplified administration of large numbers of similar information handling servers |
| US20040172465A1 (en) * | 1999-08-30 | 2004-09-02 | Brian Shuster | Method and system for redirecting a request to a server selected domain |
| US6795823B1 (en) * | 2000-08-31 | 2004-09-21 | Neoris Logistics, Inc. | Centralized system and method for optimally routing and tracking articles |
| US20040210672A1 (en) * | 2000-07-13 | 2004-10-21 | Infoblox, Inc. | Domain name service server apparatus and method |
| US20050010614A1 (en) * | 2003-07-11 | 2005-01-13 | Yi-Mei Ting | Method and apparatus for synchronous updating of multiple language web content |
| US20050027868A1 (en) * | 2003-07-31 | 2005-02-03 | International Business Machines Corporation | Method and apparatus for authenticated network address allocation |
| US20050027837A1 (en) * | 2003-07-29 | 2005-02-03 | Enterasys Networks, Inc. | System and method for dynamic network policy management |
| US6868444B1 (en) * | 2000-05-05 | 2005-03-15 | Interland, Inc. | Server configuration management and tracking |
| US20050125559A1 (en) * | 2003-12-02 | 2005-06-09 | Mutha Kailash K. | Employment of one or more identifiers of one or more communication devices to determine one or more internet protocol addresses |
| US20050171856A1 (en) * | 2004-01-30 | 2005-08-04 | Canon Usa, Inc. | Estimated time of arrival (ETA) systems and methods |
| US6981036B1 (en) * | 1999-06-11 | 2005-12-27 | Canon Kabushiki Kaisha | Network device managing apparatus and method |
| US20050289240A1 (en) * | 2004-06-25 | 2005-12-29 | Cheshire Stuart D | Method and apparatus for updating resource records in a name-server database |
| US6988148B1 (en) * | 2001-01-19 | 2006-01-17 | Cisco Technology, Inc. | IP pool management utilizing an IP pool MIB |
| US20060056418A1 (en) * | 2004-09-10 | 2006-03-16 | Rizzuto Joseph J | Methods and systems for determining reverse DNS entries |
| US20060136509A1 (en) * | 2004-12-16 | 2006-06-22 | Syam Pannala | Techniques for transaction semantics for a database server performing file operations |
| US20060155833A1 (en) * | 1998-11-12 | 2006-07-13 | Toru Matsuda | Method and apparatus for automatic network configuration |
| US20060168224A1 (en) * | 2002-09-07 | 2006-07-27 | Midgley Nicholas J | Remote dynamic configuration of a web server to facilitate capacity on demand |
| US20060190558A1 (en) * | 2005-02-09 | 2006-08-24 | Akitsugu Kanda | Computer system and storage device |
| US7143182B1 (en) | 2000-08-08 | 2006-11-28 | Cisco Technology, Inc. | Smart secretary for routing call objects in a telephony network |
| US7167904B1 (en) * | 1999-03-19 | 2007-01-23 | Network Solutions, Llc | Unified web-based interface-to multiple registrar systems |
| US20070027963A1 (en) * | 2005-07-28 | 2007-02-01 | International Business Machines Corporation | Method and apparatus for implementing service requests from a common database in a multiple DHCP server environment |
| US20070033272A1 (en) * | 2005-08-04 | 2007-02-08 | Vasu Vallabhaneni | Dynamic subnet updates |
| US7188175B1 (en) * | 2000-04-06 | 2007-03-06 | Web.Com, Inc. | Method and system for communicating between clients in a computer network |
| US7197549B1 (en) | 2001-06-04 | 2007-03-27 | Cisco Technology, Inc. | On-demand address pools |
| US7246145B1 (en) | 2000-08-08 | 2007-07-17 | Cisco Technology, Inc. | Fully distributed, scalable infrastructure, communication system |
| US7251826B1 (en) * | 1999-06-07 | 2007-07-31 | Register.Com, Inc. | Domain manager for plural domains and method of use |
| US20070183426A1 (en) * | 1999-08-20 | 2007-08-09 | International Business Machines Corporation | Method and system for optimizing performance and availability of a dynamic host configuration protocol (dhcp) service |
| US20070198664A1 (en) * | 2006-02-22 | 2007-08-23 | Microsoft Corporation | Multi-server automated redundant service configuration |
| US20070282652A1 (en) * | 2006-06-05 | 2007-12-06 | International Business Machines Corporation | System, Method and Program Product for Providing Policy Hierarchy in an Enterprise Data Processing System |
| US20080086480A1 (en) * | 2006-10-06 | 2008-04-10 | Sybase, Inc. | System and Methods For Temporary Data Management in Shared Disk Cluster |
| US7363359B1 (en) * | 1999-05-26 | 2008-04-22 | Fujitsu Limited | Element management system with automatic remote backup of network elements' local storage |
| US7386786B2 (en) | 2003-01-24 | 2008-06-10 | The Cobalt Group, Inc. | Method and apparatus for processing a dynamic webpage |
| US7415516B1 (en) | 2000-08-08 | 2008-08-19 | Cisco Technology, Inc. | Net lurkers |
| US7415468B1 (en) * | 1999-07-28 | 2008-08-19 | Benno Henricus Nicolaas Hijl | Method of identifying and registering entities and an assembly of hardware and software for applying such a method |
| US20080215756A1 (en) * | 2007-02-06 | 2008-09-04 | Samsung Electronics Co., Ltd. | Electronic device, management server, and control method thereof |
| US20080306712A1 (en) * | 2007-06-08 | 2008-12-11 | Bea Systems, Inc. | Performance Monitoring Infrastructure for Distributed Transaction Service |
| US20090083439A1 (en) * | 2007-09-20 | 2009-03-26 | Konica Minolta Business Technologies, Inc. | Data transmission device, data transmission system and address registration method |
| US20090089360A1 (en) * | 2007-09-28 | 2009-04-02 | Microsoft Corporation | Central Service Control |
| US20090094381A1 (en) * | 2007-10-05 | 2009-04-09 | Cisco Technology, Inc. | Modem prioritization and registration |
| US20090144437A1 (en) * | 2007-11-30 | 2009-06-04 | Microsoft Corporation | Securing a Server in a Dynamic Addressing Environment |
| US7788345B1 (en) * | 2001-06-04 | 2010-08-31 | Cisco Technology, Inc. | Resource allocation and reclamation for on-demand address pools |
| US20100241668A1 (en) * | 2009-03-17 | 2010-09-23 | Microsoft Corporation | Local Computer Account Management at Domain Level |
| US7929552B2 (en) | 2006-10-26 | 2011-04-19 | At&T Intellectual Property I, L.P. | Automated IP pool management |
| US8010627B1 (en) * | 1998-09-25 | 2011-08-30 | Sprint Communications Company L.P. | Virtual content publishing system |
| US8065400B1 (en) * | 1999-04-16 | 2011-11-22 | Siemens Aktiengesellschaft | Method for controlling devices that are arranged in a communications network |
| US8583769B1 (en) | 2011-08-16 | 2013-11-12 | Edgecast Networks, Inc. | Configuration management repository for a distributed platform |
| US9680790B2 (en) | 2013-08-29 | 2017-06-13 | Mastercard International Incorporated | Systems and methods for resolving data inconsistencies between domain name systems |
| US9813503B2 (en) * | 2011-06-30 | 2017-11-07 | Mitsubishi Electric Corporation | IP-address distribution system utilizing a plurality of switching devices grouped into two or more groups |
| US10326858B2 (en) | 2017-05-23 | 2019-06-18 | Cdk Global, Llc | System and method for dynamically generating personalized websites |
| US10332068B2 (en) | 2016-04-21 | 2019-06-25 | Cdk Global, Llc | Systems and methods for stocking an automobile |
| US10482475B2 (en) | 2011-02-10 | 2019-11-19 | Adp Dealer Services, Inc. | Systems and methods for providing targeted advertising |
| US10853769B2 (en) | 2016-04-21 | 2020-12-01 | Cdk Global Llc | Scheduling an automobile service appointment in a dealer service bay based on diagnostic trouble codes and service bay attributes |
| US10867285B2 (en) | 2016-04-21 | 2020-12-15 | Cdk Global, Llc | Automatic automobile repair service scheduling based on diagnostic trouble codes and service center attributes |
| US11080734B2 (en) | 2013-03-15 | 2021-08-03 | Cdk Global, Llc | Pricing system for identifying prices for vehicles offered by vehicle dealerships and other entities |
| US11080105B1 (en) | 2020-11-18 | 2021-08-03 | Cdk Global, Llc | Systems, methods, and apparatuses for routing API calls |
| US11190608B2 (en) | 2018-03-21 | 2021-11-30 | Cdk Global Llc | Systems and methods for an automotive commerce exchange |
| US11501351B2 (en) | 2018-03-21 | 2022-11-15 | Cdk Global, Llc | Servers, systems, and methods for single sign-on of an automotive commerce exchange |
| US11514021B2 (en) | 2021-01-22 | 2022-11-29 | Cdk Global, Llc | Systems, methods, and apparatuses for scanning a legacy database |
| US11803535B2 (en) | 2021-05-24 | 2023-10-31 | Cdk Global, Llc | Systems, methods, and apparatuses for simultaneously running parallel databases |
| US11983145B2 (en) | 2022-08-31 | 2024-05-14 | Cdk Global, Llc | Method and system of modifying information on file |
| US12020217B2 (en) | 2020-11-11 | 2024-06-25 | Cdk Global, Llc | Systems and methods for using machine learning for vehicle damage detection and repair cost estimation |
| US12045212B2 (en) | 2021-04-22 | 2024-07-23 | Cdk Global, Llc | Systems, methods, and apparatuses for verifying entries in disparate databases |
Families Citing this family (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1163567B1 (en) * | 1999-02-26 | 2008-11-19 | Henry Haugland | Mass generation of individual virtual servers, virtual web sites and virtual web objects |
| US6581075B1 (en) * | 2000-12-28 | 2003-06-17 | Nortel Networks Limited | System and method for database synchronization |
| JP2002208962A (en) * | 2000-12-28 | 2002-07-26 | Fujitsu Ltd | Media distribution resource management device and recording medium |
| JP4160506B2 (en) | 2001-09-28 | 2008-10-01 | レヴェル ３ シーディーエヌ インターナショナル インコーポレーテッド． | Configurable adaptive wide area traffic control and management |
| DE50301105D1 (en) * | 2002-03-27 | 2005-10-06 | Siemens Ag | AAA SERVER SYSTEM FOR EFFICIENT ACCESS CONTROL AND ADDRESS ALLOCATION |
| CA2479504C (en) * | 2002-03-29 | 2010-07-13 | Cisco Technology, Inc. | Method and system for reducing the false alarm rate of network intrusion detection systems |
| AU2003243253B2 (en) * | 2002-05-14 | 2009-12-03 | Cisco Technology, Inc. | Method and system for analyzing and addressing alarms from network intrusion detection systems |
| ATE377310T1 (en) * | 2002-07-25 | 2007-11-15 | Hewlett Packard Co | METHOD AND APPARATUS FOR DISTRIBUTING NETWORK CONFIGURATION SETTINGS |
| US20050097199A1 (en) * | 2003-10-10 | 2005-05-05 | Keith Woodard | Method and system for scanning network devices |
| US7805762B2 (en) * | 2003-10-15 | 2010-09-28 | Cisco Technology, Inc. | Method and system for reducing the false alarm rate of network intrusion detection systems |
| US8090871B2 (en) * | 2003-10-20 | 2012-01-03 | International Business Machines Corporation | Determining a remote management processor's IP address |
| FI20040978A0 (en) * | 2004-07-13 | 2004-07-13 | Nokia Corp | System, Method, Web Objects, and Computer Programs to Manage Dynamic Host Configuration Policy Frame Configuration |
| US8681779B2 (en) * | 2006-09-01 | 2014-03-25 | Alcatel Lucent | Triple play subscriber and policy management system and method of providing same |
| WO2008071227A1 (en) * | 2006-12-12 | 2008-06-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Ip address distribution in middleboxes |
| EP2264594B1 (en) * | 2009-06-18 | 2011-10-12 | Software AG | A broker system for a plurality of brokers, clients and servers in a heterogeneous network |
| US10642849B2 (en) * | 2010-10-25 | 2020-05-05 | Schneider Electric It Corporation | Methods and systems for providing improved access to data and measurements in a management system |
| US9762578B2 (en) | 2010-10-25 | 2017-09-12 | Schneider Electric It Corporation | Methods and systems for establishing secure authenticated bidirectional server communication using automated credential reservation |
| US8825839B2 (en) * | 2010-11-24 | 2014-09-02 | Unisys Corporation | Snooping DNS messages in a server hosting system providing overlapping address and name spaces |
| US8683567B2 (en) | 2011-03-31 | 2014-03-25 | Belkin International, Inc. | Method of distributing information regarding one or more electrical devices and system for the same |
| US8868784B2 (en) * | 2012-06-28 | 2014-10-21 | Alcatel Lucent | Sticky IP prioritization based on IP pool and subnet by DHCP |
| US9703646B2 (en) * | 2015-07-20 | 2017-07-11 | Bank Of America Corporation | Centralized database system |
| US10225138B2 (en) * | 2016-02-16 | 2019-03-05 | Architecture Technology Corporation | Scalable and automated network-parameter assignment |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5548756A (en) * | 1990-10-16 | 1996-08-20 | Consilium, Inc. | Object-oriented architecture for factory floor management |
| US5652908A (en) | 1991-10-02 | 1997-07-29 | International Business Machines Corporation | Method and apparatus for establishing communications sessions in a remote resource control environment |
| US5751967A (en) * | 1994-07-25 | 1998-05-12 | Bay Networks Group, Inc. | Method and apparatus for automatically configuring a network device to support a virtual network |
| US5806068A (en) * | 1991-09-20 | 1998-09-08 | Shaw; Venson M. | Document data processor for an object-oriented knowledge management system containing a personal database in communication with a packet processor |
| US5926463A (en) * | 1997-10-06 | 1999-07-20 | 3Com Corporation | Method and apparatus for viewing and managing a configuration of a computer network |
| US5930768A (en) * | 1996-02-06 | 1999-07-27 | Supersonic Boom, Inc. | Method and system for remote user controlled manufacturing |
| US5950195A (en) * | 1996-09-18 | 1999-09-07 | Secure Computing Corporation | Generalized security policy management system and method |
| US5956391A (en) * | 1996-02-09 | 1999-09-21 | Telefonaktiebolaget Lm Ericsson | Billing in the internet |
| US6012100A (en) * | 1997-07-14 | 2000-01-04 | Freegate Corporation | System and method of configuring a remotely managed secure network interface |
| US6057757A (en) * | 1995-03-29 | 2000-05-02 | Cabletron Systems, Inc. | Method and apparatus for policy-based alarm notification in a distributed network management environment |
| US6073172A (en) * | 1997-07-14 | 2000-06-06 | Freegate Corporation | Initializing and reconfiguring a secure network interface |
| US6094659A (en) * | 1997-09-26 | 2000-07-25 | 3Com Corporation | Web server for use in a LAN modem |
| US6117188A (en) * | 1998-04-27 | 2000-09-12 | Cognet Corporation | System and method using token processing to control software distribution and desktop management in a computer network environment |
| US6119129A (en) * | 1998-05-14 | 2000-09-12 | Sun Microsystems, Inc. | Multi-threaded journaling in a configuration database |
| US6128624A (en) * | 1997-11-12 | 2000-10-03 | Ncr Corporation | Collection and integration of internet and electronic commerce data in a database during web browsing |
| US6182111B1 (en) * | 1997-05-15 | 2001-01-30 | Hitachi, Ltd. | Method and system for managing distributed data |
| US6212545B1 (en) * | 1997-10-31 | 2001-04-03 | Fujitsu Limited | Distributed searching system and searching apparatus for use in the distributed searching system |
| US6343289B1 (en) * | 1997-10-31 | 2002-01-29 | Nortel Networks Limited | Efficient search and organization of a forwarding database or the like |
| US6374295B2 (en) * | 1998-10-29 | 2002-04-16 | Nortel Networks Limited | Active server management |
-
1998
- 1998-10-29 US US09/182,949 patent/US6564216B2/en not_active Expired - Lifetime
-
1999
- 1999-10-29 WO PCT/IB1999/001873 patent/WO2000026806A2/en not_active Application Discontinuation
- 1999-10-29 EP EP99954307A patent/EP1145498A2/en not_active Withdrawn
- 1999-10-29 CA CA002348490A patent/CA2348490A1/en not_active Abandoned
- 1999-10-29 AU AU10713/00A patent/AU1071300A/en not_active Abandoned
Patent Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5548756A (en) * | 1990-10-16 | 1996-08-20 | Consilium, Inc. | Object-oriented architecture for factory floor management |
| US5983004A (en) * | 1991-09-20 | 1999-11-09 | Shaw; Venson M. | Computer, memory, telephone, communications, and transportation system and methods |
| US5806068A (en) * | 1991-09-20 | 1998-09-08 | Shaw; Venson M. | Document data processor for an object-oriented knowledge management system containing a personal database in communication with a packet processor |
| US5652908A (en) | 1991-10-02 | 1997-07-29 | International Business Machines Corporation | Method and apparatus for establishing communications sessions in a remote resource control environment |
| US5751967A (en) * | 1994-07-25 | 1998-05-12 | Bay Networks Group, Inc. | Method and apparatus for automatically configuring a network device to support a virtual network |
| US6057757A (en) * | 1995-03-29 | 2000-05-02 | Cabletron Systems, Inc. | Method and apparatus for policy-based alarm notification in a distributed network management environment |
| US5930768A (en) * | 1996-02-06 | 1999-07-27 | Supersonic Boom, Inc. | Method and system for remote user controlled manufacturing |
| US5956391A (en) * | 1996-02-09 | 1999-09-21 | Telefonaktiebolaget Lm Ericsson | Billing in the internet |
| US5950195A (en) * | 1996-09-18 | 1999-09-07 | Secure Computing Corporation | Generalized security policy management system and method |
| US6182111B1 (en) * | 1997-05-15 | 2001-01-30 | Hitachi, Ltd. | Method and system for managing distributed data |
| US6012100A (en) * | 1997-07-14 | 2000-01-04 | Freegate Corporation | System and method of configuring a remotely managed secure network interface |
| US6073172A (en) * | 1997-07-14 | 2000-06-06 | Freegate Corporation | Initializing and reconfiguring a secure network interface |
| US6094659A (en) * | 1997-09-26 | 2000-07-25 | 3Com Corporation | Web server for use in a LAN modem |
| US5926463A (en) * | 1997-10-06 | 1999-07-20 | 3Com Corporation | Method and apparatus for viewing and managing a configuration of a computer network |
| US6212545B1 (en) * | 1997-10-31 | 2001-04-03 | Fujitsu Limited | Distributed searching system and searching apparatus for use in the distributed searching system |
| US6343289B1 (en) * | 1997-10-31 | 2002-01-29 | Nortel Networks Limited | Efficient search and organization of a forwarding database or the like |
| US6128624A (en) * | 1997-11-12 | 2000-10-03 | Ncr Corporation | Collection and integration of internet and electronic commerce data in a database during web browsing |
| US6117188A (en) * | 1998-04-27 | 2000-09-12 | Cognet Corporation | System and method using token processing to control software distribution and desktop management in a computer network environment |
| US6119129A (en) * | 1998-05-14 | 2000-09-12 | Sun Microsystems, Inc. | Multi-threaded journaling in a configuration database |
| US6374295B2 (en) * | 1998-10-29 | 2002-04-16 | Nortel Networks Limited | Active server management |
Non-Patent Citations (1)
| Title |
|---|
| Ahn I: "Database Issues In Telecommunications Network Management" Sigmod Record, US, Association For Computing Machinery, New Yoerk, vol. 23, No. 2, Jun. 1, 1994. |
Cited By (159)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8010627B1 (en) * | 1998-09-25 | 2011-08-30 | Sprint Communications Company L.P. | Virtual content publishing system |
| US7577723B2 (en) * | 1998-11-12 | 2009-08-18 | Ricoh Co., Ltd. | Method and apparatus for automatic network configuration |
| US20060155833A1 (en) * | 1998-11-12 | 2006-07-13 | Toru Matsuda | Method and apparatus for automatic network configuration |
| US7167904B1 (en) * | 1999-03-19 | 2007-01-23 | Network Solutions, Llc | Unified web-based interface-to multiple registrar systems |
| US8065400B1 (en) * | 1999-04-16 | 2011-11-22 | Siemens Aktiengesellschaft | Method for controlling devices that are arranged in a communications network |
| US7363359B1 (en) * | 1999-05-26 | 2008-04-22 | Fujitsu Limited | Element management system with automatic remote backup of network elements' local storage |
| US7251826B1 (en) * | 1999-06-07 | 2007-07-31 | Register.Com, Inc. | Domain manager for plural domains and method of use |
| US9106712B1 (en) | 1999-06-07 | 2015-08-11 | Web.Com Group, Inc. | Domain manager for plural domains and method of use |
| US6981036B1 (en) * | 1999-06-11 | 2005-12-27 | Canon Kabushiki Kaisha | Network device managing apparatus and method |
| US7415468B1 (en) * | 1999-07-28 | 2008-08-19 | Benno Henricus Nicolaas Hijl | Method of identifying and registering entities and an assembly of hardware and software for applying such a method |
| US20070183426A1 (en) * | 1999-08-20 | 2007-08-09 | International Business Machines Corporation | Method and system for optimizing performance and availability of a dynamic host configuration protocol (dhcp) service |
| US8370487B2 (en) * | 1999-08-20 | 2013-02-05 | International Business Machines Corporation | Method and system for optimizing performance and availability of a dynamic host configuration protocol (DHCP) service |
| US20120144033A1 (en) * | 1999-08-20 | 2012-06-07 | International Business Machines Corporation | Method and system for optimizing performance and availability of a dynamic host configuration protocol (dhcp) service |
| US8161136B2 (en) * | 1999-08-20 | 2012-04-17 | International Business Machines Corporation | Method and system for optimizing performance and availability of a dynamic host configuration protocol (DHCP) service |
| US20090319690A1 (en) * | 1999-08-30 | 2009-12-24 | Brian Shuster | System, apparatus and method for hosting and assigning domain names on a wide area network |
| US20120271918A1 (en) * | 1999-08-30 | 2012-10-25 | Brian Shuster | Systems, apparatus and method for hosting and assigning domain names on a wide area network |
| US20110252159A1 (en) * | 1999-08-30 | 2011-10-13 | Brian Shuster | Systems, Apparatus and Method For Hosting and Assigning Domain Names On A Wide Network |
| US20040172465A1 (en) * | 1999-08-30 | 2004-09-02 | Brian Shuster | Method and system for redirecting a request to a server selected domain |
| US20120259999A1 (en) * | 1999-08-30 | 2012-10-11 | Brian Shuster | Systems, Apparatus and Method for Hosting and Assigning Domain Names on a Wide Area Network |
| US20120271919A1 (en) * | 1999-08-30 | 2012-10-25 | Brian Shuster | Systems, apparatus and method for hosting and assigning domain names on a wide network |
| US7970937B2 (en) * | 1999-08-30 | 2011-06-28 | Brian Shuster | Method and system for redirecting a request to a server-selected domain |
| US20130006799A1 (en) * | 1999-08-30 | 2013-01-03 | Brian Shuster | Systems, apparatus and method for hosting and assigning domain names on a wide area network |
| US6785706B1 (en) * | 1999-09-01 | 2004-08-31 | International Business Machines Corporation | Method and apparatus for simplified administration of large numbers of similar information handling servers |
| US6704778B1 (en) * | 1999-09-01 | 2004-03-09 | International Business Machines Corporation | Method and apparatus for maintaining consistency among large numbers of similarly configured information handling servers |
| US20010027453A1 (en) * | 2000-03-29 | 2001-10-04 | Akio Suto | Distributed data processing system and method of processing data in distributed data processing system |
| US7188175B1 (en) * | 2000-04-06 | 2007-03-06 | Web.Com, Inc. | Method and system for communicating between clients in a computer network |
| US7509428B2 (en) | 2000-04-06 | 2009-03-24 | Web.Com, Inc. | Method and system for communicating between clients in a computer network |
| US20080052352A1 (en) * | 2000-05-05 | 2008-02-28 | Kim Steven D | System and Method for Managing Server Configurations |
| US20080059614A1 (en) * | 2000-05-05 | 2008-03-06 | Kim Steven D | System and Method for Managing Server Configurations |
| US20080065650A1 (en) * | 2000-05-05 | 2008-03-13 | Kim Steven D | System and Method for Managing Server Configurations |
| US8370470B2 (en) | 2000-05-05 | 2013-02-05 | Web.Com Holding Company, Inc. | System and method for managing server configurations |
| US8799416B2 (en) | 2000-05-05 | 2014-08-05 | Web.Com Holding Company, Inc. | System and method for managing server configurations |
| US20020069272A1 (en) * | 2000-05-05 | 2002-06-06 | Kim Steven D. | System and method for managing server configurations |
| US6868444B1 (en) * | 2000-05-05 | 2005-03-15 | Interland, Inc. | Server configuration management and tracking |
| US6868441B2 (en) | 2000-05-22 | 2005-03-15 | Mci, Inc. | Method and system for implementing a global ecosystem of interrelated services |
| US7856486B2 (en) | 2000-05-22 | 2010-12-21 | Verizon Business Global Llc | Method and system for implementing a global lookup in a global ecosystem of interrelated services |
| US7428723B2 (en) | 2000-05-22 | 2008-09-23 | Verizon Business Global Llc | Aggregrating related events into a single bundle of events with incorporation of bundle into work protocol based on rules |
| US8856087B2 (en) | 2000-05-22 | 2014-10-07 | Verizon Patent And Licensing Inc. | Method and system for realizing a rendezvous service in a management operations center implemented in a global ecosystem of interrelated services |
| US8843386B2 (en) | 2000-05-22 | 2014-09-23 | Verizon Patent And Licensing Inc. | Method and system for realizing an avatar in a management operations center implemented in a global ecosystem of interrelated services |
| US7802264B2 (en) | 2000-05-22 | 2010-09-21 | Verizon Business Global Llc | Method and system for implementing a databus in a global ecosystem of interrelated services |
| US7822781B2 (en) | 2000-05-22 | 2010-10-26 | Verizon Business Global Llc | Method and system for managing partitioned data resources |
| US8626877B2 (en) | 2000-05-22 | 2014-01-07 | Verizon Business Global Llc | Method and system for implementing a global information bus in a global ecosystem of interrelated services |
| US7401131B2 (en) | 2000-05-22 | 2008-07-15 | Verizon Business Global Llc | Method and system for implementing improved containers in a global ecosystem of interrelated services |
| US6922685B2 (en) * | 2000-05-22 | 2005-07-26 | Mci, Inc. | Method and system for managing partitioned data resources |
| US20030004774A1 (en) * | 2000-05-22 | 2003-01-02 | Greene William S. | Method and system for realizing an avatar in a management operations center implemented in a global ecosystem of interrelated services |
| US20030004744A1 (en) * | 2000-05-22 | 2003-01-02 | Greene William S. | Method and system for implementing a Global Information Bus in a global ecosystem of interrelated services |
| US20020188538A1 (en) * | 2000-05-22 | 2002-12-12 | Robertson James A. | Method and system for implementing a databus in a global ecosystem of interrelated services |
| US20020178026A1 (en) * | 2000-05-22 | 2002-11-28 | Robertson James A. | Method and system for implementing a global lookup in a global ecosystem of interrelated services |
| US20020173984A1 (en) * | 2000-05-22 | 2002-11-21 | Robertson James A. | Method and system for implementing improved containers in a global ecosystem of interrelated services |
| US20020147611A1 (en) * | 2000-05-22 | 2002-10-10 | Greene William S. | Method and system for realizing a rendezvous service in a management operations center implemented in a global ecosystem of interrelated services |
| US20020169644A1 (en) * | 2000-05-22 | 2002-11-14 | Greene William S. | Method and system for implementing a management operations center in a global ecosystem of interrelated services |
| US20020165727A1 (en) * | 2000-05-22 | 2002-11-07 | Greene William S. | Method and system for managing partitioned data resources |
| US20020165745A1 (en) * | 2000-05-22 | 2002-11-07 | Greene William S. | Method and system for realizing an aggregator in a management operations center implemented in a global ecosystem of interrelated services |
| US6711593B1 (en) * | 2000-06-26 | 2004-03-23 | Camstar Systems, Inc. | System and method for live update of a manufacturing system |
| US20020016858A1 (en) * | 2000-06-29 | 2002-02-07 | Sunao Sawada | Communication apparatus for routing or discarding a packet sent from a user terminal |
| US6907470B2 (en) * | 2000-06-29 | 2005-06-14 | Hitachi, Ltd. | Communication apparatus for routing or discarding a packet sent from a user terminal |
| US20040210672A1 (en) * | 2000-07-13 | 2004-10-21 | Infoblox, Inc. | Domain name service server apparatus and method |
| US7814180B2 (en) * | 2000-07-13 | 2010-10-12 | Infoblox, Inc. | Domain name service server |
| US7945695B1 (en) | 2000-08-08 | 2011-05-17 | Cisco Technology, Inc. | Smart secretary |
| US20080031242A1 (en) * | 2000-08-08 | 2008-02-07 | Cisco Technology, Inc. | Fully distributed, scalable infrastructure, communication system |
| US7415516B1 (en) | 2000-08-08 | 2008-08-19 | Cisco Technology, Inc. | Net lurkers |
| US8495140B2 (en) | 2000-08-08 | 2013-07-23 | Cisco Technology, Inc. | Fully distributed, scalable infrastructure, communication system |
| US7246145B1 (en) | 2000-08-08 | 2007-07-17 | Cisco Technology, Inc. | Fully distributed, scalable infrastructure, communication system |
| US7143182B1 (en) | 2000-08-08 | 2006-11-28 | Cisco Technology, Inc. | Smart secretary for routing call objects in a telephony network |
| US6795823B1 (en) * | 2000-08-31 | 2004-09-21 | Neoris Logistics, Inc. | Centralized system and method for optimally routing and tracking articles |
| US20040202154A1 (en) * | 2000-08-31 | 2004-10-14 | Neoris Logistics, Inc. | Centralized system and method for optimally routing and tracking articles |
| US7561533B2 (en) * | 2000-08-31 | 2009-07-14 | Neoris Logistics, Inc. | Centralized system and method for optimally routing and tracking articles |
| US7587493B1 (en) | 2001-01-19 | 2009-09-08 | Cisco Technology, Inc. | Local network address management |
| US6988148B1 (en) * | 2001-01-19 | 2006-01-17 | Cisco Technology, Inc. | IP pool management utilizing an IP pool MIB |
| US8321567B1 (en) | 2001-01-19 | 2012-11-27 | Cisco Technology, Inc. | IP pool management utilizing an IP pool MIB |
| US20020107949A1 (en) * | 2001-02-08 | 2002-08-08 | International Business Machines Corporation | Polling for and transfer of protocol data units in a data processing network |
| US20020107984A1 (en) * | 2001-02-08 | 2002-08-08 | International Business Machines Corporation | Combining network management information with application information on a computer network |
| US6874036B2 (en) * | 2001-02-08 | 2005-03-29 | International Business Machines Corporation | Network management server combining PDUs to minimize bandwidth consumption at data link layer |
| US20020107955A1 (en) * | 2001-02-08 | 2002-08-08 | International Business Machines Corporation | Protocol data unit prioritization in a data processing network |
| US20060265516A1 (en) * | 2001-05-31 | 2006-11-23 | Schilling Frank T | Generic top-level domain re-routing system |
| US20030182447A1 (en) * | 2001-05-31 | 2003-09-25 | Schilling Frank T. | Generic top-level domain re-routing system |
| US7788345B1 (en) * | 2001-06-04 | 2010-08-31 | Cisco Technology, Inc. | Resource allocation and reclamation for on-demand address pools |
| US7197549B1 (en) | 2001-06-04 | 2007-03-27 | Cisco Technology, Inc. | On-demand address pools |
| US20030033379A1 (en) * | 2001-07-20 | 2003-02-13 | Lemur Networks | Intelligent central directory for soft configuration of IP services |
| US7134140B2 (en) * | 2001-09-27 | 2006-11-07 | Mcafee, Inc. | Token-based authentication for network connection |
| US20030061509A1 (en) * | 2001-09-27 | 2003-03-27 | Fisher Lee Adam | Token-based authentication for network connection |
| US6823362B2 (en) * | 2001-10-16 | 2004-11-23 | Hewlett-Packard Development Company, L.P. | Effectively and efficiently updating content files among duplicate content servers |
| US20030074394A1 (en) * | 2001-10-16 | 2003-04-17 | Kave Eshghi | Effectively and efficiently updating content files among duplicate content servers |
| US20030101359A1 (en) * | 2001-11-29 | 2003-05-29 | International Business Machines Corporation | System and method for controlling invalid password attempts |
| WO2003067837A3 (en) * | 2002-02-06 | 2003-10-02 | Thomson Licensing Sa | Dynamic host configuration protocol lease time determination |
| US20030147421A1 (en) * | 2002-02-06 | 2003-08-07 | Gutknecht Gary Robert | Method and apparatus for dynamic host configuration protocol lease time determination |
| WO2003067837A2 (en) * | 2002-02-06 | 2003-08-14 | Thomson Licensing S.A. | Dynamic host configuration protocol lease time determination |
| US20040034705A1 (en) * | 2002-08-13 | 2004-02-19 | Mihai Focsaneanu | Connecting devices in a data network |
| US7930397B2 (en) * | 2002-09-07 | 2011-04-19 | International Business Machines Corporation | Remote dynamic configuration of a web server to facilitate capacity on demand |
| US20060168224A1 (en) * | 2002-09-07 | 2006-07-27 | Midgley Nicholas J | Remote dynamic configuration of a web server to facilitate capacity on demand |
| US20040148318A1 (en) * | 2003-01-24 | 2004-07-29 | Taylor Don H. | Staged publication and management of dynamic webpages |
| US7386786B2 (en) | 2003-01-24 | 2008-06-10 | The Cobalt Group, Inc. | Method and apparatus for processing a dynamic webpage |
| WO2004068291A2 (en) * | 2003-01-24 | 2004-08-12 | The Cobalt Group, Inc. | Staged publication and management of dynamic webpages |
| US7062506B2 (en) * | 2003-01-24 | 2006-06-13 | The Cobalt Group, Inc. | Staged publication and management of dynamic webpages |
| WO2004068291A3 (en) * | 2003-01-24 | 2004-11-04 | Cobalt Group Inc | Staged publication and management of dynamic webpages |
| US7254591B2 (en) * | 2003-07-11 | 2007-08-07 | Via Technologies, Inc. | Method and apparatus for synchronous updating of multiple language web content |
| US20050010614A1 (en) * | 2003-07-11 | 2005-01-13 | Yi-Mei Ting | Method and apparatus for synchronous updating of multiple language web content |
| US7526541B2 (en) * | 2003-07-29 | 2009-04-28 | Enterasys Networks, Inc. | System and method for dynamic network policy management |
| US20050027837A1 (en) * | 2003-07-29 | 2005-02-03 | Enterasys Networks, Inc. | System and method for dynamic network policy management |
| US20050027868A1 (en) * | 2003-07-31 | 2005-02-03 | International Business Machines Corporation | Method and apparatus for authenticated network address allocation |
| US7519988B2 (en) * | 2003-07-31 | 2009-04-14 | International Business Machines Corporation | Method and apparatus for authenticated network address allocation |
| US20050125559A1 (en) * | 2003-12-02 | 2005-06-09 | Mutha Kailash K. | Employment of one or more identifiers of one or more communication devices to determine one or more internet protocol addresses |
| US20050171856A1 (en) * | 2004-01-30 | 2005-08-04 | Canon Usa, Inc. | Estimated time of arrival (ETA) systems and methods |
| US8219503B2 (en) | 2004-01-30 | 2012-07-10 | Canon U.S.A., Inc. | Estimated time of arrival (ETA) systems and methods |
| US7536321B2 (en) | 2004-01-30 | 2009-05-19 | Canon U.S.A., Inc. | Estimated time of arrival (ETA) systems and methods |
| US8156081B2 (en) * | 2004-06-25 | 2012-04-10 | Apple Inc. | Method and apparatus for updating resource records in a name-server database |
| US20050289240A1 (en) * | 2004-06-25 | 2005-12-29 | Cheshire Stuart D | Method and apparatus for updating resource records in a name-server database |
| US7808925B2 (en) | 2004-09-10 | 2010-10-05 | Digital Envoy, Inc. | Methods and systems for determining reverse DNS entries |
| US20060056418A1 (en) * | 2004-09-10 | 2006-03-16 | Rizzuto Joseph J | Methods and systems for determining reverse DNS entries |
| AU2005284979B2 (en) * | 2004-09-10 | 2009-08-13 | Digital Envoy, Inc. | Methods and systems for determining reverse DNS entries |
| WO2006031744A3 (en) * | 2004-09-10 | 2006-06-08 | Digital Envoy Inc | Methods and systems for determining reverse dns entries |
| US20060136509A1 (en) * | 2004-12-16 | 2006-06-22 | Syam Pannala | Techniques for transaction semantics for a database server performing file operations |
| US20060190558A1 (en) * | 2005-02-09 | 2006-08-24 | Akitsugu Kanda | Computer system and storage device |
| US20070027963A1 (en) * | 2005-07-28 | 2007-02-01 | International Business Machines Corporation | Method and apparatus for implementing service requests from a common database in a multiple DHCP server environment |
| US20090132550A1 (en) * | 2005-07-28 | 2009-05-21 | International Business Machines Corporation | Implementing service requests from a common database in a multiple dhcp server environment |
| JP2007037141A (en) * | 2005-07-28 | 2007-02-08 | Internatl Business Mach Corp <Ibm> | Method and apparatus executing service request from common database within two or more dhcp server environments |
| US7506067B2 (en) * | 2005-07-28 | 2009-03-17 | International Business Machines Corporation | Method and apparatus for implementing service requests from a common database in a multiple DHCP server environment |
| US8275908B2 (en) | 2005-07-28 | 2012-09-25 | International Business Machines Corporation | Implementing service requests from a common database in a multiple DHCP server environment |
| US20070033272A1 (en) * | 2005-08-04 | 2007-02-08 | Vasu Vallabhaneni | Dynamic subnet updates |
| US20070198664A1 (en) * | 2006-02-22 | 2007-08-23 | Microsoft Corporation | Multi-server automated redundant service configuration |
| US20070282652A1 (en) * | 2006-06-05 | 2007-12-06 | International Business Machines Corporation | System, Method and Program Product for Providing Policy Hierarchy in an Enterprise Data Processing System |
| US9785477B2 (en) | 2006-06-05 | 2017-10-10 | International Business Machines Corporation | Providing a policy hierarchy in an enterprise data processing system |
| US8156082B2 (en) * | 2006-10-06 | 2012-04-10 | Sybase, Inc. | System and methods for temporary data management in shared disk cluster |
| US20080086480A1 (en) * | 2006-10-06 | 2008-04-10 | Sybase, Inc. | System and Methods For Temporary Data Management in Shared Disk Cluster |
| US7929552B2 (en) | 2006-10-26 | 2011-04-19 | At&T Intellectual Property I, L.P. | Automated IP pool management |
| US20080215756A1 (en) * | 2007-02-06 | 2008-09-04 | Samsung Electronics Co., Ltd. | Electronic device, management server, and control method thereof |
| US8271684B2 (en) * | 2007-02-06 | 2012-09-18 | Samsung Electronics Co., Ltd. | Electronic device, management server, and control method thereof for checking an IP address |
| US8898277B2 (en) * | 2007-06-08 | 2014-11-25 | Oracle International Corporation | Performance monitoring infrastructure for distributed transaction service |
| US20080306712A1 (en) * | 2007-06-08 | 2008-12-11 | Bea Systems, Inc. | Performance Monitoring Infrastructure for Distributed Transaction Service |
| US20090083439A1 (en) * | 2007-09-20 | 2009-03-26 | Konica Minolta Business Technologies, Inc. | Data transmission device, data transmission system and address registration method |
| US8180850B2 (en) * | 2007-09-20 | 2012-05-15 | Konica Minolta Business Technologies, Inc. | Data transmission device, data transmission system and address registration method |
| US20090089360A1 (en) * | 2007-09-28 | 2009-04-02 | Microsoft Corporation | Central Service Control |
| US8903969B2 (en) | 2007-09-28 | 2014-12-02 | Microsoft Corporation | Central service control |
| US20090094381A1 (en) * | 2007-10-05 | 2009-04-09 | Cisco Technology, Inc. | Modem prioritization and registration |
| US7962649B2 (en) * | 2007-10-05 | 2011-06-14 | Cisco Technology, Inc. | Modem prioritization and registration |
| US8112535B2 (en) | 2007-11-30 | 2012-02-07 | Microsoft Corporation | Securing a server in a dynamic addressing environment |
| US20090144437A1 (en) * | 2007-11-30 | 2009-06-04 | Microsoft Corporation | Securing a Server in a Dynamic Addressing Environment |
| US20100241668A1 (en) * | 2009-03-17 | 2010-09-23 | Microsoft Corporation | Local Computer Account Management at Domain Level |
| US10482475B2 (en) | 2011-02-10 | 2019-11-19 | Adp Dealer Services, Inc. | Systems and methods for providing targeted advertising |
| US9813503B2 (en) * | 2011-06-30 | 2017-11-07 | Mitsubishi Electric Corporation | IP-address distribution system utilizing a plurality of switching devices grouped into two or more groups |
| US8868701B1 (en) | 2011-08-16 | 2014-10-21 | Edgecast Networks, Inc. | Configuration management repository for a federation of distributed platforms |
| US8583769B1 (en) | 2011-08-16 | 2013-11-12 | Edgecast Networks, Inc. | Configuration management repository for a distributed platform |
| US9009277B2 (en) | 2011-08-16 | 2015-04-14 | Edgecast Networks, Inc. | Configuration management repository for a distributed platform |
| US11080734B2 (en) | 2013-03-15 | 2021-08-03 | Cdk Global, Llc | Pricing system for identifying prices for vehicles offered by vehicle dealerships and other entities |
| US10091158B2 (en) * | 2013-08-29 | 2018-10-02 | Mastercard International Incorporated | Systems and methods for resolving data inconsistencies between domain name systems |
| US9680790B2 (en) | 2013-08-29 | 2017-06-13 | Mastercard International Incorporated | Systems and methods for resolving data inconsistencies between domain name systems |
| US10332068B2 (en) | 2016-04-21 | 2019-06-25 | Cdk Global, Llc | Systems and methods for stocking an automobile |
| US10853769B2 (en) | 2016-04-21 | 2020-12-01 | Cdk Global Llc | Scheduling an automobile service appointment in a dealer service bay based on diagnostic trouble codes and service bay attributes |
| US10867285B2 (en) | 2016-04-21 | 2020-12-15 | Cdk Global, Llc | Automatic automobile repair service scheduling based on diagnostic trouble codes and service center attributes |
| US10326858B2 (en) | 2017-05-23 | 2019-06-18 | Cdk Global, Llc | System and method for dynamically generating personalized websites |
| US11190608B2 (en) | 2018-03-21 | 2021-11-30 | Cdk Global Llc | Systems and methods for an automotive commerce exchange |
| US11501351B2 (en) | 2018-03-21 | 2022-11-15 | Cdk Global, Llc | Servers, systems, and methods for single sign-on of an automotive commerce exchange |
| US11616856B2 (en) | 2018-03-21 | 2023-03-28 | Cdk Global, Llc | Systems and methods for an automotive commerce exchange |
| US12020217B2 (en) | 2020-11-11 | 2024-06-25 | Cdk Global, Llc | Systems and methods for using machine learning for vehicle damage detection and repair cost estimation |
| US11080105B1 (en) | 2020-11-18 | 2021-08-03 | Cdk Global, Llc | Systems, methods, and apparatuses for routing API calls |
| US11514021B2 (en) | 2021-01-22 | 2022-11-29 | Cdk Global, Llc | Systems, methods, and apparatuses for scanning a legacy database |
| US12045212B2 (en) | 2021-04-22 | 2024-07-23 | Cdk Global, Llc | Systems, methods, and apparatuses for verifying entries in disparate databases |
| US11803535B2 (en) | 2021-05-24 | 2023-10-31 | Cdk Global, Llc | Systems, methods, and apparatuses for simultaneously running parallel databases |
| US11983145B2 (en) | 2022-08-31 | 2024-05-14 | Cdk Global, Llc | Method and system of modifying information on file |
Also Published As
| Publication number | Publication date |
|---|---|
| CA2348490A1 (en) | 2000-05-11 |
| AU1071300A (en) | 2000-05-22 |
| US20020052876A1 (en) | 2002-05-02 |
| WO2000026806A3 (en) | 2000-10-19 |
| WO2000026806A2 (en) | 2000-05-11 |
| EP1145498A2 (en) | 2001-10-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6564216B2 (en) | 2003-05-13 | Server manager |
| US6374295B2 (en) | 2002-04-16 | Active server management |
| US6654891B1 (en) | 2003-11-25 | Trusted network binding using LDAP (lightweight directory access protocol) |
| US9154557B2 (en) | 2015-10-06 | Automatic proxy registration and discovery in a multi-proxy communication system |
| US6427170B1 (en) | 2002-07-30 | Integrated IP address management |
| US7185079B1 (en) | 2007-02-27 | Automated management of network addresses in a broadband managed access environment |
| EP1079583B1 (en) | 2007-02-14 | Method and system for optimizing performance and availability of a dynamic host configuration protocol (DHCP) service |
| US6292838B1 (en) | 2001-09-18 | Technique for automatic remote media access control (MAC) layer address resolution |
| US7509428B2 (en) | 2009-03-24 | Method and system for communicating between clients in a computer network |
| CN1985470B (en) | 2014-07-09 | System, network entities for configuration management of a dynamic host configuration protocol framework |
| EP1125421B1 (en) | 2006-06-14 | Dns relay module in a digital network modem |
| US20090299791A1 (en) | 2009-12-03 | Method and system for management of licenses |
| US7991856B2 (en) | 2011-08-02 | Network system |
| EP0918412A2 (en) | 1999-05-26 | Automatic discovery of networked devices |
| US20100202462A1 (en) | 2010-08-12 | Dynamically transitioning static network addresses |
| WO2001014989A1 (en) | 2001-03-01 | Architecture for a network management service which identifies and locates users and/or devices within an enterprise network |
| KR100527794B1 (en) | 2005-11-09 | system for interceptting an acces of a network and method thereof |
| CN114124894B (en) | 2025-01-10 | A streaming media server access method, device, equipment and storage medium |
| Cisco | 2002-08-06 | Chapter 2: Cisco ACNS Software Commands |
| Cisco | 1997-12-20 | Routing AppleTalk |
| Cisco | 1996-10-02 | Routing AppleTalk |
| Cisco | 1996-10-02 | Routing AppleTalk |
| Cisco | 1996-10-02 | Routing AppleTalk |
| Cisco | 1996-10-02 | Routing AppleTalk |
| Cisco | 1996-10-02 | Routing AppleTalk |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 1999-11-22 | AS | Assignment |
Owner name: NORTEL NETWORKS CORPORATION, CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WATERS, GLENN;REEL/FRAME:010421/0092 Effective date: 19991104 |
| 2000-08-30 | AS | Assignment |
Owner name: NORTEL NETWORKS LIMITED, CANADA Free format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:011195/0706 Effective date: 20000830 Owner name: NORTEL NETWORKS LIMITED,CANADA Free format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:011195/0706 Effective date: 20000830 |
| 2002-12-04 | FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
| 2003-04-24 | STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
| 2006-10-23 | FPAY | Fee payment |
Year of fee payment: 4 |
| 2009-12-05 | FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
| 2010-02-04 | AS | Assignment |
Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT,NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023892/0500 Effective date: 20100129 Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023892/0500 Effective date: 20100129 |
| 2010-02-05 | AS | Assignment |
Owner name: CITICORP USA, INC., AS ADMINISTRATIVE AGENT, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023905/0001 Effective date: 20100129 Owner name: CITICORP USA, INC., AS ADMINISTRATIVE AGENT,NEW YO Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023905/0001 Effective date: 20100129 Owner name: CITICORP USA, INC., AS ADMINISTRATIVE AGENT, NEW Y Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023905/0001 Effective date: 20100129 |
| 2010-02-26 | AS | Assignment |
Owner name: AVAYA INC.,NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:023998/0878 Effective date: 20091218 Owner name: AVAYA INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:023998/0878 Effective date: 20091218 |
| 2010-10-25 | FPAY | Fee payment |
Year of fee payment: 8 |
| 2011-01-19 | AS | Assignment |
Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:025662/0487 Effective date: 20110119 Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITICORP USA, INC.;REEL/FRAME:025662/0794 Effective date: 20110119 |
| 2011-01-25 | AS | Assignment |
Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:025690/0963 Effective date: 20110119 Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITICORP USA, INC.;REEL/FRAME:025691/0157 Effective date: 20110119 |
| 2011-02-03 | AS | Assignment |
Owner name: INFOBLOX INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AVAYA INC.;REEL/FRAME:025742/0258 Effective date: 20110118 |
| 2011-02-22 | AS | Assignment |
Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLAT Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535 Effective date: 20110211 Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE, PENNSYLVANIA Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535 Effective date: 20110211 |
| 2011-11-10 | AS | Assignment |
Owner name: AVAYA INC., NEW JERSEY Free format text: PATENT RELEASE (PARTIAL) 1ST CASH FLOW;ASSIGNOR:CITIBANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:027207/0180 Effective date: 20110119 Owner name: AVAYA INC., NEW JERSEY Free format text: PATENT RELEASE (PARTIAL) (2ND ABL);ASSIGNOR:CITICORP USA, INC., AS ADMINISTRATIVE AGENT;REEL/FRAME:027207/0230 Effective date: 20110119 |
| 2012-01-06 | AS | Assignment |
Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:027490/0461 Effective date: 20111206 |
| 2014-11-13 | FPAY | Fee payment |
Year of fee payment: 12 |
| 2016-11-07 | AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: FIRST LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:INFOBLOX INC.;REEL/FRAME:040575/0549 Effective date: 20161107 |
| 2016-11-08 | AS | Assignment |
Owner name: ROYAL BANK OF CANADA, AS COLLATERAL AGENT, CANADA Free format text: SECOND LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:INFOBLOX INC.;REEL/FRAME:040579/0302 Effective date: 20161107 |
| 2017-01-27 | AS | Assignment |
Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS INC.;OCTEL COMMUNICATIONS CORPORATION;AND OTHERS;REEL/FRAME:041576/0001 Effective date: 20170124 |
| 2017-12-15 | AS | Assignment |
Owner name: OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION), CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INTEGRATED CABINET SOLUTIONS INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST, NA;REEL/FRAME:044892/0001 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 023892/0500;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044891/0564 Effective date: 20171128 Owner name: OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INTEGRATED CABINET SOLUTIONS INC., CALIFORNI Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: VPNET TECHNOLOGIES, INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 |
| 2018-01-10 | AS | Assignment |
Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:045034/0001 Effective date: 20171215 Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW Y Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:045034/0001 Effective date: 20171215 |
| 2018-01-11 | AS | Assignment |
Owner name: AVAYA, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITICORP USA, INC.;REEL/FRAME:045045/0564 Effective date: 20171215 Owner name: SIERRA HOLDINGS CORP., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITICORP USA, INC.;REEL/FRAME:045045/0564 Effective date: 20171215 |
| 2018-01-23 | AS | Assignment |
Owner name: CITIBANK, N.A., AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:045124/0026 Effective date: 20171215 |
| 2019-10-23 | AS | Assignment |
Owner name: INFOBLOX, INC., CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS (RELEASES RF 040579/0302);ASSIGNOR:ROYAL BANK OF CANADA, AS COLLATERAL AGENT;REEL/FRAME:050809/0980 Effective date: 20191018 |
| 2020-12-03 | AS | Assignment |
Owner name: INFOBLOX INC., CALIFORNIA Free format text: RELEASE OF FIRST LIEN SECURITY INTEREST IN PATENTS (RELEASES RF 040575/0549);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:054585/0914 Effective date: 20201201 |
| 2023-04-26 | AS | Assignment |
Owner name: AVAYA INTEGRATED CABINET SOLUTIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001 Effective date: 20230403 Owner name: AVAYA MANAGEMENT L.P., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001 Effective date: 20230403 Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001 Effective date: 20230403 Owner name: AVAYA HOLDINGS CORP., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001 Effective date: 20230403 |
| 2023-05-18 | AS | Assignment |
Owner name: AVAYA MANAGEMENT L.P., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: CAAS TECHNOLOGIES, LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: HYPERQUALITY II, LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: HYPERQUALITY, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.), NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: VPNET TECHNOLOGIES, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: OCTEL COMMUNICATIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: AVAYA INTEGRATED CABINET SOLUTIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: INTELLISIST, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622 Effective date: 20230501 |