Limitations when managing resources outside of PowerVC
When you switch from using PowerVC to manage your resources to accessing the managed resource directly, you might see unexpected or adverse results in PowerVC.
As you begin to manage resources in PowerVC, you might want to perform certain operations directly on the resource. For example, you are managing a virtual machine with PowerVC, but you use another method to stop the virtual machine. In this case, PowerVC might not be notified that the virtual machine was stopped and might not immediately reflect the updated status of the virtual machine. PowerVC typically polls a resource to obtain an updated the next time that you use PowerVC to manage the resource. As a result, operations from PowerVC might fail until the state of the virtual machine in PowerVC is the same as the state on the virtual machine itself.
When you perform a management operation outside of PowerVC, such as adding or deleting resources, the action can adversely affect the operation of PowerVC and the data center. For example, you might delete a virtual machine by using a Platform Manager for the virtual machine. The virtual machine goes into Error state and you need to take the additional step of deleting the virtual machine in PowerVC. Similar results can occur when you remove a disk or network device for a virtual machine that PowerVC is managing.
For appropriate results, use PowerVC to perform management tasks on the virtual machines and associated resources in your PowerVC environment.