This section provides a sample of configuring network access rights for users when the Portal server is Down (using a service scheme) using the merge method. You can also use the create method to configure network access rights for users when the Portal server is Down (using a service scheme).
Operation |
XPATH |
|---|---|
edit-config:merge |
/huawei-nac-portal:portal-access/configure-mode/unified-mode/portal-access-profile/authorize-of-authentication-event/authorize-parameters/service-scheme |
Item |
Data |
Description |
|---|---|---|
service-scheme |
serscheme_2 |
Configure network access rights for users when the Portal server is Down (using the service scheme serscheme_2). |
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<error-option>rollback-on-error</error-option>
<config>
<portal-access xmlns="urn:huawei:params:xml:ns:yang:huawei-nac-portal">
<portal-access-profile xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:operation="merge">
<name>portal_1</name>
<authorize-of-authentication-event>
<authentication-event>portal-server-down</authentication-event>
<service-scheme>serscheme_2</service-scheme>
</authorize-of-authentication-event>
</portal-access-profile>
</portal-access>
<aaa xmlns="urn:huawei:params:xml:ns:yang:huawei-aaa">
<service-scheme xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:operation="merge">
<name>serscheme_2</name>
<vsys>vsys</vsys>
</service-scheme>
</aaa>
</config>
</edit-config>
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="41">
<rpc-error>
<error-app-tag>-1</error-app-tag>
<error-message> Service Scheme lsw_ss does not exist.</error-message>
<error-info>Error on node /huawei-nac-portal:portal-access/portal-access-profile[name="portal_1"]/authorize-of-authentication-event[authentication-event="portal-server-down"]/service-scheme</error-info>
</rpc-error>
</rpc-reply>