Configuring an HACA Server Template

This section provides a sample of configuring an HACA server template using the merge method. You can also use the create method to configure an HACA server template.

**Table 1** Configuring an HACA server template
Operation	XPATH
edit-config:merge	/huawei-aaa-haca:aca

Data Requirements

**Table 2** Configuring an HACA server template
Item	Data	Description
Name of an HACA server template	hacaserver1	Configure an HACA server template named hacaserver1, enable HACA, set the IP address of the HACA server to 10.1.1.1, set the port number of the HACA server to 1111, configure a PKI realm named default, set the interval at which HACA heartbeat packets are sent to 200 minutes, set the interval for reconnecting to the HACA server to 200 minutes, and set the response timeout interval of the HACA server to 200 seconds.
Whether to enable HACA	true
IP address of an HACA server	10.1.1.1
Port number of an HACA server	1111
Name of a PKI realm	default
Interval at which HACA heartbeat packets are sent	200
Interval for reconnecting to the HACA server	200
Response timeout interval of an HACA server	200

Request Example

<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="43a8e485-35d2-499e-895c-e2d2d5f555a8">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config>
   <aca xmlns="urn:huawei:params:xml:ns:yang:huawei-aaa-haca">
    <haca-server xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:operation="merge">
     <name>hacaserver1</name>
     <vsys>public</vsys>
     <enable>true</enable>
     <server>
      <server-ip>10.1.1.1</server-ip>
      <port>1111</port>
     </server>
     <pki-domain>default</pki-domain>
     <heart-beat>200</heart-beat>
     <detection-function>
      <reconnect-interval>200</reconnect-interval>
     </detection-function>
     <timeout>200</timeout>
    </haca-server>
   </aca>
  </config>
 </edit-config>
</rpc>

Response Example

Sample of a successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="43a8e485-35d2-499e-895c-e2d2d5f555a8">
  <ok/>
</rpc-reply>