Cisco Cisco Elastic Services Controller 1.0 Guide Du Développeur
<metric_occurrences_true>3</metric_occurrences_true>
<metric_occurrences_false>3</metric_occurrences_false>
<metric_collector>
<type>ICMPPing</type>
<nicid>0</nicid>
<poll_frequency>15</poll_frequency>
<polling_unit>seconds</polling_unit>
<continuous_alarm>false</continuous_alarm>
</metric_collector>
</kpi>
</kpi_data>
<metric_occurrences_false>3</metric_occurrences_false>
<metric_collector>
<type>ICMPPing</type>
<nicid>0</nicid>
<poll_frequency>15</poll_frequency>
<polling_unit>seconds</polling_unit>
<continuous_alarm>false</continuous_alarm>
</metric_collector>
</kpi>
</kpi_data>
<rules>
<admin_rules>
<rule>
<event_name>VM_ALIVE</event_name>
<action>ALWAYS log</action>
<action>FALSE recover autohealing</action>
<action>TRUE servicebooted.sh</action>
</rule>
</admin_rules>
<admin_rules>
<rule>
<event_name>VM_ALIVE</event_name>
<action>ALWAYS log</action>
<action>FALSE recover autohealing</action>
<action>TRUE servicebooted.sh</action>
</rule>
</admin_rules>
</rules>
<config_data>
<configuration>
<dst>iosxe_config.txt</dst>
<file>N/A</file>
</configuration>
</config_data>
<scaling>
<min_active>0</min_active>
<config_data>
<configuration>
<dst>iosxe_config.txt</dst>
<file>N/A</file>
</configuration>
</config_data>
<scaling>
<min_active>0</min_active>
<max_active>0</max_active>
<elastic>true</elastic>
</scaling>
</vm_group>
</service_definition>
</services>
</tenant>
</tenants>
</esc_datamodel>
<elastic>true</elastic>
</scaling>
</vm_group>
</service_definition>
</services>
</tenant>
</tenants>
</esc_datamodel>
</config>
</edit-config>
</rpc>
</edit-config>
</rpc>
5.1.11.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
status of rpc-error if the request was rejected. See section
5.1.11.3 Configuration Activation
On Success:
A successful update Service workflow will trigger events and operational data changes for the added
VNF.
VNF.
Event notification
The process for deploying a VM for the added VNF is the same as the deployment section including the
notifications sent (see deployment section) such as a VM_DEPLOYED and VM_ALIVE escEvent with a
success status.
notifications sent (see deployment section) such as a VM_DEPLOYED and VM_ALIVE escEvent with a
success status.