I have created new Direct Link 2.0 service to setup a interconnection between a IBM Cloud VPC and a IBM Power Subnet.
I have found out the routing won't automatically work after I created the connection. I will need to create support ticket, then support will setup the routing between the VPC and the Power subnet.
I suggest to add features :
Since the VPC and Power subnet is already defined in the DL 2.0 connection, the routing should be automatically created.
Additionally Customer should be provided with option to add larger subnet routing rules for the connection.
For example, if I have a VPC with address prefix 10.100.0.0/24 and a Power subnet 10.100.1.0/24, once I created the DL connection, the routing between them should be automatically created. I should also have option to tell Power subnet to route 10.0.0.0/8 , a bigger subnet through the VPC. That way we can setup VSI ( or IBM VPN server when it's capable ) as transit VPN gateway to allow full connectivity between Power subnet and On-premises network.
| Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
After the cloud connection is created, the customer has to associate the subnet with the cloud connection in PowerVS (step 4) as documented here: https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-cloud-connections#create-cloud-connections