A Service defines how the HA Cloud Connector will react to a failure of the Real Servers and the Destination it chooses to move the Elastic IP to. To understand the context of the data in our demo, you will need to see our ADC's configuration.
We have two Virtual Services defined in our example.
The first Virtual Service on port 443, is the main Ingress VS through which users access the Application. The Elastic IP is attached to the network interface (NIC-2) for this IP address.
The second on port 80, associated with NIC-1, is the Monitoring VS and corresponds to the one defined in the Service definition explained later in this section.
Both Virtual Services terminate to the same Real Servers.
This is the case on both ADCs, except for the different Virtual IP addresses.
In the image below, you can see our demo example for the Services page.
In this example, you will see that the entry for the Monitoring VS matches the Monitoring NIC 1 VS defined in our ADC.
There will be no entries in the HA Cloud Connector you have just deployed, and you need to define your Service.
Click the Add Service button to create a new entry line.
Field
Description
Monitoring VS
Select the Monitoring VS you created in your ADC from the drop-down.
Public Address
Select the Elastic IP address that you have allocated in the AWS Instance.
Preferred Destination
The Preferred Destination is where you would like traffic ingressing into the Elastic IP to be routed to.
Second Destination
The Destination where you would like traffic ingressing into the Elastic IP to be routed to in the event of failure.
Fallback
When Enabled is selected, the Elastic IP will be moved back to the Preferred Destination when the failed Service is restored.
You must define the Virtual Service entry within the HA Cloud Connector on both ADCs.
Note: The Service definition should appear so the Preferred and Secondary destinations are interchanged on the two ADCs.
