Abstract: Various embodiments of methods and systems for network infrastructure configuration based on network device configuration templates are provided. A network device configuration template is received where the network device configuration template corresponds to network device configuration data based on template elements. Template elements include variable placeholders, versions, Stock Keeping Units (SKUs), firmware, and target devices identified in the network device configuration template. Values for the template elements are referenced from a dataset storage component. The network device configuration data are classified into different classification units. The network device configuration data are merged with the network device configuration template that programmatically defines configuration of network devices. A network device configuration instance is generated based on evaluating the template elements and replacing template elements with values from the dataset storage.

Abstract: Embodiments are directed to routing requests with different protocols to the same destination. In one scenario, a computer system receives a request that uses a specified protocol. The request includes a request source identifier and a request destination identifier. The computer system identifies, based on both the request source identifier and the request destination identifier, a destination to send the request to and generates a routing entry for the request that indicates which destination the first request was sent to. The computer system receives another request that uses a different protocol. This request includes a request source identifier and a request destination identifier of its own. The computer system determines that the request source identifier and request destination identifier of the subsequent request match those of the generated routing entry, and routes the subsequent request to the destination indicated in the routing entry.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: Bypassing a load balancer that initially appeared in a multi-message flow from a source machine served by a source intermediary and a target machine served on a target intermediary. One or more original network messages (and perhaps just the first) of the flow arrive from the source intermediary at the load balancer, which selects which machine is to be a destination machine, and it turns out selects the destination machine serviced by the destination intermediary. In response to receiving this message, the destination intermediary instructs the source intermediary to transmit subsequent messages in the flow in a manner that bypasses the load balancer. To facilitate this, the source intermediary may modify addressing of subsequent flow messages from the source machine such that they are rerouted to the destination machine without addressing the load balancer.

Abstract: The obtaining of a lease on a resource in a circumstance in which multiple lease servers are capable of granting a lease to the resource. A computing entity attempts to obtain the lease on the resource by causing a lease request to be sent to each of at least most (and perhaps all) of the lease servers. In response, the computing entity receives one or more responses to the lease requests. If the computing entity receives grants of a lease from a majority of the lease servers that are capable of granting a lease to the resource, then it is determined that the computing entity acquired a lease on the resource. On the other hand, if the computing entity receives grants of a lease from less than a majority of the lease servers, it is determined that the computing entity failed to acquire the lease on the resource.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: The present invention discloses a system and method for management of test or non-production environment. The method comprises planning the non-production environment design, wherein planning is based on plurality of inputs. The planning stage is preceded by engagement wherein engagement with functional groups takes place. The planned non-production environment design is analyzed based upon the requirements wherein analysis consists of reviewing plurality of non-production environment designs. This stage is followed by creation of non-production environment wherein non-production environment is built on analyzed design. After this stage the non-production environment is deployed. After deployment there is provision for on-going supports to test services via established Information Technology service management processes. Non-production environment services manage the on-going booking and allocation of the non-production environment through various in-house and third party tools.

Abstract: A load balancer that is able to detect and mitigate a Denial of Service (DOS) attack. The load balancer is placed in the flow path of network data packets that are destined for one or more tenant addresses. The load balancer analyzes performance parameters regarding the network data packets that are destined for the one or more tenant addresses and are received at the load balancer. The performance parameters describe network data packet flow to the tenant addresses. The load balancer detects, based on the analysis of the performance parameters, that one or more of the tenant addresses are being subjected to a DOS attack. The load balancer performs a mitigation operation to isolate the one or more tenant addresses being subjected to the DOS attack.

Abstract: An access control system for a secure facility includes an authorization system having an interface, in the form of an interrogator, for receiving the request signal indicative of a user seeking authorization for a predetermined action, such as gaining access through a door. In one example, an authorization system may include an interface for receiving a request signal indicative of a party seeking authorization for a predetermined action. A first processor, that is responsive to the request signal, determines if the authorization is to be granted. If so, the first processor may generate an authorization signal that includes information that is securely coded, and which is indicative of the determination. An operating device, physically spaced from the first processor, may receive the authorization signal, and may decode the securely coded information and subsequently initiating the action, if appropriate.

