The following table lists terms and definitions used in this LSNAT configuration discussion.
LSNAT Configuration Terms and Definitions
| Term | Definition |
|---|---|
| application content verification (ACV) | A fail detection method for the verification of application content on a server. |
| binding | A resource that tracks a connection from client to the LSNAT router and from the LSNAT router to the real server. |
| ICMP ping | A fail detection method that sends a ping packet to the IP address of the remote service before a session is created. |
| least connections | A load balancing algorithm that assigns sessions based upon the server in the pool with the least current active sessions assigned. |
| load balancing | An LSNAT feature that assigns sessions over multiple real servers based upon a configured predictor. |
| LSNAT | LSNAT is a load balancing routing feature that provides load sharing between multiple servers grouped into server farms. LSNAT can be tailored to individual services or all services. |
| port service verification | A tracked object manager fail detection feature that assures that the protocol port is in an up state before beginning a session. |
| predictor | A load balancing (sharing) algorithm such as round robin, weighted round robin and least connection. |
| probe | A tracked object manager object of protocol type ICMP, UDP, or TCP that tracks the availability of a remote service, by actively transmitting network packets to a specified remote host. |
| probe one and two | Up to two probes, that can be a default probe or administratively created probe, labeled one and two, applied to a server context. |
| real server | The actual physical server that provides the services requested by the client. |
| request packet | A data packet sent by the client to the virtual server requesting services. |
| response packet | A data packet sent by the real server to the service requesting client. |
| server farm | A logical entity of multiple real servers that faces the client through a virtual server. |
| session sticky type | The concept that the client will be directed to the same physical server for the duration of a session based upon a configured binding type (TCP, SIP, or SIP DPORT). |
| simple round robin | A load balancing algorithm that assigns sessions based upon an equal weight ordering of the servers. When all servers in the ordering have been assigned a session, the algorithm returns to the first server in the server list. |
| sticky mode | An LSNAT feature that assures all service requests from a particular client will be directed to the same real server for that session. |
| tracked object manager | An application that determines the state of a remote service using administratively configured and default probes. |
| Virtual IP (VIP) address | The IP address of the LSNAT virtual server that functions as the public face of the real server. |
| virtual server | A logical entity that the client interacts with by acting as the public face for the real server. |
| weighted round robin | A load balancing algorithm that assigns sessions based upon the configured server weight. For instance, if there are two servers the first of which has a weight of 2 and the second has a weight of 3, then for every 5 sessions, the first will be assigned 2 sessions and the second will be assigned 3 sessions. |
Print
this page
Email this topic
Feedback
View PDF
Download EPUB