-
Getting Started with NetScaler
-
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
-
Basic components of authentication, authorization, and auditing configuration
-
-
Web proxy support for outbound calls to IDP or third party endpoints
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud™
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
Troubleshoot authentication, authorization and auditing issues
-
Configure EULA as an authentication factor in NetScaler nFactor system
-
Configure periodic Endpoint Analysis scan as a factor in nFactor authentication
-
Configure post-authentication Endpoint Analysis scan as a factor in NetScaler nFactor authentication
-
Configure pre-authentication Endpoint Analysis scan as a factor in nFactor authentication
-
Configure pre-auth and post-auth EPA scan as a factor in nFactor authentication
-
Configure prefill user name from certificate in NetScaler nFactor authentication
-
Configure protected user as an authentication factor in NetScaler nFactor authentication
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
Source IP address whitelisting for GSLB communication channels
-
Use case: Deployment of domain name based autoscale service group
-
Use case: Deployment of IP address based autoscale service group
-
-
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 and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Support for hybrid Post Quantum cryptography on the frontend
-
-
Create a certificate signing request and use SSL certificates on a NetScaler appliance
-
Configure SSL acceleration with HTTP on the front end and SSL on the back end
-
Export certificates used on a NetScaler appliance as PFX file
-
Configure SSL monitoring when client authentication is enabled on the back-end service
-
Configure SSL action to forward client traffic if a cipher is not supported on the ADC
-
Configure synchronization of files in a high availability setup
-
-
-
Authentication and authorization for System Users
-
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
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 Bidirectional Forwarding Detection
Bidirectional Forwarding Detection (BFD) protocol is a mechanism for fast detection of failures of forwarding paths. BFD detects path failures in the order of milliseconds. BFD is used with dynamic routing protocols.
In BFD operation, routing peers exchange BFD packets at a negotiated interval. If a packet is not received from a peer within the negotiated interval plus grace interval, the peer is considered to be dead and a notification will be sent to the set of registered routing protocols. In turn, the routing protocols recalculate the best path and reprogram the routing table. BFD supports smaller time interval, when compared to the timers provided by the routing protocols, thus resulting in faster detection of failures.
The NetScaler appliance supports BFD for the following routing protocols: BGP (IPv4 and IPv6), OSPFv2 (IPv4), and OSPFv3 (IPv6). BFD support in the NetScaler appliance is compliant with RFCs 5880, 5881, and 5883.
Points to Consider for Configuring Bidirectional Forwarding Detection
Before you start configuring BFD, consider the following points:
- Make sure that you understand the different components of BFD, described in RFCs 5880, 5881, and 5883.
- BFD on a NetScaler appliance is supported for the following routing protocols:
- BGP (IPv4 and IPv6)
- OSPFv2 (IPv4)
- OSPFv3 (IPv6)
- BFD on a NetScaler appliance is not supported for the following routing protocols:
- ISIS
- RIP (IPv4)
- RIPng (IPv6)
- The following BFD features are not supported on a NetScaler appliance:
- BFD Echo mode
- BFD Authentication
- BFD Demand asynchronous mode
- The minimum values for BFD interval and BFD Rx timers are 100 milliseconds.
- When BFD is used in a topology with shared IP addresses (for example, Layer 2 high availability setup with SNIP addresses or a cluster setup with striped IP addresses), BFD brings down the active sessions during a failover because the BFD failure detection time (order of milliseconds) is lesser than the HA failover detection interval (3–4 seconds). Therefore, Citrix® recommends usage of Graceful restart in layer-2 HA topologies as the routes are retained during the failover process.
Configuration Steps
Configuring BFD on a NetScaler appliance consists of the following tasks:
- Configure BFD Parameters
- Configure BFD Support for Dynamic Routing Protocols
Configure BFD Parameters
The NetScaler appliance provides separate BFD session parameters for single hop sessions, IPv4 multiple hop sessions, and IPv6 multiple hop sessions. If you do not configure BFD parameters for a type of session, the default values are applied for that session.
The default value of each BFD parameter is same for single hop sessions, IPv4 multiple hop sessions, and IPv6 multiple hop sessions. The following table displays the default value of each BFD parameter.
| BFD Parameter Name | Default Value |
|---|---|
| Interval | 750 milliseconds |
| Minimum Rx | 500 milliseconds |
| Multiplier | 3 |
IMPORTANT:
Mellanox NICs in a NetScaler ADC appliance take around 1500 ms to initialize. You must set the BFD timers to more than 1500 ms for a NetScaler appliance with Mellanox NICs. Citrix recommends setting the BFD timers to 3000 ms:
- Interval Tx = 600 ms
- Minimum Rx = 600 ms
- Multipler = 5
Configuring BFD Parameters for a Single Hop Session
To configure BFD parameters for a single hop session by using the VTYSH command line, at the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
interface vlan ID> |
Enter the interface configuration mode. |
bfd singlehop-peer interval <num> minrx <num> multiplier <num> |
Configure the BFD parameters on the specified interface. |
Sample configuration:
> vtysh
ns# configure terminal
ns(config)# interface vlan3
ns(config-if)# bfd singlehop-peer interval 200 minrx 200 multiplier 5
ns(config-if)# exit
<!--NeedCopy-->
Configuring BFD Parameters for IPv4 Multiple Hop Sessions
To configure BFD parameters for IPv4 multiple hop sessions by using the VTYSH command line, at the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
bfd multihop-peer <ipv4addr> interval <num> minrx <num> multiplier <num> |
Configure the BFD parameters for IPv4 multiple hops sessions. |
Sample configuration:
> vtysh
ns# configure terminal
ns(config)# bfd multihop-peer 20.20.20.138 interval 300 minrx 300 multiplier 5
ns(config)# exit
<!--NeedCopy-->
Configuring BFD Parameters for IPv6 Multiple Hop Sessions
To configure BFD parameters for IPv6 multiple hop sessions by using the VTYSH command line, at the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
bfd multihop-peer ipv6 <ipv6addr> interval <num> minrx <num> multiplier <num> |
Configure the BFD parameters for IPv6 multiple hops sessions. |
Sample configuration:
> vtysh
ns(config)# bfd multihop-peer ipv6 20fe:125::138 interval 500 minrx 500 multiplier 5
ns(config)# exit
<!--NeedCopy-->
Configure BFD Support for Dynamic Routing Protocols
You can enable BFD for a dynamic routing protocol for a type of session with a peer. For example, single hop and multiple hops. The NetScaler appliance applies the relevant BFD parameter settings to the session.
Configuring BFD for an IPv4 BGP Single Hop Session
To configure BFD for an IPv4 BGP single hop session by using the VTYSH command line, at the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
router bgp <asnumber> |
BGP autonomous system. asnumber is a required parameter. |
neighbor <ipv4addr> remote-as <num> |
Update the IPv4 BGP table with the IPv4 address of the neighbor in the specified autonomous system. |
neighbor <ipv4addr> fall-over bfd |
Enable BFD for the specified neighbor. |
Sample configuration:
> vtysh
ns# configure terminal
ns(config)#router bgp 1
ns(config-router)#neighbor 20.20.20.138 remote-as 1
ns(config-router)#neighbor 20.20.20.138 fall-over bfd
ns(config-router)#redistribute kernel
ns(config-router)#exit
<!--NeedCopy-->
Configuring BFD for an IPv4 BGP Multiple Hop Session
To configure BFD for an IPv4 BGP multiple hop session by using the VTYSH command line, at the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
router bgp <asnumber> |
BGP autonomous system. asnumber is a required parameter. |
neighbor <ipv4addr> remote-as <num> |
Update the IPv4 BGP table with the IPv4 address of the neighbor in the specified autonomous system. |
neighbor <ipv4addr> fall-over bfd multihop |
Enable BFD for the specified neighbor. |
Sample configuration:
> vtysh
ns# configure terminal
ns(config)#router bgp 1
ns(config-router)#neighbor 20.20.20.138 remote-as 1
ns(config-router)#neighbor 20.20.20.138 fall-over bfd multihop
ns(config-router)#redistribute kernel
ns(config-router)#exit
<!--NeedCopy-->
Configuring BFD for an IPv6 BGP Single Hop Session
To configure BFD for an IPv6 BGP single hop session by using the VTYSH command line, at the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
router bgp <asnumber> |
BGP autonomous system. asnumber is a required parameter. |
neighbor <ipv6addr> remote-as <num> |
Update the IPv6 BGP table with the link local IPv6 address of the neighbor in the specified autonomous system. |
neighbor <ipv6addr> fall-over bfd |
Enable BFD for the specified neighbor. |
address-family ipv6 |
Enter address family configuration mode. |
neighbor <ipv6addr> activate |
Exchange prefixes for the IPv6 router family between the peer and the local node by using the link local address. |
Sample configuration:
> vtysh
ns# configure terminal ns(config)#router bgp 1
ns(config-router)#neighbor 30fe:123::124 remote-as 1
ns(config-router)#neighbor 30fe:123::124 fall-over bfd
ns(config-router)#address-family ipv6
ns(config-router-af)#neighbor 30fe:123::124 activate
ns(config-router-af)#redistribute kernel
ns(config-router-af)#exit
<!--NeedCopy-->
Configuring BFD for an IPv6 BGP Multiple Hop Session
To configure BFD for an IPv6 BGP multiple hop session by using the VTYSH command line, at the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
router bgp <asnumber> |
BGP autonomous system. asnumber is a required parameter. |
neighbor <ipv6addr> remote-as <num> |
Update the IPv6 BGP table with the link local IPv6 address of the neighbor in the specified autonomous system. |
neighbor <ipv6addr> fall-over bfd multihop |
Enable BFD for the specified neighbor. |
address-family ipv6 |
Enter address family configuration mode. |
neighbor <ipv6addr> activate |
Exchange prefixes for the IPv6 router family between the peer and the local node by using the link-local address. |
Sample configuration:
> vtysh
ns# configure terminal
ns(config)# bfd multihop-peer ipv6 20fe:125::138 interval 500 minrx 500 multiplier 5
ns(config)#router bgp 1
ns(config-router)#neighbor 20fe:125::138 remote-as 1
ns(config-router)#neighbor 20fe:125::138 fall-over bfd multihop
ns(config-router)#address-family ipv6
ns(config-router-af)#neighbor 20fe:125::138 activate
ns(config-router-af)#redistribute kernel
ns(config-router-af)#end
<!--NeedCopy-->
Configuring BFD for OSPFv2 (IPv4) on Interfaces
You can enable BFD on all or on a specific interface that uses the OSPFv2 protocol.
To configure BFD for OSPFv2 on all interfaces by using the VTYSH command line:
At the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
router ospf <process tag> |
Enter OSPFv2 configuration mode. |
bfd all-interfaces |
Enable BFD on all interfaces that use OSPFv2. |
Sample configuration:
> vtysh
ns# configure terminal
ns(config)#router ospf 1
ns(config-router)#bfd all-interfaces
ns(config-router)#redistribute kernel
ns(config-router)#exit
<!--NeedCopy-->
To configure BFD for OSPFv2 on a specific interface by using the VTYSH command line:
At the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
interface <vlan ID> |
Enter the interface configuration mode. |
ip ospf bfd |
Enable BFD on the specified interface that uses OSPFv2. |
Sample configuration:
> vtysh
ns# configure terminal
ns(config)# interface vlan5
ns(config-if)# ip ospf bfd
ns(config-if)# exit
<!--NeedCopy-->
Configuring BFD for OSPFv3 (IPv6) on Interfaces
You can enable BFD on all or on a specific interface that uses the OSPFv3 protocol.
To configure BFD for OSPFv3 on all interfaces by using the VTYSH command line:
At the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
router ipv6 ospf <process tag> |
Enter OSPFv3 configuration mode. |
bfd all-interfaces |
Enable BFD on all interfaces that use OSPFv3. |
Sample configuration:
> vtysh
ns# configure terminal
ns(config)#router ipv6 ospf 10
ns(config-router)#bfd all-interfaces
ns(config-router)#redistribute kernel
ns(config-router)#exit
<!--NeedCopy-->
To configure BFD for OSPFv3 on a specific interface by using the VTYSH command line:
At the command prompt, type the following commands, in the order shown:
| Command | Specifies |
|---|---|
vtysh |
Display VTYSH command prompt. |
configure terminal |
Enter global configuration mode. |
interface <vlan ID> |
Enter the interface configuration mode. |
ipv6 ospf bfd |
Enable BFD on the specified interface that uses OSPFv3. |
Sample configuration:
> vtysh
ns# configure terminal
ns(config)# interface vlan15
ns(config-if)# ipv6 ospf bfd
ns(config-if)# exit
<!--NeedCopy-->
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.