More Information About HW-Avpair (188)

Attribute-value pair, which is the framework attribute of extensible sub-attributes. The format is a character string of <attribute-name>=<value>. <attribute-name> supports the following sub-parameter functions:

  1. In EDSG service delivery: This attribute is used to return the policy configuration during EDSG service policy template downloading and corresponds to command lines. The formats of value are consistent with the command parameters.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      service:service-group

      service:service-group=<service-group-name> [ inbound | outbound ] [ priority <0-1000>]

      Returns the service group of a downloaded EDSG service template. A service group is used to determine the matching rule of an EDSG service flow.

      The corresponding command is service-group. The service group name, direction, and priority are separated with a space in between. Each attribute can contain only one service group name, one direction, and one priority. The sequence cannot be adjusted.

      service:authentication-scheme

      service:authentication-scheme=<authentication-scheme-name>

      Returns the authentication policy of a downloaded EDSG service template. The corresponding command is authentication-scheme.

      service:accounting-scheme

      service:accounting-scheme=<accounting-scheme-name>

      Returns the accounting policy of a downloaded EDSG service template. The corresponding command is accounting-scheme.

      service:prepaid-config

      service:prepaid-config=< prepaid-profile-name>

      Returns the prepaid template of a downloaded EDSG service template. The corresponding command is prepaid-profile.

      service:radius-server-group

      service:radius-server-group=<radius-server-group-name>

      Returns the RADIUS server group of a downloaded EDSG service template. The corresponding command is radius-server group.

      service:diameter-monitor-key

      service:diameter-monitor-key=<diameter-monitor-key>

      Returns the Diameter monitoring key value of an EDSG service template. The corresponding command is diameter monitor-key.

      service:service-class-inbound

      service:service-class-inbound={ cs7 | cs6 | ef | af4 | af3 | af2 | af1 | be }

      Returns the upstream service-class information of a downloaded EDSG service template. The corresponding command is service-class { cs7 | cs6 | ef | af4 | af3 | af2 | af1 | be } inbound.

      service:service-class-outbound

      service:service-class-outbound={ cs7 | cs6 | ef | af4 | af3 | af2 | af1 | be }

      Returns the downstream service-class information of a downloaded EDSG service template. The corresponding command is service-class { cs7 | cs6 | ef | af4 | af3 | af2 | af1 | be } outbound.

      service:time-range

      service:time-range=<time-range-name>< >type=rate;dir={in|out|both};cir=<cir-value>;pir=<pir-value>;cbs=<cbs-value>;pbs=<pbs-value>;

      Returns the time range template of a downloaded EDSG service template. The format requirements are as follows:

      • The type parameter must be carried in this attribute, and the type parameter must be the first parameter after the space.
      • The cir parameter must be carried in this attribute.
      • The dir parameter may not be carried in this attribute. The default value of the dir parameter is both.
      • The pbs parameter can be carried in this attribute only when the cbs parameter is carried in this attribute.
      • The device does not check time range templates delivered by the RADIUS server. If a RADIUS-delivered time range template already exists, the existing time range template takes effect. If a RADIUS-delivered time range template does not exist, the time range template fails to take effect. However, if a time range template with the same name as the RADIUS-delivered time range template is configured later, the time range template takes effect. Similarly, if a time range template applied to an EDSG service template is deleted, the bandwidth configured for the time range template of the EDSG service template fails to take effect. If a time range template with the same name as the deleted time range template is reconfigured, the EDSG service template updates the bandwidth based on the newly configured time range template.
      • A maximum of three time range templates can be applied to an EDSG service template. If more than three time range templates are applied to an EDSG service template, the EDSG service template fails to be downloaded.

      service:ip-type

      service:ip-type=<ip-type>

      Returns the service IP type of the EDSG service template. The corresponding command is ip-type ipv6.

      service:http-redirect-profile

      service:http-redirect-profile=<http-redirect-profile>

      Returns the name of the redirection profile of the EDSG service template. The corresponding command is http-redirect-profile.

      service:redirect-config

      service:redirect-config=<redirect-config>

      Returns the name of the forcible redirection profile of the EDSG service template. The corresponding command is service force redirect.

      service:traffic-match-user-group

      service:traffic-match-user-group={ inbound | outbound | both }

      Configures upstream, downstream, or both upstream and downstream EDSG service traffic to match a user group. The corresponding command is traffic match user-group.

      service:fq-pbs-in

      service:fq-pbs-in

      Returns the inbound flow-queue bandwidth of an EDSG service template. This parameter takes effect only for EDSG services whose rate limiting mode is user-queue and does not take effect for EDSG services whose rate limiting mode is CAR. The value ranges from 1 to 4194304. The corresponding command is rate-limit cir cir-value [ pir pir-value ] [ cbs cbs-value [ pbs pbs-value ] [ flow-queue-pbs flow-queue-pbs ] ] inbound.

      service:fq-pbs-out

      service:fq-pbs-out

      Returns the outbound flow-queue bandwidth of an EDSG service template. This parameter takes effect only for EDSG services whose rate limiting mode is user-queue and does not take effect for EDSG services whose rate limiting mode is CAR. The value ranges from 1 to 4194304. The corresponding command is rate-limit cir cir-value [ pir pir-value ] [ cbs cbs-value [ pbs pbs-value ] [ flow-queue-pbs flow-queue-pbs ] ] outbound.

      qos:rate-unit

      qos:rate-unit=<rate-unit>

      Returns the bandwidth unit of the EDSG service template. No such a command is available.

    • Example

      service:authentication-scheme=defalut1

      service:service-group=service1 inbound 10

      service:accounting-scheme=default0

      service:prepaid-config=prepaid1

      service:radius-server-group=aaa

      service:diameter-monitor-key=123

      service:service-class-inbound=ef

      service:service-class-outbound=ef

      service:time-range=time_range1 type=rate;dir=both;cir=1000;pir=1000;cbs=187000;pbs=187000;

      service:ip-type=ipv6

      service:http-redirect-profile=redirect1

      service:redirect-config=forceredirect1

      service:traffic-match-user-group=both

      service:fq-pbs-in=500

      service:fq-pbs-out=800

      qos:rate-unit=kbps

  2. Used in an Access-Accept packet to set a UNR tag for a user IPv4 host route

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      route-tag

      route-tag=<0-4294967294>

      This attribute is delivered to a device through an Access-Accept packet and sent to a RADIUS server through an Accounting-Request packet. COA- or COA re-authentication-based delivery is not supported. This attribute is used together with Framed-route (22) or with Framed-IP-Address (8) plus Framed-IP-Netmask (9) and takes effect to the UNR tag in the route generated using Framed-route (22) or using Framed-IP-Address (8) plus Framed-IP-Netmask (9). The route tag in the same frameroute varies with users. The attribute delivered by the first user prevails and is not updated later.

    • Example

      route-tag =5

  3. Used in EDSG real-time accounting and stop-accounting merging packets to identify them as merging accounting packets

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      acct:merge

      acct:merge=1

      This attribute identifies a packet as a merging accounting packet.

    • Example

      acct:merge=1

  4. Used in EDSG real-time accounting and stop-accounting merging packets to notify a RADIUS server of statistics about discarded FQ traffic

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      acct:dropped-cs7

      acct:dropped-cs7 = <high,low>;<0-4294967295>; <high,low>;<0-4294967295>

      This attribute is used in EDSG real-time accounting and stop-accounting merging packets to notify a RADIUS server of statistics about discarded CS7 traffic:

      • The first <high, low> indicates the number of upstream left-most 32 bytes and right-most 32 bytes, respectively.
      • The first <0-4294967295> indicates the number of upstream packets.
      • The second <high,low> indicates the number of downstream left-most 32 bytes and right-most 32 bytes, respectively.
      • The second <0-4294967295> indicates the number of downstream packets.

      acct:dropped-cs6

      acct:dropped-cs6 = <high,low>;<0-4294967295>; <high,low>;<0-4294967295>

      This attribute is used in EDSG real-time accounting and stop-accounting merging packets to notify a RADIUS server of statistics about discarded CS6 traffic. The data meaning is the same as the acct:dropped-cs7 attribute.

      acct:dropped-ef

      acct:dropped-ef = <high,low>;<0-4294967295>; <high,low>;<0-4294967295>

      This attribute is used in EDSG real-time accounting and stop-accounting merging packets to notify a RADIUS server of statistics about discarded EF traffic. The data meaning is the same as the acct:dropped-cs7 attribute.

      acct:dropped-af4

      acct:dropped-af4 = <high,low>;<0-4294967295>; <high,low>;<0-4294967295>

      This attribute is used in EDSG real-time accounting and stop-accounting merging packets to notify a RADIUS server of statistics about discarded AF4 traffic. The data meaning is the same as the acct:dropped-cs7 attribute.

      acct:dropped-af3

      acct:dropped-af3 = <high,low>;<0-4294967295>; <high,low>;<0-4294967295>

      This attribute is used in EDSG real-time accounting and stop-accounting merging packets to notify a RADIUS server of statistics about discarded AF3 traffic. The data meaning is the same as the acct:dropped-cs7 attribute.

      acct:dropped-af2

      acct:dropped-af2 = <high,low>;<0-4294967295>; <high,low>;<0-4294967295>

      This attribute is used in EDSG real-time accounting and stop-accounting merging packets to notify a RADIUS server of statistics about discarded AF2 traffic. The data meaning is the same as the acct:dropped-cs7 attribute.

      acct:dropped-af1

      acct:dropped-af1 = <high,low>;<0-4294967295>; <high,low>;<0-4294967295>

      This attribute is used in EDSG real-time accounting and stop-accounting merging packets to notify a RADIUS server of statistics about discarded AF1 traffic. The data meaning is the same as the acct:dropped-cs7 attribute.

      acct:dropped-be

      acct:dropped-be = <high,low>;<0-4294967295>; <high,low>;<0-4294967295>

      This attribute is used in EDSG real-time accounting and stop-accounting merging packets to notify a RADIUS server of statistics about discarded BE traffic. The data meaning is the same as the acct:dropped-cs7 attribute.

    • Example

      acct:dropped-cs7 = <0,100>;<200>; <0,100>;<200>

      acct:dropped-cs6 = <0,100>;<200>; <0,100>;<200>

      acct:dropped-ef = <0,100>;<200>; <0,100>;<200>

      acct:dropped-af4 = <0,100>;<200>; <0,100>;<200>

      acct:dropped-af3 = <0,100>;<200>; <0,100>;<200>

      acct:dropped-af2 = <0,100>;<200>; <0,100>;<200>

      acct:dropped-af1 = <0,100>;<200>; <0,100>;<200>

      acct:dropped-be = <0,100>;<200>; <0,100>;<200>

  5. Used in an authentication reply packet or a COA message to deliver a traffic policy

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:traffic-policy

      subscriber:traffic-policy=<traffic-policy-name>

      This attribute is used to deliver a traffic policy, with the upstream and downstream directions not differentiated.

    • Example

      subscriber:traffic-policy =tp

  6. Used in an authentication reply packet or a COA message to deliver user FQ parameters

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:fq

      subscriber:fq={cs7|cs6|ef|af4|af3|af2|af1|be };{ {shaping.value=<8-4294967294>|shaping.percentage=<0-100>}[<space>pbs=<1-4194304>]};sch={pq|lpq|wfq<space>weight=<1-100> };[dir={in|out}];

      This attribute is used in users' Access-Accept packets and COA messages and cannot be sent to RADIUS servers.

      • subscriber: sub-attribute name, which indicates that this attribute applies only to users.

      • fq: flow queue. Only one flow queue can be specified for each attribute. If a flow queue is not specified, the attribute fails to be parsed, causing a user access failure. A maximum of eight flow queues can take effect in each time of attribute delivery. When duplicate flow queues are sent, the queue sent later takes effect.

      • shaping: rate limit of a flow queue, followed by .value (in kbit/s) or .percentage (in percentage). If a value is specified, the shaping values of different queues sent at the same time cannot be over 2000 times larger or smaller than one another.

      • pbs: peak burst size. If the pbs parameter is required, the shaping value is followed by a space and then pbs=an integer (in bytes).

      • sch: scheduling mode, which can be lpq, pq, or wfq. If the sch parameter is not specified, no scheduling mode information is carried. If the wfq parameter is specified, the parameter is followed by a space and weight=an integer.

      • dir: flow direction, which can be in or out. If the dir parameter is not specified, the attribute applies to both inbound and outbound directions.

      The FQ parameters sent by the RADIUS server are QoS parameters. However, affected by the FQ and QoS parameters that take effect on the device, there are scenarios in which the attribute does not take effect despite its correct format. Instances of ineffective scenarios include:
      • No rate limit is configured or CAR is configured on the device.

      • Users have configured the four-flow-queue mode or a priority translation profile. The parameters of these configurations are incompatible with those in the flow-queue profile delivered by a RADIUS server.
      • A RADIUS server delivers queues, causing the proportion of the shaping value (in percentage) of one queue to the shaping value (in percentage) of another queue to exceed 2000 folds.
      • A RADIUS server delivers queues, causing the shaping values of queues in the user flow-queue profile to have different units.
      • FQ parameters are delivered to unsupported types of users, such as home users.
      • The flow queue rates are implemented using CAR through the queue cos-value car { car-value | car-percentage car-percentage-value } [ pbs pbs-value ] command run in the flow queue profile view.
      • Either shaping or sch must be delivered.
    • Example

      subscriber:fq=ef;shaping.value=1000 pbs=3000;sch=wfq weight=20;dir=out;

  7. Used in an authentication reply packet or a COA message to deliver a GQ profile name

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:gq-inbound

      subscriber:gq-inbound =<gq-inbound-name>

      This attribute is used to deliver a GQ profile name used in the upstream direction.

      subscriber:gq-outbound

      subscriber:gq-outbound =<gq-outbound-name>

      This attribute is used to deliver a GQ profile name used in the downstream direction.

    • Example

      subscriber:gq-inbound =gq_in

  8. Sent by a RADIUS server to online users to deliver or cancel the in-arrears identifier

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:lease-timeout-offline

      subscriber:lease-timeout-offline={enable | disable}

      This attribute is sent by a RADIUS server to online users to deliver or cancel the in-arrears identifier.

    • Example

      subscriber:lease-timeout-offline=enable

  9. Sent by a RADIUS server to online users or users who request to go online to deliver the user-group attribute.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:user-group

      subscriber:user-group=<user-group-name>

      This attribute is sent by a RADIUS server to online users or users who request to go online to deliver the user-group attribute.

    • Example

      subscriber:user-group=group1

  10. Used in an authentication response packet to deliver the Framed-Route attribute.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:framed-route

      subscriber:framed-route=<address>[/<subnet mask length>]<space>[<next-hop>]<space>[<hop count>]<space>[preference<space><preference value>]

      This attribute is used to deliver the Framed-Route attribute in an authentication response packet sent by the RADIUS server. A maximum of 128 Framed-route attributes can be delivered in an authentication response packet per user, but the total length of the packet must not exceed 4096 bytes.

      It is recommended that the preference value delivered in the RUI scenario be less than the default protocol value . If the delivered preference value is larger than the default protocol value, traffic may be interrupted on the new master device after a master/backup device switchover is performed.

    • Example

      subscriber:framed-route=192.168.1.0/24 0.0.0.0 2 preference 200

  11. Sent by a RADIUS server to online users or users who request to go online to deliver the upstream VPN instance.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:vpn-instance-inbound

      subscriber:vpn-instance-inbound=<vpn-instance-name>

      This attribute is sent by a RADIUS server to online users or users who request to go online to deliver the upstream VPN instance.

    • Example

      subscriber:vpn-instance-inbound=vpn1

  12. Used in a RADIUS Accounting-Request packet to carry the VPN ID.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:vpnid

      subscriber:vpnid=<vpn-instance-id>

      This attribute is used to carry the VPN ID in an Accounting-Request packet to be sent to the RADIUS server.

    • Example

      subscriber:vpnid=1

  13. Used in a RADIUS authentication response packet to deliver the PCP enabling flag.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      pcp-flag

      pcp-flag=<flag>

      This attribute is used to deliver the PCP-flag attribute in a RADIUS authentication response packet.

      The <flag> value can be:
      • 0: disabled
      • 1: enabled
    • Example

      pcp-flag=1

  14. Used to deliver IPv6 frame-route in RADIUS authentication response packets.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:framed-ipv6-route

      subscriber:framed-ipv6-route= <IPv6 address > [/< mask length >] < space > [< next hop >] < space > [< hop count >] < space > [preference< space >< route priority >]

      The framed-ipv6-route is delivered through RADIUS authentication response packets. A maximum of 128 framed IPv6 routes can be delivered to each user, and the maximum packet length is 4096.

      The preference value delivered in RUI scenarios is recommended to be lower than the default value. Otherwise, traffic on the new host may be interrupted after a master/slave main control board switchover.

    • Example

      subscriber:framed-ipv6-route=2001:db8:1::1/64 :: 10 preference 200

  15. Used as the unit of the bandwidth value carried in authentication response packets, accounting request packets, CoA request packets, and CoA ACK packets.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      qos:rate-unit

      qos:rate-unit=kbps

      This attribute specifies the unit of the values of HW-Input-Committed-Information-Rate (HUAWEI-2), HW-Input-Peak-Information-Rate (HUAWEI-3), HW-Output-Committed-Information-Rate (HUAWEI-5), and HW-Output-Peak-Information-Rate (HUAWEI-6).

    • Example

      qos:rate-unit=kbps

  16. Used to carry the rate limit mode and statistics counting mode of EDSG services in COA request packets.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      service:traffic-mode

      service:traffic-mode

      Used to carry the rate limit mode and statistics counting mode of EDSG services in COA request packets.This attribute is used to deliver the rate limit mode and statistics counting mode of EDSG services. The value can be 0, 1, or 2.

      • 0: rate limit separation and statistics separation.
      • 1: rate limit separation and statistics non-separation.
      • 2: rate limit non-separation and statistics non-separation.
    • Example

      service:traffic-mode=1

  17. It is used to carry UP-related information in the authentication request packets and accounting packets for users' value-added services.

    • Attribute description

      Attribute Name

      Attribute Format

      Usage Scenario

      subscriber:nas-type

      subscriber:nas-type=<nas-type>

      It is used to specify the device type, which distinguishes the CUSP device and non-CUSP device. The value can be 1 or 2. Value 1 indicates the non-CUSP device, and value 2 indicates the CUSP device.

    • Example

      subscriber:nas-type=2

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >