Cisco Cisco Intelligent Automation for Cloud 4.3.1 User Guide

Page of 208
176
Error Remediation
Remediating Errors
8.
Proceed to Remediating Errors to take action.
Remediating Errors
If you ever receive an e-mail notification of a discovery error related to a platform element you defined, follow the 
instructions in this section to remediate the error.
1.
Choose Operations > Error Remediation.
2.
The Error Remediation Portlet displays.
3.
To remediate an error, click the gear icon 
 next to the error you want to fix.
4.
From the Remediation pop-up, click one of the following, as appropriate.
Cancel—(Always available) Halt the service immediately and take no further action. No cleanup or verification of 
the integrity of data is performed.
Restart—Performs a Cancel followed by Restart. To do a rollback it requires a special rollback flag set in the ERS 
instrumentation. The flag is set to False by default.
Retry—Attempts to resume service fulfillment at the step that failed. A retry of the step is executed from a start 
point set in the service orchestration.
Ignore—Attempts to resume service fulfillment, skipping the step that failed.
Rollback—Relinquishes all resources, all infrastructure and service item changes are reversed, and restores the 
cloud to the state prior to the service fulfillment request. In the case of Restart, the Rollback flag is set to true, 
so a Rollback is getting executed on Restart. 
5.
Choose to send an email (optional).
Note:
 Sending an email is only available for Cancel and Rollback operations. It will send an email to the end user who 
submitted the request that the request did fail.
6.
Close the popup.
Handling Infrastructure Errors
As a Cloud Provider Technical Administrator, you are entrusted with maintaining the cloud system and ensuring maximal 
uptime. If problems arise with fulfillment of a customer’s requisition (for example, a new virtual machine), you receive an 
email notification error with error code, Description, automation summary link and link to the Cloud Service Errors portlet. 
Service problems can arise in any of the following conditions:
Blade error has disabled all VMs running on it
Blade error has occurred on a physical blade
Cisco UCS Manager, VMware vCenter, LDAP server, or blades in the physical pool have failed
Connection is lost
Capacity has reached the maximum limit
The notification will identify the failing service and provide any or all of the following information:
Automation summary
Steps you must take to fix the problem, such as: