In the event the Forge appliance needs to be moved after its initial configuration, the IP addresses originally assigned to it will need to be changed as well.
There are three things you need to do to change the Forge appliance IP addresses gracefully:
Prepare any currently protected workloads for the change
Make the change
Reconfigure workloads to reflect the change
Before you can change the IP addresses assigned to a PlateSpin Forge appliance, any currently protected workloads need to be paused.
NOTE:Ensure at least one incremental has been run for each workload prior to relocating it (changing its IP address).
To pause currently protected workloads:
Login to the PlateSpin Forge web client.
Select all the workloads and click.
The status Paused is displayed in the column for all the workloads.
NOTE:Wait for any running replications to complete before proceeding to Making the Change.
If you are changing IP address(es) because you want to physically move the Forge appliance, follow the steps in To shutdown the Forge Management VM and To shutdown the Appliance Host. Otherwise, you can now proceed to the next part of the IP Change procedure: Making the Change.
There are three ways that you can shutdown the Forge Management VM:
Use a web browser:
Logon to the Forge web client
Click thelink at the bottom of the page to open the Forge Management VM Settings page.
Use Remote Desktop:
Connect to the Forge Management VM using Remote Desktop.
Use the VMware Infrastructure Client:
NOTE:If the VMware Infrastructure Client is already installed, skip to Step 3.c.
From a workstation other than your Forge appliance, open a Web browser and navigate to the ESX Server’s IP address (the Appliance Host IP address).
Click thelink, and then follow the instructions to download and install the software. Ignore any SSL warnings.
On your Forge appliance, select.
Login using the ESX Server (Appliance Host) IP address and the username/password you setup.
The VIC Inventory UI is displayed.
Click on the Console tab.
In Windows, select.
Once the Forge Management VM is shutdown, you need to shutdown the Appliance Host.
At the Forge Console, press Alt-F2 to switch to the ESX Server console.
NOTE:To switchback to the Forge Console, press Alt-F1.
Login as the superuser using login ID root and the password you setup.
Type in shutdown and hit Enter.
Once the Forge Appliance Host is shutdown, power the appliance down and perform the physical move. When the appliance is in the new location, make all required connections and power it on.
You can now proceed to the next part of the IP Change procedure: Making the Change.
When all the currently protected workloads are paused, you can proceed with changing the IP addresses.
NOTE:If you want to change IP address(es) because you are physically moving the Forge appliance, move the appliance prior to proceeding.
To change the IP address:
At the Forge console, login as the superuser. This is root for the field and the password you setup during the initial configuration in the field. Click .
The PlateSpin Forge Appliance Configuration dialog is displayed.
If you only want to change the Management VM IP address, click Step 4.and proceed to
Change theaddress, , and IP address as desired for the Appliance Host. Optionally, you can change the as well. Click .
The PlateSpin Forge Appliance Host credentials dialog is displayed.
NOTE:You may also use DHCP, but only if static IP lease is enabled. It is also recommended that in multiple appliance environments you should assign unique hostnames to the appliances to avoid hostname conflicts.
Login using the PlateSpin Forge Appliance Host login and password setup during the initial configuration of the appliance. Click.
The PlateSpin Forge Management VM network settings dialog is displayed.
If you only want to change the Appliance Host IP address, click Step 7.and proceed to
Change theaddress, , and IP address as desired for the Management VM. Optionally, you can change the as well. Click .
NOTE:You may also use DHCP, but only if static IP lease is enabled. It is also recommended that in multiple appliance environments you should assign unique hostnames to the Management VMs to avoid hostname conflicts.
If aside from IP address changes, you also want to change the workgroup or domain assignment, click Step 9.. Otherwise, click and proceed to
Enter the domain, and or specify the Workgroup to which you want to add the Forge Appliance. Click .
A configuration review dialog is displayed with a summary of the parameters you have changed. Use this information to verify your settings. Clickto accept the changes.
Your changes, if any, are applied to the Management VM.
NOTE:You can selectat this point to abandon the changes or use to go and edit your changes.
You can now proceed to the third part of the IP Change procedure: Reconfiguring Workloads to Reflect the Change.
Once you have physically moved the Forge appliance (if necessary) and changed the IP address(es) of the Forge appliance, you might need to reconfigure the replication IP addresses of any currently protected (and paused) workloads so that they adhere to any new subnets or networks as a result of the move.
NOTE:If you cannot connect to the Forge web client after changing the Forge Appliance Host or Management VM IP addresses, verify that the Windows firewall has not been set to On. If it has, set it to Off and try connecting again.
To reconfigure workloads to reflect the change:
Login to the PlateSpin Forge web client.
Click the Workloads tab.
For each workload:
Click the name of the workload in the Workload column.
The Workload Details page is displayed.
In the Replication Settings section, change the Replication Network configuration to reflect the changes you made to the PlateSpin Forge appliance IP address.
Clickat the bottom of the Workload Details page.
Click the Workloads tab to return to the Workloads page.
Once all the paused workloads have been reconfigured, select all the workloads on the Workloads page and click.
The workloads return to their previous replication schedule.
NOTE:Changing the replication IP address for a workload using the Block-based Transfer Method will cause a warning to display in the Workload Details page notifying you that the production workload (source machine) will reboot after the next scheduled incremental replication runs. You can manually run the incremental replication instead of waiting for the schedule, forcing an immediate reboot of the production workload, if desired.
WARNING:The first incremental replication after a source reboot may fail if the source hasn’t completely rebooted when the incremental runs. If this occurs, manually run the replication again or wait for the next scheduled replication.
To manually run a scheduled incremental replication:
Logon to the PlateSpin Forge web client.
The Workloads page is displayed.
Select the workload(s) for which you would like to manually run incremental replication(s).
Incremental replications using the Block-based transfer method that have had their Replication IP address(es) changed since their last scheduled replication will force the production workload(s) to reboot.
NOTE:Manual incremental replications do not remove the next scheduled incremental replication for that workload from the schedule, but in the above scenario they do remove the forced reboot.