This section provides a sample of configuring the device to send EAP packets with a code number to 802.1X users using the merge method.
Operation |
XPATH |
|---|---|
edit-config:merge |
/huawei-nac-dot1x:dot1x-access/configure-mode/unified-mode/dot1x-access-profile/eap-notify-packet |
Item |
Data |
Description |
|---|---|---|
name |
test |
Configure the 802.1X access profile named test. |
eap-code |
10 |
Set the code number in EAP packets sent to users to 10. |
data-type |
12 |
Set the data type in EAP packets sent to users to 12. |
<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:eap-notify-packet>
<hw-nac-dot1x:eap-code>10</hw-nac-dot1x:eap-code>
<hw-nac-dot1x:data-type>12</hw-nac-dot1x:data-type>
</hw-nac-dot1x:eap-notify-packet>
</hw-nac-dot1x:dot1x-access-profile>
</hw-nac-dot1x:dot1x-access>
</config>
</edit-config>
</rpc>
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="12">
<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']/eap-notify-packet/eap-code</error-path>
<error-message>parse rpc config error.(Value "4" does not satisfy the constraint "5..255" (range, length, or pattern).).</error-message>
</rpc-error>
</rpc-reply>