Configuring Network Access Rights for Users When the 802.1X Client Does Not Respond

This section provides a sample of configuring network access rights for users when the 802.1X client does not respond using the merge method. You can also use the create method to configure network access rights for users when the 802.1X client does not respond.

**Table 1** Configuring network access rights for users when the 802.1X client does not respond
Operation	XPATH
edit-config:merge	/huawei-nac-dot1x:dot1x-access/configure-mode/unified-mode/dot1x-access-profile/authorize-of-authentication-event

Data Requirement

**Table 2** Configuring network access rights for users when the 802.1X client does not respond
Item	Data	Description
name	test	Configure network access rights for users when the 802.1X client does not respond. The 802.1X access profile must exist on the switch.
authentication-event	client-no-response
vlan-id	4000

Request Example

<?xml version='1.0' encoding='UTF-8'?>
<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>
   <dot1x-access xmlns="urn:huawei:params:xml:ns:yang:huawei-nac-dot1x">
    <dot1x-access-profile>
     <name>test</name>
     <authorize-of-authentication-event>
      <authentication-event>client-no-response</authentication-event>
      <vlan-id>4000</vlan-id>
     </authorize-of-authentication-event>
    </dot1x-access-profile>
   </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="43a8e485-35d2-499e-895c-e2d2d5f555a8">
 <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="43a8e485-35d2-499e-895c-e2d2d5f555a8">
  <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>