Hi everyone,
We are planning to migrate our firewall management interface from an old subnet (e.g., 192.168.0.0/26) to a new one (e.g., 192.168.100.0/26), and I would like to ask for best practices to perform the change without losing connectivity to the firewall during the transition.
Current situation:
- Management interface is currently in 192.168.0.0/26
- The new subnet will be 192.168.100.0/26, with:
- .1 = VIP
- .2 = FW1
- .3 = FW2
Static routes will be updated accordingly:
All current static routes pointing to 192.168.0.X will be switched to point to the new IP 192.168.100.10.
Question:
We identified two possible migration options, but we’re looking for advice on the safest path:
Option 1: Use a free physical interface (e.g., eth1-02)
- If confirmed, we could reassign this port for the new management IP and swap routes once reachable
Option 2: Reuse the existing interface by switching port mode to trunk
- Convert the switch port from access to trunk
Objective:Perform the migration with no loss of connectivity, particularly for remote management and routing.
If anyone has gone through a similar migration or has specific recommendations (including hidden gotchas), your input would be highly appreciated!
Thanks in advance!