Cisco Cisco Elastic Services Controller 2.2 開発者ガイド

                  <bootup_time>600</bootup_time> 
                  <recovery_wait_time>0</recovery_wait_time> 
                  <interfaces> 
                    <interface> 
                      <nicid>0</nicid> 
                      <network>N/A</network> 
                    </interface> 
                  </interfaces> 
                  <kpi_data> 
                    <kpi> 
                      <event_name>VM_ALIVE</event_name> 
                      <metric_value>50</metric_value> 

                      <metric_cond>GT</metric_cond> 
                      <metric_type>UINT32</metric_type> 
                      <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> 
                  <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> 
                    <max_active>0</max_active> 
                    <elastic>true</elastic> 
                  </scaling> 
                </vm_group> 
              </deployment> 
            </deployments> 

          </tenant> 
        </tenants> 
      </esc_datamodel> 
</config> 

  </edit-config> 
 
</rpc>

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 

  for more details.