Cisco Cisco Elastic Services Controller 1.1 Developer's Guide

    <svcid>90044227-1475-45c2-83ff-aed132f77256</svcid> 
    <depid>187bc0b5-9d0b-4c01-8353-89454a6a1da6</depid> 
    <vm_source> 
  </vm_source> 
    <vm_target> 
  </vm_target> 
    <event> 
      <type>SERVICE_ALIVE</type> 
    </event> 
  </escEvent> 
</notification> 

If there are errors during rebooting the service, there will be a final notification indicating the error: 

<?xml version="1.0" encoding="UTF-8"?> 
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> 
  <eventTime>2015-05-19T21:21:00.527+00:00</eventTime> 
  <escEvent xmlns="http://www.cisco.com/esc/esc"> 
    <status>FAILURE</status> 
    <status_message>Service group reboot failed</status_message> 
    <svcname>CIRROS_HEZH</svcname> 
    <svcversion>1.6</svcversion> 

    <depname>dep</depname> 
    <tenant>hezh-yesc-0520</tenant> 
    <svcid>90044227-1475-45c2-83ff-aed132f77256</svcid> 
    <depid>187bc0b5-9d0b-4c01-8353-89454a6a1da6</depid> 
    <vm_source> 
  </vm_source> 
    <vm_target> 
  </vm_target> 

    <event> 
      <type>SERVICE_ALIVE</type> 
    </event> 
  </escEvent> 
</notification> 

 

5.2.1.4.1  Netconf Request  

<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> 
  <edit-config> 
    <target> 
      <running/> 
    </target> 

    <config> 
      <serviceAction xmlns="http://www.cisco.com/esc/esc"> 
        <actionType>DISABLE_MONITOR</actionType> 
        <tenantName>sampleTenant</tenantName> 
        <depName>sampleDep </depName> 
        <serviceName>SampleSvc</serviceName> 
        <serviceVersion1.1</serviceVersion> 
      </serviceAction> 
    </config> 
  </edit-config> 
</rpc> 
 

5.2.1.4.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 

a Configuration Request  for more details.