This section provides a sample of checking EFM session information using the get method.
Operation |
XPATH |
|---|---|
get |
/ietf-interfaces/interfaces-state/interface/huawei-efm:efm/efm |
<?xml version='1.0' encoding='UTF-8'?>
<rpc message-id="28" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter type="subtree">
<if:interfaces-state xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces">
<if:interface>
<if:name/>
<huawei-efm:efm xmlns:huawei-efm="urn:huawei:params:xml:ns:yang:huawei-efm"/>
</if:interface>
</if:interfaces-state>
</filter>
</get>
</rpc>
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="28">
<data>
<interfaces-state xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces">
<interface>
<name>GigabitEthernet0/0/1</name>
<efm xmlns="urn:huawei:params:xml:ns:yang:huawei-efm">
<port-efm-status>detect</port-efm-status>
<time-out>0</time-out>
<errored-code-statistics>
<errors>0</errors>
<error-running-total>0</error-running-total>
<event-running-total>0</event-running-total>
</errored-code-statistics>
<errored-frame-statistics>
<errors>0</errors>
<error-running-total>0</error-running-total>
<event-running-total>0</event-running-total>
</errored-frame-statistics>
<errored-frame-period-statistics>
<errors>0</errors>
<error-running-total>0</error-running-total>
<event-running-total>0</event-running-total>
</errored-frame-period-statistics>
<errored-frame-seconds-statistics>
<errors>0</errors>
<error-running-total>0</error-running-total>
<event-running-total>0</event-running-total>
</errored-frame-seconds-statistics>
</efm>
</interface>
<interface>
<name>NULL0</name>
</interface>
<interface>
<name>MEth0/0/1</name>
</interface>
<interface>
<name>Vlanif1</name>
</interface>
<interface>
<name>GigabitEthernet0/0/2</name>
</interface>
<interface>
<name>GigabitEthernet0/0/3</name>
</interface>
<interface>
<name>GigabitEthernet0/0/4</name>
</interface>
<interface>
<name>GigabitEthernet0/0/5</name>
</interface>
<interface>
<name>GigabitEthernet0/0/6</name>
</interface>
<interface>
<name>GigabitEthernet0/0/7</name>
</interface>
<interface>
<name>GigabitEthernet0/0/8</name>
</interface>
<interface>
<name>GigabitEthernet0/0/9</name>
</interface>
<interface>
<name>GigabitEthernet0/0/10</name>
</interface>
<interface>
<name>GigabitEthernet0/0/11</name>
</interface>
<interface>
<name>GigabitEthernet0/0/12</name>
</interface>
<interface>
<name>GigabitEthernet0/0/13</name>
</interface>
<interface>
<name>GigabitEthernet0/0/14</name>
</interface>
<interface>
<name>GigabitEthernet0/0/15</name>
</interface>
<interface>
<name>GigabitEthernet0/0/16</name>
</interface>
<interface>
<name>GigabitEthernet0/0/17</name>
</interface>
<interface>
<name>GigabitEthernet0/0/18</name>
</interface>
<interface>
<name>GigabitEthernet0/0/19</name>
</interface>
<interface>
<name>GigabitEthernet0/0/20</name>
</interface>
<interface>
<name>GigabitEthernet0/0/21</name>
</interface>
<interface>
<name>GigabitEthernet0/0/22</name>
</interface>
<interface>
<name>GigabitEthernet0/0/23</name>
</interface>
<interface>
<name>GigabitEthernet0/0/24</name>
</interface>
</interfaces-state>
</data>
</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="28">
<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>