This section provides a sample of enabling the function of triggering 802.1X authentication through multicast packets immediately after an interface goes Up using the merge method.
Operation |
XPATH |
---|---|
edit-config:merge |
/huawei-nac-dot1x:dot1x-access/multicast-trigger-function/port-up-enable |
Item |
Data |
Description |
---|---|---|
port-up-enable |
true |
Enable the function of triggering 802.1X authentication through multicast packets immediately after an interface goes Up. |
<?xml version='1.0' encoding='UTF-8'?> <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:multicast-trigger-function> <hw-nac-dot1x:port-up-enable>true</hw-nac-dot1x:port-up-enable> </hw-nac-dot1x:multicast-trigger-function> </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/multicast-trigger-function/port-up-enable</error-path> <error-message>parse rpc config error.(Invalid value "1" in "port-up-enable" element.).</error-message> </rpc-error> </rpc-reply>