The Global View section is used to know the actual instant state of the system, like a photo system status.
Under this section you’ll be able to analyze the farms state, memory, cpu consumption, established connections and the % of established connections from the total system connections consumed by every farm.
The Global Farms Information table summarizes the farm status you’ll be able to control the farms status with a simple view, which of them are on UP status, how many resources are using and which of them are on DOWN status.
In this table you can analyze:
o The % of cpu usage by the farms
o The % of memory usage by the farms
o The number of “Total connections on system” shows the concurrent connections that is used by the farm compared with the total connections established on the system.
The Memory table shows the global memory status measured in Megabytes.
MemTotal: It’s the total ram memory on the system.
MemFree: It’s the total free memory not cached by the system.
MemUsed: It’s the memory used by the system.
Buffers: It’s the memory used by the buffers.
Cached: It’s the total memory cached by the system.
SwapTotal: It’s the total swap memory reserved.
SwapFree: It’s the swap memory not used by the system, on optimal systems it should be the same that SwapTotal.
SwapUsed: It’s the swap used memory by the system, on optimal systems should be 0.
The Load table shows the system load:
The Network Traffic Interfaces table shows the system traffic consumption since last time that the ZenLB was switched on:
Under the Farms section you’ll be able to access to the main configuration panel of virtual services.
Through the Add New Farm icon, you can define a new farm with the following properties:
Farm Description Name: It’s an identification for the farm and could be used to define a description of the virtual service to be provided.
Profile: Define the type of farm and load balancing method for the new farm. You could choose one of the following profiles:
TCP: It’s a simple load balancing that delivers traffic in raw TCP data at application layer (layer 7). The basic mechanism is about open 2 sockets for every connection, one to the client and other to the real server, and then delivers the raw data between them. The selection of this method could be adecuated for protocols like SMTP, RDP, IMAP, LDAP, SSH, etc. This profile is marked as obsolete, use the L4 profile farms instead. In order to configure this farm profile, a virtual IP address and a virtual TCP port will be required.
UDP: It’s a simple load balancing that delivers traffic in raw UDP data at application layer (layer 7). The basic mechanism is about open 2 sockets for every connection, one to the client and other to the real server, and then delivers the raw data between them. The selection of this method could be adecuated for protocols like DNS, NTP, TFTP, BOOTP, SNMP, etc. This profile is marked as obsolete, use the L4 profile farms instead. In order to configure this farm profile, a virtual IP address and a virtual UDP port will be required.
HTTP: It’s an advanced HTTP layer 7 load balancing (or Application Delivery Controller) with proxy special properties. It’s included in this profile features like HTTPS layer 7 load balancing combinated with SSL offload acceleration This profile is adecuated for web services (web application servers included) and all application protocols based on HTTP and HTTPS protocols like WebDav, RDP over HTTP, ICA over HTTP, etc. In order to configure this farm profile, a virtual IP address and a virtual TCP port will be required.
L4xNAT: It’s an high performance load balancing system at routing layer 4 which combines multiples of load balancing methods like Source NAT and Destination NAT. This profile could handle any kind of protocols like TCP, UDP, ICMP, etc, and all protocols based on them. In order to configure this farm profile, a virtual IP address will be required. Later, in the main farm configuration, it’s possible to specify a TCP or UDP protocol and a port o port range.
DATALINK: It’s a routing load balancing system at layer3 which balances the load through routes across different networks allowing to balance routers uplink accesses to internet. This is a protocol agnostic load balancing method. In order to configure this farm profile, a virtual IP address will be required.
Once the farm description name and profile is selected, please click on the “Save & continue” button in order to continue with the farm configuration.
Virtual IP: The list shows all the IP addresses available in the system network configuration to be used to configure a virtual service for a farm. This IP would be the bind address where the virtual service will be listen on for client requests. If the cluster service is enabled then the physical IP address of the cluster nodes and the management web GUI IP address aren’t listed.
Virtual Port: This field has to be a port number available on the system, where the virtual service will be listening in. This field will be only present if the farm profile requires it.
According to the profile selected, you’ll be allowed to select 1 virtual port (HTTP, TCP and UDP), a range of virtual ports (L4xNAT), all virtual ports (L4xNAT) or none of them (DATALINK).
In order to finalize the process adding a new farm press the Save button.
Once the new farm is created, it will be shown under the Farms Table with the basic data about the virtual service: the farm name, the virtual IP, the virtual Port(s), the farm connections, PID, status, profile and actions. The connections data is gathered from the system information.
The Pending Conns are calculated with the input SYN requests that are pending to be processed in the system for this farm.
The Established Conns are calculated with the input ESTABLISHED requests that are processing currently.
The Closed Conns are calculated with the CLOSE WAIT connections which have been already processed in the system.
The PID field shows the process ID within the system.
The Status field shows the state of the farm system process with a green dot if the farm is up and a red dot if the farm is down.
The Profile field shows the profile definition selected at the creation time for the current farm.
The Actions field shows the available options for every farm, which could be:
Stop Farm: The selected farm will be stopped, and the virtual service will be disabled. Once the farm is stopped, it will not be started at the boot up process of the load balancer. The status field will be shown with a red dot and the PID will be disappeared. A confirmation window will be shown.
Start Farm: If the farm is stopped, only this icon and delete icon will be shown. The selected farm will be started, and the virtual service will be enabled. The status field will be shown with a green dot. A confirmation windows will be shown and the PID will appear again.
Edit Farm: You’ve to select this action to edit the farm properties and the definition of the real servers for the current farm. The properties to be configured depends on the load balancing profile selected for the current virtual service.
Delete Farm: This action disables the current farm and removes the virtual service. A confirmation window will be shown.
View Farm Backend Status: This action shows a complete backend status, pending connections, established connections and closed connections of every real server, the clients and the properties for every backend.
If a datalink profile farm is configured, the farms table information changes in order to better adapt to the information gathered by this kind of farms.
The special field for datalink farms are the following:
The IP is the ip address where the farm is listening for new packets.
The Interface is the networking interface where the farm is listening for input packets. This interface will be set according to the ip address established in the IP field.
The Rx Bytes/sec shows the bytes per seconds for the incoming traffic in the interface.
The Rx Packets/sec shows the number of packets per seconds for the incoming traffic in the interface.
The Tx Bytes/sec shows the bytes per seconds for the outcoming traffic in the interface.
The Tx Packets/sec shows the number of packets per seconds for the outcoming traffic in the interface.