Configuring the RADIUS Traffic Unit, Retransmission Times, Timeout Interval, and Back-to-Active Interval

This section describes how to configure the traffic unit used by a RADIUS server, number of times that RADIUS packets can be retransmitted, timeout interval of RADIUS request packets, and interval for the server to return to the active state using the rpc method.

**Table 1** Configuring the RADIUS traffic unit, retransmission times, timeout interval, and back-to-active interval
Operation	XPATH
edit-config:create	/huawei-aaa-radius:radius/radius-server/options

Data Requirement

**Table 2** Configuring the RADIUS traffic unit, retransmission times, timeout interval, and back-to-active interval
Item	Data	Description
Traffic unit used by a RADIUS server	byte	Set the traffic unit used by a RADIUS server to bytes.
Interval for the RADIUS server to return to the active state	3	Set the interval for the RADIUS server to return to the active state to 3 minutes.
Timeout interval of RADIUS request packets	3	Set the timeout interval of RADIUS request packets to 3 seconds.
Number of times RADIUS request packets can be retransmitted	2	Set the number of times RADIUS request packets can be retransmitted to 2.

Request Example

<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>
  <radius xmlns="urn:huawei:params:xml:ns:yang:huawei-aaa-radius">
   <radius-server xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:operation="merge">
    <vsys>public</vsys>
    <name>test12345</name>
    <options xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:operation="merge">
     <traffic-unit>byte</traffic-unit>
     <dead-time>3</dead-time>
     <timeout-timer>3</timeout-timer>
     <retransmit-time>2</retransmit-time>
    </options>   
   </radius-server>
  </radius>
 </config>
 </edit-config>
</rpc>

Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="123">
  <ok/>
</rpc-reply>

Sample of failed response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="123">
 <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>