Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Support
Technical Documentation
Content Explorer New
 
Enterprise MIBs
 
EOL Documentation
 
Feature Explorer Login required New
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > JunosE Software > AAA Accounting Messages During IPCP Negotiations for Dual-Stack Subscribers
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...
 

Related Documentation

  • AAA Access Messages During IPCP Negotiations for Dual-Stack Subscribers
  • Juniper Networks VSAs
  • Juniper Networks VSAs Supported for Subscriber AAA Accounting Messages
  • IPCP Renegotiation of IPv4 Addresses for Dual-Stack Subscribers
 

AAA Accounting Messages During IPCP Negotiations for Dual-Stack Subscribers

The Ipv4-release-control RADIUS VSA attribute [26-164] is supported only in Interim-Acct messages. The following sections describe the different scenarios during the negotiation of IPCP packets for IPv4 addresses and release of addresses for terminated user sessions in a dual-stack network, and the transmission of interim accounting messages between the router and the AAA server.

Interim-Acct Messages When an IPv4 Address is Assigned

The following RADIUS attributes are always included in Interim-Acct messages when an IPv4 address is assigned to a dual-stack subscriber during an IPCP negotiation:

  • [55] Event-Timestamp
  • [25] Class
  • [97] Framed-Ipv6-Prefix
  • [8] Framed-Ip-Address
  • [9] Framed-Ip-Netmask

The other attributes supported in Interim-Acct messages are included, based on the user configuration settings.

Interim-Acct Messages When an IPv4 Address is Not Assigned

The following RADIUS attributes are always included in Interim-Acct messages when an IPv4 address is not assigned to a dual-stack subscriber during an IPCP negotiation:

  • [55] Event-Timestamp
  • [25] Class
  • [97] Framed-Ipv6-Prefix

The other attributes supported in Interim-Acct messages are included, based on the user configuration settings.

The following RADIUS attributes are never included in Interim-Acct messages when IPv4 address assignment fails:

  • [8] Framed-Ip-Address
  • [9] Framed-Ip-Netmask

Interim-Acct Messages During a Successful IPCP Renegotiation for IPv4 Addresses

The following RADIUS attributes are always included in Interim-Acct messages upon the receipt of IPCP configuration requests for IPv4 addresses from CPE and a successful IPCP renegotiation:

  • [26-164] Ipv4-release-control
  • [55] Event-Timestamp
  • [25] Class
  • [97] Framed-Ipv6-Prefix
  • [8] Framed-Ip-Address
  • [9] Framed-Ip-Netmask
  • [123] Delegated-Ipv6-Prefix
  • [44] Acct-Session-Id

The other attributes supported in Interim-Acct messages are included, based on the user configuration settings.

Interim-Acct Messages During a Failed IPCP Renegotiation for IPv4 Addresses

The following RADIUS attributes are always included in Interim-Acct messages after the receipt of IPCP configuration requests for IPv4 addresses from CPE and a failed IPCP renegotiation:

  • [26-164] Ipv4-release-control
  • [55] Event-Timestamp
  • [25] Class
  • [97] Framed-Ipv6-Prefix
  • [123] Delegated-Ipv6-Prefix
  • [44] Acct-Session-Id

The other attributes supported in Interim-Acct messages are included, based on the user configuration settings.

The following RADIUS attributes are never included in Interim-Acct messages when IPv4 address assignment fails after an IPCP renegotiation:

  • [8] Framed-Ip-Address
  • [9] Framed-Ip-Netmask

Interim-Acct Messages When an IPv4 Address is Released

The following RADIUS attributes are always included in Interim-Acct messages when an IPv4 address is released upon the termination of a subscriber session:

  • [26-164] Ipv4-release-control
  • [55] Event-Timestamp
  • [25] Class
  • [97] Framed-Ipv6-Prefix
  • [123] Delegated-Ipv6-Prefix
  • [44] Acct-Session-Id

The other attributes supported in Interim-Acct messages are included, based on the user configuration settings.

The following RADIUS attributes are never included in Interim-Acct messages when an IPv4 address is released to the AAA server:

  • [8] Framed-Ip-Address
  • [9] Framed-Ip-Netmask

For both these attributes, even if the IP address assigned to the user is 0.0.0.0, it is discarded and not included in the accounting messages.

 

Related Documentation

  • AAA Access Messages During IPCP Negotiations for Dual-Stack Subscribers
  • Juniper Networks VSAs
  • Juniper Networks VSAs Supported for Subscriber AAA Accounting Messages
  • IPCP Renegotiation of IPv4 Addresses for Dual-Stack Subscribers
 

Published: 2012-06-27

 
  • About Juniper
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Green Networking
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Developers
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out