Configuring an Interface to Report EFM Errored Frame Seconds

This section provides a sample of configuring an interface to report EFM errored frame seconds using the edit-config method.

**Table 1** Configuring an interface to report EFM errored frame seconds
Operation	XPATH
edit-config	/ietf-interfaces/interfaces/interface/name /ietf-interfaces/interfaces/interface/huawei-efm:efm/error-frame-second/enabled

Data Requirements

Item	Data	Description
Interface name	GigabitEthernet0/0/1	Specify the interface that needs to be configured to report EFM errored frame seconds.
Whether the interface is configured to report EFM errored frame seconds	true	Configure an interface to report EFM errored frame seconds.

Request Example

<?xml version='1.0' encoding='UTF-8'?>
<rpc message-id="17" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <if:interfaces xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces">
        <if:interface>
          <if:name>GigabitEthernet0/0/1</if:name>
          <huawei-efm:efm xmlns:huawei-efm="urn:huawei:params:xml:ns:yang:huawei-efm">
            <huawei-efm:error-frame-second>
              <huawei-efm:enabled>true</huawei-efm:enabled>
            </huawei-efm:error-frame-second>
          </huawei-efm:efm>
        </if:interface>
      </if:interfaces>
    </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="17">
  <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="17">
  <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>