Configuring Whether to Enable Alarm Reporting

This section provides a sample of configuring whether to enable alarm reporting using the create method.

**Table 1** Configuring whether to enable alarm reporting
Operation	XPATH
edit-config:create	/ietf-alarms:alarms/control/notify-status-changes

Data requirement

**Table 2** Configuring whether to enable alarm reporting
Item	Data	Description
Alarm enablement status	true	Enables alarm reporting.

Request example

<?xml version='1.0' encoding='UTF-8'?>
<rpc message-id="6" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <edit-config>
    <target>
      <running/>
    </target>
    <error-option>rollback-on-error</error-option>
    <config>
      <alarms:alarms xmlns:alarms="urn:ietf:params:xml:ns:yang:ietf-alarms" xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0" xc:operation="create">
        <alarms:control>
          <alarms:notify-status-changes>true</alarms:notify-status-changes>
        </alarms:control>
      </alarms:alarms>
    </config>
  </edit-config>
</rpc>

Response example

Sample of successful response

<?xml version='1.0' encoding='UTF-8'?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="6">
  <ok/>
</rpc-reply>

Sample of failed response

<?xml version='1.0' encoding='UTF-8'?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="7">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>operation-failed</error-tag>
    <error-severity>error</error-severity>
    <error-message>parse rpc config error.</error-message>
  </rpc-error>
</rpc-reply>