---
title: Migrating ADC services from Citrix Netscaler to RELIANOID
description: "# Overview Application delivery is imperative to all companies whose interest is maintaining long-term performance, reliability, security, and efficiency. [RELIANOID ADC’s](https://www.relianoid.com/products/enterprise/) performance and high speed delivery helps ensure the distribution of traffic across various backend servers or data centers is…"
url: "https://www.relianoid.com/resources/knowledge-base/howtos/migrating-adc-services-from-citrix-netscaler-to-relianoid/"
updated: "2025-07-14"
category: "Howto's"
---

# Migrating ADC services from Citrix Netscaler to RELIANOID

# Overview

Application delivery is imperative to all companies whose interest is maintaining long-term performance, reliability, security, and efficiency. [RELIANOID ADC’s](https://www.relianoid.com/products/enterprise/) performance and high speed delivery helps ensure the distribution of traffic across various backend servers or data centers is **fast** and **efficient**, boosting client-server communication.

This article will explain various concepts used in Citrix Netscaler. Later, we will use these configurations to describe how to set up a high-availability network and create a virtual service that receives traffic from the web and distributes it to a cluster of servers in **RELIANOID ADC**.

For an in-depth comparison between Citrix Netscaler and RELIANOID ADC, read this article: [Citrix Netscaler and RELIANOID Comparison](/top-load-balancers/citrix-netscaler-alternative/)

# Prerequisites

To follow this guide, ensure the following conditions are met.

1. An instance of RELIANOID ADC must be installed on your workstation, bare metal, virtual environment, or a cloud platform. For on-premise deployment, [request an evaluation](https://www.relianoid.com/enterprise-edition-evaluation-request/).
2. Must have access to the Web graphical interface. If you don’t, follow this quick [installation guide](https://www.relianoid.com/knowledge-base_category/enterprise-edition/).
3. Must be familiar with the Netscaler platform and knowledgeable about its concepts.
4. A virtual server is essential when distributing traffic to backend servers. Follow this guide: [Layer 4 and Layer 7 Virtual Server Configuration](https://www.relianoid.com/knowledge-base/howtos/layer-7-and-layer-4-load-balancing-with-zevenet-e-e-v6-2/)

# Basic concepts

**Virtual Servers:** A Virtual Server in Citrix Netscaler receives all incoming traffic from external networks. This interface has a virtual **IPADDRESS** and **Port** that listen for incoming traffic from the web. A Virtual Server in Citrix Netscaler is the same as a Farm when using RELIANOID’s load balancer.

**Service Groups:** Service Groups separate different types of resources of the same application accessed through the same domain. One may host an **SMTP**, **RDP**, or **SIP** service on the same domain, whose resources are separated by different service groups. A service group is the same as a Service in RELIANOID ADC.

**Monitors:** Monitors track the health of nodes serving an application by sending probe signals and listening for echoes. These signals check whether a backend server and its service are healthy. RELIANOID ADC uses a set of inbuilt plugins called Farmguardian for health monitoring.

**Servers:** Servers are backend computers that host and serve an application within a local network. These hosts process all requests from the web and send back responses requested by the clients. **Servers** are called Backends in the RELIANOID load balancer.

**DNS:** This module is used when load-balancing traffic between data centers in different geographies. The module used for global load balancing in RELIANOID ADC is called GSLB.

**Security:** This option provides high security for a web application when using Citrix Netscaler. A few of its features include an HTTP DoS policy, content inspection policies, and an SSL Forward Proxy policy. RELIANOID uses the IPDS module that provides security at all layers. The module includes the RBL, Blacklist, WAF policies, and DoS protection.

**High Availability:** High Availability is imperative when there is a need to maintain accessibility at all moments without clients experiencing downtime. We maintain the high availability of an application through failover. RELIANOID uses the Cluster settings to provide the utmost reliability, preventing downtime incase of component failure.

**Reporting:** Reporting is a set of monitoring graphs about resource usage by the load balancer, traffic statistics, and the active throughput of the load balancer. RELIANOID usages Monitoring **graphs**, **stats**, and **Logs** to help end users track resource usage over a specified timeframe.

# Example configurations: Highly Availability

Regarding risk management, a high availability setup offers a backup for disaster recovery in case of power **outages/surges**, **catastrophic breakdown** of nodes, or **path disconnection**. A downtime of an hour within a year can lead to tremendous losses for a digital company. It is essential that one chooses the right ADC partner to ensure high uptime.

A highly available system requires at least two identical nodes with the same configurations, one being a master and the other(s) as the backup(s). Only the master node owns the floating IP address through which the traffic flows, and when the master goes down or in maintenance mode, one of the backups will pick up, preventing IP conflicts.

Let us configure a highly available system in **Citrix Netscaler** and demonstrate similar implementations in **RELIANOID ADC**.

## Netscaler configurations

1. On the menu, click **System**.
2. Click the **High Availability** drop-down menu.
3. Click on the **Nodes** option.
4. Click on the **Add** button below the Nodes Label
5. Enter the **Remote Node IP address** of the other active instance.
6. Enter the **User name** and **Password** of the remote instance.
7. Click the **Create** button.
8. Click the **Save** button at the top right of the table to save the configurations.
