Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
Install a Citrix ADC VPX instance on Linux-KVM platform
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
Deploy a Citrix ADC VPX instance on Microsoft Azure
Network architecture for Citrix ADC VPX instances on Microsoft Azure
Configure multiple IP addresses for a Citrix ADC VPX standalone instance
Configure a high-availability setup with multiple IP addresses and NICs
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
Configure address pools (IIP) for a Citrix Gateway appliance
Upgrade and downgrade a Citrix ADC appliance
Solutions for Telecom Service Providers
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
Authentication, authorization, and auditing application traffic
Configuring authentication, authorization, and auditing policies
Configuring Authentication, authorization, and auditing with commonly used protocols
Use an on-premises Citrix Gateway as the identity provider for Citrix Cloud
Troubleshoot authentication issues in Citrix ADC and Citrix Gateway with aaad.debug module
-
-
-
-
-
Persistence and persistent connections
Advanced load balancing settings
Gradually stepping up the load on a new service with virtual server–level slow start
Protect applications on protected servers against traffic surges
Retrieve location details from user IP address using geolocation database
Use source IP address of the client when connecting to the server
Use client source IP address for backend communication in a v4-v6 load balancing configuration
Set a limit on number of requests per connection to the server
Configure automatic state transition based on percentage health of bound services
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
Use case 3: Configure load balancing in direct server return mode
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
Use case 7: Configure load balancing in DSR mode by using IP Over IP
Use case 10: Load balancing of intrusion detection system servers
Use case 11: Isolating network traffic using listen policies
Use case 12: Configure Citrix Virtual Desktops for load balancing
Use case 13: Configure Citrix Virtual Apps for load balancing
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
Authentication and authorization
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
Configuring CloudBridge Connector between Datacenter and AWS Cloud
配置一个CloudBridge连接器之间的隧道a Citrix ADC Appliance and Virtual Private Gateway on AWS
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
配置一个CloudBridge连接器之间的隧道a Citrix ADC Appliance and Cisco IOS Device
配置一个CloudBridge连接器之间的隧道a Citrix ADC Appliance and Fortinet FortiGate Appliance
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde.(Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique.(Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica.(Aviso legal)
此内容已经过机器动态翻译。放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다.책임 부인
Este texto foi traduzido automaticamente.(Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt.(Haftungsausschluss)
Ce article a été traduit automatiquement.(Clause de non responsabilité)
Este artículo ha sido traducido automáticamente.(Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configuring Virtual MAC Addresses
A Virtual MAC address (VMAC) is a floating entity shared by the primary and the secondary nodes in an HA setup.
In an HA setup, the primary node owns all of the floating IP addresses, such as the MIPs, SNIPs, and VIPs. The primary node responds to Address Resolution Protocol (ARP) requests for these IP addresses with its own MAC address. As a result, the ARP table of an external device (for example, an upstream router) is updated with the floating IP address and the primary node’s MAC address.
When a failover occurs, the secondary node takes over as the new primary node. It then uses Gratuitous ARP (GARP) to advertise the floating IP addresses that it acquired from the primary. However, the MAC address that the new primary advertises is the MAC address of its own interface.
Some devices (notably a few routers) do not accept the GARP messages generated by the Citrix ADC appliance. As a result, some external devices retain the old IP to MAC mapping advertised by the old primary node. This can result in a site going down.
You can overcome this problem by configuring a Virtual MAC on both nodes of an HA pair. Both nodes then possess identical MAC addresses. Therefore, when failover occurs, the MAC address of the secondary node remains unchanged, and the ARP tables on the external devices do not need to be updated.
To create a Virtual MAC, you need to first create a Virtual Router ID (VRID) and bind it to an interface. (In an HA setup, you need to bind the VRID to the interfaces on both nodes.) Once the VRID is bound to an interface, the system generates a Virtual MAC with the VRID as the last octet.
This section includes the following details:
Configuring IPv4 Virtual MACs
When you create a IPv4 Virtual MAC address and bind it to a interface, any IPv4 packet sent from the interface uses the Virtual MAC address that is bound to the interface. If there is no IPv4 Virtual MAC bound to an interface, the interface’s physical MAC address is used.
The generic Virtual MAC is of the form00:00:5e:00:01:
. For example, if you create a VRID with a value of 60 and bind it to an interface, the resulting Virtual MAC is 00:00:5e:00:01:3c, where 3c is the hex representation of the VRID. You can create 255 VRIDs with values from 1 to 255.
Creating or modifying an IPv4 Virtual MAC
You create an IPv4 virtual MAC by assigning it a virtual router ID. You can then you bind the Virtual MAC to an interface. You cannot bind multiple VRIDs to the same interface. To verify the Virtual MAC configuration, you should display and examine the Virtual MACs and the interfaces bound to the Virtual MACs.
To add a Virtual MAC by using the command line interface
At the command prompt, type:
add vrID
bind vrid
-ifnum show vrID
Example
> add vrID 100 Done > bind vrid 100 -ifnum 1/1 1/2 1/3 Done
To unbind interfaces from a Virtual MAC by using the command line interface
At the command prompt, type:
unbind vrid
-ifnum show vrID
To configure a Virtual MAC by using the GUI
Navigate toSystem>Network>VMACand, on theVMACtab, add a new Virtual MAC, or edit an existing Virtual MAC.
Removing an IPv4 Virtual MAC
To remove an IPv4 virtual MAC, you delete its virtual router ID.
To remove an IPv4 Virtual MAC by using the command line interface
At the command prompt, type:
rm vrid
Example
rm vrid 100s
To remove an IPv4 Virtual MAC by using the GUI
Navigate toSystem>Network>VMACand, on theVMACtab, delete the IPv4 Virtual MAC.
Configuring IPv6 Virtual MAC6s
The Citrix ADC supports Virtual MAC6 for IPv6 packets. You can bind any interface to a Virtual MAC6, even if an IPv4 Virtual MAC is bound to the interface. Any IPv6 packet sent from the interface uses the Virtual MAC6 bound to that interface. If there is no Virtual MAC6 bound to an interface, an IPv6 packet uses the physical MAC.
Creating or Modifying a Virtual MAC6
You create an IPv6 virtual MAC by assigning it an IPv6 virtual router ID. You can then you bind the Virtual MAC to an interface. You cannot bind multiple IPv6 VRIDs to an interface. To verify the Virtual MAC6 configuration, you should display and examine the Virtual MAC6s and the interfaces bound to the Virtual MAC6s.
To add a Virtual MAC6 by using the command line interface
At the command prompt, type:
add vrID6
bind vrID6
-ifnum show vrID6
Example
> add vrID6 100 Done > bind vrID6 100 -ifnum 1/1 1/2 1/3 Done
To unbind interfaces from a Virtual MAC6 by using the command line interface
At the command prompt, type:
unbind vrID6
-ifnum show vrID6
To configure a Virtual MAC6 by using the GUI
Navigate toSystem>Network>VMACand, on theVMAC6tab, add a new Virtual MAC6, or edit an existing Virtual MAC6.
Removing a Virtual MAC6
To remove an IPv4 virtual MAC, you delete its virtual router ID.
To remove a Virtual MAC6 by using the command line interface
At the command prompt, type:
rm vrid6
Example
rm vrid6 100s
To remove a Virtual MAC6 by using the GUI
Navigate toSystem>Network>VMACand, on theVMAC6tab, delete the virtual router ID.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.