Cisco Cisco Elastic Services Controller 2.1 Developer's Guide
Recovery Initialize
When a VM recovery is triggered, an escEvent of type VM_RECOVERY_INIT with a status of SUCCESS will
be sent to Netconf subscribers. This indicates that the recovery workflow has been started. This will
hard reboot the VM instance and checks if the VM comes back up.
If the VM comes up successfully, an escEvent of type VM_RECOVERY_COMPLETE with a status of
SUCCESS with be sent.
be sent to Netconf subscribers. This indicates that the recovery workflow has been started. This will
hard reboot the VM instance and checks if the VM comes back up.
If the VM comes up successfully, an escEvent of type VM_RECOVERY_COMPLETE with a status of
SUCCESS with be sent.
Attempts for recovery
If the VM did not come up after this attempt, then ESC tries to undeploy and redeploy the VM and
corresponding escEvent of type VM_RECOVERY_UNDEPLOYED and VM_RECOVERY_DEPLOYED will be
sent. If the undeploy and redeploy also fails to get the VM back up, this undeploy and redeploy cycle will
be retried to a maximum value of “
corresponding escEvent of type VM_RECOVERY_UNDEPLOYED and VM_RECOVERY_DEPLOYED will be
sent. If the undeploy and redeploy also fails to get the VM back up, this undeploy and redeploy cycle will
be retried to a maximum value of “
vm_recovery_retries_max
”
times which is configurable.
Recovery complete
If the VM comes alive at any attempt during the undeploy and deploy, an escEvent of type
VM_RECOVERY_COMPLETE with a status of SUCCESS with be sent. But if the VM does not come up after
all the redeploy attempts, then
all the redeploy attempts, then
an escEvent of type
VM_RECOVERY_COMPLETE with a status of FAILURE
will be sent.
The various event notifications generated during VM recovery are given below.
Success Event notifications
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-04-28T23:38:45.107+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>Recovery event for VM [csr-reg__12605__vnf-tenant__vnf-tenantcsr-
depcsr-reg1.2__0__csr-vm__0] triggered. Processing Auto healing. Proceeding with
Recovery.</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>3e0d269a-c3a4-454a-832f-44e0528ed2c1</depid>
<vm_group>csr-vm</vm_group>
<vm_source>
<vmid>9b252ece-7973-4b1f-832e-fe53c68fb963</vmid>
<hostid>a2f7615e78330dd28697588ddfb9516504b19642f53d39d7cff4f6ab</hostid>
</vm_source>
<vm_target/>
<event>
<type>VM_RECOVERY_INIT</type>
</event>
</escEvent>
</notification>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-04-28T23:38:52.073+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>VM [csr-reg__12605__vnf-tenant__vnf-tenantcsr-depcsr-
reg1.2__0__csr-vm__0] has been undeployed.</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>3e0d269a-c3a4-454a-832f-44e0528ed2c1</depid>
<eventTime>2015-04-28T23:38:52.073+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>VM [csr-reg__12605__vnf-tenant__vnf-tenantcsr-depcsr-
reg1.2__0__csr-vm__0] has been undeployed.</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>3e0d269a-c3a4-454a-832f-44e0528ed2c1</depid>