Description

Radius accounting feature is not working on EX3400 switches.

AVP: t=Acct-Input-Octets(42) l=6 val=0
AVP: t=Acct-Output-Octets(43) l=6 val=0
AVP: t=Acct-Session-Time(46) l=6 val=12
AVP: t=Acct-Input-Packets(47) l=6 val=520538
AVP: t=Acct-Output-Packets(48) l=6 val=2106672
AVP: t=Acct-Terminate-Cause(49) l=6 val=Admin-Reboot(7)
AVP: t=Acct-Input-Gigawords(52) l=6 val=60519852
AVP: t=Acct-Output-Gigawords(53) l=6 val=185322927

The Acct-Input-Gigawords and the Acct-Output-Gigawords mentioned above are having values that are too huge.
Hence, the server is taking the value in TB for a session lenght of 1 minute. Which is not correct. The above is collected from the radius accounting request packet.

Symptoms

Customer is using the Dot1x Radius Authentication and Accounting and noticed that when the Stop Accounting(due to disconnect) is sent to the Radius server the Acct-Input-Gigawords and the Acct-Output-Gigawords is having huge value as below which is not expected.


AVP: t=Acct-Input-Octets(42) l=6 val=0

AVP: t=Acct-Output-Octets(43) l=6 val=0

AVP: t=Acct-Session-Time(46) l=6 val=12

AVP: t=Acct-Input-Packets(47) l=6 val=520538

AVP: t=Acct-Output-Packets(48) l=6 val=2106672

AVP: t=Acct-Terminate-Cause(49) l=6 val=Admin-Reboot(7)

AVP: t=Acct-Input-Gigawords(52) l=6 val=60519852. <<====== 

AVP: t=Acct-Output-Gigawords(53) l=6 val=185322927 <======

Solution

No workaround possible. 

Issue is resolved in

evo:23.4R2-S5-EVO
evo:24.2R2-S1-EVO 
evo:24.4R2-EVO
evo:25.1R1-EVO
evo:25.2R1-EVO
junos :23.4R2-S5 
junos:24.2R2-S1 
junos:24.4R2
junos:25.1R1
junos:25.2R1

Modification History

2025-02-10 : Article Created