Overview #

Application delivery is critical for scalability and reliability. While Array Networks APV Series appliances provide SSL acceleration, traffic steering, and global load balancing, many enterprises face challenges with licensing costs, lack of flexibility, and vendor lock-in.

RELIANOID ADC provides a modern, open, and cost-efficient alternative. It offers advanced Layer 4–7 load balancing, SSL offloading, GSLB, WAF, and automation APIs, making it an ideal replacement for legacy Array APV deployments.

This technical guide provides a structured walkthrough for migrating your Application Delivery Controller (ADC) services from Array APV to RELIANOID, with direct terminology mapping and step-by-step configuration examples.

Prerequisites #

This guide is intended for systems administrators or DevOps engineers who meet the following requirements:

1. RELIANOID ADC installed and running (bare metal, VM, or public cloud). You can request an evaluation if needed.
2. Administrator access to the RELIANOID Admin Panel. See installation guide if not yet configured.
3. Administrator access to your current Array APV management console.
4. Familiarity with Array APV concepts such as Virtual Services, Real Services, and GSLB.
5. At least one existing APV service configuration available for reference during migration.

Terminology Mapping #

Real Service → Backend: A server handling client requests.
Group → Service: A set of backends serving the same application.
Virtual Service → Farm: Virtual IP and port listener that applies load-balancing rules.
Weight/Ratio → Weights: Used to prioritize stronger backends.
Connection Limit → Max. Conns: Restricts simultaneous connections per backend.
Health Check → Farmguardian: Active service checks for backend health.
SSL Profile → HTTPS Parameters: Configuration for TLS/SSL protocols and ciphers.
Policy → Header/Redirect Rules: For content switching and conditional redirection.
AppVelocity → HTTP Optimizations: Caching, compression, and multiplexing at LSLB level.
WebWall/DDoS → IPDS + WAF: Security modules for L7 firewalling and attack mitigation.

Migration Strategy #

Before migrating services, follow these preparatory steps:

1. Export APV configurations for backup and reference.
2. Document VIPs, SSL certificates, persistence settings, and policies.
3. Identify custom health checks that must be replicated in RELIANOID Farmguardian.
4. Schedule a maintenance window to minimize downtime during cutover.

Step-by-Step Migration Example: Conditional Redirection #

A common policy is to redirect HTTP requests to HTTPS or forward specific hostnames to a new domain.

Array APV Policy #

1. Login to the APV console.
2. Navigate to Virtual Service > Policies.
3. Create a new policy.
4. Define condition: HTTP Host = mydomain.com.
5. Add action: Redirect to https://www.mydomain.com.
6. Attach the policy to the Virtual Service.

RELIANOID Redirect Rule #

1. Navigate to LSLB > Farms.
2. Create or edit a Layer 7 farm (HTTP listener).
3. Open the Services tab.
4. Enable Redirect option.
5. Enter target URL https://www.mydomain.com.
6. Select 301 (permanent) or 302 (temporary) as redirect code.
7. Click Apply.

Step-by-Step Migration Example: DNS Load Balancing (GSLB) #

RELIANOID GSLB enables DNS-based traffic distribution across multiple data centers.

Array APV GSLB #

1. Create Data Centers (e.g., US_DC, EU_DC).
2. Add Servers with backend IPs.
3. Create Virtual Services per app.
4. Group into GSLB Pools.
5. Bind pools to a Wide IP (domain).
6. Enable monitors and set algorithm (e.g., Round Robin).

RELIANOID GSLB #

1. Go to GSLB > Farms and click Create Farm.
2. Name the farm (e.g., ns1-globalfarm).
3. Select virtual interface and set Port 53.
4. Add a Service with algorithm Round Robin.
5. Configure health checks with Farmguardian.
6. Add backend data center IPs.
7. Open Zones tab → add ydomain.com.
8. Create DNS records (A, CNAME, MX, etc.).
9. Restart the farm to apply changes.