Enabling forcibly sending stop-accounting packets

About forcibly sending stop-accounting packets

Typically, if the device does not send a start-accounting packet to the RADIUS server for an authenticated user, it does not send a stop-accounting packet when the user goes offline. If the server has generated a user entry for the user without start-accounting packets, it does not release the user entry when the user goes offline. This feature forces the device to send stop-accounting packets to the RADIUS server when the user goes offline for timely releasing the user entry on the server.

Procedure

  1. Enter system view.

    system-view

  2. Enable RADIUS scheme view.

    radius scheme radius-scheme-name

  3. Enable the device to send stop-accounting packets when users for which no start-accounting packets are sent go offline.

    stop-accounting-packet send-force

    By default, forcibly sending stop-accounting packets is disabled. The device does not send stop-accounting packets when users for which no start-accounting packets are sent go offline.