New! View global litigation for patent families

US20020010767A1 - Server manager for a configuration database and method therefor - Google Patents

Server manager for a configuration database and method therefor Download PDF

Info

Publication number
US20020010767A1
US20020010767A1 US09183537 US18353798A US2002010767A1 US 20020010767 A1 US20020010767 A1 US 20020010767A1 US 09183537 US09183537 US 09183537 US 18353798 A US18353798 A US 18353798A US 2002010767 A1 US2002010767 A1 US 2002010767A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
server
manager
servers
database
dhcp
Prior art date
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.)
Granted
Application number
US09183537
Other versions
US6374295B2 (en )
Inventor
Tony Farrow
Ian Hamilton
Glenn Waters
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Infoblox Inc
Original Assignee
Nortel Networks Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12207Address allocation
    • H04L29/12216Internet Protocol [IP] addresses
    • H04L29/12235Internet Protocol [IP] addresses using the Bootstrap Protocol [BOOTP] or variants
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12207Address allocation
    • H04L29/12216Internet Protocol [IP] addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12207Address allocation
    • H04L29/12301Address allocation involving update or notification mechanisms, e.g. update of a Domain Name Server with Dynamic Host Configuration Protocol [DHCP] assigned addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2007Address allocation internet protocol [IP] addresses
    • H04L61/2015Address allocation internet protocol [IP] addresses using the dynamic host configuration protocol [DHCP] or variants
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2007Address allocation internet protocol [IP] addresses
    • H04L61/2023Address allocation internet protocol [IP] addresses using the bootstrap protocol [BOOTP] or variants
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2076Address allocation involving update or notification mechanisms, e.g. update of a domain name server with dynamic host configuration protocol [DHCP] assigned addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12047Directories; name-to-address mapping
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping

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

    BACKGROUND OF THE INVENTION
  • [0001]
    1. Field of the Invention
  • [0002]
    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.
  • [0003]
    2. Description of the Related Art
  • [0004]
    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) network 101 including one or more Domain Name Service (DNS) servers 102A-N, one or more Dynamic Host Configuration Protocol (DHCP) servers 103A-N and a central database 104. Typically, the one or more DNS servers 102A-N and DHCP servers 103A-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.
  • [0005]
    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
  • [0006]
    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
  • [0007]
    In mid-to large-scale networks, a significant number of transmissions between the central database 104 and the DNS servers 102A-N and DHCP servers 103A-N occur. Each DNS server 102A-N and DHCP server 103A-N must individually contact the central database 104 to obtain any configuration changes made to the network that were stored in the central database 104. If there are a large number of DNS servers 102A-N and DHCP servers 103A-N, for example 100, on the network, a bandwidth issue is created at the central database 104.
  • [0008]
    Therefore, it would be useful to provide an improved means of communicating between a database and one or more servers.
  • SUMMARY OF THE INVENTION
  • [0009]
    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) 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 DRAWINGS
  • [0010]
    [0010]FIG. 1 is an overall diagram of a conventional TCP/IP network.
  • [0011]
    [0011]FIG. 2 is an overall diagram of a TCP/IP network as may implement the present invention.
  • [0012]
    [0012]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.
  • [0013]
    [0013]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.
  • [0014]
    [0014]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.
  • [0015]
    [0015]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.
  • [0016]
    [0016]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.
  • [0017]
    [0017]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.
  • [0018]
    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 INVENTION
  • [0019]
    [0019]FIG. 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.
  • [0020]
    In the described embodiment, the network includes a server manager 201, one or more DNS servers 202A-N, one or more DHCP servers 203A-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 202A-N and DHCP servers 203A-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. However, in alternative networks, the LDAP server 209 can communicate directly with the central database 204.
  • [0021]
    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. In the described embodiment, 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. Since changes in configuration in the network are stored in the delta-logging facility, audit records can be kept accurately and 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.
  • [0022]
    In the described embodiment, the one or more DNS servers 202A-N are Berkeley Internet Name Domain (BIND) 4.9.5 DNS servers, BIND 8.1.1 DNS servers or the like. These servers 202A-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 202A-N to the server manager 201 enable dynamic DNS updates and dynamic DNS reconfiguration. In the described embodiment, the one or more DHCP servers 203A-N are based on the BootP. These servers 203A-N also communicate with the server manager 201 through a TCP link and update the central database 204 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.
  • [0023]
    The server manager 201, DNS 202A-N and DHCP 203A-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
  • [0024]
    In the described embodiment, the DNS servers 202A-N and DHCP servers 203A-N must first login with the server manager 201. If the login process is successful, the servers 202A-N, 203A-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 202A-N, 203A-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.
  • [0025]
    [0025]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. First, the one or more DNS servers 202A-N and DHCP servers 203A-N establish a TCP link to the server manager 201, step 301. Next, each server 202A-N, 203A-N issues a login request by providing a userid and a password to the server manager 201, step 302. The password for each server 202A-N, 203A-N is only known by each individual server and the server manager 201.4 The server manager 201 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, step 303. If the password is correct, the server, for example a DNS server 202A, 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 202A must reinitiate a TCP link to the server manager 201 and start the login process from the beginning, step 301.
  • [0026]
    After logging in with the server manager 201, each DNS server 202A-N and DHCP server 203A-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.
  • [0027]
    Once the DNS servers 202A-N and DHCP servers 203A-N establish a link with the server manager 201, 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 202A-N and DHCP servers 203A-N on the network from a single point and acts as a single pipeline to the central database 204. For example, when a new client 208 sends a request for an IP address to a DHCP server 203A, the DHCP server 203A determines if it can send configuration information to the requesting client 208. If the DHCP server 203A 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 203A 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 202A detects the new IP address through the server manager and updates its DNS information. When the lease expires or the client 208 leaves the network and releases the IP address, the DHCP server 203A notifies the central database 204 of the change through the server manager 201. The IP address is available for reassignment by the DHCP server 203A to a new client. Therefore, the server manager 201 eliminates the need for the individual DNS servers 202A-N and DHCP servers 203A-N to establish direct communication channels with the central database by providing access to the central database 204 through one communication channel 206. (more????)
  • [0028]
    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.
  • [0029]
    [0029]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 203A.5 When the server manger 201 receives a request for configuration information from a DHCP server 203A, 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 203A, step 404. It then builds a subnet list associated with the DHCP server 203A based on the range and host lists, step 405. Finally, it builds a network list associated with the DHCP server 203A based on the subnet list, step 406. The server manager 201 then requests the configuration information from the central database 204 based on the lists provided by the DHCP server 203A 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 203A requesting the configuration information, step 409. 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 database 204 by the DHCP servers 203A-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 203A-N that needs configuration information from the central database 204.
  • [0030]
    The server manager 201 also notifies each DHCP server 203A-N of any changes to the central database 201. Once the DHCP servers 203A-N have logged in with the server manager 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 203A-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 203A-N servers coupled in communication with the server manager 201. Once at least one of the DHCP servers 203A-N is communicating 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 203A-N, step 503.8 Depending on what configuration changes occurred in the network, the server manager 201 retrieves the appropriate information, step 504 and distributes it to the appropriate DHCP 203A-N servers.9 If the server manager 201 finds no changes or has completed distributing the changes to the DHCP server 203A-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 203A-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.
  • [0031]
    The server manager 201 also processes host commit requests from DHCP servers 203A-N.10 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. Upon receiving a request from a DHCP server 203A 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 203A that the domain is unavailable.11 If the domain does not exist in the central database 204, the label12 may be assigned to the host and the server manager 201 notifies the DHCP server 203A 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 database 204 that owns the label, the label may be assigned to the requesting host and the server manager notifies the DHCP server 203A 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 203A that the domain is unavailable. If the IP addresses match, the label is updated and the server manager 201 notifies the DHCP server 203A 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 203A 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 manager 201 notifies the DHCP server 203A 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 203A that the host commit failed, otherwise the server manager 201 notifies the DHCP server 203A that the host has been committed and transmits the host information to the central database 204.
  • [0032]
    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 202A.14 When the server manager 201 receives a configuration update message from a DNS server 202A, 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. However, if the server id is a valid domain name and the version number is valid, the server manager 201 receives the primary and secondary zones managed by the DNS server 202A, step 604. The server manager 201 then issues a configuration update request for each zone managed by the DNS server 202A 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. 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 202A.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 202A. For each secondary zone, the server manager 201 sends that zone transfer list to the DNS server 202A. Finally, the server manager 201 sends information about the root server on the network to the DNS server 202A.17
  • [0033]
    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 202A-N. The process of polling the delta-logging facility in the central database 204 for the DNS servers 202A-N is similar to the process previously described in FIG. 5 for the DHCP servers 203A-N. However, 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 203A-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 database 204 for changes since the only server manager 201 is coupled in communication with the central database 204.
  • [0034]
    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.
  • [0035]
    The server manager 201 also has the ability to actively manage the DNS 202A to 202N and DHCP 203A-N servers and report their operational status to the NMS 205. In the described embodiment, 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 202A-N and DHCP 203A-N servers that are linked with the server manager 201. In one embodiment, the NMS 205 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 DNS 202A-N and DHCP 203A-N servers on the network and transmitting the status information to the NMS 205. 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.21 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. These traps can then be viewed from the GUI by the network administrator. 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.
  • [0036]
    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 client 208 requests an IP address from the DHCP server 203N on the network, step 801. The DHCP server 203N 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 203N 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. 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 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 203N 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. In the described embodiment, the binding server 209 communicates with the server manager 201 over a single channel 211 to store the credentials in the central database 204. However, 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.
  • [0037]
    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.
  • [0038]
    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 (10)

    What is claimed is:
  1. 1. An network comprising one or more servers coupled in communication with a server manager.
  2. 2. An network as recited by claim 1 further comprising a Network Management Station (NMS) coupled in communication with the server manager.
  3. 3. An network as recited by claim 1 wherein the server manager communicates with the one or more servers through a TCP/IP connection.
  4. 4. An network as recited by claim 1 wherein the server manager queries the one or more servers to determine the operational status of the one or more servers.
  5. 5. An network as recited by claim 2 wherein the NMS receives SNMP traps containing the operational status of the one or more servers from the server manager.
  6. 6. An network as recited by claim 5 wherein the SNMP traps notify the NMS when:
    (a) the one or more servers starts executing;
    (b) the one or more servers stops executing; or
    (c) there is an invalid login from the one or more servers.
  7. 7. A method for ascertaining the operational state of one or more servers in an network through a server manager comprising the steps of:
    (a) communicating by the one or more servers with the server manager to identify itself;
    (b) actively querying the one or more servers by the server manager to determine the operational status of the one or more servers.
  8. 8. The method as recited by claim 7 wherein the one or more servers communicates with the server manager through a TCP/IP connection.
  9. 9. The method as recited by claim 7 further comprising the step of receiving at a NMS the operational status of the one or more servers from the server manager through an SNMP trap.
  10. 10. The method as recited by claim 9 wherein the SNMP trap notifies the NMS when:
    (a) the one or more servers starts executing;
    (b) the one or more servers stops executing; or
    (c) there is an invalid login from the one or more servers.
