Supported Error-Cause Codes (Radius Attribute 101); Qualifications For Disconnect; Table 45: Error-Cause Codes (Radius Attribute 101) - Juniper JUNOSE SOFTWARE 11.2.X - BROADBAND ACCESS CONFIGURATION GUIDE 7-20-2010 Configuration Manual

JunosE 11.2.x Broadband Access Configuration Guide

Supported Error-Cause Codes (RADIUS Attribute 101)

Qualifications for Disconnect

234
If AAA successfully disconnects the user, the response is a RADIUS-formatted packet
with a Disconnect-ACK message.
If AAA cannot disconnect the user, the request is malformed, or attributes are missing
from the request, the response is a RADIUS-formatted packet with a Disconnect-NAK
message.
When a disconnect request fails, the RADIUS dynamic-request server includes an
error-cause attribute (RADIUS attribute 101) in the Disconnect-NAK message that it
sends back to the RADIUS server. If the detected error does not map to one of the
supported error-cause attributes, the router sends the Disconnect-NAK without an
error-cause attribute. Table 45 on page 234 lists the supported error-cause codes.

Table 45: Error-Cause Codes (RADIUS Attribute 101)

Code Value
401 Unsupported
attribute
402 Missing attribute
404 Invalid request
503 Session context not
found
504 Session context not
removable
506 Resources
unavailable
For the server to disconnect a user, the Disconnect-Request message must contain an
attribute with a session ID. The Disconnect-Request message can contain an
Acct-Session-Id (44) attribute or a Acct-Multi-Session-Id (50) attribute for the session
ID or both. If both the Acct-Session-Id and Acct-Multi-Session-Id attributes are present
in the request, the router uses both attributes. If the User-Name (1) attribute is also
present in the request, the username and session ID are used to perform the disconnection.
Authentication, authorization, and accounting (AAA) services handle the actual request.
Description
The request contains an attribute that is not supported (for
example, a third-party attribute).
A critical attribute (for example, the session identification attribute)
is missing from a request.
Some other aspect of the request is invalid, such as if one or more
attributes (for example, the packet mirroring Mirror Identifier value)
are not formatted properly.
The session context identified in the request does not exist on the
NAS.
The subscriber identified by attributes in the disconnect request
is owned by a component that does not support RADIUS-initiated
disconnect (for example, IP LAC subscribers cannot be
disconnected).
A request could not be honored due to lack of available NAS
resources (such as memory).
Copyright © 2010, Juniper Networks, Inc.