Savvis provider issues

This topic contains information to help you troubleshoot the Savvis resource provider. For information about troubleshooting BMC Cloud Lifecycle Management, see Troubleshooting.

You can check the following log files for entries that might help diagnose the problem:

Log file	Location
csm.log	Windows: C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\logs\csm.log Linux: /opt/bmc/BMCCloudLifeCycleManagement/Platform_Manager/logs/csm.log
processes.log	Windows: C:\Program Files\BMC Software\AO-Platform\CDP\tomcat\logs\processes.log Linux: /opt/bmc/AO-Platform/CDP/tomcat/logs/processes.log

The following table contains explanations and workarounds for problems you might encounter when working with the Savvis resource provider:

Problem	Solution
Provisioning in Savvis fails due to incorrect disk, RAM and CPU values.	Ensure that blueprint is configured with allowable values from Savvis.
Delay in Network Container and VM creation and VM operations.	Savvis manually handles failures. This will be corrected by Savvis finally and will be reflected in BMC Cloud Lifecycle Management.
Failure in Savvis operations due to poll timeout.	Increase poll interval and/or poll count.

Savvis provider issues

Comments