This section provides a sample of enabling the Portal server detection function using the merge method. You can also use the create method to enable the Portal server detection function.
Operation |
XPATH |
|---|---|
edit-config:merge |
/huawei-aaa-portal/portal/portal-server/server-detect-function/server-detect-enable |
Item |
Data |
Description |
|---|---|---|
server-detect-enable |
true |
Enable the Portal server detection function. |
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="123">
<edit-config>
<target>
<running/>
</target>
<error-option>rollback-on-error</error-option>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<portal xmlns="urn:huawei:params:xml:ns:yang:huawei-aaa-portal">
<portal-server xc:operation="merge">
<name>huawei</name>
<server-detect-function>
<server-detect-enable xc:operation="merge">true</server-detect-enable>
</server-detect-function>
</portal-server>
</portal>
</config>
</edit-config>
</rpc>
Sample of successful response
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_012824316d704d43adb16b1a4245d273"> <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="37">
<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>