Q: Why does the system transmit realtime accounting packets since the relevant switch of MA5200 has been off?
1. Check the accounting policy, and the realtime accounting is off:
Accounting-scheme-name : pppoe
Accounting-method : RADIUS
Realtime-accounting-switch : Disabled //Realtime accounting switch is disabled
Start-accounting-fail-policy : Online
Realtime-accounting-fail-policy : Online
Realtime-accounting-failure-retries : 3
2. However, the realtime accounting packets are captured in debug packets:
Code : 4
Len : 347
ID : 174
[User-name(1) ]  [test@isp]
[NAS-Port(5) ] [6 ] 
[NAS-IP-Address(4) ] [6 ] [222.x.x.x]
[Framed-IP-Address(8) ] [6 ] [58.x.x.x]
[Filter-ID(11) ] [3 ] 
[NAS-Identifier(32) ]  [MA5200G]
[Acct-Status-Type(40) ] [6 ]  //It is realtime accounting packets if it equal to 3
[Acct-Delay-Time(41) ] [6 ] 
3. Check the radius packets, and it is found that code＝2 is configured with realtime accounting interval:
*Nov 26 16:34:26 2005 MA5200G RDS/8/debug2:
Radius Received a Packet
Server Template: 0
Server IP : 211.x.x.x
Server Port : 1812
Code : 2
Len : 86
ID : 63
[Framed-Protocol(7) ] [6 ] 
[Acct_Interim_Interval(85) ] [6 ]  //Realtime accounting interval value
When the configurations of MA5200 conflict with the attribute flooded by radius, it is subject to that flooded by radius. Therefore, if the switch for realtime accounting of MA5200 is disabled, and the radius floods the realtime accounting interval, it will transmit realtime accounting packets according to the interval flooded by radius.
1. Disable No. 85 attribute for realtime accounting at Radius server, so MA5200 will not flood realtime accounting packets again.
2. Use the Radius attribute conversion of MA5200 to disable the packets transmitted by server. It is similar to that Radius does not floods the attribute, and the local configurations will take effect.
Note: In code＝4, when Acct-Status-Type(40) equal to 1, it is accounting start packet; when 2, it is accounting stop packet; when 3, it is realtime accounting packet.