No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Fat AP and Cloud AP V200R010C00 Command Reference

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
radius-server support chargeable-user-identity

radius-server support chargeable-user-identity

Function

The radius-server support chargeable-user-identity command configures a device to support the CUI attribute.

The undo radius-server support chargeable-user-identity command restores the default settings.

By default, a device does not support the CUI attribute.

Format

radius-server support chargeable-user-identity [ not-reject ]

undo radius-server support chargeable-user-identity

Parameters

Parameter

Description

Value

not-reject

Configures the device not to process the CUI attribute.

-

Views

RADIUS server template view

Default Level

2: Configuration level

Usage Guidelines

In a scenario where roaming accounting is performed on a carrier network, the same user may have register different user names in different network environments. Therefore, the user name cannot be used as the unique ID for accounting. In this case, you can use the RADIUS Chargeable-User-Identity (CUI) attribute defined in the RFC to resolve this issue. RADIUS authentication servers can provide users with unique CUI attribute values that function as the users' accounting IDs.

By default, RADIUS Access-Request packets sent by a device do not carry the CUI attribute. If Access-Accept packets responded by the RADIUS server carry the CUI attribute, the device retains this attribute in the Accounting-Request(Start), Accounting-Request(Interim-update), and Accounting-Request(Stop) packets without any processing.

After the radius-server support chargeable-user-identity [ not-reject ] command is configured, the RADIUS Access-Request packets sent by the device carry the CUI attribute and the attribute value is Null.
  • If Access-Accept packets responded by the RADIUS server carry the CUI attribute, the device retains this attribute in the Accounting-Request(Start), Accounting-Request(Interim-update), and Accounting-Request(Stop) packets without any processing; the previously delivered CUI attribute is carried in the Access-Request packets triggered by the subsequent reauthentication, authentication coverage, and roaming for users.
  • If Access-Accept packets responded by the RADIUS server does not carry the CUI attribute or carry the CUI attribute whose value is Null:
    • If the not-reject parameter is not specified, user authentication fails.
    • If the not-reject parameter is specified, the device ignores the CUI attribute and user authentication succeeds.

Example

# Configure a device to support the CUI attribute.

<Huawei> system-view
[Huawei] radius-server template test1
[Huawei-radius-test1] radius-server support chargeable-user-identity
Translation
Download
Updated: 2019-11-21

Document ID: EDOC1100064352

Views: 211512

Downloads: 122

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next