Problem with Acct-Session-Id malformed field

@LuizPuppin Hi,
which Acct-Session-Id version is configured?

Version 2

Hi,
it's normal, the format is modified in the version V800R010C10SPC500.
In the previous version the last six bytes of the RADIUS attribute Acct-Session-ID (44) indicate the index of a BRAS user, expressed in hexadecimal notation.
In the version V800R010C10SPC500 the last six bytes of the RADIUS attribute Acct-Session-ID (44) indicate the index of a BRAS user, expressed in the Base-64 format.

But this information was not changed on HeDex. ;)
We have a clients who use a software to collect this informations and th parameter is configured to recieve Hex Decimal information.
You have a link where I can see this change to send to clients?

Please download the NE20E-S V800R010C10SPC500 Release Notes.

Hello,

I have this problem too with the version V800R010C10SPC500.

I'm using acct-session-id-version version3, and we can't get the user-index based on the reported RADIUS Acct-Session-Id, neither with hexadecimal, the decimal nor the base64.

For example:

display access-user username ******** verbose
  -------------------------------------------------------------------
Basic:
  User access index             : 262
  State                         : Used
  User name                     : ********
  Domain name                   : ********
  User backup state             : No
  RUI user state                : -
  User access interface         : GigabitEthernet0/3/1.1003


User access index = 262
Acct-Session-Id = 32AAAAEO


Trying to get user-index via encode/decode base64:

beraca:~ rafael$ perl -MMIME::Base64 -e 'print encode_base64(262);'
MjYy
beraca:~ rafael$ perl -MMIME::Base64 -e 'print encode_base64(000262);'
MTc4

beraca:~ rafael$ perl -MMIME::Base64 -e 'print decode_base64(AAAAEO);'

beraca:~ rafael$ perl -MMIME::Base64 -e 'print decode_base64(EO);'

beraca:~ rafael$ perl -MMIME::Base64 -e 'print decode_base64(MjYy);'
262

As you can see, the AAAAEO doesn't match the user-index in base64 format.

Do you know how can I convert the value to match user-index?

Hi,
the user access index and Acct-Session-ID are two different parameters.
user access index is used to mark the access user locally, while the Acct-Session-ID is a unique Accounting ID to make it easy to match start and stop records in a log file.

Hello @chenhui,

In according with Hdx, the acct-session-id is generated based on information that belongs to the current connection. Its not just a random number.

@rganacim Hi,
I checked with the R&D guys, the first two digits of the acct-session-id is in hexadecimal notation, the last 6 digits is in 64-base.
let's take an example, acct-session-id = 32AAAAEO, the AAAAEO is in 64-base, and it indicates the user access id. AAAAEO equals 270(decimal), AAAAEG equals 262(decimal)