Patent application number | Description | Published |
20090106404 | Method and Apparatus for Dynamically Configuring Virtual Internet Protocol Addresses - A host node connected to a network using an Internet Protocol automatically identifies multiple adapters connected to the same network, preferably by broadcasting a Dynamic Host Configuration Protocol (DHCP) request for assignment of an IP address on a first adapter, and listening to the request on a second adapter, thereby determining that both adapters are on the same network. The host preferably causes an IP address to be generated for one of the adapters, and automatically configures the adapters to share the IP address thus generated as a virtual IP address, assigning one of the adapters as a primary adapter. Preferably, the host automatically detects deactivation of the primary adapter and switches the virtual address assignment to a different adapter. | 04-23-2009 |
20100306378 | AUTOMATIC PORT CONFLICT RESOLUTION DURING APPLICATION DEPLOYMENT - Systems, methods and articles of manufacture are disclosed for identifying and resolving port conflicts during application deployment. The port conflicts may be identified based on application documentation and active port information. The port conflicts may be resolved by identifying an available port and providing information about the available port to a conflicting application. The port conflicts may also be resolved by identifying an available IP address and providing a port on the available IP address to a conflicting application. Further, if conflicting applications allow port sharing, the port conflicts may be resolved by providing port sharing information to the conflicting applications. | 12-02-2010 |
20110010413 | TCP/IP HOST NAME RESOLUTION ON A PRIVATE NETWORK - Systems, methods and articles of manufacture are disclosed for resolving hostnames on a private network with a distributed DNS server configuration. One embodiment of the invention provides for a client resolver configured to communicate with a distributed network of servers. The client resolver receives a hostname query and determines if the hostname query is of the type single lablel hostname or fully qualified hostname. If the hostname query received is of the type fully qualified hostname, the client resolver routes the hostname query to a server with a longest matching domain suffix. If the hostname query received is of the type single label hostname the client resolver generates one or more new fully qualified hostnames and routes the hostname query to each server on the private network. | 01-13-2011 |
20110010437 | NETWORK DEVICE CONFIGURATION - Systems, methods and articles of manufacture are disclosed for configuring a network device on a private network. A network device broadcasts a status message to the private network. The network device receives a request from a client and sends a response. The network device and the client establish a direct message route wherein one or more network configuration settings are exchanged between the client computer and the network device. | 01-13-2011 |
20110010463 | PROPOGATION OF DNS SERVER IP ADDRESSES IN A PRIVATE NETWORK - Systems, methods and articles of manufacture are disclosed for updating IP addresses on a private network. A DNS server receives an updated IP address and stores both the updated IP address and an old IP address. The DNS server includes the updated IP address in responses to all DNS query requests, wherein the DNS query requests are to the old IP address. Further, the DNS server deletes the old IP address and updates the DNS server network settings with the updated IP address after every remote client on the private network has stored the updated IP address. | 01-13-2011 |
20110055374 | COMPUTER IMPLEMENTED DNS SERVER IP ADDRESS LOOKUP MECHANISM - Systems, methods and articles of manufacture are disclosed for resolving hostnames on a private network with a public Internet server. One embodiment of the invention provides for a public Internet server configured to generate a private network ID when a new private network is identified, wherein the private network ID is a unique reference to all nodes within a private network and wherein the private network is comprised of one or more private DNS servers. The public internet server stores the private network ID and an IP address for at least one or more private DNS servers on the private network and sends, upon request, the private network ID to at least one of the private DNS servers. | 03-03-2011 |
20120030274 | MANAGING ALIAS HOST AND DOMAIN NAMES ON A DNS SERVER - Embodiments of the invention provide a method of managing aliases on a server, including deleting unused aliases, while minimizing required administrator interaction. The server may include expirable alias records, containing an expiration value and an inactivity timer. An alias manager component may process the expirable records. If the alias manager component determines a particular record has expired, the alias manager component may delete that record. | 02-02-2012 |
20130091100 | MANAGING AN ALIAS HOST AND DOMAIN NAMES ON A DNS SERVER - Embodiments of the invention provide a method of managing aliases on a server, including deleting unused aliases, while minimizing required administrator interaction. The server may include expirable alias records, containing an expiration value and an inactivity timer. An alias manager component may process the expirable records. If the alias manager component determines a particular record has expired, the alias manager component may delete that record. | 04-11-2013 |
20130166706 | EXTENDING A DHCP RELAY TO BACKUP A DHCP SERVER - Techniques are described for providing a backup DHCP server using a DHCP relay agent. Embodiments retrieve DHCP server configuration information specifying a configuration of one or more DHCP servers. Additionally, embodiments monitor, at a DHCP relay agent, DHCP lease traffic between the one or more DHCP servers and one or more DHCP clients passing through the DHCP relay agent. Upon determining that the one or more DHCP servers have failed, DHCP server services are provided at the DHCP relay agent, based on the received DHCP server configuration information and the monitored DHCP lease traffic. | 06-27-2013 |
20130166707 | EXTENDING A DHCP RELAY TO BACKUP A DHCP SERVER - Techniques are described for providing a backup DHCP server using a DHCP relay agent. Embodiments retrieve DHCP server configuration information specifying a configuration of one or more DHCP servers. Additionally, embodiments monitor, at a DHCP relay agent, DHCP lease traffic between the one or more DHCP servers and one or more DHCP clients passing through the DHCP relay agent. Upon determining that the one or more DHCP servers have failed, DHCP server services are provided at the DHCP relay agent, based on the received DHCP server configuration information and the monitored DHCP lease traffic. | 06-27-2013 |
20130166723 | DUPLICATE IP ADDRESS DETECTION BY A DHCP RELAY AGENT - Techniques are described for detecting duplicate IP addresses at a DHCP relay agent. Embodiments identify a list of DHCP clients that have valid IP address leases from one or more DHCP servers. Additionally, network traffic from a first node passing through the DHCP relay agent is monitored. Embodiments then determine whether the first node is using a duplicate IP address, based on the monitored network traffic and the identified list of DHCP clients. | 06-27-2013 |
20130166737 | DUPLICATE IP ADDRESS DETECTION BY A DHCP RELAY AGENT - Techniques are described for detecting duplicate IP addresses at a DHCP relay agent. Embodiments identify a list of DHCP clients that have valid IP address leases from one or more DHCP servers. Additionally, network traffic from a first node passing through the DHCP relay agent is monitored. Embodiments then determine whether the first node is using a duplicate IP address, based on the monitored network traffic and the identified list of DHCP clients. | 06-27-2013 |
20130166748 | CLIENT-DRIVEN LOAD BALANCING OF DYNAMIC IP ADDRESS ALLOCATION - Techniques are described for load balancing between DHCP servers at a DHCP client. Embodiments receive load information from each of two or more DHCP servers. Here, the load information describes a current workload of the respective DHCP server from which the load information is received. One of the two or more DHCP servers is then selected at the DHCP client based on the received load information. Additionally, embodiments accept an IP address offer from the selected DHCP server. | 06-27-2013 |
20130166754 | CLIENT-DRIVEN LOAD BALANCING OF DYNAMIC IP ADDRESS ALLOCATION - Techniques are described for load balancing between DHCP servers at a DHCP client. Embodiments receive load information from each of two or more DHCP servers. Here, the load information describes a current workload of the respective DHCP server from which the load information is received. One of the two or more DHCP servers is then selected at the DHCP client based on the received load information. Additionally, embodiments accept an IP address offer from the selected DHCP server. | 06-27-2013 |
20140036924 | MULTI-CHASSIS LINK AGGREGATION IN A DISTRIBUTED VIRTUAL BRIDGE - Techniques are described for routing data frames using a distributed virtual bridge in a highly integrated networked system. The distributed virtual bridge creates and manages a type of LAG referred to as “unified link aggregation group” (ULAG). Two or more link aggregation groups that span multiple physically-separated switches or chassis (referred to as MLAGs) are unified or aggregated to form a ULAG. Applications view the ULAG as a single logical link, and as long as at least one of the sub links in any of the MLAGs that are part of the ULAG is operational, network connectivity is maintained. | 02-06-2014 |
20140198668 | DATA LINK LAYER SWITCH FRAME FORWARDING ANALYSIS - Systems and methods to analyze layer-2 data frame switch forwarding are provided. A first switch may be coupled to a second switch. The first switch may maintain state information mirroring the state of the second switch. A sequence number may be appended to a data frame that is received at the first switch. Forwarding compliance of the second switch may be determined by analyzing a runtime attribute of the first switch. | 07-17-2014 |
20140198790 | DATA LINK LAYER ANALYSIS WITH PACKET TRACE REPLAY - Systems and methods to analyze layer-2 data frame switch forwarding are provided. A packet replay module may be configured to replay a data frame from at least one of a packet trace file and a live network, and a first switch may include a first port and may be configured to receive the data frame from the packet replay module and to determine a runtime attribute associated with forwarding the data frame in a second switch. | 07-17-2014 |
20140269685 | SYSTEM GUIDED SURROGATING CONTROL IN BROADCAST AND MULTICAST - Method, computer program product, and system to assist in distribution of packets between a plurality of switch elements in a distributed switch, by monitoring an attribute of each of the plurality of switch elements including a first switch element and a first surrogate switch element, the first surrogate switch element in a first level of a hierarchy and configured using a default hierarchy configuration, the default hierarchy configuration forwarding a data frame to at least one of: a destination switch element of the data frame, and a second surrogate switch element, the second surrogate switch element in a second hierarchy level; computing a score, based on the monitored attribute, for each of the switch elements; and upon determining the score of the first switch element is greater than the score of the first surrogate switch element, designating the first switch element as the first surrogate switch element. | 09-18-2014 |
20140269742 | SYSTEM GUIDED SURROGATING CONTROL IN BROADCAST AND MULTICAST - Method, computer program product, and system to assist in distribution of packets between a plurality of switch elements in a distributed switch, by monitoring an attribute of each of the plurality of switch elements including a first switch element and a first surrogate switch element, the first surrogate switch element in a first level of a hierarchy and configured using a default hierarchy configuration, the default hierarchy configuration forwarding a data frame to at least one of: a destination switch element of the data frame, and a second surrogate switch element, the second surrogate switch element in a second hierarchy level; computing a score, based on the monitored attribute, for each of the switch elements; and upon determining the score of the first switch element is greater than the score of the first surrogate switch element, designating the first switch element as the first surrogate switch element. | 09-18-2014 |