Citrix as a Application Load Balancer

-


We have different option available in market for the ALB (Application load balancer) one of them is Citrix. As per my experience with F5 and AVI Citrix flow is just like same mostly in interviews I say this that if one person has the understanding of the concepts and flow, he/she will be able to operate/manage the solution of any vendor. Same is the case with ALB's flow is same just name are different for each vendor.

As in F5 we have a management IP to manage it in Citrix we have NetScaler IP to manage it and configure it. We do have Self IP/Floating IP to communicate with servers if we are using SNAT in Citrix we have Subnet IP serve the same purpose. For services to expose via F5 we have Virtual IP's Luckly in Citrix it also known as Virtual IP.

We have different modes of deployment one Arm and Two Arm any one can be used. HA deployment is quite simple in Citrix then off F5 as we just need to add the Node its IP and username, Password to be added in HA also the Subnet IP's will be replicated on both boxes you don't need to configure separately on both its a plus from F5.

One need to define the Subnet/Virtual IP and then assign it VLAN's and Interface for the communication between ALB to Server and from client to VIP IP same as F5. Steps for the creation of backend servers and VIPs are quite same as of F5 if one has hands-on it with it, he/she can do it easily.


I know there are many articles on the internet explaining its deployment steps, Main purpose of writing this article is that we should focus on the logic rather than vendors as all are using same logic only GUI and steps for the deployment is different.


I will keep exploring the Citrix load balancer for exposing services on HTTPs and will see how it works with the WAF and SSL offloading part. Will see how its work with Automation via ansible.


Enterprise DC Engineer
Happy Learning
Limit is Sky.



Comments

Post a Comment

Popular posts from this blog

Flow with respect to Networks in AWS

-
Image
Flow with respect to Networks in AWS which need to be clear to expose any application on AWS and having some of services in on-premises. I will compare AWS services with on-prem technology, so it become ease to understand.                                                           Building Block of AWS Networking VPC: Consider it as a switch place in multiple Data center and all switches are connected with each other we can further have small subnets on it which can be part of all switches or only one depend upon the planning and requirements. Route Tables : Each subnet we create in VPC can have each route table or all subnets have one, Route table is used to control the routing of subnets and how traffic will be routed for any workload on the subnets. Route table can be attached to few other services of AWS as per requirements. NAT Gateway: I...
Read more

Important concepts in ACI Physical/Access polices Concepts

-
Image
I know Cisco ACI has been around for a long time. The first time I got into it was in 2021. It was not that hard to relate the legacy concepts with ACI but doing a job via CLI and doing it via GUI have a lot of differences. In this particular blog, I will discuss the key concepts without explaining the ACI core components like leaf switches, spine switches, and APIC. Cisco ACI is a policy-driven solution in which everything has an object assigned to it, and you need to connect all those dots to make your network work. In a legacy network, we have devices like bare metal servers, L2 switches, L3 switches, routers, and firewalls. We connect the networks using different protocols to make our network work, but sometimes there are physical requirements that need to be fulfilled to get the required topology. In Cisco ACI, we have all these kinds of devices, and they are connected to our fabric. However, in ACI, we have a term called "domains," which include four different types: Ph...
Read more

1 sec and Team work Story

-
Image
 I n the world of IT, a single second can be the difference between success and failure. Recently, I experienced this firsthand when a 1-second delay caused a critical application flow to shut down. Through intense troubleshooting, collaboration, and respect for diverse opinions, we identified and resolved the issue. This experience taught me the importance of: - Active listening among all stakeholders - Exploring all options and possibilities - Embracing the value of diverse perspectives - The power of collaboration and teamwork - The crucial role of TCP dumps in troubleshooting In IT, every problem requires a unique solution, and collaboration is key to finding it. Delay we Observe at Client end server end had no delay though Raja Shajeel Ahmad Enterprise DC Engineer Happy Learning The limit is the sky. #TeamWork#TCPDump#HappyLearning
Read more