Cisco Cisco Elastic Services Controller 2.2 Developer's Guide
<vm_group>CSR</vm_group>
<vm_source>
<vmid>5283bcab-c1c3-4699-9bbe-cf143b26c6aa</vmid>
<hostid>c64e652a4561392ae20ae702eceae53e417302e0d2d63e41d66a15cc</hostid>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>VM_MONITOR_SET</type>
</event>
</escEvent>
</notification>
<vm_source>
<vmid>5283bcab-c1c3-4699-9bbe-cf143b26c6aa</vmid>
<hostid>c64e652a4561392ae20ae702eceae53e417302e0d2d63e41d66a15cc</hostid>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>VM_MONITOR_SET</type>
</event>
</escEvent>
</notification>
6.2.2.6 Recovery VM
6.2.2.6.1 Netconf Request
<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<recoveryVmAction xmlns="http://www.cisco.com/esc/esc">
<actionType>DO</actionType>
<vmName> sampleVmName </vmName>
</recoveryVmAction>
<recoveryVmAction xmlns="http://www.cisco.com/esc/esc">
<actionType>DO</actionType>
<vmName> sampleVmName </vmName>
</recoveryVmAction>
</rpc>
6.2.2.6.2 Netconf Response
An rpc-reply response is returned with a status of ok if the request was accepted for
activation, or a status of rpc-error if the request was rejected. See section
activation, or a status of rpc-error if the request was rejected. See section
a Configuration Request for more details.
6.2.2.6.3 Event Notifications
When the rpc-reply response is OK, then the recovery begins. This recovery procedure is the same as
auto recovery. Event notifications are as follows. Here is the default recovery policy setting:
REBOOT_THEN_REDPLOY. For details of recovery workflow, please refer to the ESC user document.
auto recovery. Event notifications are as follows. Here is the default recovery policy setting:
REBOOT_THEN_REDPLOY. For details of recovery workflow, please refer to the ESC user document.
VM Recovery Init:
<?xml version="1.0" encoding="UTF-8"?>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2016-06-23T18:12:04.519+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_code>200</status_code>
<status_message>Recovery event for VM [depzz_g1_0_50521f93-7374-4881-960b-
95aa13d55ddf] triggered. </status_message>
<depname>depzz</depname>
<tenant>ttt</tenant>
<tenant_id>721d0a0aaf5a40299650d4ec74f48f1a</tenant_id>
<svcid>NULL</svcid>
<depid>d4778a3a-deba-4df7-9614-03f31f1beab3</depid>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2016-06-23T18:12:04.519+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_code>200</status_code>
<status_message>Recovery event for VM [depzz_g1_0_50521f93-7374-4881-960b-
95aa13d55ddf] triggered. </status_message>
<depname>depzz</depname>
<tenant>ttt</tenant>
<tenant_id>721d0a0aaf5a40299650d4ec74f48f1a</tenant_id>
<svcid>NULL</svcid>
<depid>d4778a3a-deba-4df7-9614-03f31f1beab3</depid>
<vm_group>g1</vm_group>
<vm_source>
<vmid>1dd943b9-93a4-4987-b26b-1b8fd264774d</vmid>
<vmid>1dd943b9-93a4-4987-b26b-1b8fd264774d</vmid>
<hostid>4f926bb44423804ea8d87cac946b80e637c315f4f606bfa788b19b8c</hostid>
<hostname>my-ucs-7</hostname>
</vm_source>
<vm_target/>
<event>
<type>VM_RECOVERY_INIT</type>
</event>
<hostname>my-ucs-7</hostname>
</vm_source>
<vm_target/>
<event>
<type>VM_RECOVERY_INIT</type>
</event>