The Mode column indicates the high availability role selected for the current VIP. For the modes, see System > Clustering>Roles.
Option
Description
Active
In Cluster mode, the value of this field is Active. When you have an HA pair of ADC appliances in your datacentre, one of them will show Active and the other Passive. If the current appliance
Passive
When the ADC is acting as a secondary member of a cluster, then Passive is shown in the Mode column.
Manual
The Manual role allows the ADC pair to run in Active-Active mode for different Virtual IP addresses. In such cases, the Primary column will contain a box next to each unique Virtual IP that is selectable for Active or left un-ticked for Passive.
Stand-Alone
The ADC is acting as a stand-alone device and is not in High Availability mode. As such, the Primary column will state Stand-alone.
VIP
This column provides visual feedback on the status of each Virtual Service. The indicators are color-coded and are as follows:
LED
Meaning
?
Online
?
Failover-Standby. This virtual service is hot-standby
?
Indicates a "secondary" is holding off for a "primary."
?
Service Needs attention. This indication may result from a Real Server failing a health monitor check or has been changed manually to Offline. Traffic will continue to flow but with reduced Real Server capacity
?
Offline. Content servers are unreachable, or no content servers enabled
?
Finding status
?
Not licensed or licensed Virtual IPs exceeded
Enabled
The default for this option is Enabled, and the checkbox shows as ticked. You can disable the Virtual Service by double-clicking the line, unticking the checkbox, and then clicking the Update button.
IP Address
Add your IPv4 address in decimal dotted notation or an IPv6 address. This value is the Virtual IP address (VIP) for your service. Example IPv4 "192.168.1.100". Example Ipv6 “2001:0db8:85a3:0000:0000:8a2e:0370:7334”
Subnet Mask/Prefix
Add your subnet mask in decimal dotted notation. Example "255.255.255.0". You can also use the subnet value such as /24, or for IPv6, add in your Prefix. For more information about IPv6, please see HTTPs://en.wikipedia.org/wiki/IPv6_address
Port
Add the port number associated with your service. The port can be a TCP or UDP port number. Example TCP "80" for Web Traffic and TCP "443" for Secured Web Traffic. You can also specify a range of values such as 80-87.
Currently, it is not possible to use comma separated values to specify non-contiguous port values.
Service Name
Add in a friendly name to identify your service. Example "Production Web Servers." This field is also used when using GSLB.
Service Type
Please note that with all "Layer 4" service types, the ADC will not interact or modify the data stream, so flightPATH is unavailable with Layer 4 service types. Layer 4 services simply load balance the traffic according to the load balancing policy:
Service Type
Port/Protocol
Service Layer
Comment
Layer 4 TCP
Any TCP port
Layer 4
The ADC will not alter any information in the data stream and will perform standard load balancing the traffic according to the load balancing policy
Layer 4 UDP
Any UDP port
Layer 4
As with Layer 4 TCP, the ADC will not alter any information in the data stream and will perform standard load balancing the traffic according to the load balancing policy
Layer 4 TCP/UDP
Any TCP or UDP port
Layer 4
It is ideal if your service has a primary protocol such as UDP but will fall back to TCP. The ADC will not alter any information in the data stream and will perform standard load balancing the traffic according to the load balancing policy
DNS
TCP/UDP
Layer 4
Used to load balance DNS servers.
HTTP(S)
HTTP or HTTPS protocol
Layer 7
The ADC can interact, manipulate and modify the data stream using flightPATH.
FTP
File Transfer Protocol
Layer 7
Using separate control and data connections between client and server
SMTP
Simple Mail Transfer Protocol
Layer 4
Use when load balancing mail servers
POP3
Post Office Protocol
Layer 4
Use when load balancing mail servers
IMAP
Internet Message Access Protocol
Layer 4
Use when load balancing mail servers
RDP
Remote Desktop Protocol
Layer 4
Use when load balancing Terminal Services servers
RPC
Remote Procedure Call
Layer 4
Use when load balancing systems using RPC calls
RPC/ADS
Exchange 2010 Static RPC for Address Book Service
Layer 4
Use when load balancing Exchange servers
RPC/CA/PF
Exchange 2010 Static RPC for Client Access & Public Folders
Layer 4
Use when load balancing Exchange servers
DICOM
Digital Imaging and Communications in Medicine
Layer 4
Use when load balancing servers using DICOM protocols
