Sending the Acct-Start and Acct-Update Messages After NCP Negotiation Is Completed

You can use the aaa accounting delay-start command to delay the sending of the Acct-Start message from the Broadband Remote Access Server (B-RAS) to the RADIUS server until IPCP or IPv6CP negotiation is completed. When Network Control Protocol (NCP) negotiation is completed, IP notifies authentication, authorization, and accounting (AAA) to set a user IP address or user interface ID (in case of Point-to-Point Protocol version 6 [PPPv6] subscribers). Only then does the B-RAS send the Acct-Start message to the RADIUS server. This ensures that the Framed-Interface-Id [96] or Framed-IP-Address [8] RADIUS attributes that are negotiated during Internet Protocol Control Protocol (IPCP) or Internet Protocol version 6 Control Protocol (IPv6CP) are present in the Acct-Start message, thereby reducing the number of accounting messages from two to one for each subscriber.

To delay the sending of the Acct-Start message from the B-RAS to the RADIUS server:

host1(config)#aaa accounting delay-start enable

Use the no version to immediately send the Acct-Start message from the B-RAS to the RADIUS server when AAA receives authentication-grant permission from the RADIUS server.

You can use the aaa accounting immediate-update-framed-ipv6-interfaceId-negotiation command to send the Acct-Update message with the Framed-Interface-Id [96] RADIUS attributes from the B-RAS to the RADIUS server for PPPv6 users immediately after NCP negotiation is completed.

To send the Acct-Update message with the Framed-Interface-Id [96] RADIUS attributes from the B-RAS to the RADIUS server:

host1(config)#aaa accounting immediate-update-framed-ipv6-interfaceId-negotiation enable

Use the no version to immediately send the Acct-Update message without the Framed-Interface-Id [96] RADIUS attributes from the B-RAS to the RADIUS server after IP notifies AAA to set a user IP address or user interface ID.

Related Documentation