Migrating existing network configurations to Power Edge Router

IBM Power Virtual Server located in IBM data centers: Off-premises

IBM Power Virtual Server Private Cloud: On-premises

If you have manually configured subnets and Direct Link through a support ticket, consider migrating your workspace to Power Edge Router (PER). With PER, you can use the built-in redundancy and much higher bandwidth.

To migrate your workspace to PER, complete the following steps:

1. Create a case from the Support Center of IBM Cloud.

2. Select Workspace for Power Virtual Server and Power VS Network Related under Topic and Subtopic respectively.

3. Provide a short description of your migration requirements in the Subject.

4. In the Description box under additional information, provide the following information and click Next:

   1. The CRN (Cloud Resource Name) of your workspace that you want to upgrade.
   2. The list of subnets configured in the workspace.
   3. The list of Direct Link connections to which the subnets are attached.

   The IBM Power Virtual Server operation team processes the support ticket by configuring the PER and other network devices in parallel to the Direct Link configuration. When the PER configuration is complete, you are notified through a ticket update that the PER configuration is ready for your validation and testing.

5. Schedule a maintenance window, during which you need to provision the Transit Gateway to conclude the PER network construction. See the PER use cases for more information. To force the network to go through the PER network, complete the following steps:

   1. From the IBM Cloud catalog, browse your provisioned Direct Link connections.
   2. Click a Direct Link connection to open the connection details page.
   3. Click the BGP tab and then open the Route Filter details.
   4. Under Import route filters and Export route filters, select Deny all import routes to block the Direct Link routes and force the traffic to go through the PER network.

   Repeat the preceding steps for each of the Direct Link connections. If you face any PER connectivity problem, you can revert to the Direct Link path. To revert, select Permit all import routes to unblock the Direct Link routes and disconnect the workspace from the Transit Gateway.

6. Upon successful testing, for example, through a ping test, delete the Direct Link connections and notify IBM by updating the ticket.

7. The Power Virtual Server team marks the workspace as Migrated and closes the ticket.

After the workspace is migrated to the PER network through the ticketing process, continue to refer to the support ticket for network configuration information (subnet create, delete, and update gateway). Before you delete your old migrated workspace, open a support ticket to remove the configuration of the backend devices. Then, you can delete the workspace.