This article is an FAQ on the Fail-To-Wire (FTW) functionality found in the new Citrix CloudBridge 2000 and Citrix CloudBridge 3000 appliances.

Q: What is the supported software release?

A: The FTW feature is supported with the following software releases:

• SVM build: NS 10.0.72.5007

• CloudBridge build: 6.2.2.45

• BIOS version 3.0a

•  IPMI firmware version: 2.05

• Supplemental pack 1.3

Q: What is an FTW event?

A: Fail-To-Wire (FTW) functionality provides a mechanism to connect link layer (L2) signals of two data ports on a Network Interface Card (NIC) using a Relay Switch. The Relay Switch provides a direct physical path for incoming traffic to exit directly without going through the NIC driver. This is called bypass mode of the FTW card.

All accelerated connections are reset or disconnected during an FTW event and must be re-established. Unaccelerated connections are not reset or disconnected. When the CloudBridge resumes operation, to get optimization on current connections, FTW must be re-established.

Q: What triggers an FTW event?

A: The following scenarios trigger the FTW event:

•  Lack of FTW Daemon heartbeats

• FTW Daemon crash

• FTW service goes down

• XenServer or CloudBridge instance goes down

• CloudBridge system is powered down

Q: What does not trigger an FTW event?

A: The following scenarios do not trigger the FTW event:

• All components such as SVM, XenServer, and Branch Repeater are up and running

• SVM goes down, restarts or crashes

• CloudBridge is at full capacity

• The graphical user interface of the Branch Repeater VPX instance is inaccessible

• Interfaces are down or disconnected

Q: What are some Inline (L2) Configuration Requirements?

A: The following are some of the Inline Configuration requirements for the FTW feature:

• LAN and WAN interfaces are directly connected to 1 GB Layer 2 Switch

• Ensure apA, apB, and apC are on separate VLANs

Q: How are the interfaces mapped?

A: The following table provides information on how the interfaces are mapped: