nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How-To Articles

X5 to X6 Migration Runbook

This runbook is written to walk step‑by‑step (including CLI details) through migrating an existing X5 NIOS Grid to X6 vNIOS, preserving IPs and services.

Scope, Assumptions, and Terminology

Scope

Existing Grid is running on X5 appliances (Grid Master, HA pairs, and/or standalone members).
Target platform is X6 appliances.
NIOS version meets X6 + mixed X5/X6 requirements (see below).

Assumptions

User has:
- Admin access to Grid Manager and CLI on all X5 nodes.
- Infoblox Support Portal account with entitlements for X6 vNIOS licenses.

Terminology

GM - Grid Master
GMC - Grid Master Candidate
HA pair - Active/Passive pair using VRRP (VIP, node1, node2)

High Level Migration Pattern Overview

You will follow this pattern for each X5 node being replaced:

Pre‑deploy the corresponding X6 VM with temp IP and licenses.
For HA pairs:
1. Always replace the passive node first.
2. Then force failover so X6 becomes active.
3. Then replace the remaining X5 node.
For standalone nodes:
1. Shut down X5.
2. Move its IP(s) to X6.
3. Join X6 to Grid as that member.
Preserve IPs and hostnames so upstream clients and Anycast/load balancers see no change.

Migration Steps

Pre-Work on Existing X5 Grid

1.1 Confirm NIOS Version and X6 Support

In Grid Manager:
1. Go to Grid → Grid Manager → Members.
2. Confirm that Grid Master (and Grid overall) runs NIOS 9.0.1 or later.
If Grid is below 9.0.1:
1. Plan and execute an upgrade to a supported 9.x release per standard Infoblox upgrade procedure and release notes.
2. Only proceed with X6/mixed X5 - X6 migration after upgrade completes.

Requirement: X6 + mixed X5/X6 and mixed HA are supported starting with NIOS 9.0.1+.

1.2 Capture Grid Membership and Security Settings

In Grid Manager:
1. Go to Grid → Grid Manager → Grid Properties → Edit.
2. Under Grid, record:
  1. Grid Name
Note the Grid Shared Secret (this was previously created, and if not known by the user or stored elsewhere, it cannot be viewed once created and redacted in the Grid Properties. Create a new Grid Shared Secret if you don’t know the previously created one. Important Note - Online grid members already joined to the grid will not be effected by a changed Grid Shared Secret. Offline members will need to be reset and rejoined with the grid.
Record GM and member IPs:
1. Go to Grid → Grid Manager → Members.
2. Export or note:
  1. GM VIP
  2. Each member’s LAN1, HA IP’s.

Grid Name, Shared Secret, and GM VIP will be used during the set membership step later on.

1.3 Take a Fresh Grid Backup

In Grid Manager:
1. Go to Grid → Grid Manager → Toolbar On Far Right: Backup.
2. Take a full Grid backup.
3. Download and store the backup off‑system (not on any node or ESXi datastore).

Keep this backup until after a full burn‑in period on X6 (one or two maintenance cycles).

Setting Up New X6 Appliance

2.1 Power On and Access NIOS CLI

At the console login prompt:

login: admin

password: infoblox

Default credentials are admin / infoblox (change later).

You should see the CLI prompt:

Infoblox >

2.2 Temporary Licenses (Optional - for Staging)

If permanent licenses are not yet available, you can use a temporary 60‑day license so the appliance can join the Grid and run services while you finalize licensing.

From the CLI:

Infoblox > set temp_license
1. DNSone (DNS, DHCP)
2. DNSone with Grid (DNS, DHCP, Grid)
3. Network Services for Voice (DHCP, Grid)
4. Add NIOS License
5. Add DNS Server license
6. Add DHCP Server license
7. Add Grid license
...
Select license (1-20) or q to quit: 4

Apply the Grid temporary license? (y or n): y

Ensure you have at least Grid + NIOS licenses present to join the Grid.

The appliance will restart after applying licenses in some cases; wait for reboot if prompted.

Initial Network Configuration on X6 (Temporary IP)

Before you swap IPs from X5, configure each X6 VM with a temporary LAN1 IP.

From CLI on the X6 VM:

Infoblox > set network
NOTICE: All HA configurations are performed from the GUI. This interface is used only to configure a standalone node or to join a Grid.

Enter IP address: 192.0.2.50 # temporary IP for LAN1
Enter netmask: [Default: 255.255.255.0]: 255.255.255.0
Enter gateway address [Default: 192.0.2.1]: 192.0.2.1
Become Grid member? (y or n): n
The network settings have been updated.

This brings the node up as a standalone appliance not yet joined to the Grid.

Test connectivity:

Infoblox > ping 192.0.2.1 # default gateway
Infoblox > ping <GM_VIP_IP> # Grid Master VIP

Successful ping validates network path and routing.

Detailed Migration — HA Pair: X5 Hardware → X6 vNIOS

Repeat this section for each HA pair. Always start with the less critical / least busy pair if possible.

4.1 Identify HA Pair and Passive Node

In Grid Manager:
1. Go to Grid → Grid Manager → Members.
2. Locate the HA pair (the member row will show two nodes).
3. Confirm which node is Active and which is Passive.

4.2 Shut Down the Passive X5 Node

You must fully stop the passive X5 hardware before moving its IP to X6.

Option A - GUI

In Grid Manager → Members:
1. Select the HA member (the X5 pair).
2. Click Control → Shutdown.
3. Choose the appropriate node (Passive) if prompted.
4. Confirm shutdown.

Option B - CLI on X5 node

From the X5 console/SSH:

login: admin
password: <X5_admin_password>

Infoblox > shutdown
This will power off the appliance. Are you sure? (y or n): y

Wait until the X5 node is fully powered off (console stopped, no network traffic).

4.3 Move IPs from Passive X5 to X6 VM

On the corresponding X6 VM (currently using temporary IP):

login: admin
password: <current_admin_password>
Infoblox >

2. Reconfigure network to use the old X5 node’s IPs (for LAN1, HA, MGMT as applicable).

Example:

Infoblox > set network

NOTICE: All HA configurations are performed from the GUI. This interface is used only to configure a standalone node or to join a Grid.

Enter IP address: <OLD_X5_LAN1_IP>
Enter netmask: [Default: <old_netmask>]: <OLD_X5_NETMASK>
Enter gateway address [Default: <old_gateway>]: <OLD_X5_GATEWAY>
Become Grid member? (y or n): n
The network settings have been updated.

If the node uses MGMT and HA interfaces, you will configure those later via GUI after Grid join, but the LAN1 IP must match the old X5 LAN1 IP so Grid membership mapping works.

3. Test connectivity from the X6 VM:

Infoblox > ping <default_gateway>
Infoblox > ping <GM_VIP_IP>
Infoblox > ping <HA_peer_LAN_or_VIP>

All pings should be successful.

4.4 Join X6 appliance to the Grid as Replacement Member

On the X6 VM CLI:

Infoblox > set membership
Enter Grid Master VIP: <GM_VIP_IP>
Enter Grid Name: <GRID_NAME> # from Section 1.2
Enter Grid Shared Secret: <SHARED_SECRET>

Join Grid as member with attributes:
Join Grid Master VIP: <GM_VIP_IP>
Grid Name: <GRID_NAME>
Grid Shared Secret: <SHARED_SECRET>
WARNING: Joining a Grid will replace all the data on this node!
Is this correct? (y or n): y
Are you sure? (y or n): y
The network settings have been updated.

This command instructs the X6 VM to join as a Grid member, using its current IP and matching the pre‑existing member record for the old X5 node (same IP, hostname, etc.).

What happens:

X6 connects to GM using the GM VIP and shared secret.
GM recognizes the IP/hostname as the existing member and rebinds that member to the new HWID.
X6 pulls full configuration and database from GM.

4.5 Wait for Full Synchronization

In Grid Manager → Members:
1. Verify the HA pair shows:
  1. X6 node now present where X5 was.
  2. Status Passive or Online / In Sync (depending on role in pair).
On X6 CLI, you can also run:

Infoblox > show network
Infoblox > show grid

to verify Grid membership and network state.

Do not proceed until status is fully In‑Sync / OK.

4.6 Force HA Failover so X6 Becomes Active

Once the X6 node is in sync as Passive, promote it to Active.

In Grid Manager → Members:
1. Select the HA member.
2. Click Control → Force HA Failover.
3. Confirm.
Wait for:
1. X6 node to become Active.
2. Remaining X5 node to become Passive.
3. Status shows In Sync / OK.

This step ensures production traffic is now served by X6 before you replace the second node.

4.7 Replace the Remaining X5 Node in the HA Pair

Repeat Sections 4.2 - 4.5 for the remaining X5 node:

Confirm the remaining X5 node is Passive (if not, force failover one last time so it becomes Passive).
Shut down that Passive X5 node (GUI or CLI).
On the second X6 VM:
1. Reconfigure set network to use the second X5 node’s LAN1 IP (and later MGMT/HA if needed).
2. Run set membership with GM VIP, Grid Name, Shared Secret.
3. Wait for the HA pair to show both nodes as X6, with clear Active/Passive roles and in‑sync status.

At the end:

The HA pair consists solely of two X6 vNIOS VMs.
The VIP and node IPs are unchanged from the original X5 pair.
All services (DNS, DHCP, Anycast, etc.) continue to function with minimal disruption.

Post-Migration Validation

5.1 Grid and HA Health

In Grid Manager:
1. Check Dashboard and Grid → Grid Manager → Members:
  1. All members Online / In Sync.
  2. HA pairs show clear Active / Passive states with only X6 nodes.
Check logs / alarms for any capacity or license warnings.

5.2 Service Validation

Perform representative tests for each role.

DNS:
- From several client segments, run:
  - Forward lookups (nslookup or dig) against the relevant X6 VIPs.
  - Reverse lookups where applicable.
- Verify RPZ/DTC/DFP behavior if in use.
DHCP:
- Renew or obtain leases on key scopes. Confirm:
  - Expected IP range.
  - Options & reservations behave as before.
Anycast / Load Balancers / BFD:
- Confirm routers / load balancers see the X6 VIPs as healthy next‑hops.
- Verify failover between HA nodes behaves correctly after forced failover tests.