No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Real-Time Accounting Fails to be Performed on the Server Because the accounting send-update Command Is Not Run on the ME60

Publication Date:  2018-10-09 Views:  307 Downloads:  0

Issue Description


PC—switch—ME60—Non-huawei aggregation devices—RADIUS server

The server vendor personnel reported that the server failed to receive accounting update packets from users, and accurate traffic accounting failed to be implemented.

Handling Process

1. Run the accounting send-update command in the accounting scheme view to enable the device to send real-time accounting packets immediately after receiving accounting start responses.

2. To prevent a large number of accounting packets from being generated in a short time due to concurrent login of a large number of users, negotiate with the server vendor to configure an interval for sending real-time accounting packets. For example, setting the interval to 6 minutes.
   accounting interim interval 6

Root Cause

Configure a DAA accounting template on the ME60 and run the test-aaa test1 111111 radius-group rd1 command. The command output shows that accounting is successfully performed.

Check the accounting scheme acct1. By default, RADIUS accounting is used.

By default, the ME60 does not send real-time accounting packets immediately after receiving accounting response packets from the accounting server. Therefore, the server does not receive real-time accounting update packets.


Configure a DAA accounting policy on the ME60 to work with the server. Pay attention to the configuration of real-time traffic accounting.