An LTM Specialist is experiencing issues in a failover event. Certain long-lasting FTP event. Certain long-lasting FTP connections using a single node pool are forced to reconnect. The bigip.conf extract is shown:

What does the LTM Specialist need to change in the configuration to avoid this issue?
Suggested Answer: C
Get Premium 301a Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
The stem mentions that it is a single server node, so there is no need to consider the factors of session maintenance. The actual requirement is to maintain the original connection status during failover. You need to configure connection mirroring to synchronize the connection status between the devices in the cluster in real time.
11 comments · newest first
MA
Malcolm
12 months ago
SNAT pool won't help in this scenario, just saying.
SH
Shaquana
12 months ago
Definitely need to check that ftp profile too.
AL
Altha
1 year ago
Surprised this is an issue with a single node pool!
CH
Charisse
1 year ago
I disagree, persistence mirroring might be better for this.
CO
Cordie
1 year ago
Looks like connection mirroring is the way to go.
JO
Jolene
1 year ago
I feel like snatpool was mentioned in a different context, but I don't see how it relates to this failover issue.
FR
Franchesca
1 year ago
I'm leaning towards the FTP profile option, but I can't recall the specifics of how it would prevent reconnections.
LE
Lezlie
1 year ago
I think we had a similar practice question about FTP connections and persistence. Maybe persistence mirroring could help?
KI
Kimberely
1 year ago
I remember we discussed connection mirroring in class, but I'm not entirely sure if that's the right choice here.
DE
Delbert
1 year ago
Hmm, I'm not entirely sure about this one. The wording is a bit tricky, and I'm not 100% clear on the differences between significant deficiencies and material weaknesses. I'll have to think this through carefully.
AD
Adell
1 year ago
Wait, I'm a bit confused. Does "ledger-type transactions" mean we can only post certain types of entries in the general journal? I'll need to think this through carefully.