Change-Of-Authorization Messages; Message Exchange; Supported Error-Cause Codes (Radius Attribute 101); Table 46: Error-Cause Codes (Radius Attribute 101) - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

JunosE 11.3.x Broadband Access Configuration Guide

Change-of-Authorization Messages

Message Exchange

Supported Error-Cause Codes (RADIUS Attribute 101)

242
The RADIUS dynamic-request server receives and processes the unsolicited CoA messages
from RADIUS servers. The RADIUS-initiated CoA feature uses the following codes in its
RADIUS request and response messages:
CoA-Request (43)
CoA-ACK (44)
CoA-NAK (45)
The RADIUS server and the router's RADIUS dynamic-request server exchange messages
using UDP. The CoA-Request message sent by the RADIUS server has the same format
as the Disconnect-Request packet that is sent for a disconnect operation.
The response is either a CoA-ACK or a CoA-NAK message:
If AAA successfully changes the authorization, the response is a RADIUS-formatted
packet with a CoA-ACK message, and the data filter is applied to the session.
If AAA is unsuccessful, the request is malformed, or attributes are missing, the response
is a RADIUS-formatted packet with a CoA-NAK message.
When AAA is unsuccessful, the RADIUS dynamic-request server includes an error-cause
attribute (RADIUS attribute 101) in the CoA-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 CoA-NAK without an error-cause attribute. Table 46 on
page 242 lists the supported error-cause codes.

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

Code Value
401 Unsupported
attribute
402 Missing attribute
404 Invalid request
503 Session context not
found
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.
Copyright © 2010, Juniper Networks, Inc.