Patent application number | Description | Published |
20130212295 | APPLICATION LAYER NETWORK TRAFFIC PRIORITIZATION - Layer-7 application layer message (“message”) classification is disclosed. A network traffic management device (“NTMD”) receives incoming messages over a first TCP/IP connection from a first network for transmission to a second network. Before transmitting the incoming messages onto the second network, however, the NTMD classifies the incoming messages according to some criteria, such as by assigning one or more priorities to the messages. The NTMD transmits the classified messages in the order of their message classification. Where the classification is priority based, first priority messages are transmitted over second priority messages, and so forth, for example. | 08-15-2013 |
20130219030 | IN SERVICE UPGRADES FOR A HYPERVISOR OR HARDWARE MANAGER HOSTING VIRTUAL TRAFFIC MANAGERS - Embodiments are directed towards upgrading hypervisors operating in hardware clusters that may be hosting one or more virtual clusters of virtual traffic managers. Virtual clusters may be arranged to span multiple computing devices in the hardware cluster. Spanning the virtual clusters across multiple hardware nodes the virtual cluster may enable the virtual clusters to remain operative while one or more hardware nodes may be upgraded. Hypervisor may include a management control plane for virtual clusters of virtual traffic managers. Hypervisors running on hardware nodes may manage the lower level networking traffic topology while the virtual traffic managers may manage the higher level network processing. Further, hypervisor based management control planes may interface with the virtual clusters and virtual traffic manager's using pluggable translation modules may enable different versions of hypervisor based management control planes and virtual traffic managers to communicate and cooperatively manage network traffic. | 08-22-2013 |
20130290699 | METHODS FOR SECURE COMMUNICATION BETWEEN NETWORK DEVICE SERVICES AND DEVICES THEREOF - A method, non-transitory computer readable medium, and network device that generates a network communication including a destination address associated with a second network device and a destination port number, wherein the destination port number corresponds to a service operating on the second network device. An initial SSL handshake protocol message is generated and at least the destination port number is inserted into a server name indicator (SNI) extension of the initial SSL handshake protocol message. An SSL connection is established with the second network device using a predetermined port number and the initial SSL handshake protocol message is sent to the second network device. Information included in the network communication is sent to the second network device using the SSL connection. | 10-31-2013 |
20140040477 | CONNECTION MESH IN MIRRORING ASYMMETRIC CLUSTERED MULTIPROCESSOR SYSTEMS - Embodiments are directed towards establishing a plurality of connections between each of a plurality of first computing devices in a primary chassis with each of a plurality of second computing devices in a failover chassis. A first computing device uses the plurality of connections as mesh connections to select a second computing device in which to route information about received packets. Routing of information about the packets to the selected second computing device includes modifying a source port number in the packets to include an identifier of the first computing device and an identifier of the second computing device. The information may indicate that the failover chassis is to perform specialized routing of the modified packets. | 02-06-2014 |
20140143375 | METHODS FOR OPTIMIZING SERVICE OF CONTENT REQUESTS AND DEVICES THEREOF - A method, non-transitory computer readable medium, and network traffic management apparatus that receives a request for content from a client computing device. A length of the content is determined. A plurality of requests for a portion of the length of the content is sent to a plurality of server computing devices, wherein the portion of the length of the content is specified as a byte range in a range header of each of the plurality of requests. A plurality of responses to the plurality of requests is received. At least a subset of the plurality of responses is output to the client computing device. | 05-22-2014 |
20140189686 | ELASTIC OFFLOAD OF PREBUILT TRAFFIC MANAGEMENT SYSTEM COMPONENT VIRTUAL MACHINES - Embodiments are directed towards employing a traffic management system (TMS) that is enabled to deploy component virtual machines (CVM) to the cloud to perform tasks of the TMS. In some embodiments, a TMS may be employed with one or more CVMs. In at least one embodiment, the TMS may maintain an image of each CVM. Each CVM may be configured to perform one or more tasks, to operate in specific cloud infrastructures, or the like. The TMS may deploy one or more CVMs locally and/or to one or more public and/or private clouds. In some embodiments, deployment of the CVMs may be based on a type of task to be performed, anticipated resource utilization, customer policies, or the like. The deployment of the CVMs may be dynamically updated based on monitored usage patterns, task completions, customer policies, or the like. | 07-03-2014 |
20140258369 | SERVER TO CLIENT REVERSE PERSISTENCE - Embodiments may be directed towards enabling one or more load balance servers to maintain connection flow persistence if the server initiates to the communication to a client. A packet traffic management device may (PTMD) intercept the request from the server and generate reverse persistence information. The PTMD may include a portion of the reverse persistence information in the request before forwarding the request to the targeted client device. The client device may send the response to the PTMD. The PTMD may employ reverse persistence information to identify the target server. The PTMD may remove the reverse persistence information from the response sent by the client and forward the response to the determined server. Removing the reverse persistence information may remove evidence that the PTMD intervened in the connection between the client and server. | 09-11-2014 |