Configuring the Type of Packets that Can Trigger 802.1X Authentication

This section provides a sample of configuring the type of packets that can trigger 802.1X authentication using the merge method.

**Table 1** Configuring the type of packets that can trigger 802.1X authentication
Operation	XPATH
edit-config:merge	/huawei-nac-dot1x:dot1x-access/configure-mode/unified-mode/dot1x-access-profile/trigger-packet

Data Requirements

**Table 2** Configuring the type of packets that can trigger 802.1X authentication
Item	Data	Description
name	test	Configure the 802.1X access profile named test.
trigger-packet	dhcp arp	Configure the device to use DHCP and ARP packets to trigger 802.1X authentication.

Request Example

<rpc message-id="0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <hw-nac-dot1x:dot1x-access xmlns:hw-nac-dot1x="urn:huawei:params:xml:ns:yang:huawei-nac-dot1x">
        <hw-nac-dot1x:dot1x-access-profile xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0" xc:operation="merge">
          <hw-nac-dot1x:name>test</hw-nac-dot1x:name>
          <hw-nac-dot1x:trigger-packet>arp</hw-nac-dot1x:trigger-packet>
    <hw-nac-dot1x:trigger-packet>dhcp</hw-nac-dot1x:trigger-packet>
        </hw-nac-dot1x:dot1x-access-profile>
      </hw-nac-dot1x:dot1x-access>
    </config>
  </edit-config>
</rpc>

Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="0">
 <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="20">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>operation-failed</error-tag>
    <error-severity>error</error-severity>
    <error-path>/huawei-nac-dot1x:dot1x-access/dot1x-access-profile[name='hu']/handshake/packet-type</error-path>
    <error-message>parse rpc config error.(Invalid value "request" in "packet-type" element.).</error-message>
  </rpc-error>
</rpc-reply>