radius-attribute include hw-avpair

Function

The radius-attribute include hw-avpair command allows RADIUS packets to carry the hw-avpair attribute.

The undo radius-attribute include hw-avpair command deletes the hw-avpair attribute from RADIUS packets.

By default, the specified attribute cannot be added to a RADIUS packet.

This command is supported only on the NetEngine 8000 F1A.

Format

radius-attribute include hw-avpair hw-avpair-name packet-type

radius-attribute include hw-avpair hw-avpair-name-without-packet-type

undo radius-attribute include hw-avpair hw-avpair-name packet-type

undo radius-attribute include hw-avpair hw-avpair-name-without-packet-type

undo radius-attribute include hw-avpair accounting-request

Parameters

Parameter	Description	Value
packet-type	Specifies the packet type.	The below values are supported: accounting-request:Indicates user accounting packets. access-request:Indicates user authentication packets.
hw-avpair hw-avpair-name	Specifies the value of the HW-AVPair attribute to be encapsulated into the authentication or accounting packets to be sent to the RADIUS server.	The below values are supported: subscriber:fq: allows IPv4 user accounting packets to carry the effective flow-queue parameter value. subscriber:vpnid: allows user accounting packets to carry user VPN indexes. subscriber:link-address: allows authentication packets to carry DHCPv6 addresses.
hw-avpair hw-avpair-name-without-packet-type	Specifies the value of the HW-AVPair attribute to be encapsulated into the authentication and accounting packets to be sent to the RADIUS server.	The below values are supported: subscriber:nas-type: is used to distinguish between a non-forwarding-control separation device and a forwarding-control separation device.
accounting-request	Configures the attribute in the accounting-request packet.	-

Views

RADIUS server group view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
radius	write

Usage Guidelines

Usage Scenario

By default, many attributes are not carried in packets, which prevents unnecessary or unidentifiable attributes from being sent to a RADIUS server. To allow an attribute to be carried in a packet, run the radius-attribute include hw-avpair command.You can run the display radius-attribute command to check whether a RADIUS attribute is carried in a packet.

Configuration Impact

If an attribute is not carried in a packet by default, run the radius-attribute include hw-avpair command to allow the attribute to be carried in the packet. If you also specify a packet type, the attribute is carried only in this type of packets.

If you specify multiple attributes, all the specified attributes are carried in packets.

Example

# Allow the effective flow-queue parameter value to be carried in accounting start packets and accounting stop packets.

<HUAWEI> system-view
[~HUAWEI] radius-server group huawei
[*HUAWEI-radius-huawei] commit
[~HUAWEI-radius-huawei] radius-attribute include hw-avpair subscriber:fq accounting-request