Coyote Point Systems Equalizer Especificaciones descargar pdf (Pagina 587)

packet

A group of data that is transmitted as a single entity.

passive FTP connection

An Equalizer option that rewrites outgoing FTP PASV control messages from the servers so that they contain the

IP address of the virtual cluster rather than that of the server. See FTP and PASV.

PASV

Passive mode FTP; a mode with which you can establish FTP connections for clients that are behind firewalls. See

firewall, FTP, and passive FTP connections.

pattern match

A pattern of ASCII or hexadecimal data that filters data.

payload

The set of data to be transmitted. A payload contains user information, user overhead information, and other

information that a user requests. A payload does not include system overhead information. Also known as the

mission bit stream.

persistence

The act of storing or retaining data for use at a later time, especially data that shows the state of the network

before processing resumes. See cookie and IP-address-based persistence.

Persistence

Often, when a client (web browser) connects to an application, there is some "shared state" between the client

and server which cannot be used with any other server. Using the following example: You point your web

browser at www.website.com and log in. The server notes that you are logged in and allows you to use the

application. Now,for example, there were two servers and a load balancer, and that the load balancer just

alternated handing any requests it recieved between the two servers... You've been connected to server "A"

where you log in. You then send a different request (run a report) and the load balancer sends your request to

server "B". Since you are not logged into server "B" so you get an error and are asked to log in again. This is

because you have NO PERSISTENCE. Your connection does not get connected to the same server each time.

What you need is some way for the load balancer to recognize your browser and always send your requests to

server "A". We do this in two ways. #1 is called "IP persistence" or "sticky persistence". The load balancer

remembers your IP address the first time you connect to a server and records which server you were connected

to. The next time you connect, Equalizer looks up your IP address in an internal table and notes that you belong

on server "A", so that is where you are sent. Sticky Persistence is available with both L4 and L7 load balancing.

An alternate persistence scheme is available under L7 only. It is called "cookie persistence" and it uses

information stored at the client (a cookie http://en.wikipedia.org/wiki/HTTP_cookie) to recall which server it

should be connected to. The advantage of keeping the persistence information on the client is that no memory is

used on the Eq. This way millions of clients can have poersistence for an indefinate period of time. With sticky

persistence the number of persistent clients is limited by the memory available to store the sticky table.

physical server

A machine located on the internal network that provides services on specific IP addresses and ports. See server

and virtual web server. See also authoritative name server, back-end server, name server, and proxy server.

piece

An atom followed by a single *, +, or ?, or by a bound. See atom, branch, and regular expression.

ping

A program used to test reachability of destinations by sending them an ICMP echo request and waiting for a

reply. See echo and probe. See also CMP echo request

587

Equalizer Administration Guide

1 2 ... 582 583 584 585 586 587 588 589 590 591 592 593 594

Comentarios a estos manuales

Sin comentarios

Coyote Point Systems Equalizer Especificaciones Pagina 587

Comentarios a estos manuales

Relacionado con productos y manuales para Ecualizadores de audio Coyote Point Systems Equalizer