About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Getting help and support for IBM® Power® Virtual Server with VPC landing zone
If you experience an issue or have questions when deploying Power Virtual Server with VPC landing zone, you can use the following resources before you open a support case.
- Review the FAQs in the deployment guide.
Check the status of the IBM Cloud platform and resources by going to the Status page.
Review the GitHub issues to see
whether other users experienced the same problem.- Review the troubleshooting documentation to troubleshoot and resolve common issues.
Ask product experts and the community questions on the sap-on-power-deployable-architectures Slack
channel.
If you still can't resolve the problem, you can open a support case. For more information, see Creating support cases. And, if you're looking to provide feedback, see Submitting feedback.
Providing support case details
To ensure that the support team can start investigating your case to provide a timely resolution, include details from the Schematics logs:
-
Find the Schematics log:
- In the IBM Cloud console, go to Schematics > Workspaces > deployable architecture instance.
- From the workspace Activity page, select the Schematics apply action that failed.
- Click Jobs to see the detailed log output.
-
Provide errors from the Schematics log:
-
In the log file, find the last action that Schematics started before the error occurred. For example, in the following log output, Schematics tried to run a copy script in the
instances_modulemodule by using the Terraformnull_resource.2021/05/24 05:03:41 Terraform apply | module.instances_module.module.compute_remote_copy_rpms.null_resource.remote_copy[0]: Still creating... [5m0s elapsed] 2021/05/24 05:03:41 Terraform apply | 2021/05/24 05:03:42 Terraform apply | 2021/05/24 05:03:42 Terraform apply | 2021/05/24 05:03:42 Terraform apply | Error: timeout - last error: ssh: rejected: connect failed (Connection timed out) -
Paste the errors into the case details.
-
-
Provide the architecture name, source URL, and version from the log:
- In the log file, find the architecture information. In the following example, you see the
Related Workspace,sourcerelease, andsourceurl:
023/04/13 20:50:40 Related Workspace: name=auto-test-infra-osa21-13-04-2023, sourcerelease=(not specified), sourceurl=https://github.com/terraform-ibm-modules/terraform-ibm-powervs-infrastructure/archive/v4.2.0.tar.gz, folder=terraform-ibm-powervs-infrastructure-4.2.0/examples/ibm-catalog/deployable-architectures/full-stack- Copy the architecture information and paste it into the case details.
- In the log file, find the architecture information. In the following example, you see the
Routing your support case
To route your support case correctly to speed up resolution, select the applicable product when you open the case.
Routing when you can't deploy successfully
If you can't deploy your deployable architecture, open a support case with the most likely cause of the issue:
- If you identified the service that you think is causing the error from the Schematics log, use the name of that service as the product name in the case.
- If you can't identify the error from the Schematics log, use the name of the deployable architecture as it is listed in the IBM Cloud catalog.
Routing when you deployed successfully
If you successfully deployed, yet have an issue with a service in the deployable architecture, open a support case and use the name of that service.