US09183537 1998-10-29 1998-10-29 Active server management Active US6374295B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09183537 US6374295B2 (en) 1998-10-29 1998-10-29 Active server management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09183537 US6374295B2 (en) 1998-10-29 1998-10-29 Active server management
PCT/IB1999/001878 WO2000026807A3 (en) 1998-10-29 1999-10-29 Active server management

Publications (2)

Publication Number Publication Date
US20020010767A1 true true US20020010767A1 (en) 2002-01-24
US6374295B2 US6374295B2 (en) 2002-04-16

Family

ID=22673228

Family Applications (1)

Application Number Title Priority Date Filing Date
US09183537 Active US6374295B2 (en) 1998-10-29 1998-10-29 Active server management

Country Status (2)

Country Link
US (1) US6374295B2 (en)
WO (1) WO2000026807A3 (en)

Cited By (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010032237A1 (en) * 2000-01-06 2001-10-18 Nobumasa Miyake Method of setting up internet server and method of setting information communication apparatus
US20020042721A1 (en) * 2000-10-05 2002-04-11 Alcatel Network management client
US20020091827A1 (en) * 2000-11-01 2002-07-11 Raymond King Domain name acquisition and management system and method
US6487594B1 (en) * 1999-11-30 2002-11-26 Mediaone Group, Inc. Policy management method and system for internet service providers
US20030074394A1 (en) * 2001-10-16 2003-04-17 Kave Eshghi Effectively and efficiently updating content files among duplicate content servers
US20040034705A1 (en) * 2002-08-13 2004-02-19 Mihai Focsaneanu Connecting devices in a data network
US20040083306A1 (en) * 2002-10-24 2004-04-29 International Business Machines Corporation Method and apparatus for maintaining internet domain name data
US20040172465A1 (en) * 1999-08-30 2004-09-02 Brian Shuster Method and system for redirecting a request to a server selected domain
US6836798B1 (en) * 2002-12-31 2004-12-28 Sprint Communications Company, L.P. Network model reconciliation using state analysis
US20050038889A1 (en) * 2003-08-15 2005-02-17 Thomas Frietsch Network server and method of discovery of a network node
US20050108408A1 (en) * 2003-10-27 2005-05-19 Nec Viewtechnology, Ltd. Method and apparatus for setting network
US20050289240A1 (en) * 2004-06-25 2005-12-29 Cheshire Stuart D Method and apparatus for updating resource records in a name-server database
US20060047792A1 (en) * 2000-11-02 2006-03-02 Microsoft Corporation Dynamically configuring a server computer
US20070033272A1 (en) * 2005-08-04 2007-02-08 Vasu Vallabhaneni Dynamic subnet updates
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
US20070291742A1 (en) * 2004-11-26 2007-12-20 Siemens Schweiz Ag Method for Configuring a Device Using Dhcp Via Pppoe
US20080040423A1 (en) * 2006-08-09 2008-02-14 Quanta Computer Inc. Method for detecting status of host and/or I/O peripherals in centralized computer system
US7389345B1 (en) 2003-03-26 2008-06-17 Sprint Communications Company L.P. Filtering approach for network system alarms
US7421493B1 (en) 2003-04-28 2008-09-02 Sprint Communications Company L.P. Orphaned network resource recovery through targeted audit and reconciliation
US20080244043A1 (en) * 2007-03-30 2008-10-02 Brother Kogyo Kabushiki Kaisha Network system and network device
US20080275992A1 (en) * 2005-02-09 2008-11-06 Access Systems Americas, Inc. System and method of managing connections between a computing system and an available network using a connection manager
US20090055354A1 (en) * 2005-05-11 2009-02-26 Saeed Arad Method and Apparatus for Searching
US20090248841A1 (en) * 2008-03-28 2009-10-01 Motorola, Inc. Unique prefix assignment with automatic address configuration
US20100217875A1 (en) * 2007-07-23 2010-08-26 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for use in a communications network
US20100257272A1 (en) * 2007-07-23 2010-10-07 Telefonaktiebolaget Lm Ericsson Method and apparatus for use in a communications network
CN102484784A (en) * 2009-09-02 2012-05-30 阿尔卡特朗讯 Notification within a wireless communication network using a dhcp server
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
USRE45445E1 (en) * 2002-11-06 2015-03-31 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement for preventing illegitimate use of IP addresses
US9444779B2 (en) 2012-06-04 2016-09-13 Microsoft Technology Lincensing, LLC Dynamic and intelligent DNS routing with subzones
US20160371158A1 (en) * 2014-09-30 2016-12-22 International Business Machines Corporation Multi-site disaster recovery consistency group for heterogeneous systems
US20170024288A1 (en) * 2015-07-20 2017-01-26 Bank Of America Corporation Centralized database system
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

Families Citing this family (61)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6564216B2 (en) * 1998-10-29 2003-05-13 Nortel Networks Limited Server manager
US7167904B1 (en) * 1999-03-19 2007-01-23 Network Solutions, Llc Unified web-based interface-to multiple registrar systems
WO2000065507A8 (en) * 1999-04-22 2001-11-15 Network Solutions Inc Business rule engine
US6587455B1 (en) * 1999-05-27 2003-07-01 Telefonaktiebolaget Lm Ericsson (Publ) Automatic discovery of nodes associated with a virtual subnet
US7251826B1 (en) 1999-06-07 2007-07-31 Register.Com, Inc. Domain manager for plural domains and method of use
US6708187B1 (en) * 1999-06-10 2004-03-16 Alcatel Method for selective LDAP database synchronization
US7032022B1 (en) 1999-06-10 2006-04-18 Alcatel Statistics aggregation for policy-based network
JP2003502757A (en) 1999-06-10 2003-01-21 アルカテル・インターネツトワーキング・インコーポレイテツド Policy-based network architecture
CA2281367C (en) * 1999-09-01 2002-12-17 Ibm Canada Limited-Ibm Canada Limitee Method and apparatus for simplified administration of large numbers of similar information handling servers
US6760324B1 (en) * 1999-09-10 2004-07-06 Array Telecom Corporation Method, system, and computer program product for providing voice over the internet communication
US6826690B1 (en) * 1999-11-08 2004-11-30 International Business Machines Corporation Using device certificates for automated authentication of communicating devices
US6823454B1 (en) * 1999-11-08 2004-11-23 International Business Machines Corporation Using device certificates to authenticate servers before automatic address assignment
DE69935339T2 (en) * 1999-12-02 2007-11-15 Sony Deutschland Gmbh Protocol for instant messaging
US6868444B1 (en) * 2000-05-05 2005-03-15 Interland, Inc. Server configuration management and tracking
US6842769B1 (en) * 2000-05-05 2005-01-11 Interland, Inc. Automatically configured network server
US7962603B1 (en) 2000-06-06 2011-06-14 Nobuyoshi Morimoto System and method for identifying individual users accessing a web site
WO2002005510A1 (en) * 2000-07-11 2002-01-17 Nokia Corporation Method for providing a dns server address list from a server to a client
US6895431B1 (en) * 2000-09-29 2005-05-17 Interland, Inc. Providing user access to dynamic updating of remote configuration information
US6920506B2 (en) 2001-06-28 2005-07-19 Canon Information Systems, Inc. Discovery and management of network printers
US7454482B2 (en) 2001-06-28 2008-11-18 Canon Information Systems, Inc. Print queue manager
JP2003052660A (en) * 2001-07-25 2003-02-25 Ge Medical Systems Global Technology Co Llc Method for registering protocol/medical image, method for providing medical image, method for utilizing protocol, protocol/medical image registering system, medical image providing system, protocol utilizing system, vender terminal equipment, user terminal equipment and protocol managing server apparatus
US20030055961A1 (en) * 2001-09-20 2003-03-20 Minoru Torii Network device management apparatus, management system, and management method, and network device
US7416858B2 (en) * 2001-10-10 2008-08-26 Neose Technologies, Inc. Pharmaceutical compositions of glycoconjugates
WO2003050648A3 (en) * 2001-11-12 2004-07-08 Worldcom Inc System and method for implementing frictionless micropayments for consumable services
US7519729B2 (en) * 2002-02-27 2009-04-14 Ricoh Co. Ltd. Method and apparatus for monitoring remote devices through a local monitoring station and communicating with a central station supporting multiple manufacturers
US20050235000A1 (en) * 2002-03-27 2005-10-20 Wolfgang Keil Aaa server system for efficient control and address assignment
WO2003090428A1 (en) * 2002-04-19 2003-10-30 Nagravision Sa Method for the transmission of management messages in an ip network broadcasting system
US7600003B1 (en) * 2002-04-22 2009-10-06 Cisco Technology, Inc. Method and apparatus for dynamically configuring customer premises network equipment
KR100505221B1 (en) * 2002-07-03 2005-08-03 엘지전자 주식회사 Remote Control System of Home Appliance Network and Its Operating Method for the same
US7143435B1 (en) 2002-07-31 2006-11-28 Cisco Technology, Inc. Method and apparatus for registering auto-configured network addresses based on connection authentication
DE10329858A1 (en) * 2003-07-02 2005-01-27 Siemens Ag Method for configuration of a device in a data network
US7254591B2 (en) * 2003-07-11 2007-08-07 Via Technologies, Inc. Method and apparatus for synchronous updating of multiple language web content
US7519988B2 (en) * 2003-07-31 2009-04-14 International Business Machines Corporation Method and apparatus for authenticated network address allocation
US8254896B2 (en) * 2003-08-25 2012-08-28 Research In Motion Limited Implementing a web server on a mobile station
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
US7181653B2 (en) * 2003-12-11 2007-02-20 Lenovo Singapore Pte, Ltd Method for establishing network connections
US20050144287A1 (en) * 2003-12-11 2005-06-30 International Business Machines Corporation Computer product and system for establishing network connections
US20050128952A1 (en) * 2003-12-11 2005-06-16 International Business Machines Corporation Executing and implementing a service for establishing network connections
US7865617B1 (en) * 2004-06-10 2011-01-04 Infoblox Inc. Maintaining consistency in a database
US20050234954A1 (en) * 2004-04-16 2005-10-20 Infoblox Maintaining data integrity in a distributed environment
US7940730B1 (en) * 2004-11-04 2011-05-10 At&T Mobility Ii Llc Network-initiated method and system for establishing data communication using IP with a wireless terminal
US20060250982A1 (en) * 2005-05-05 2006-11-09 Harrow Products Llc Methods and systems for discovering and configuring network devices
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
US20070061355A1 (en) * 2005-09-13 2007-03-15 International Business Machines Corporation Computer- implemented method, system, and program product for managing data for an information technology (IT) migration
US20070198993A1 (en) * 2006-02-06 2007-08-23 Zhongyao Zhang Communication system event handling systems and techniques
US20070282782A1 (en) * 2006-05-31 2007-12-06 Carey Julie M Method, system, and program product for managing information for a network topology change
US8862735B1 (en) * 2006-12-05 2014-10-14 Aol Inc. IP address management of multiple DHCP and DNS servers
US7694016B2 (en) * 2007-02-07 2010-04-06 Nominum, Inc. Composite DNS zones
US7694019B2 (en) * 2007-03-09 2010-04-06 International Business Machines Corporation System and method for accessing multiple addresses per domain name using networked repository
US7689671B2 (en) * 2007-03-09 2010-03-30 International Business Machines Corporation System and method for multiple IP addresses during domain name resolution
US8898277B2 (en) * 2007-06-08 2014-11-25 Oracle International Corporation Performance monitoring infrastructure for distributed transaction service
US9137093B1 (en) * 2007-07-02 2015-09-15 Comscore, Inc. Analyzing requests for data made by users that subscribe to a provider of network connectivity
US7962649B2 (en) * 2007-10-05 2011-06-14 Cisco Technology, Inc. Modem prioritization and registration
US8239422B2 (en) 2007-10-18 2012-08-07 At&T Intellectual Property I, Lp Methods and apparatus to provision network resource records
US20100281146A1 (en) * 2009-04-30 2010-11-04 Vivotek Inc. Dynamic domain name service system and automatic registration method
US7965630B1 (en) 2009-09-08 2011-06-21 Southern Company Services, Inc. Load balancing port proxy for dynamically controlling routing of query requests
US8510807B1 (en) 2011-08-16 2013-08-13 Edgecast Networks, Inc. Real-time granular statistical reporting for distributed platforms
US9736005B2 (en) 2011-12-22 2017-08-15 International Business Machines Corporation Duplicate IP address detection by a DHCP relay agent
US8972542B2 (en) * 2011-12-22 2015-03-03 International Business Machines Corporation Extending a DHCP relay to backup a DHCP server
US9680790B2 (en) 2013-08-29 2017-06-13 Mastercard International Incorporated Systems and methods for resolving data inconsistencies between domain name systems
JPWO2015122176A1 (en) * 2014-02-12 2017-03-30 日本電気株式会社 The information processing apparatus, a communication method, a network controller, a network control method, communication system and program

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4949248A (en) * 1988-07-15 1990-08-14 Caro Marshall A System for shared remote access of multiple application programs executing in one or more computers
US5287343A (en) * 1991-02-25 1994-02-15 Matsushita Electric Works, Ltd. Network administration system
EP0537903A2 (en) 1991-10-02 1993-04-21 International Business Machines Corporation Distributed control system
US5287461A (en) * 1991-10-31 1994-02-15 Sun Microsystems, Inc. Method and apparatus for remotely accessing a plurality of server consoles
US5600797A (en) * 1993-11-24 1997-02-04 Intel Corporation System for identifying new client and allocating bandwidth thereto by monitoring transmission of message received periodically from client computers informing of their current status
JP3521955B2 (en) 1994-06-14 2004-04-26 株式会社日立製作所 Hierarchical network management system
US5586304A (en) * 1994-09-08 1996-12-17 Compaq Computer Corporation Automatic computer upgrading
US6076107A (en) * 1995-05-09 2000-06-13 International Business Machines Corporation Method for reducing SNMP instrumentation message flows
US5581552A (en) * 1995-05-23 1996-12-03 At&T Multimedia server
US5748896A (en) * 1995-12-27 1998-05-05 Apple Computer, Inc. Remote network administration methods and apparatus
US5774660A (en) * 1996-08-05 1998-06-30 Resonate, Inc. World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network
US5996010A (en) * 1996-08-29 1999-11-30 Nortel Networks Corporation Method of performing a network management transaction using a web-capable agent
US5909549A (en) * 1996-11-12 1999-06-01 International Business Machines Corporation Network management system wherein the managed device reestablishes a connection to a management station after detecting a broken connection
US6006264A (en) * 1997-08-01 1999-12-21 Arrowpoint Communications, Inc. Method and system for directing a flow between a client and a server

Cited By (66)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
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
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
US7970937B2 (en) * 1999-08-30 2011-06-28 Brian Shuster Method and system for redirecting a request to a server-selected domain
US20040172465A1 (en) * 1999-08-30 2004-09-02 Brian Shuster Method and system for redirecting a request to a server selected domain
US6487594B1 (en) * 1999-11-30 2002-11-26 Mediaone Group, Inc. Policy management method and system for internet service providers
US20010032237A1 (en) * 2000-01-06 2001-10-18 Nobumasa Miyake Method of setting up internet server and method of setting information communication apparatus
US20020042721A1 (en) * 2000-10-05 2002-04-11 Alcatel Network management client
US7752260B2 (en) 2000-11-01 2010-07-06 Snapnames.Com, Inc. Domain name acquisition and management system and method
US8015244B2 (en) 2000-11-01 2011-09-06 Snapnames.Com, Inc. Domain name acquisition and management system and method
US20100115043A1 (en) * 2000-11-01 2010-05-06 Snapnames.Com, Inc. Demand based domain name auctionability
WO2002056132A3 (en) * 2000-11-01 2003-03-06 Snapnames.Com, Inc. Domain name acquisition and management system and method
US7606858B2 (en) 2000-11-01 2009-10-20 Snapnames.Com, Inc. Domain name acquisition and management system and method
US7627628B2 (en) 2000-11-01 2009-12-01 Snapnames.Com, Inc. Demand based domain name auctionability
WO2002056132A2 (en) * 2000-11-01 2002-07-18 Snapnames Com Inc Domain name acquisition and management system and method
US20060161683A1 (en) * 2000-11-01 2006-07-20 Snapnames.Com, Inc. Domain name acquisition and management system and method
US20060161682A1 (en) * 2000-11-01 2006-07-20 Snapnames.Com, Inc. Domain name acquisition and management system and method
US7039697B2 (en) 2000-11-01 2006-05-02 Snapnames.Com Inc. Registry-integrated internet domain name acquisition system
US20070083652A1 (en) * 2000-11-01 2007-04-12 Snapnames.Com, Inc. Demand based domain name auctionability
US20020091827A1 (en) * 2000-11-01 2002-07-11 Raymond King Domain name acquisition and management system and method
US7490124B2 (en) 2000-11-01 2009-02-10 Snapnames.Com, Inc. Domain name acquisition and management system and method
US7418471B2 (en) 2000-11-01 2008-08-26 Snapnames.Com, Inc. Domain name acquisition and management system and method
US20060047792A1 (en) * 2000-11-02 2006-03-02 Microsoft Corporation Dynamically configuring a server computer
US7287067B2 (en) * 2000-11-02 2007-10-23 Microsoft Corporation Dynamically configuring a server computer
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
US20040034705A1 (en) * 2002-08-13 2004-02-19 Mihai Focsaneanu Connecting devices in a data network
US7734745B2 (en) * 2002-10-24 2010-06-08 International Business Machines Corporation Method and apparatus for maintaining internet domain name data
US20040083306A1 (en) * 2002-10-24 2004-04-29 International Business Machines Corporation Method and apparatus for maintaining internet domain name data
USRE45445E1 (en) * 2002-11-06 2015-03-31 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement for preventing illegitimate use of IP addresses
US6836798B1 (en) * 2002-12-31 2004-12-28 Sprint Communications Company, L.P. Network model reconciliation using state analysis
US7389345B1 (en) 2003-03-26 2008-06-17 Sprint Communications Company L.P. Filtering approach for network system alarms
US7421493B1 (en) 2003-04-28 2008-09-02 Sprint Communications Company L.P. Orphaned network resource recovery through targeted audit and reconciliation
US8260916B2 (en) * 2003-08-15 2012-09-04 Hewlett-Packard Development Company, L.P. Network server and method of discovery of a network node
US20050038889A1 (en) * 2003-08-15 2005-02-17 Thomas Frietsch Network server and method of discovery of a network node
US20050108408A1 (en) * 2003-10-27 2005-05-19 Nec Viewtechnology, Ltd. Method and apparatus for setting network
US7702793B2 (en) * 2003-10-27 2010-04-20 Nec Display Solutions, Ltd. Method and apparatus for setting network using DHCP server or client function
US20050289240A1 (en) * 2004-06-25 2005-12-29 Cheshire Stuart D Method and apparatus for updating resource records in a name-server database
US8156081B2 (en) * 2004-06-25 2012-04-10 Apple Inc. Method and apparatus for updating resource records in a name-server database
US20070291742A1 (en) * 2004-11-26 2007-12-20 Siemens Schweiz Ag Method for Configuring a Device Using Dhcp Via Pppoe
US20080275992A1 (en) * 2005-02-09 2008-11-06 Access Systems Americas, Inc. System and method of managing connections between a computing system and an available network using a connection manager
US8260820B2 (en) * 2005-05-11 2012-09-04 Royce Technology Ltd. Method and apparatus for searching
US20090055354A1 (en) * 2005-05-11 2009-02-26 Saeed Arad Method and Apparatus for Searching
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
US20080040423A1 (en) * 2006-08-09 2008-02-14 Quanta Computer Inc. Method for detecting status of host and/or I/O peripherals in centralized computer system
US7590730B2 (en) * 2006-09-08 2009-09-15 Quanta Computer, Inc. Method for detecting status of host and/or I/O peripherals in centralized computer system
US7827277B2 (en) * 2007-03-30 2010-11-02 Brother Kogyo Kabushiki Kaisha Network system including device managing apparatus that manages network devices through a network
US20080244043A1 (en) * 2007-03-30 2008-10-02 Brother Kogyo Kabushiki Kaisha Network system and network device
US20100257272A1 (en) * 2007-07-23 2010-10-07 Telefonaktiebolaget Lm Ericsson Method and apparatus for use in a communications network
US20100217875A1 (en) * 2007-07-23 2010-08-26 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for use in a communications network
US8782208B2 (en) * 2007-07-23 2014-07-15 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for use in a communications network
US20090248841A1 (en) * 2008-03-28 2009-10-01 Motorola, Inc. Unique prefix assignment with automatic address configuration
US20120231831A1 (en) * 2009-09-02 2012-09-13 Telemaco Melia Notification within a wireless communication network
KR101456436B1 (en) * 2009-09-02 2014-10-31 알까뗄 루슨트 Notification within a wireless communication network using a dhcp server
US8811995B2 (en) * 2009-09-02 2014-08-19 Alcatel Lucent Notification within a wireless communication network
CN102484784A (en) * 2009-09-02 2012-05-30 阿尔卡特朗讯 Notification within a wireless communication network using a dhcp server
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
US9438698B2 (en) 2011-03-31 2016-09-06 Belkin International, Inc. Method of distributing information regarding one or more electrical devices and system for the same
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
US9444779B2 (en) 2012-06-04 2016-09-13 Microsoft Technology Lincensing, LLC Dynamic and intelligent DNS routing with subzones
US20160371158A1 (en) * 2014-09-30 2016-12-22 International Business Machines Corporation Multi-site disaster recovery consistency group for heterogeneous systems
US20170024288A1 (en) * 2015-07-20 2017-01-26 Bank Of America Corporation Centralized database system
US9703646B2 (en) * 2015-07-20 2017-07-11 Bank Of America Corporation Centralized database system

Also Published As

Publication number Publication date Type
US6374295B2 (en) 2002-04-16 grant
WO2000026807A3 (en) 2000-08-31 application
WO2000026807A2 (en) 2000-05-11 application

Similar Documents

Publication Publication Date Title
Guttman Service location protocol: Automatic discovery of IP network services
US6654796B1 (en) System for managing cluster of network switches using IP address for commander switch and redirecting a managing request via forwarding an HTTP connection to an expansion switch
US6412007B1 (en) Mechanism for authorizing a data communication session between a client and a server
US7073055B1 (en) System and method for providing distributed and dynamic network services for remote access server users
US6606315B1 (en) Synchronizing service instructions among forwarding agents using a service manager
US7725602B2 (en) Domain name resolution using a distributed DNS network
US6687222B1 (en) Backup service managers for providing reliable network services in a distributed environment
US6697862B1 (en) System and method for network address maintenance using dynamic host configuration protocol messages in a data-over-cable system
US5862348A (en) Method and apparatus for connecting a client node to a server node based on load levels
US7200673B1 (en) Determining the geographic location of a network device
US7051066B1 (en) Integrating service managers into a routing infrastructure using forwarding agents
US6351773B1 (en) Methods for restricting access of network devices to subscription services in a data-over-cable system
US7734745B2 (en) Method and apparatus for maintaining internet domain name data
US7000015B2 (en) System and methods for providing physical location information and a location method used in discovering the physical location information to an application on a computing device
US6189102B1 (en) Method for authentication of network devices in a data-over cable system
US6061739A (en) Network address assignment using physical address resolution protocols
US7346686B2 (en) Load balancing using distributed forwarding agents with application based feedback for different virtual machines
US7730187B2 (en) Remote domain name service
US6704278B1 (en) Stateful failover of service managers
US6912567B1 (en) Broadband multi-service proxy server system and method of operation for internet services of user's choice
US6826172B1 (en) Network probing using overlapping probe packets
US7103651B2 (en) Method and apparatus for discovering client proximity network sites
US6748434B2 (en) Adaptive node selection
US7127524B1 (en) System and method for providing access to a network with selective network address translation
US6735169B1 (en) Cascading multiple services on a forwarding agent

Legal Events

Date Code Title Description
AS Assignment

Owner name: NORTEL NETWORKS CORPORATION, CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FARROW, TONY;HAMILTON, IAN;WATERS, GLENN;REEL/FRAME:010421/0115;SIGNING DATES FROM 19991104 TO 19991117

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

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

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

AS Assignment

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

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

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

AS Assignment

Owner name: AVAYA INC., NEW JERSEY

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITICORP USA, INC.;REEL/FRAME:025691/0157

Effective date: 20110119

Owner name: AVAYA INC., NEW JERSEY

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:025690/0963

Effective date: 20110119

AS Assignment

Owner name: INFOBLOX INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AVAYA INC.;REEL/FRAME:025742/0134

Effective date: 20110118

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

AS Assignment

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

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

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

FPAY Fee payment

Year of fee payment: 12

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

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

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

AS Assignment

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: 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: 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

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: 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: 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

AS Assignment

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

AS Assignment

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

Owner name: AVAYA, INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITICORP USA, INC.;REEL/FRAME:045045/0564

Effective date: 20171215

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