Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Savvis Provider issues

See the following sections for information about troubleshooting issues of the Savvis 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

Provisioning in Savvis fails

If provisioning in Savvis fails due to incorrect disk, RAM and CPU values, you must ensure that the blueprint is configured with allowable values from Savvis.

Delay in Network Container and VM creation and VM operations

There might be 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

 If there is failure in Savvis operations due to poll timeout, you must increase the poll interval and/or poll count.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*