versus{ networks }
Application Delivery Controller

F5 BIG-IP GTM → EfficientIP GSLB Migration

Migrate F5 GTM Wide IPs — or LTM virtual servers — to EfficientIP GSLB Applications, tracked through five phases: Discover, Translate, Load into EIP, Validate, and Cutover.

CautionVersus does not currently offer a virtual-server migration path from F5 BIG-IP to NetScaler. The only F5-sourced ADC migration types implemented today move virtual services to VMware AVI (see the A10 → AVI guide for the general legacy-ADC-to-AVI wizard) or, as covered on this page, move F5 GTM Wide IPs / LTM VSes to EfficientIP GSLB. NetScaler appears elsewhere in Versus only as a source device type for migrations targeting AVI, never as a migration target.
1

Discover

2

Translate

3

Load into EIP

4

Validate

5

Cutover

Prerequisites

  • The F5 BIG-IP source device in Versus Device Inventory, reachable via iControl REST — with either the GTM/DNS module licensed and Wide IPs configured, or LTM virtual servers you intend to migrate directly.
  • An EfficientIP appliance added to Versus and configured as an EfficientIP Target — required before a plan can move past the Discover phase.
1Create the Migration Plan

Navigate to Application Migration and select the F5 → EIP GSLB Plans tab (distinct from the ADC / GTM Plans tab used for AVI migrations).

F5 to EIP GSLB Migration Plans — empty state
F5 → EIP GSLB Migration Plans — before any plan has been created

Click Create First Plan (or New Plan) and fill in:

  • Plan Name
  • Source Type — either F5 GTM / BIG-IP DNS Wide IPs or F5 LTM Virtual Servers.
  • F5 Source Device
  • EfficientIP Target
  • Notes (optional)
New F5 to EIP GSLB Migration Plan form
Plan creation — source type, F5 source device, and EfficientIP target
NoteThis demo instance has no EfficientIP device registered and no GTM Wide IPs configured on its F5 units, so the plan cannot actually be created here — both are required before the Discover phase can run. Phases 2–5 below are described from the product code rather than shown live.
2Discover

Versus pulls candidate objects from the F5 source — Wide IPs (with pool members resolved to IPs) if the source type is GTM, or eligible virtual servers if the source type is LTM. Select which candidates to include in the plan; for LTM sources, each candidate is flagged eligible or not based on its configuration.

3Translate

Each selected item is translated into a projected EfficientIP GSLB Application: record type (A/AAAA/CNAME), target GSLB zone, and the member pool (IP, weight, name) carried over from the F5 side.

4Load into EIP

Translated objects are created on the EfficientIP appliance via its API. Each item's load status and any load errors are tracked individually, so a single failed object doesn't block the rest of the plan.

5Validate (Parity)

Versus compares the newly-created EfficientIP GSLB Applications against the source F5 objects to confirm parity before any traffic decision moves — this is a read-only check, not a cutover.

6Cutover

Cutover is a deliberate two-step sequence, not a single switch:

  1. Lower DNS TTL — reduces the TTL on the source records ahead of time, so the eventual cutover propagates quickly.
  2. Execute Cutover — repoints resolution to the EfficientIP GSLB Applications. The plan is marked Completed once this step is confirmed.

Quick Reference

PhaseWhat HappensTraffic Impact
1 — DiscoverPull Wide IPs or eligible LTM VSes from the F5 sourceNone
2 — TranslateProject EfficientIP GSLB Application objectsNone
3 — Load into EIPCreate objects on the EfficientIP appliance via APINone
4 — ValidateConfirm parity between EIP and the F5 sourceNone
5 — CutoverLower TTL, then repoint resolution to EfficientIPDNS propagation window
← All docsOpen a support case