The MAG-c RADIUS Attributes and IU Triggers lists all supported RADIUS attributes and RADIUS interim update (IU) triggers for MAG-c.

It covers content for the release specified in the About tab, and may also contain content that will be released in later maintenance loads. Refer to the applicable MAG-c Release Notes for information about features supported in each load of the release software.

Filtering

To filter in a specific column, enter text in the field at the top of the column.

To filter across all columns, enter text in the "Show" or "Hide" fields in the "Filter" section to display or hide rows that have matched content.

To hide or show a specific column, click on the column name in the "Toggle column visibility" section.

Exporting data

Use the "CSV - Export All" button to export all filtered rows with all columns to a CSV file.

Use the "CSV - Export Visible" button to export all filtered rows with only the visible columns to a CSV file.

Clear filters

Use the "Clear filters" button to clear all input fields and to close all record details.

Table columns

The following tables describe the columns of the RADIUS attributes list in the Attributes tab and the columns of the RADIUS IU triggers list in the IU Triggers tab.

Column Description
ID ID of the attribute.

Standard RADIUS attribute IDs are assigned by IANA.
VSA (Vendor-Specific Attribute) and EVS (Extended-Vendor-Specific) attribute IDs are assigned by the specific vendor.
The VSA IDs in the list are assigned by Nokia or an SDO (Standards Developing Organization) such as BBF and 3GPP.

Note:

Attribute IDs follow the dotted number notation that is specified in RFC 6929, Remote Authentication Dial In User Service (RADIUS) Protocol Extensions.
For example:
  • 1 (User-Name): a standard attribute type
  • 26.6527.11 (Alc-Subsc-ID-Str): a Nokia VSA with attribute type 26, Vendor-Id 6527, Vendor-Type 11
  • 241.26.6527.77 (Alc-Max-Total-Volume): a Nokia EVS attribute with attribute type 241, EVS-Type 26, Vendor-Id 6527, Vendor-Type 77
Name Name of the attribute.
Description Description of the attribute.
Type Type of the attribute value; for example, String, IPv4 address.
Limits Limits that apply to the attribute type; for example, 32 characters for a String.
Empty if there are no limits other than those of the type; for example, a string has an implicit limit equal to the maximum attribute size.
In case an attribute can be present more than once (0+), the maximum number of instances of the attribute can be defined here.
Format Format and example of the attribute value; for example, description of the values in an Enum, formatting rules for a String.
Access Request Presence of the attribute in the Access-Request message:
  • 0: The attribute is not present in the message
  • 0+: 0 or more instances of the attribute can be present in the message
  • 0-1: 0 or 1 instance of the attribute can be present in the message
  • 1: Exactly 1 instance of the attribute is present in the message
Access Accept Presence of the attribute in the Access-Accept message:
  • 0: The attribute is not present in the message
  • 0+: 0 or more instances of the attribute can be present in the message
  • 0-1: 0 or 1 instance of the attribute can be present in the message
  • 1: Exactly 1 instance of the attribute is present in the message
Authentication Include-Attribute CLI The CLI command to enable inclusion of the attribute in the RADIUS authentication request messages.
Possible values are:
  • the CLI command in the config>mobile>profile>bng>radius-authentication-profile>include-attribute context
  • the CLI command including the context if the context is different from the config>mobile>profile>bng>radius-authentication-profile>include-attribute context
  • empty (no value) if the attribute is never included in the RADIUS authentication request messages
  • <unconditional> if the attribute, when it has a value, is always included in the RADIUS authentication request messages
Accounting Start Presence of the attribute in the Accounting Start message:
  • 0: The attribute is not present in the message
  • 0+: 0 or more instances of the attribute can be present in the message
  • 0-1: 0 or 1 instance of the attribute can be present in the message
  • 1: Exactly 1 instance of the attribute is present in the message
Accounting Stop Presence of the attribute in the Accounting Stop message:
  • 0: The attribute is not present in the message
  • 0+: 0 or more instances of the attribute can be present in the message
  • 0-1: 0 or 1 instance of the attribute can be present in the message
  • 1: Exactly 1 instance of the attribute is present in the message
Accounting Update Presence of the attribute in the Accounting Interim Update message:
  • 0: The attribute is not present in the message
  • 0+: 0 or more instances of the attribute can be present in the message
  • 0-1: 0 or 1 instance of the attribute can be present in the message
  • 1: Exactly 1 instance of the attribute is present in the message
Accounting Include-Attribute CLI The CLI command to enable inclusion of the attribute in the RADIUS accounting messages.
Possible values are:
  • the CLI command in the config>mobile>profile>charging>bng-charging>radius>session>include-attribute context
  • empty (no value) if the attribute is never included in the RADIUS accounting messages
  • <unconditional> if the attribute, when it has a value, is always included in the RADIUS accounting messages
CoA Request Presence of the attribute in the CoA Request message:
  • 0: The attribute is not present in the message
  • 0+: 0 or more instances of the attribute can be present in the message
  • 0-1: 0 or 1 instance of the attribute can be present in the message
  • 1: Exactly 1 instance of the attribute is present in the message
CoA Key The attribute can be used as (part of) the CoA key to identify one or multiple sessions.
IPoE Session The attribute applies to IPoE sessions.
PPPoE Session The attribute applies to PPPoE sesssions.
PPPoE LAC Session The attribute applies to PPPoE LAC sessions. A PPPoE LAC session is a PPPoE session that is forwarded to an L2TP LNS instead of routed locally.
FWA Session The attribute applies to FWA sessions. A Fixed Wireless Access (FWA) session uses mobile wireless access technology for connectivity.

Column Description
ID ID of the trigger. This equals the value of the Alc-Acct-Triggered-Reason attribute.
Name Human-readable name of the trigger as it appears in the published RADIUS dictionary.
Description Description of the trigger.
Buffered as critical When buffering of the Interim Update messages is enabled, up to four critical Interim Update messages per session are buffered to prevent loss of data. Critical Interim Update messages are not overwritten because they relate to events that would be lost in subsequent accounting messages, such as termination of a service.

Only the last non-critical Interim Update message per session is buffered. It is overwritten with the Stop message when the session terminates.
CLI The CLI command to enable sending this trigger. The context is: config>mobile>profile>charging>bng>radius>session>update-triggers
Session Accounting The trigger applies to session accounting.