attribute 25 car 属性值格式

No.

25

Attribute Name

Class

Attribute Value Type

String

Standard Defined

RFC 2865

Server Type

All

Value of Length field (in Bytes)

1~253

Description

If the RADIUS Access-Accept packet sent by the RADIUS server to the NAS carries the Class attribute, the Class attribute must also be carried in the subsequent RADIUS Accounting-Request packets sent from the NAS to the RADIUS server. A RADIUS Access-Accept packet can carry zero to eight Class attributes.

Note:

The Class attribute is used in two application scenarios. In addition to the standard scenario described by RFC 2865, the Class attribute can be delivered with QoS parameters contained. The details are as follows:

1. If the radius-server class-as-car command is run in the RADIUS server group view, the Class attribute is parsed as CAR parameters:

For a standard RADIUS server, the Class attribute can carry CAR parameters after the radius-server class-as-car command is run. If the Class attribute carries CAR parameters, the total length of the CAR parameters is at least 32 bytes, and the CAR parameter string can consist of only digits ranging from 0 to 9. The first 32 bytes are divided into four 8-bytes (from left to right), which are used to indicate the upstream PIR, upstream CIR, downstream PIR, and downstream CIR, respectively, expressed in bit/s. For other types of RADIUS servers, the Class attribute cannot carry CAR parameters.

Irrespetive of whether the Class attribute is used to carry CAR parameters, the Class attribute is eventually transmitted back to the RADIUS server. When the Class attribute carries CAR parameters, a NAS detects whether the first 32 bytes are characters, and discards the subsequent bytes. Only one Class attribute takes effect. If multiple Class attributes are contained in a packet, the CAR parameters of the last valid Class attribute are used.

2. The Class attribute can also be used to send descriptions of user access VLANs or PVCs to a RADIUS server. If the "link-account resolve" command is run on a BAS interface, the command takes effect only for common Layer 2 users who are not authenticated but are charged by a RADIUS server.

The rules for delivering the Class attribute in a CoA message are as follows:

1. If the radius-server class-as-car [enable-pir] command is not run in the view of the RADIUS server group to which the authorization server belongs, the Class attribute can be modified using a CoA message. The Class attribute delivered in a CoA message replaces the existing Class attribute of a user.
2. If the radius-server class-as-car [enable-pir] command is run in the view of the RADIUS server group to which the authorization server belongs, the Class attribute delivered in a CoA message fails to take effect.
3. After the value-added-service edsg modify-synchronous class command is run, the Class attribute can be delivered together with EDSG service attributes in a CoA message. If this command is not run, the Class attribute is ignored if it is delivered in a CoA message used to activate or deactivate the EDSG service.
4. The Class attribute can be delivered in a CoA message used to deactivate the EDSG service. Accounting Stop packets of the deactivated service carry the old Class attribute.
5. The Class attribute can be delivered in a CoA message used to activate the EDSG service. Accounting Start packets of the activated service carry the new Class attribute.
6. The Class attribute can be delivered in a CoA message used to replace the EDSG service. Accounting Stop packets of the replaced service carry the old Class attribute. Accounting Start packets of the new service carry the new Class attribute.
7. If the radius-server coa-request hw-policy-name daa coexist-with-user command is configured, the Class attribute can be delivered in a CoA message used to activate the DAA service. If this command is not configured, the Class attribute delivered in a CoA message used to activate the DAA service is ignored.
8. The Class attribute cannot be delivered in a CoA message used to activate the BOD service. If the Class attribute is delivered in a CoA message used to activate the BOD service, the Class attribute is ignored.
9. After the Class attribute is changed using a CoA message, all accounting packets carry the newly delivered Class attribute, including accounting packets of the user, accounting packets of EDSG services, and accounting packets of DAA services.