Abstract: A load balancer that is able to detect and mitigate a Denial of Service (DOS) attack. The load balancer is placed in the flow path of network data packets that are destined for one or more tenant addresses. The load balancer analyzes performance parameters regarding the network data packets that are destined for the one or more tenant addresses and are received at the load balancer. The performance parameters describe network data packet flow to the tenant addresses. The load balancer detects, based on the analysis of the performance parameters, that one or more of the tenant addresses are being subjected to a DOS attack. The load balancer performs a mitigation operation to isolate the one or more tenant addresses being subjected to the DOS attack.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: Bypassing a load balancer that initially appeared in a multi-message flow from a source machine served by a source intermediary and a target machine served on a target intermediary. One or more original network messages (and perhaps just the first) of the flow arrive from the source intermediary at the load balancer, which selects which machine is to be a destination machine, and it turns out selects the destination machine serviced by the destination intermediary. In response to receiving this message, the destination intermediary instructs the source intermediary to transmit subsequent messages in the flow in a manner that bypasses the load balancer. To facilitate this, the source intermediary may modify addressing of subsequent flow messages from the source machine such that they are rerouted to the destination machine without addressing the load balancer.

Abstract: A cloud computing environment providing a network service for a client computing entity. The network service is not an application level service, but rather a service that operates at or below the network layer in the protocol stack. For instance, the network service might be a network endpoint service such as a network address service (such as DNS) or a dynamic network service (such as DHCP), or a network traffic service such as a firewall service or a secure tunneling service (such as VPN). The service might also provide a pipeline of network services for network level traffic to and from the client computing entity. The cloud environment uses policy to determine which of a plurality of communication channels to use when exchanging cloud service data for the network service.

Abstract: Load balancing for single-address tenants. When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: Described herein are systems and methods for commissioning access control devices. In overview, a carrier substrate such as a smartcard is used to commission a plurality of access control devices. Measures are implemented such that the individual access control devices are uniquely commissioned. That is, no two devices apply identical commissioning data, hi some embodiments this is achieved by, as part of the commissioning process at a given access control device, modifying one or more aspects of the data carried by the carrier substrate.

Abstract: The present invention discloses a system and method for management of test or non-production environment. The method comprises planning the non-production environment design, wherein planning is based on plurality of inputs. The planning stage is preceded by engagement wherein engagement with functional groups takes place. The planned non-production environment design is analyzed based upon the requirements wherein analysis consists of reviewing plurality of non-production environment designs. This stage is followed by creation of non-production environment wherein non-production environment is built on analyzed design. After this stage the non-production environment is deployed. After deployment there is provision for on-going supports to test services via established Information Technology service management processes. Non-production environment services manage the on-going booking and allocation of the non-production environment through various in-house and third party tools.

Abstract: The movement of a Virtual IP (VIP) address from cluster node to cluster node is coordinated via a load balancer. All or a subset of the nodes in a load balancer cluster may be configured as possible hosts for the VIP. The load balancer directs VIP traffic to the Dedicated IP (DIP) address for the cluster node that responds affirmatively to periodic health probe messages. In this way, a VIP failover is executed when a first node stops responding to probe messages, and a second node starts to respond to the periodic health probe messages. In response to an affirmative probe response from a new node, the load balancer immediately directs the VIP traffic to the new node's DIP. The probe messages may be configured to identify which nodes are currently responding affirmatively to probes to assist the nodes in determining when to execute a failover.

Abstract: Individual role instance reachability and load balancing are simultaneously provided for role instances of an application running in a hosting environment. Instance endpoints may be assigned to each role instance. Each instance endpoint may comprise a combination of an IP address, a transport protocol, and a unique port number. Additionally, a load balanced endpoint may be assigned to the group of role instances. The load balanced endpoint may comprise a combination of an IP address, transport protocol, and another unique port number. When application messages are issued to the data center, the messages are routed in accordance with endpoints used by the messages. For an instance endpoint, the message is routed to a role instance corresponding with the instance endpoint without load balancing. For the load balanced endpoint, the message is routed to any one of the role instances using load balancing.

Abstract: Described herein are systems and methods for configuring access control devices. In overview, some embodiments provide for a method whereby a smartcard is used to configure a disconnected access control device. A user presents this smartcard to a connected access control device which, in response to the presentation of this card, allows the user to download to the smartcard one or more aspects of configuration data for a specified disconnected access control device. The user subsequently presents the smartcard to the relevant disconnected access control device, which uploads and selectively applies the one or more aspects of configuration data.