Mapping Application Terminate Reasons To Radius Terminate Codes; Table 8: Supported Radius Acct-Terminate-Cause Codes - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

Software for e series broadband services routers broadband access configuration guide
Hide thumbs Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12:
Table of Contents

Advertisement

JunosE 11.3.x Broadband Access Configuration Guide

Mapping Application Terminate Reasons to RADIUS Terminate Codes

82
The JunosE Software uses a default configuration that maps terminate reasons to RADIUS
Acct-Terminate-Cause attributes. You can optionally create customized mappings
between a terminate reason and a RADIUS Acct-Terminate-Cause attribute—these
mappings enable you to provide different information about the cause of a termination.
When a subscriber's L2TP or PPP session is terminated, the router logs a message for
the internal terminate reason and logs another message for the RADIUS
Acct-Terminate-Cause attribute (RADIUS attribute 49). RADIUS attribute 49 is also
included in RADIUS Acct-Off and Acct-Stop messages. You can use the logged
information to help monitor and troubleshoot terminated sessions.
Use the show terminate-code command to display information about the mappings
between application terminate reasons and RADIUS Acct-Terminate-Cause attributes.
Table 8 on page 82 lists the IETF RADIUS Acct-Terminate-Cause codes that you can use
to map application terminate reasons. In addition, you can also configure and use
proprietary codes for values beyond 22.

Table 8: Supported RADIUS Acct-Terminate-Cause Codes

Code
Name
1
User Request
2
Lost Carrier
3
Lost Service
4
Idle Timeout
5
Session Timeout
6
Admin Reset
7
Admin Reboot
8
Port Error
9
NAS Error
10
NAS Request
11
NAS Reboot
Description
User initiated the disconnect (log out)
DCD was dropped on the port
Service can no longer be provided; for example, the user's
connection to a host was interrupted
Idle timer expired
Subscriber reached the maximum continuous time allowed for
the service or session
System administrator reset the port or session
System administrator terminated the session on the NAS; for
example, prior to rebooting the NAS
NAS detected an error on the port that required ending the session
NAS detected an error (other than on the port) that required
ending the session
NAS ended the session for a non-error reason
NAS ended the session due to a non-administrative reboot
Copyright © 2010, Juniper Networks, Inc.

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents