Cisco Cisco Elastic Services Controller 1.1 Developer's Guide
<tenant>SystemAdminTenantId</tenant>
<vm_source>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>CREATE_SUBNET</type>
</event>
</escEvent>
</notification>
<vm_source>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>CREATE_SUBNET</type>
</event>
</escEvent>
</notification>
On Failure:
Event notification
An escEvent of type CREATE_ SUBNET with a status of FAILURE will be sent to Netconf subscribers if the
configuration action cannot be complete for some reason. If a FAILURE event occurs, there may be
cleanup required as described below under Handling Activation Failures
configuration action cannot be complete for some reason. If a FAILURE event occurs, there may be
cleanup required as described below under Handling Activation Failures
Handling Activation Failures
If a failure occurs while activating a Create Subnet configuration change, the Netconf client should
explicitly bring the configuration back to a consistent state by sending the corresponding Delete Subnet
configuration change. A Delete Subnet sent at this stage should return an <ok> status, and will also
generate a DELETE_SUBNET Success Notification. The configuration change can then be retried
explicitly by the Netconf client once the underlying issue is resolved.
explicitly bring the configuration back to a consistent state by sending the corresponding Delete Subnet
configuration change. A Delete Subnet sent at this stage should return an <ok> status, and will also
generate a DELETE_SUBNET Success Notification. The configuration change can then be retried
explicitly by the Netconf client once the underlying issue is resolved.