Got it

BRAS accounting packet not sending IPv6 Address to AAA server

Created: Sep 29, 2021 15:39:34Latest reply: Sep 30, 2021 07:17:45 218 10 1 0 0
  Rewarded HiCoins: 0 (problem resolved)

BRAS accounting packet not sending IPv6 Address to AAA server, any aditional configuration required for this

Featured Answers

Recommended answer

zaheernew
MVE Author Created Sep 29, 2021 17:17:52

Hi Hi friend


I don't know how much my solution will help you. Anyway, try the following steps.


  • Allow the initial accounting packet (start) to be delivered within a configurable (preferably modest) timeframe, given that at least one of the IPv6 address allocations has been completed.

    • During this period, PPP should finish at least one of the IPv4/IPv6 address negotiations; else, the PPP session should be terminated. Send the accounting start record for this protocol if at least one protocol address assignment is successful, and allow for an extra accounting (interim/alive) record to be sent as soon as the other protocol completes. However, don't add any extra time to the first accounting while you're waiting for both IPv4 and IPv6 addresses to be assigned. If SLAAC is used, this first accounting record (start) should include IPv6 address (IPV6CP) interface-id, as well as the option to add the ICMPv6 RA prefix. IPCP/IPV6CP assignments should take less than 100ms, according to my measurements (on an averagely loaded BRAS/BNG), but SLAAC completion could take up to 500ms after PPP.


Allow a second accounting packet (interim/alive) to be sent a little later (with a longer timescale) if some IPv6 information was not included in the initial accounting packet and the user should be allowed to customize both times.

  • Following the acquisition of any IPv6 address/prefix via DHCPv6 and/or DHCPv6-PD, a second accounting record should be provided. Because DHCPv6 runs asynchronously on top of IPv6 and you can't predict when the CPE will ask for an address/prefix using it, it's advisable to keep a separate accounting record for it, even if it's only for a few seconds. DHCPv6 completion could take up to 3-5 seconds after PPP, depending on the CPE's ability to launch DHCPv6 at the proper moment (after that, it's just a few ms till the prefix is issued), according to my measurements.

  • In unusual instances, SLAAC and/or DHCPv6 IA-NA is completed later, and DHCPv6-PD occurs later, a third accounting record should be issued.


Allow an extra accounting packet (interim/alive) to be transmitted whenever a DHCPv6 prefix delegation occurs, but only if the prefix delegation's information was not included in the prior two accounting packets.

  • If the DHCPv6/DHCPv6-PD assignment occurs during the initially limited timeframe, the information should be provided in the initial accounting packet as well. Alternatively, if SLAAC accounting was not completed within the first timeframe, the information should be included in the second accounting package.

  • Furthermore, it is self-evident that if PPP protocol rejects are received for IPv6, there should be no delay in the rejected protocol completing the address assignment.


All of the foregoing is worth discussing assuming that the prefix assigned via DHCPv6-PD is included in the radius accounting packets. There have been several attempts to remedy this, as well as the IPv6 accounting in general.


CLI Example :

"aaa accounting include auth-profile delegated-ipv6-prefix", "aaa accounting delay-start extended-time", "aaa accounting delay-start [all]"


Thank You.

View more
  • x
  • convention:

simchamnan
simchamnan Created Sep 30, 2021 05:49:50 (1) (0)
 
zaheernew
zaheernew Reply simchamnan  Created Sep 30, 2021 05:56:18 (0) (0)
 
AndresMoreno
AndresMoreno Reply zaheernew  Created Sep 30, 2021 14:06:41 (0) (0)
 
zaheernew
zaheernew Reply AndresMoreno  Created Sep 30, 2021 16:36:39 (0) (0)
Admin Thank you so much  
All Answers
Hello! Thank you for contacting us.
We are working on an answer for you.
View more
  • x
  • convention:

simchamnan
simchamnan Created Sep 30, 2021 05:49:58 (0) (0)
 
zaheernew
zaheernew MVE Author Created Sep 29, 2021 17:17:52

Hi Hi friend


I don't know how much my solution will help you. Anyway, try the following steps.


  • Allow the initial accounting packet (start) to be delivered within a configurable (preferably modest) timeframe, given that at least one of the IPv6 address allocations has been completed.

    • During this period, PPP should finish at least one of the IPv4/IPv6 address negotiations; else, the PPP session should be terminated. Send the accounting start record for this protocol if at least one protocol address assignment is successful, and allow for an extra accounting (interim/alive) record to be sent as soon as the other protocol completes. However, don't add any extra time to the first accounting while you're waiting for both IPv4 and IPv6 addresses to be assigned. If SLAAC is used, this first accounting record (start) should include IPv6 address (IPV6CP) interface-id, as well as the option to add the ICMPv6 RA prefix. IPCP/IPV6CP assignments should take less than 100ms, according to my measurements (on an averagely loaded BRAS/BNG), but SLAAC completion could take up to 500ms after PPP.


Allow a second accounting packet (interim/alive) to be sent a little later (with a longer timescale) if some IPv6 information was not included in the initial accounting packet and the user should be allowed to customize both times.

  • Following the acquisition of any IPv6 address/prefix via DHCPv6 and/or DHCPv6-PD, a second accounting record should be provided. Because DHCPv6 runs asynchronously on top of IPv6 and you can't predict when the CPE will ask for an address/prefix using it, it's advisable to keep a separate accounting record for it, even if it's only for a few seconds. DHCPv6 completion could take up to 3-5 seconds after PPP, depending on the CPE's ability to launch DHCPv6 at the proper moment (after that, it's just a few ms till the prefix is issued), according to my measurements.

  • In unusual instances, SLAAC and/or DHCPv6 IA-NA is completed later, and DHCPv6-PD occurs later, a third accounting record should be issued.


Allow an extra accounting packet (interim/alive) to be transmitted whenever a DHCPv6 prefix delegation occurs, but only if the prefix delegation's information was not included in the prior two accounting packets.

  • If the DHCPv6/DHCPv6-PD assignment occurs during the initially limited timeframe, the information should be provided in the initial accounting packet as well. Alternatively, if SLAAC accounting was not completed within the first timeframe, the information should be included in the second accounting package.

  • Furthermore, it is self-evident that if PPP protocol rejects are received for IPv6, there should be no delay in the rejected protocol completing the address assignment.


All of the foregoing is worth discussing assuming that the prefix assigned via DHCPv6-PD is included in the radius accounting packets. There have been several attempts to remedy this, as well as the IPv6 accounting in general.


CLI Example :

"aaa accounting include auth-profile delegated-ipv6-prefix", "aaa accounting delay-start extended-time", "aaa accounting delay-start [all]"


Thank You.

View more
  • x
  • convention:

simchamnan
simchamnan Created Sep 30, 2021 05:49:50 (1) (0)
 
zaheernew
zaheernew Reply simchamnan  Created Sep 30, 2021 05:56:18 (0) (0)
 
AndresMoreno
AndresMoreno Reply zaheernew  Created Sep 30, 2021 14:06:41 (0) (0)
 
zaheernew
zaheernew Reply AndresMoreno  Created Sep 30, 2021 16:36:39 (0) (0)
Admin Thank you so much  
i_f48.gif
View more
  • x
  • convention:

zaheernew
zaheernew Created Sep 30, 2021 06:06:55 (0) (0)
 
Hi nikhil.a3444,
bro Forgive me for not understanding what you're trying to say. Can you be more specific?
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.