Cisco Cisco Elastic Services Controller 2.3 Developer's Guide

    <status_message>VM [csr-reg__12605__vnf-tenant__vnf-tenantcsr-depcsr-
reg1.2__0__csr-vm__0] has been deployed as part of 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> 
      <vmid>250e515b-978f-4358-b455-124b72608ba2</vmid> 

      <hostid>a2f7615e78330dd28697588ddfb9516504b19642f53d39d7cff4f6ab</hostid> 
    </vm_target> 
    <event> 
      <type>VM_RECOVERY_DEPLOYED</type> 
    </event> 
  </escEvent> 
</notification> 

 

 

<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> 
  <eventTime>2015-04-28T23:39:21.125+00:00</eventTime> 
  <escEvent xmlns="http://www.cisco.com/esc/esc"> 
    <status>SUCCESS</status> 

    <status_message>Successfully recovered VM [csr-reg__12605__vnf-tenant__vnf-
tenantcsr-depcsr-reg1.2__0__csr-vm__0].</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> 
      <vmid>250e515b-978f-4358-b455-124b72608ba2</vmid> 
      <hostid>a2f7615e78330dd28697588ddfb9516504b19642f53d39d7cff4f6ab</hostid> 
    </vm_target> 
    <event> 
      <type>VM_RECOVERY_COMPLETE</type> 

    </event> 
  </escEvent> 
</notification> 

 

On Failure: 

An escEvent of type VM_RECOVERY_COMPLETE with a status of FAILURE will be sent to Netconf 
subscribers if the recovery workflow results in a failure. If a FAILURE event occurs, there may be cleanup 
required as described below under Handling Recovery Failures. 

If a failure occurs while attempting a recovery, the Netconf client should explicitly bring the 
configuration back to a consistent state by sending the corresponding Undeploy service configuration 
change. Refer to section 6.1.11 for Undeploy service configuration.  The Undeploy would send escEvents 
of type VM_UNDEPLOYED , DELETE_SUBNET (if any subnets were created during deployment) , 
DELETE_NETWORK (if any networks were created during deployment) and SERVICE_UNDEPLOYED . The