RADIUS accounting attributes

ESM accounting

There are currently three accounting modes in Enhanced Subscriber Management accounting:

  • Host accounting (H)

  • Session accounting (S)

  • Queue instance accounting (Q)

A single host can have up to two simultaneously active accounting modes.

The Acct Reporting Level column in Enhanced Subscriber Management accounting (applicability) shows the accounting mode messages that report the attribute:

  • HSQ means the attribute is present in the accounting messages of all accounting modes

  • H->S->Q means the attribute is present in the accounting messages of a single accounting mode:

    • If Host accounting is enabled, then the attribute is present in the accounting messages that belong to this mode.

    • Else if session accounting is enabled, then the attribute is present in the accounting messages that belong to this mode.

    • Else if Queue instance accounting is enabled, then the attribute is present in the accounting messages that belong to this mode.

Each accounting mode has a unique accounting session ID.

Host accounting (per subscriber host):

show service id <svc-id> subscriber-hosts detail

Acct-Session-Id       : 241AFF000000204FE9D801

Session accounting (per PPPoE or IPoE session):

show service id <svc-id> ppp session detail
show service id <svc-id> ipoe session detail

Acct-Session-Id   : 241AFF000000214FE9D801

Queue instance accounting (per queue instance):

show service id <svc-id> subscriber-hosts detail

Acct-Q-Inst-Session-Id: 241AFF000000224FE9D801

An overview of active accounting modes and corresponding session IDs can be displayed with the show service active-subscribers hierarchy radius-acct command.

The Host or Session accounting session ID can be included in a RADIUS Access Request:

configure
    subscriber-mgmt
        authentication-policy <name> 
            include-radius-attribute acct-session-id [host|session]

The format of the accounting session ID appearing in RADIUS accounting messages can be configured to be:

  • a hexadecimal number format as a fixed length string of 22 characters composed of:
    • 6 hexadecimal characters derived from the chassis Base MAC address (show chassis): XOR of bytes 1 and 4, bytes 2 and 5, and bytes 3 and 6
    • 8 hexadecimal characters containing an unsigned 32 bit sequence number (CPM wide, wraps around at 4294967295 decimal)
    • 8 hexadecimal characters containing the session creation time (UNIX epoch time in seconds)
  • a description format as a variable length string: <subscriber-id>@<sap-id>@<sla-profile>_<creation-time>
configure
    subscriber-mgmt
        radius-accounting-policy <name> 
            session-id-format {description | number}

An Acct-Multi-Session-Id is included in all RADIUS accounting messages (start/stop/interim):

Table 1. Enhanced Subscriber Management accounting [50] Acct-Multi-Session-Id values
queue-instance-accounting host-accounting session-accounting [50] Acct-Multi-Session-Id

Not present

Queue Instance Acct-Session-Id

Queue Instance Acct-Session-Id

Queue Instance Acct-Session-Id

Queue Instance Acct-Session-Id

Session Acct-Session-Id

The reporting of volume counters in accounting is coupled to the sending of periodic or host triggered Accounting Interim Updates messages. Volume based accounting is therefore enabled using the interim-update CLI parameter for all accounting modes and, or by the host-update CLI parameter in session accounting mode as shown in Accounting statistics type.

Table 2. Accounting statistics type
Accounting mode Statistics type

host-accounting interim-update

session-accounting interim-update [host-update]

session-accounting host-update

queue-instance-accounting interim-update

Time and volume based accounting

host-accounting

session-accounting

queue-instance-accounting

Time based accounting

The different sets of volume accounting attributes that can be included in the Accounting Interim and Stop messages are controlled using include-radius-attribute CLI commands. Multiple volume reporting types can be enabled simultaneously:

configure
  subscriber-mgmt
    radius-accounting-policy <name>
      include-radius-attribute
        [no] detailed-acct-attributes  # 64 bit per queue/policer counters
        [no] std-acct-attributes       # 32 bit aggregate counters (v4+v6)
        [no] v6-aggregate-stats        # 32 bit aggregate counters (v6 only) 
Table 3. Enhanced Subscriber Management accounting (description)
Attribute ID Attribute name Description

1

User-Name

Refers to the user to be authenticated in the Access-Request. The format for IPoE/PPPoE hosts depends on configuration parameters pppoe-access-method, ppp-user-name or user-name-format in the CLI context configure subscriber-mgmt authentication-policy name. The format for ARP-hosts is not configurable and always the host IPv4-address. The RADIUS User-Name specified in an Access-Accept or CoA is reflected in the corresponding accounting messages. The attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no user-name.

4

NAS-IP-Address

The identifying IP Address of the NAS requesting the Authentication or Accounting. Included when the RADIUS server is reachable using IPv4.

The address is determined by the routing instance through which the RADIUS server can be reached:

‟Management” — The active IPv4 address in the Boot Options File (bof address ipv4-address)

‟Base” or ‟VPRN”— The IPv4 address of the system interface (configure router interface system address address).

The default NAS-IP-Address value can be overwritten:

ESM: configure aaa radius-server-policy policy-name servers source-address ip-address

DSM: configure aaa isa-radius-policy name nas-ip-address-origin {isa-ip | system-ip}

5

NAS-Port

The physical access-circuit on the NAS which is used for the Authentication or Accounting of the user. The format of this attribute is configurable on the NAS as a fixed 32 bit value or a parameterized 32 bit value. The parameters can be a combination of outer and inner vlan ID, slot number, MDA number, port number, lag-id, pw-id, pxc-id, pxc-subport and fixed bit values (zero or one) but cannot exceed 32 bits. The format can be configured for following applications: configure aaa l2tp-accounting-policy name include-radius-attribute nas-port, configure router l2tp cisco-nas-port, configure service vprn service-id l2tp cisco-nas-port, configure subscriber-mgmt authentication-policy name include-radius-attribute nas-port, configure subscriber-mgmt radius-accounting-policy name include-radius-attribute nas-port.

6

Service-Type

The type of service the PPPoE user has requested, or the type of service to be provided for the PPPoE user. Optional in RADIUS-Accept and CoA. Treated as a session setup failure if different from Framed-User.

7

Framed-Protocol

The framing to be used for framed access in case of PPPoE users. Optional in RADIUS-Accept and CoA. Treated as a session setup failure if different from PPP.

8

Framed-IP-Address

The IPv4 address assigned to the subscriber host. Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no framed-ip-addr.

9

Framed-IP-Netmask

The IPv4 netmask assigned to the subscriber host. Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no framed-ip-netmask.

22

Framed-Route

The routing information (IPv4 managed route) to be configured on the NAS for a host (dhcp, pppoe, arp) that operates as a router without NAT (so called Routed subscriber host). Valid RADIUS learned managed routes can be included in RADIUS accounting messages with following configuration: configure subscriber-mgmt radius-accounting-policy name include-radius-attribute framed-route. Associated managed routes for an instantiated routed subscriber host are included in RADIUS accounting messages independent of the state of the managed route (Installed, Shadowed or HostInactive). In case of a PPP session, when a Framed-Route is available while the corresponding routed subscriber host is not yet instantiated, the managed route is in the state ‟notYetInstalled” and is not included in RADIUS accounting messages.

25

Class

The attribute sent by the RADIUS server to the NAS in an Access-Accept or CoA and is sent unmodified by the NAS to the Accounting server as part of the Accounting-Request packet. Strings with a length longer than the defined Limits are accepted but truncated to this boundary.

30

Called-Station-Id

Allows the NAS to send in an Access Request and, or Accounting Request information with respect to the user called. Attribute is omitted in authentication/accounting using: configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute no called-station-id.

Supported applications:

  • LNS

    The content is the string passed in the [21] Called Number AVP of the L2TP ICRQ message.

  • WLAN Gateway / vRGW

    This reflects the currently learned AP-MAC and SSID. These can be learned using EAP, DHCP (option 82), DHCPv6 LDRA (interface-id), ARP/ND over GRE or L2TP cookie.

31

Calling-Station-Id

Allows the NAS to send unique information identifying the user who requested the service. This format is driven by configuration (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute calling-station-id <llid | mac | remote-id | sap-id | sap-string>). The LLID (logical link identifier) is the mapping from a physical to logical identification of a subscriber line and supplied by a RADIUS llid-server. The sap-string maps to configure service ies | vprn service-id subscriber-interface ip-int-name group-interface ip-int-name sap sap-id calling-station-id sap-string. A [31] Calling-Station-Id attribute value longer than the allowed maximum is treated as a setup failure. The attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no calling-station-id.

For DSM the Calling-Station-Id is always equal to the remote-id if present and the UE MAC address otherwise.

32

NAS-Identifier

A string (configure system name system-name) identifying the NAS originating the Accounting requests and sent when nas-identifier is included for the corresponding application: configure subscriber-mgmt radius-accounting-policy (ESM accounting), configure aaa isa-radius-policy (LSN accounting, WLAN-GW) and configure aaa l2tp-accounting-policy (L2TP accounting).

40

Acct-Status-Type

Indicates whether this Accounting-Request marks the beginning of the user service (Start) or the end (Stop) or reports interim updates.

41

Acct-Delay-Time

Indicates how many seconds the client has been trying to send this accounting record for. In initial accounting messages this attribute is included with value 0 for ESM and omitted for DSM. Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no acct-delay-time.

42

Acct-Input-Octets

Indicates how many octets have been received from the user over the course of this service being provided and included when standard accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute std-acct-attributes). [52] Acct-Input-Gigawords indicates how many times (if greater than zero) the [42] Acct-Input-Octets counter has wrapped around 2^32.

43

Acct-Output-Octets

Indicates how many octets have been sent to the user over the course of this service being provided and included when standard accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute std-acct-attributes). [53] Acct-Output-Gigawords indicates how many times (if greater than zero) the [43] Acct-Output-Octets counter has wrapped around 2^32.

44

Acct-Session-Id

A unique identifier that represents a subscriber host, a set of subscriber hosts that belong to the same queue-instance, or a set of hosts that belong to a PPPoE or IPoE session. The attribute can have a fixed 22 byte hexadecimal number format or a variable length description format (configure subscriber-mgmt radius-accounting-policy name session-id-format {number | description}). For DSM, the attribute has a fixed 10-byte hexadecimal number format with each byte separated by a hyphen.

This attribute (in number format) can be used as CoA or Disconnect Message key to target the hosts or session.

45

Acct-Authentic

Indicates how the user was authenticated. Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no acct-authentic.

46

Acct-Session-Time

Reports the elapsed time in seconds over the course of this service being provided. When the accounting session time equals zero (example when the accounting start is followed immediately by an accounting interim update or by an accounting stop within the same second), then the attribute is not included.

47

Acct-Input-Packets

Indicates how many packets have been received from the user over the course of this service being provided and included when standard accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute std-acct-attributes). There is no overflow attribute when attribute wraps around 2^32.

48

Acct-Output-Packets

Indicates how many packets have been send to the user over the course of this service being provided and included when standard accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute std-acct-attributes). There is no overflow attribute when attribute wraps around 2^32.

49

Acct-Terminate-Cause

Indicates how the subscriber host or queue-instance or PPPoE/IPoE session was terminated. An overview of the mapping between [26.6527.226] Alc-Error-Code / [26.6527.227] Alc-Error-Message and the corresponding [49] Acct-Terminate-Cause attribute value can be displayed with the command: tools dump aaa radius-acct-terminate-cause.

50

Acct-Multi-Session-Id

A unique Accounting ID that links together multiple related accounting sessions. (see Enhanced Subscriber Management accounting [50] Acct-Multi-Session-Id values) Each linked accounting session has a unique [44] Acct-Session-Id and the same [50] Acct-Multi-Session-Id.

This attribute is not sent if only queue-instance accounting mode is enabled.

The attribute can have a fixed 22 byte hexadecimal number format or a variable length description format (configure subscriber-mgmt radius-accounting-policy name session-id-format {number | description}).

For DSM the attribute has a fixed 10 byte hexadecimal number format with each byte separated by a hyphen. There are no DSM hosts linked together through this attribute.

52

Acct-Input-Gigawords

Indicates how many times (one or more) the [42] Acct-Input-Octets counter has wrapped around 2^32 in the course of delivering this service and send together with [42] Acct-Input-Octets, [43] Acct-Output-Octets and [53] Acct-Output-Gigawords when standard accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute std-acct-attributes). The attribute is not sent when its value=0.

53

Acct-Output-Gigawords

Indicates how many times (one or more) the [43] Acct-Output-Octets counter has wrapped around 2^32 in the course of delivering this service and send together with [42] Acct-Input-Octets, [43] Acct-Output-Octets and [52] Acct-Input-Gigawords when standard accounting attributes are configured (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute std-acct-attributes). The attribute is not sent when its value=0.

55

Event-Timestamp

Record the time that this event occurred on the NAS, in seconds since January 1, 1970 00:00 UTC

61

NAS-Port-Type

The type of the physical port of the NAS which is authenticating the user and value automatically determined from subscriber SAP encapsulation. It can be overruled by configuration. Included only if include-radius-attribute nas-port-type is added per application: configure subscriber-mgmt radius-accounting-policy (ESM accounting), configure aaa isa-radius-policy (LSN accounting, WLAN-GW) and configure aaa l2tp-accounting-policy (L2TP accounting). Checked for correctness if returned in CoA.

64

Tunnel-Type

(L2TP LAC and LNS only) The tunneling protocols to be used (in the case of a tunnel initiator) or the tunneling protocol in use (in the case of a tunnel terminator). This attribute is mandatory in LAC Access-Accept and its value must be L2TP.

The attribute is included in Acct-Request messages if the tunnel-server-attrs (LNS) or tunnel-client-attrs (LAC) option is configured in the configure subscriber-mgmt radius-accounting-policy name include-radius-attribute CLI context.

65

Tunnel-Medium-Type

(L2TP LAC and LNS only) The transport medium to use when creating a tunnel for protocols (such as L2TP) that can operate over multiple transports. This attribute is mandatory in LAC Access-Accept and its value must be IP or IPv4.

The attribute is included in Acct-Request messages if the tunnel-server-attrs (LNS) or tunnel-client-attrs (LAC) option is configured in the configure subscriber-mgmt radius-accounting-policy name include-radius-attribute CLI context.

66

Tunnel-Client-Endpoint

(L2TP LAC and LNS only) The dotted-decimal IP address of the initiator end of the tunnel. Preconfigured values are used when attribute is omitted (configure router/service vprn service-id l2tp local-address). If omitted in Access Accept on LAC and no local-address configured, then the address is taken from the interface with name system.

The attribute is included in Acct-Request messages if the tunnel-server-attrs (LNS) or tunnel-client-attrs (LAC) option is configured in the configure subscriber-mgmt radius-accounting-policy name include-radius-attribute CLI context.

67

Tunnel-Server-Endpoint

(L2TP LAC and LNS only) The dotted-decimal IP address of the server end of the tunnel is also on the LAC the dest-ip for all L2TP packets for that tunnel.

The attribute is included in Acct-Request messages if the tunnel-server-attrs (LNS) or tunnel-client-attrs (LAC) option is configured in the configure subscriber-mgmt radius-accounting-policy name include-radius-attribute CLI context.

68

Acct-Tunnel-Connection

(L2TP LAC and LNS only) The format of the attribute in Acct-Request messages can be configured with configure subscriber-mgmt radius-accounting-policy name acct-tunnel-connection-fmt ascii-spec. By default, the Call Serial Number is inserted.

The attribute is included in Acct-Request messages if the tunnel-server-attrs (LNS) or tunnel-client-attrs (LAC) option is configured in the configure subscriber-mgmt radius-accounting-policy name include-radius-attribute CLI context.

87

NAS-Port-Id

A text string which identifies the physical/logical port of the NAS which is authenticating the user and, or reported for accounting. Attribute is also used in CoA and Disconnect Message (part of the user identification-key).

See [87] NAS-Port-Id attribute details for a detailed description of the attribute format.

The physical port can have an optional prefix-string (max 8 chars) and suffix-string (max 64 chars) added for Accounting (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute nas-port-id [prefix-string string] [suffix circuit-id | remote-id]).

90

Tunnel-Client-Auth-ID

(L2TP LAC and LNS only) Used during the authentication phase of tunnel establishment and copied by the LAC in L2TP SCCRQ AVP 7 Host Name. The value with tag 0 is used as default for the tunnels where the value is not specified. Pre-configured values are used when the attribute is omitted (configure router/service vprn service-id l2tp local-name host-name). The system name (configure system name system-name) is copied in AVP Host Name if this attribute is omitted and no local-name is configured.

The attribute is included in Acct-Request messages if the tunnel-server-attrs (LNS) or tunnel-client-attrs (LAC) option is configured in the configure subscriber-mgmt radius-accounting-policy name include-radius-attribute CLI context.

91

Tunnel-Server-Auth-ID

(L2TP LAC and LNS only) Used during the authentication phase of tunnel establishment. For authentication the value of this attribute is compared with the value of AVP 7 Host Name from the received LNS SCCRP. Authentication from LAC point of view passes if both attributes are the same. This authentication check is not performed if the RADIUS attribute is omitted.

The attribute is included in Acct-Request messages if the tunnel-server-attrs (LNS) or tunnel-client-attrs (LAC) option is configured in the configure subscriber-mgmt radius-accounting-policy name include-radius-attribute CLI context.

95

NAS-IPv6-Address

The identifying IP Address of the NAS requesting the Authentication or Accounting. Included when the RADIUS server is reachable using IPv6.

The address is determined by the routing instance through which the RADIUS server can be reached:

‟Management” — The active IPv6 address in the Boot Options File (bof address ipv6-address)

‟Base” or ‟VPRN” — The IPv6 address of the system interface (configure router interface system ipv6 address ipv6-address).

The address can be overwritten with the configured ipv6-source-address (configure aaa radius-server-policy policy-name servers ipv6-source-address ipv6-address).

96

Framed-Interface-Id

Contains the IPv6 interface ID from the user. The attribute can optionally be included in Accounting messages (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute framed-interface-id). The Framed-Interface-Id attribute is not sent in RADIUS Authentication and silently ignored in RADIUS Accept.

97

Framed-IPv6-Prefix

The IPv6 prefix or prefix length to be configured using SLAAC (Router Advertisement) to the WAN side of the user. Any non /64 prefix-length for SLAAC host creation is treated as a session setup failure for this host. This attribute is an alternative to [100] Framed-IPv6-Pool and [26.6527.99] Alc-IPv6-Address, which assigns IPv6 addressing to the wan-side of a host using DHCPv6 IA-NA. Attribute is also used in CoA and Disconnect Message (part of the ESM or AA user identification-key). Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no framed-ipv6-prefix.

For Distributed Subscriber Management (DSM), if SLAAC is active for a UE, the attribute contains the prefix assigned to this UE. Inclusion of this attribute is enabled using configure aaa isa-radius-policy name acct-include-attributes framed-ipv6-prefix.

99

Framed-IPv6-Route

The routing information (IPv6 managed route) to be configured on the NAS for a v6 wan-host (IPoE or PPPoE) that operates as a router and, or a DHCPv6 IA-PD host modeled as a managed route. Valid RADIUS learned managed routes and DHCPv6 IA-PD hosts modeled as a managed route can be included in RADIUS accounting messages with following configuration: configure subscriber-mgmt radius-accounting-policy name include-radius-attribute framed-ipv6-route. Associated managed routes for an instantiated routed subscriber host are included in RADIUS accounting messages independent of the state of the managed route (Installed, Shadowed or HostInactive). In case of a PPP session, when a Framed-IPv6-Route is available while the corresponding routed subscriber host is not yet instantiated, the managed route is in the state ‟notYetInstalled” and is not included in RADIUS accounting messages.

123

Delegated-IPv6-Prefix

Attribute that carries the Prefix (IPv6 prefix or prefix length) to be delegated using DHCPv6 (IA-PD) for the LAN side of the user (IPoE, PPPoE). Maps to DHCPv6 option IA-PD [25] sub-option IA-Prefix [26] Prefix. An exact Delegated-prefix-Length [DPL] match with configure service ies | vprn service-id subscriber-interface ip-int-name ipv6 delegated-prefix-length [48 to 64] is required with the received attribute prefix-length unless a variable DPL is configured (configure service ies | vprn service-id subscriber-interface ip-int-name ipv6 delegated-prefix-length variable).In the latter case we support multiple hosts for the same group-interface having different prefix-length [48 to 64] per host. Simultaneous returned attributes [123] Delegated-IPv6-Prefix and [26.6527.131] Alc-Delegated-IPv6-Pool are handled as host setup failures. Attribute is also used in CoA and Disconnect Message (part of the ESM or AA user identification-key). Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no delegated-ipv6-prefix.

26.3561.1

Agent-Circuit-Id

Information describing the subscriber agent circuit identifier corresponding to the logical access loop port of the Access Node/DSLAM from which a subscriber's requests are initiated. Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute circuit-id.

26.3561.2

Agent-Remote-Id

An operator-specific, statically configured string that uniquely identifies the subscriber on the associated access loop of the Access Node/DSLAM. Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute remote-id.

26.3561.129

Actual-Data-Rate-Upstream

Actual upstream train rate of a subscriber's synchronized DSL link and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.130

Actual-Data-Rate-Downstream

Actual downstream train rate of a subscriber's synchronized DSL link and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.131

Minimum-Data-Rate-Upstream

The subscriber's operator-configured minimum upstream data rate and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.132

Minimum-Data-Rate-Downstream

The subscriber's operator-configured minimum downstream data rate and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.133

Attainable-Data-Rate-Upstream

The subscriber's attainable upstream data rate and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.134

Attainable-Data-Rate-Downstream

The subscriber's attainable downstream data rate and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.135

Maximum-Data-Rate-Upstream

The subscriber's maximum upstream data rate, as configured by the operator and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.136

Maximum-Data-Rate-Downstream

The subscriber's maximum downstream data rate, as configured by the operator and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.137

Minimum-Data-Rate-Upstream-Low-Power

The subscriber's minimum upstream data rate in low power state, as configured by the operator and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.138

Minimum-Data-Rate-Downstream-Low-Power

The subscriber's minimum downstream data rate in low power state, as configured by the operator and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.139

Maximum-Interleaving-Delay-Upstream

The subscriber's maximum one-way upstream interleaving delay, as configured by the operator and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.140

Actual-Interleaving-Delay-Upstream

The subscriber's actual one-way upstream interleaving delay and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.141

Maximum-Interleaving-Delay-Downstream

The subscriber's maximum one-way downstream interleaving delay, as configured by the operator and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.142

Actual-Interleaving-Delay-Downstream

The subscriber's actual one-way downstream interleaving delay and maps to values received during PPPoE discovery (tag 0x0105) or DHCP (opt-82). Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.3561.144

Access-Loop-Encapsulation

The last mile encapsulation used by the subscriber on the DSL access loop and maps to values received during PPPoE discovery Tags (tag 0x0105) or DHCP Tags (opt-82). Attribute is included or excluded in RADIUS/Accounting-Request based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options. Last mile encapsulation information can be used to adjust automatically the egress aggregate rate for this subscriber. Preconfigured encapsulation types are used if PPP/IPoE access loop information (tags) is not available (configure subscriber-mgmt sub-profile subscriber-profile-name egress encap-offset type type or configure subscriber-mgmt local-user-db local-user-db-name ppp host host-name access-loop-encapsulation encap-offset type type). [26.6527.133] Alc-Access-Loop-Encap-Offset when returned in Access-Accept is taken into account (overrules received tags and preconfigured encapsulation types) for ALE adjust (last mile aware shaping) but is not reflected in access-loop-options send to RADIUS. Alc-Access-Loop-Encap from ANCP are currently not taken into account for ALE adjust.

26.3561.254

IWF-Session

The presence of this Attribute indicates that the IWF has been performed with respect to the subscriber's session. IWF is used to enable the carriage of PPP over ATM (PPPoA) traffic over PPPoE. The Access Node inserts the PPPoE Tag 0x0105, vendor-id 0x0de9 with sub-option code 0xFE, length field is set to 0x00 into the PPPoE Discovery packets when it is performing an IWF functionality. Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.6527.11

Alc-Subsc-ID-Str

A subscriber is a collection of subscriber-hosts (typically represented by IP-MAC combination) and is uniquely identified by a subscriber string. Subscriber-hosts queues/policers belonging to the same subscriber (residing on the same forwarding complex) can be treated under one aggregate scheduling QoS mechanism. Fallback to preconfigured values if attribute is omitted. Attribute values longer than the allowed string value are treated as setup failures. Can be used as key in CoA and Disconnect Message. Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no subscriber-id.

For DSM accounting sessions the Alc-Subsc-ID-Str reflects the UE MAC address.

26.6527.12

Alc-Subsc-Prof-Str

The subscriber profile is a template that contains settings (accounting, IGMP, HQoS, and so on) which are applicable to all hosts belonging to the same subscriber were [26.6527.12] Alc-Subsc-Prof-Str is the string that maps (configure subscriber-mgmt sub-ident-policy sub-ident-policy-name sub-profile-map) to such a subscriber profile (configure subscriber-mgmt sub-profile subscriber-profile-name). Strings longer than the allowed maximum are treated as setup failures. Unreferenced strings (string does not map to a policy) are silently ignored and preconfigured defaults are used. Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no sub-profile.

26.6527.13

Alc-SLA-Prof-Str

The SLA profile is a template that contains settings (filter, QoS, host-limit, and so on) which are applicable to individual hosts were [26.6527.13] Alc-SLA-Prof-Str is the string that maps (configure subscriber-mgmt sub-ident-policy sub-ident-policy-name sla-profile-map) to such an SLA profile (configure subscriber-mgmt sla-profile sla-profile-name). Strings longer than the allowed maximum are treated as setup failures. Unreferenced strings (a string that does not map to a policy) are silently ignored and preconfigured defaults are used. The attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no sla-profile.

26.6527.19

Alc-Acct-I-Inprof-Octets-64

Indicates how many queue | policer ingress forwarded bytes have been handled for this user over the course of this service being provided.

  • queue | policer stat-mode = *:

    Count in-profile bytes (IPv4 and IPv6)

    [26.6527.107] Alc-Acct-I-statmode VSA only included for policers

  • queue stat-mode = v4-v6:

    Count IPv4 bytes (in- and out-of-profile)

    [26.6527.107] Alc-Acct-I-statmode VSA included for queues with value v4-v6

  • policer stat-mode = v4-v6:

    This attribute is not used. For policers, ingress forwarded IPv4 bytes (in- and out-of-profile) are reported with attribute [26.6527.108] Alc-Acct-I-Hiprio-Octets_64.

The attribute is included when detailed queue/policer statistics VSAs are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes).

26.6527.20

Alc-Acct-I-Outprof-Octets-64

Indicates how many queue|policer ingress forwarded bytes have been handled for this user over the course of this service being provided.

  • queue|policer stat-mode = *:

    Count out-of-profile bytes (IPv4 and IPv6)

    [26.6527.107] Alc-Acct-I-statmode VSA only included for policers

  • queue stat-mode = v4-v6:

    Count IPv6 bytes (in- and out-of-profile)

    [26.6527.107] Alc-Acct-I-statmode VSA included for queues with value v4-v6

  • policer stat-mode = v4-v6:

    This attribute is not used. For policers, ingress forwarded IPv6 bytes (in- and out-of-profile) are reported with attribute [26.6527.109] Alc-Acct-I-Lowprio-Octets_64.

The attribute is included when detailed queue/policer statistics VSAs are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes).

26.6527.21

Alc-Acct-O-Inprof-Octets-64

Indicates how many queue|policer egress forwarded bytes have been handled for this user over the course of this service being provided.

  • queue|policer stat-mode = *

    Count in-profile bytes (IPv4 and IPv6)

    [26.6527.127] Alc-Acct-O-statmode VSA only included for policers

  • queue stat-mode = v4-v6

    Count IPv4 bytes (in- and out-of-profile)

    [26.6527.127] Alc-Acct-O-statmode VSA included for queues with value v4-v6

  • policer stat-mode = v4-v6

    This attribute is not used. For policers, egress forwarded IPv4 bytes (in- and out-of-profile) are reported with attribute [26.6527.110] Alc-Acct-O-Hiprio-Octets_64.

The attribute is included when detailed queue/policer statistics VSAs are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes).

26.6527.22

Alc-Acct-O-Outprof-Octets-64

Indicates how many queue|policer egress forwarded bytes have been handled for this user over the course of this service being provided.

  • queue|policer stat-mode = *

    Count out-of-profile bytes (IPv4 and IPv6)

    [26.6527.127] Alc-Acct-O-statmode VSA only included for policers

  • queue stat-mode = v4-v6

    Count IPv6 bytes (in- and out-of-profile)

    [26.6527.127] Alc-Acct-O-statmode VSA included for queues with value v4-v6

  • policer stat-mode = v4-v6

    This attribute is not used. For policers, egress forwarded IPv6 bytes (in- and out-of-profile) are reported with attribute [26.6527.111] Alc-Acct-O-Lowprio-Octets_64.

The attribute is included when detailed queue/policer statistics VSAs are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes).

26.6527.23

Alc-Acct-I-Inprof-Pkts-64

Indicates how many queue|policer ingress forwarded packets have been handled for this user over the course of this service being provided.

  • queue|policer stat-mode = *

    Count out-of-profile bytes (IPv4 and IPv6)

    [26.6527.107] Alc-Acct-I-statmode VSA only included for policers

  • queue stat-mode = v4-v6

    Count IPv4 packets (in- and out-of-profile)

    [26.6527.107] Alc-Acct-I-statmode VSA included for queues with value v4-v6

  • policer stat-mode = v4-v6

    This attribute is not used. For policers, ingress forwarded IPv4 packets (in- and out-of-profile) are reported with attribute [26.6527.112] Alc-Acct-I-Hiprio-Packets_64.

The attribute is included when detailed queue/policer statistics VSAs are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes).

26.6527.24

Alc-Acct-I-Outprof-Pkts-64

Indicates how many queue|policer ingress forwarded packets have been handled for this user over the course of this service being provided.

  • queue|policer stat-mode = *

    Count out-of-profile packets (IPv4 and IPv6)

    [26.6527.107] Alc-Acct-I-statmode VSA only included for policers

  • queue stat-mode = v4-v6

    Count IPv6 packets (in- and out-of-profile)

    [26.6527.107] Alc-Acct-I-statmode VSA included for queues with value v4-v6

  • policer stat-mode = v4-v6

    This attribute is not used. For policers, ingress forwarded IPv6 packets (in- and out-of-profile) are reported with attribute [26.6527.113] Alc-Acct-I-Lowprio-Packets_64.

The attribute is included when detailed queue/policer statistics VSAs are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes).

26.6527.25

Alc-Acct-O-Inprof-Pkts-64

Indicates how many queue|policer egress forwarded packets have been handled for this user over the course of this service being provided.

  • queue|policer stat-mode = *

    Count in-profile packets (IPv4 and IPv6)

    [26.6527.127] Alc-Acct-O-statmode VSA only included for policers

  • queue stat-mode = v4-v6

    Count IPv4 packets (in- and out-of-profile)

    [26.6527.127] Alc-Acct-O-statmode VSA included for queues with value v4-v6

  • policer stat-mode = v4-v6

    This attribute is not used. For policers, egress forwarded IPv4 packets (in- and out-of-profile) are reported with attribute [26.6527.114] Alc-Acct-O-Hiprio-Packets_64.

The attribute is included when detailed queue/policer statistics VSAs are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes).

26.6527.26

Alc-Acct-O-Outprof-Pkts-64

Indicates how many queue|policer egress forwarded packets have been handled for this user over the course of this service being provided.

  • queue|policer stat-mode = *

    Count out-of-profile packets (IPv4 and IPv6)

    [26.6527.127] Alc-Acct-O-statmode VSA only included for policers

  • queue stat-mode = v4-v6

    Count IPv6 packets (in- and out-of-profile)

    [26.6527.127] Alc-Acct-O-statmode VSA included for queues with value v4-v6

  • policer stat-mode = v4-v6

    This attribute is not used. For policers, egress forwarded IPv6 packets (in- and out-of-profile) are reported with attribute [26.6527.115] Alc-Acct-O-Lowprio-Packets_64.

The attribute is included when detailed queue/policer statistics VSAs are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes).

26.6527.27

Alc-Client-Hardware-Addr

The MAC address from a user that requests a service and included in CoA, Authentication or Accounting (configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute mac-address).

26.6527.36

Alc-DHCP-Vendor-Class-Id

Initiated by DHCP clients using option 60 [Class-id] and reflected in Accounting. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute dhcp-vendor-class-id).

26.6527.69

Alc-Acct-I-High-Octets-Drop_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters high-octets-discarded-count is enabled. Customized records are available for queues, not for policers.

Counts ingress dropped bytes:

  • no queue stat-mode

    Count high-priority bytes (IPv4 and IPv6)

    [26.6527.107] Alc-Acct-I-statmode VSA not included

  • queue stat-mode = v4-v6

    Count IPv4 bytes (high- and low-priority)

    [26.6527.107] Alc-Acct-I-statmode VSA included with value v4-v6

26.6527.70

Alc-Acct-I-Low-Octets-Drop_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters low-octets-discarded-count is enabled. Customized records are available for queues, not for policers.

Counts ingress dropped bytes:

  • no queue stat-mode

    Count low-priority bytes (IPv4 and IPv6)

    [26.6527.107] Alc-Acct-I-statmode VSA not included

  • queue stat-mode = v4-v6

    Count IPv6 bytes (high- and low-priority)

    [26.6527.107] Alc-Acct-I-statmode VSA included with value v4-v6

26.6527.71

Alc-Acct-I-High-Pack-Drop_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters high-packets-discarded-count is enabled. Customized records are available for queues, not for policers.

Counts ingress dropped packets:

  • no queue stat-mode

    Count high-priority packets (IPv4 and IPv6)

    [26.6527.107] Alc-Acct-I-statmode VSA not included

  • queue stat-mode = v4-v6

    Count IPv4 packets (high- and low-priority)

    [26.6527.107] Alc-Acct-I-statmode VSA included with value v4-v6

26.6527.72

Alc-Acct-I-Low-Pack-Drop_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters low-packets-discarded-count is enabled. Customized records are available for queues, not for policers.

Counts ingress dropped packets:

  • no queue stat-mode

    Count low-priority packets (IPv4 and IPv6)

    [26.6527.107] Alc-Acct-I-statmode VSA not included

  • queue stat-mode = v4-v6

    Count IPv6 packets (high- and low-priority)

    [26.6527.107] Alc-Acct-I-statmode VSA included with value v4-v6

26.6527.73

Alc-Acct-I-High-Octets-Offer_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters high-octets-offered-count is enabled. Customized records are available for queues, not for policers.

Counts ingress high priority offered bytes (IPv4 and IPv6); also when queue stat-mode = v4-v6.

26.6527.74

Alc-Acct-I-Low-Octets-Offer_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters low-octets-offered-count is enabled. Customized records are available for queues, not for policers.

Counts ingress low priority offered bytes (IPv4 and IPv6); also when queue stat-mode = v4-v6.

26.6527.75

Alc-Acct-I-High-Pack-Offer_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters high-packets-offered-count is enabled. Customized records are available for queues, not for policers.

Counts ingress high priority offered packets (IPv4 and IPv6); also when queue stat-mode = v4-v6.

26.6527.76

Alc-Acct-I-Low-Pack-Offer_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters low-packets-offered-count is enabled. Customized records are available for queues, not for policers.

Counts ingress low priority offered packets (IPv4 and IPv6); also when queue stat-mode = v4-v6.

26.6527.77

Alc-Acct-I-Unc-Octets-Offer_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters uncolored-octets-offered-count is enabled. Customized records are available for queues, not for policers.

Counts ingress uncolored offered bytes (IPv4 and IPv6); also when queue stat-mode = v4-v6.

26.6527.78

Alc-Acct-I-Unc-Pack-Offer_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id i-counters uncolored-packets-offered-count is enabled. Customized records are available for queues, not for policers.

Counts ingress uncolored offered packets (IPv4 and IPv6); also when queue stat-mode = v4-v6.

26.6527.81

Alc-Acct-O-Inprof-Pack-Drop_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id e-counters in-profile-packets-discarded-count is enabled. Customized records are available for queues, not for policers.

Counts egress dropped packets:

  • no queue stat-mode

    Count in-profile packets (IPv4 and IPv6)

    [26.6527.127] Alc-Acct-O-statmode VSA not included

  • queue stat-mode = v4-v6

    Count IPv4 packets (in- and out-of-profile)

    [26.6527.127] Alc-Acct-O-statmode VSA included with value v4-v6.

26.6527.82

Alc-Acct-O-Outprof-Pack-Drop_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id e-counters out-profile-packets-discarded-count is enabled. Customized records are available for queues, not for policers.

Counts egress dropped packets:

  • no queue stat-mode

    Count out-of-profile packets (IPv4 and IPv6)

    [26.6527.127] Alc-Acct-O-statmode VSA not included

  • queue stat-mode = v4-v6

    Count IPv6 packets (in- and out-of-profile)

    [26.6527.127] Alc-Acct-O-statmode VSA included with value v4-v6.

26.6527.83

Alc-Acct-O-Inprof-Octs-Drop_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id e-counters in-profile-octets-discarded-count is enabled. Customized records are available for queues, not for policers.

Counts egress dropped bytes:

  • no queue stat-mode

    Count in-profile bytes (IPv4 and IPv6)

    [26.6527.127] Alc-Acct-O-statmode VSA not included

  • queue stat-mode = v4-v6

    Count IPv4 bytes (in- and out-of-profile)

    [26.6527.127] Alc-Acct-O-statmode VSA included with value v4-v6.

26.6527.84

Alc-Acct-O-Outprof-Octs-Drop_64

A customized record and provides the flexibility to reduce the volume of data generated, network operators can define the record that needs to be collected. This attribute is generated when configure subscriber-mgmt radius-accounting-policy name custom-record queue queue-id e-counters out-profile-octets-discarded-count is enabled. Customized records are available for queues, not for policers.

Counts egress dropped bytes:

  • no queue stat-mode

    Count out-of-profile bytes (IPv4 and IPv6)

    [26.6527.127] Alc-Acct-O-statmode VSA not included

  • queue stat-mode = v4-v6

    Count IPv6 bytes (in- and out-of-profile)

    [26.6527.127] Alc-Acct-O-statmode VSA included with value v4-v6.

26.6527.96

Alc-Credit-Control-Quota

DSM only.

For Distributed Subscriber Management (DSM), this VSA signals any unconsumed quota at the time of the report. The VSA is only included if configured under the configure aaa isa-radius-policy name acct-include-attributes credit-control-quota context. An explicit 0 is signaled when all quotas are exhausted. If no quota was applied, the VSA is not present, even if configured.

26.6527.99

Alc-Ipv6-Address

The IPv6 address to be configured to the WAN side of the user (IPoE,PPPoE) using DHCPv6 (IA-NA). Maps to DHCPv6 option IA-NA[3] sub-option IA-Address[5] address. This attribute is an alternative to [97] Framed-IPv6-Prefix and [100] Framed-IPv6-Pool, which also assigns IPv6 addressing to the wan-side of a host using SLAAC or DHCPv6 IA-NA. Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no ipv6-address.

For Distributed Subscriber Management (DSM), if IA-NA is active for a UE, the attribute contains the address assigned to this UE. Inclusion of this attribute is enabled using configure aaa isa-radius-policy name acct-include-attributes ipv6-address.

26.6527.100

Alc-Serv-Id

DSM only. The attribute contains the service ID where the Layer 3 tunnel is terminated. The attribute is omitted in case of a Layer 2 tunnel or if the service ID is not known.

26.6527.102

Alc-ToServer-Dhcp-Options

DSM only. The attribute contains all dhcpv4 options received in the last DHCPv4 message. Each dhcpv4 option is stored in a separate attribute.

26.6527.107

Alc-Acct-I-statmode

Identifies what ingress counters the operator wants to maintain for the policer and defined by configure qos sap-ingress policy-id policer policer-id stat-mode stat-mode. The default stat-mode is minimal and the full list of stat-modes can be found in the Quality of Service Guide.

For both policers and queues, the ingress stat-mode can be configured to v4-v6 at the sla-profile CLI context.

For example:

configure subscriber-mgmt sla-profile sla-profile-name ingress qos policy-id queue queue-id stat-mode v4-v6

With ingress stat-mode v4-v6:

  • Ingress forwarded/dropped counters are reporting IPv4 counters in the in-profile attributes and IPv6 counters in the out-of-profile attributes.

  • The Alc-Acct-I-statmode VSA is included with value v4-v6 for both queues and, or policers.

26.6527.108

Alc-Acct-I-Hiprio-Octets_64

Policer-specific counter. Indicates how many policer ingress-forwarded-bytes have been handled for this user over the course of this service being provided.

  • stat-mode = *(specific stat-mode only)

    ingress forwarded high-priority bytes

  • stat-mode = v4-v6

    ingress forwarded IPv4 bytes (in- and out-of-profile)

The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.109

Alc-Acct-I-Lowprio-Octets_64

Policer-specific counter. Indicates how many policer ingress-forwarded-bytes have been handled for this user over the course of this service being provided.

  • stat-mode = *(specific stat-mode only)

    ingress forwarded low-priority bytes

  • stat-mode = v4-v6

    ingress forwarded IPv6 bytes (in- and out-of-profile)

The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.110

Alc-Acct-O-Hiprio-Octets_64

Policer-specific counter. Indicates how many policer egress-forwarded-bytes have been handled for this user over the course of this service being provided.

  • stat-mode = *(specific stat-mode only)

    egress forwarded high-priority bytes

  • stat-mode = v4-v6

    egress forwarded IPv4 bytes (in- and out-of-profile)

The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.111

Alc-Acct-O-Lowprio-Octets_64

Policer-specific counter. Indicates how many policer egress-forwarded-bytes have been handled for this user over the course of this service being provided.

  • stat-mode = *(specific stat-mode only)

    egress forwarded low-priority bytes

  • stat-mode = v4-v6

    egress forwarded IPv6 bytes (in- and out-of-profile)

The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.112

Alc-Acct-I-Hiprio-Packets_64

Policer-specific counter. Indicates how many policer ingress-forwarded-packets have been handled for this user over the course of this service being provided.

  • stat-mode = *(specific stat-mode only)

    ingress forwarded high-priority packets

  • stat-mode = v4-v6

    ingress forwarded IPv4 packets (in- and out-of-profile)

The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.113

Alc-Acct-I-Lowprio-Packets_64

Policer-specific counter. Indicates how many policer ingress-forwarded-packets have been handled for this user over the course of this service being provided.

  • stat-mode = *(specific stat-mode only)

    ingress forwarded low-priority packets

  • stat-mode = v4-v6

    ingress forwarded IPv6 packets (in- and out-of-profile)

The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.114

Alc-Acct-O-Hiprio-Packets_64

Policer-specific counter. Indicates how many policer egress forwarded-packets have been handled for this user over the course of this service being provided.

  • stat-mode = *(specific stat-mode only)

    egress forwarded high-priority packets

  • stat-mode = v4-v6

    egress forwarded IPv4 packets (in- and out-of-profile)

The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.115

Alc-Acct-O-Lowprio-Packets_64

Policer-specific counter. Indicates how many policer egress forwarded packets have been handled for this user over the course of this service being provided.

  • stat-mode = *(specific stat-mode only)

    egress forwarded low-priority packets

  • stat-mode = v4-v6

    egress forwarded IPv6 packets (in- and out-of-profile)

The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.116

Alc-Acct-I-All-Octets_64

Policer-specific counter. Indicates how many policer ingress-forwarded-bytes have been handled for this user over the course of this service being provided. The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.117

Alc-Acct-O-All-Octets_64

Policer-specific counter. Indicates how many policer egress-forwarded-bytes have been handled for this user over the course of this service being provided. The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.118

Alc-Acct-I-All-Packets_64

Policer-specific counter. Indicates how many policer ingress-forwarded-packets have been handled for this user over the course of this service being provided. The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.119

Alc-Acct-O-All-Packets_64

Policer-specific counter. Indicates how many policer egress-forwarded-packets have been handled for this user over the course of this service being provided. The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.121

Alc-Nat-Port-Range

This attribute is used to report allocated or released NAT resources for an L2-Aware NAT subscriber. The reported NAT resources include a public IPv4 address, a public port range, an outside routing instance and a NAT policy name.

This attribute is included in accounting by configuring the nat-port-range option under the configure subscriber-mgmt radius-accounting-policy name include-radius-attributes CLI hierarchy.

26.6527.127

Alc-Acct-O-statmode

Identifies what egress counters the operator wants to maintain for the policer and defined by configure qos sap-egress policy-id policer policer-id stat-mode stat-mode. The default stat-mode is minimal and the full list of stat-modes can be found in the Quality of Service Guide.

For both policers and queues, the egress stat-mode can be configured to IPv4-IPv6 at the sla-profile CLI context.

For example:

configure subscriber-mgmt sla-profile sla-profile-name egress qos policy-id queue queue-id stat-mode v4-v6

With egress stat-mode v4-v6:

  • Egress forwarded or dropped counters are reporting IPv4 counters in the in-profile attributes and IPv6 counters in the out-of-profile attributes.

  • The Alc-Acct-O-statmode VSA is included with value v4-v6 for both queues and, or policers.

26.6527.140

Alc-Nat-Outside-Serv-Id

DSM only. For a DSM UE, this attribute includes the service ID of the outside VRF where IPv4 traffic is forwarded after NAT.

26.6527.141

Alc-Nat-Outside-Ip-Addr

DSM only. For a DSM UE, this attribute contains the IPv4 address of the UE after NAT.

26.6527.146

Alc-Wlan-APN-Name

This VSA contains the Access Point Name string as signaled in incoming GTP-C messages for FWA sessions.

To include this attribute use the command configure subscriber-mgmt radius-accounting-policy name include-radius-attribute apn.

26.6527.147

Alc-MsIsdn

This VSA includes the MSISDN (telephone number) as signaled in incoming GTP-C messages for FWA sessions.

To include this attribute use the command configure subscriber-mgmt radius-accounting-policy name include-radius-attribute msisdn.

26.6527.148

Alc-RSSI

Received Signal Strength Indication. Used in conjunction with the radius-proxy track-accounting feature. When the RADIUS proxy receives this attribute in an accounting message, it is copied into the DHCP lease state and echoed by SR OS accounting.

26.6527.149

Alc-Num-Attached-UEs

Indicates the total number of UEs that are currently attached to the tunnel of the UE for which the accounting message is generated. In an accounting stop message this counter includes the UE for which the accounting stop is generated, even if the UE is being removed. Therefore the reported counter can only be zero for non-wlan-gw/vRGW UEs. Inclusion can be configured with the option wifi-num-attached-ues. For ESM in configure subscriber-mgmt radius-accounting-policy name include-radius-attribute, and for DSM in configure aaa isa-radius-policy name acct-include-attributes.

26.6527.163

Alc-Acct-Triggered-Reason

A reason attribute included in Acct-Interim messages to specify the reason for the interim update. Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no alc-acct-triggered-reason.

26.6527.175

Alc-DSL-Line-State

Status of the DSL line obtained using ANCP can be one of three value: SHOWTIME (the modem is ready to transfer data), IDLE (the line is idle) or SILENT (the line is silent). Attribute is included or excluded based on configure subscriber-mgmt radius-accounting-policy name include-radius-attribute access-loop-options.

26.6527.176

Alc-DSL-Type

Type of the DSL line (ADSL1, ADSL2, ADSL2PLUS, VDSL1, VDSL2, SDSL, other) obtained using ANCP.

Attribute is included or excluded based on configure subscriber-mgmt authentication-policy/radius-accounting-policy name include-radius-attribute access-loop-options.

26.6527.184

Alc-Wlan-Ue-Creation-Type

DSM only. Indicates if the UE is either an ESM host (IOM) or DSM host (ISA). Fixed to ISA in case of DSM.

26.6527.191

Alc-ToServer-Dhcp6-Options

DSM only. If IA-NA is active, the attribute contains the options sent by the client in the last DHCPv6 transaction. Inclusion of this attribute is enabled using configure aaa isa-radius-policy name acct-include-attributes dhcp6-options.

26.6527.194

Alc-IPv6-Acct-Input-Packets

Aggregate of all ingress forwarded IPv6 packet counters for policers and queues that have stat-mode v4-v6 enabled (example: configure subscriber-mgmt sla-profile sla-profile-name ingress qos policy-id queue | policer id stat-mode v4-v6).

Included when IPv6 aggregated accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute v6-aggregate-stats). There is no overflow attribute when counter wraps around 2^32.

26.6527.195

Alc-IPv6-Acct-Input-Octets

Aggregate of all ingress forwarded IPv6 octet counters for policers and queues that have stat-mode v4-v6 enabled (example: configure subscriber-mgmt sla-profile sla-profile-name ingress qos policy-id queue | policer id stat-mode v4-v6).

Included when IPv6 aggregated accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute v6-aggregate-stats).

[26.6527.196] Alc-IPv6-Acct-Input-Gigawords indicates how many times (if greater than zero) this counter has wrapped around 2^32.

26.6527.196

Alc-IPv6-Acct-Input-GigaWords

Indicates how many times (one or more) the [26.6527.195] Alc-IPv6-Acct-Input-Octets counter has wrapped around 2^32 in the course of delivering this service. The attribute is not sent when its value equals zero.

Included when IPv6 aggregated accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute v6-aggregate-stats).

26.6527.197

Alc-IPv6-Acct-Output-Packets

Aggregate of all egress forwarded IPv6 packet counters for policers and queues that have stat-mode v4-v6 enabled (example: configure subscriber-mgmt sla-profile sla-profile-name egress qos policy-id queue | policer id stat-mode v4-v6).

Included when IPv6 aggregated accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute v6-aggregate-stats). There is no overflow attribute when counter wraps around 2^32.

26.6527.198

Alc-IPv6-Acct-Output-Octets

Aggregate of all egress forwarded IPv6 octet counters for policers and queues that have stat-mode v4-v6 enabled (example: configure subscriber-mgmt sla-profile sla-profile-name egress qos policy-id queue | policer id stat-mode v4-v6).

Included when IPv6 aggregated accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute v6-aggregate-stats).

[26.6527.199] Alc-IPv6-Acct-Output-Gigawords indicates how many times (if greater than zero) this counter has wrapped around 2^32.

26.6527.199

Alc-IPv6-Acct-Output-Gigawords

Indicates how many times (one or more) the [26.6527.198] Alc-IPv6-Acct-Output-Octets counter has wrapped around 2^32 in the course of delivering this service. The attribute is not sent when its value equals zero.

Included when IPv6 aggregated accounting attributes are configured. (configure subscriber-mgmt radius-accounting-policy name include-radius-attribute v6-aggregate-stats).

26.6527.206

Alc-Wlan-SSID-VLAN

On a WLAN-GW group interface this attribute indicates the UE VLAN tag inside of the tunnel. This VLAN is usually used to differentiate between SSIDs. If no VLAN is present or the host is not active on a wlan-gw-group interface this attribute is not sent.

(configure subscriber-mgmt radius-accounting-policy name include- radius-attribute wifi-ssid-vlan).

26.6527.226

Alc-Error-Code

The [26.6527.226] Alc-Error-Code and [26.6527.227] Alc-Error-Message attributes specify the reason why a subscriber session has ended. Each numeric Alc-Error-Code corresponds with a human readable Alc-Error-Message string.

An overview of the Error Codes and their mapping to Termination Causes can be displayed with: tools dump aaa radius-acct-terminate-cause

Included with following CLI: configure subscriber-mgmt radius-accounting-policy name include-radius-attribute alc-error-code.

26.6527.227

Alc-Error-Message

The [26.6527.226] Alc-Error-Code and [26.6527.227] Alc-Error-Message attributes specify the reason why a subscriber session has ended. Each numeric Alc-Error-Code corresponds with a human readable Alc-Error-Message string.

An overview of the Error Codes and their mapping to Termination Causes can be displayed with: tools dump aaa radius-acct-terminate-cause

Included with following CLI: configure subscriber-mgmt radius-accounting-policy name include-radius-attribute alc-error-code.

26.6527.228

Alc-Trigger-Acct-Interim

This attribute, when received in a CoA message, triggers an accounting interim update message for accounting modes that have interim-updates enabled. The Alc-Trigger-Acct-Interim attribute with free formatted string value is echoed in the CoA triggered accounting interim update message. The [26.6527.163] Alc-Acct-Triggered- Reason attribute in the interim update is set to 18 (CoA-Triggered).

26.6527.230

Alc-Acct-O-Exprof- Octets_64

Policer-specific counter. Indicates how many policer egress-exceed- profile-forwarded-bytes have been handled for this user over the course of this service being provided. The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.231

Alc-Acct-O-Exprof- Packets_64

Policer-specific counter. Indicates how many policer egress-exceed- profile-forwarded-packets have been handled for this user over the course of this service being provided. The attribute is included in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes for specific policer stat-mode only.

26.6527.239

Alc-BRG-Num-Active-Sessions

This attribute applies to vRGW only. Indicates the total number of device sessions that are active (such as, DHCP completed) and linked to the related BRG instance. In accounting stop messages, this counter includes the session related to this accounting stop, even if the session is being removed. Inclusion for ESM can be configured with configure subscriber-mgmt radius-accounting-policy name include-radius-attribute brg-num-active-sessions.

26.6527.240

Alc-Nat-Port-Range-Freed

This attribute contains information about the released NAT resources after a NAT policy change triggered using CoA in L2-Aware NAT.

241.26.6527.9

Alc-Bridge-Id

This attribute applies to vRGW only. The attribute contains the bridge domain ID for the subscribers Home LAN Extension (HLE) service.

241.26.6527.10

Alc-Vxlan-VNI

This attribute applies to vRGW only. The attribute contains the VXLAN Network Identifier (VNI) used for egress VXLAN packets of the Home LAN Extension (HLE) service.

241.26.6527.14

Alc-RT

This attribute applies to vRGW only. The attribute contains the Route Target of the Home LAN Extension (HLE) BGP EVPN service.

241.26.6527.15

Alc-RD

This attribute applies to vRGW only. The attribute contains the Route Distinguisher of the Home LAN Extension (HLE) BGP EVPN service.

241.26.6527.19

Alc-Bonding-Id

This attribute indicates the connection is part of a bonding context. If the bonding-id is equal to the subscriber-id this indicates the bonding subscriber, else it is one of the access connections. Inclusion of this attribute can be configured using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute bonding-id.

241.26.6527.23

Alc-Bonding-Active-Connection

This attribute indicates which connections are active in a bonding subscriber. Inclusion of this attribute can be configured using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute bonding-active-connections.

241.26.6527.25

Alc-Steering-Profile

This attribute contains the name of the steering profile that is attached to the L2TP LAC session.

The attribute is included in Start, Interim-Update and Stop messages when a steering profile is attached and when enabled in configuration with configure subscriber-mgmt radius-accounting-policy name include-radius-attribute steering-profile.

241.26.6527.28

Alc-HLE-Device-Type

Indicate the type of Home LAN Extension host. Value is fixed to "Device in the home".

241.26.6527.36

Alc-Bonding-Load-Balance-Stats

This attribute indicates how many subscriber egress packets/octets have been sent toward each access connection because of load balancing. Note that the access connection can still drop packets as a result of its own QoS enforcement and therefore have a lower forwarded count.

Inclusion of this attribute is subject to configure subscriber-mgmt radius-accounting-policy name include-radius-attribute detailed-acct-attributes.

241.26.6527.47

Alc-SPI-Sharing-Id

Reports the SLA Profile Instance (SPI) sharing type and identifier that corresponds with the queue instance of this accounting session: per SAP (no identifier), per session (IPoE or PPP SPI sharing ID), or per group (group ID). Together with the SLA profile name, the SPI sharing identifier uniquely identifies the SLA Profile Instance (queue instance).

Inclusion of this attribute can be configured using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute spi-sharing-id.

241.26.6527.48

Alc-Firewall-Info

Provides the firewall policy and associated outside service used by the subscriber to which this VSA relates.

Inclusion of this attribute can be configured using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute firewall-info.

241.26.6527.56

Alc-Gtp-Bearer-Fteid

Applies to FWA sessions only. This attribute reflects the current F-TEID used by the GTP-U bearer.

To include this attribute use the command configure subscriber-mgmt radius-accounting-policy name include-radius-attribute bearer-fteid.

241.26.6527.59

Alc-Xconnect-Tunnel-Home-Ipv6

Provides the x-connect IPv6 gateway address configured on the home WLAN-GW (H-GW) used by the visited WLAN-GW (V-GW) to setup a x-connect tunnel to the H-GW.

To include this attribute add the option xconnect-tunnel-home-address in configure subscriber-mgmt radius-accounting-policy name include-radius-attribute for ESM, and in configure aaa isa-radius-policy name acct-include-attributes for DSM.

241.26.6527.63

Alc-Millisecond-Event-Timestamp

DSM only. Record the time that this event occurred on the NAS, in milliseconds since January 1, 1970 00:00 UTC.

To include this attribute use the command configure aaa isa-radius-policy name acct-include-attributes millisecond-event-timestamp.

241.26.6527.64

Alc-GTP-Change-Detail

Applies to FWA sessions only.

For GTP S11 hosts, this attribute reflects which changes occurred for the session. Multiple instances of this attribute may be included to indicate multiple changes.

241.26.6527.86

Alc-ISA-Event-Timestamp

This attribute reflects the time of an L2 aware NAT event that occurred in ISA or ESA, such as allocation or de-allocation of extended port bock for an L2aware NAT subscriber. It records the time that this event occurred in seconds since January 1, 1970 00:00 UTC.

See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Multicast Routing Protocols Guide for details on integrated L2aware NAT RADIUS logging and BNG accounting.

26.10415.1

3GPP-IMSI

Applies to FWA sessions only.

This attribute reflects the IMSI of the session. To include this attribute use the command configure subscriber-mgmt radius-accounting-policy name include-radius-attribute imsi.

26.10415.20

3GPP-IMEISV

This VSA includes the International Mobile Equipment Identity and Software Version as signaled in incoming GTP-C messages.

Inclusion of this attribute can be configured using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute imei.

26.10415.22

3GPP-User-Location-Info

Applies to FWA sessions only.

This attribute reflects the latest User Location Info value received using GTP. To include this attribute use the command configure subscriber-mgmt radius-accounting-policy name include-radius-attribute uli.

26.25053.2

Ruckus-Sta-RSSI

Received Signal Strength Indication. Used in conjunction with the radius-proxy track-accounting feature. When the radius-proxy receives this attribute in an accounting message, it is copied into the DHCP lease state and echoed by the SR OS accounting.

Table 4. Enhanced Subscriber Management accounting (limits)
Attribute ID Attribute name Type Limits SR OS format

1

User-Name

string

253 chars

The format depends on authentication method and configuration

For example:

User-Name user1@domain1.com

4

NAS-IP-Address

ipaddr

4 bytes

# ip-address

For example:

NAS-IP-Address = 192.0.2.1

5

NAS-Port

integer

4 bytes

nas-port <binary-spec>

<binary-spec>=<bit-specification><binary-spec>

<bit-specification> = 0 | 1 | <bit-origin> <bit-origin> = *<number-of-bits><origin> <number-of-bits> = [1 to 32]

<origin> =

s: slot number

m: MDA number

p: port number, lag-id, pw-id or pxc-id

o: outer VLAN ID

i: inner VLAN ID

c: pxc-subport (a=0, b=1)

Only the lower bits of the specified origin are included if the number of bits assigned for that origin is not enough to hold its maximum value. For example, when specifying 10 bits for an outer VLAN ID (*10o), then VLAN 3000 (binary 1011 1011 1000) would be reported as 952 (binary 11 1011 1000)

For example:

configured nas-port *12o*10i*3s*2m*5p for SAP 2/2/4:221.7 corresponds to the binary value 000011011101 0000000111 010 10 00100 resulting in NAS-Port = 231742788

6

Service-Type

integer

2 (mandatory value)

PPPoE and PPPoL2TP hosts only

For example:

Service-Type = Framed-User

7

Framed-Protocol

integer

1 (fixed value)

PPPoE and PPPoL2TP hosts only

For example:

Service-Type = PPP

8

Framed-IP-Address

ipaddr

4 bytes

For example:

# ip-address 10.11.12.13 Framed-IP-Address 0a0b0c0d

9

Framed-IP-Netmask

ipaddr

4 bytes

For example:

Framed-IP-Netmask = 255.255.255.255 #PPPoE residential Framed-IP-Netmask = 255.255.255.0 #PPPoE Business with IPCP option 144 support Framed-IP-Netmask = 255.255.255.0 # IPoE

22

Framed-Route

string

max. 16 Framed-Routes

<ip-prefix>/<prefix-length> <space> 0.0.0.0 <space> <metric> [<space> tag <space> <tag-value>] <space> pref <space> <preference-value>”

The gateway address is always reported as "0.0.0.0", representing the host ip.

For example:

Framed-Route = "192.168.1.0/24 0.0.0.0 0 pref 0" corresponds with a managed route with default metrics (metric=0, no tag, preference=0)

Framed-Route = "192.168.1.0/24 0.0.0.0 10 tag 3 pref 100" corresponds with a managed route with metric=10, tag=3 and preference=100

25

Class

octets

Up to 6 attributes. Max. value length for each attribute is 253 chars

For example:

Class = My Class

30

Called-Station-Id

string

64 chars

LNS: L2TP Called Number AVP21 from LAC

For example:

Called-Station-Id = 4441212 WLAN Gateway / vRGW: AP-MAC and SSID, separated by a colon

For example:

Called-Station-Id = 00:00:01:00:00:01:my_ssid

31

Calling-Station-Id

string

64 chars

# llid | mac | remote-id | sap-id | sap-string (64 char. string configured at sap-level)

For example:

include-radius-attribute calling-station-id sap-id Calling-Station-Id = 1/1/2:1.1

32

NAS-Identifier

string

64 chars

For example:

NAS-Identifier = PE1-Antwerp

40

Acct-Status-Type

integer

4

1=Start, 2=Stop, 3=Interim Update, 7=Accounting-On, 8=Accounting-Off, 9=Tunnel-Start, 10=Tunnel-Stop, 11=Tunnel-Reject, 12=Tunnel-Link-Start, 13=Tunnel-Link-Stop, 14=Tunnel-Link-Reject, 15=Failed

41

Acct-Delay-Time

integer

4294967295 seconds

For example:

# initial accounting start:

Acct-Delay-Time = 0

# no ack and retry after 5 seconds:

Acct-Delay-Time = 5

42

Acct-Input-Octets

integer

32 bit counter

For example:

Acct-Input-Octets = 5000

43

Acct-Output-Octets

integer

32 bit counter

For example:

Acct-Output-Octets = 2000

44

Acct-Session-Id

string

22 bytes (number format) max. 253 bytes (description format)

29 bytes (DSM format)

Internal generated 22 byte string (number format): Acct-Session-Id = 241AFF0000003250B5F750

DSM: Acct-Session-Id = 01-02-00-00-00-19-00-00-00-01

45

Acct-Authentic

integer

4

# value = 2 (local) for local user database authentication 1=Radius, 2=Local

For example:

AUTHENTIC [45] 4 Radius(1)

46

Acct-Session-Time

integer

4 bytes 4294967295 seconds

(DSM)

42949672 seconds (ESM)

The attribute value wraps after approximately 497 days (ESM):

For example:

Acct-Session-Time = 870

47

Acct-Input-Packets

integer

32 bit counter 4294967295 packets

For example:

Acct-Input-Packets = 15200

48

Acct-Output-Packets

integer

32 bit counter 4294967295 packets

For example:

Acct-Output-Packets = 153537

49

Acct-Terminate-Cause

integer

4 bytes

Supported causes: 1=User-Request, 2=Lost-Carrier, 3=Lost-Service, 4=Idle-Timeout, 5=Session-Timeout, 6=Admin-Reset, 8=Port-Error, 10=NAS-Request, 15=Service-Unavailable See also table Acct Terminate Cause for complete overview

For example:

Acct-Terminate-Cause = User-Request

50

Acct-Multi-Session-Id

string

22 bytes (number format)

253 bytes (description format)

29 bytes (DSM format)

Internal generated 22 byte string (number format): Acct-Multi-Session-Id = 241AFF0000003250B5F750

DSM: Acct-Multi-Session-Id = 01-02-00-00-00-19-00-00-5b-d9

52

Acct-Input-Gigawords

integer

32 bit counter

For example:

Acct-Input-Gigawords = 1

53

Acct-Output-Gigawords

integer

32 bit counter

For example:

Acct-Output-Gigawords = 3

55

Event-Timestamp

date

4 bytes

For example:

# Jul 6 2012 17:28:23 CEST is reported as 4FF70417 Event-Timestamp = 4FF70417

61

NAS-Port-Type

integer

4 bytes Values [0 to 255]

Values as defined in RFC 2865 and RFC 4603 For LNS, the value is set to virtual (5)

For example:

NAS-Port-Type = PPPoEoQinQ (34)

64

Tunnel-Type

integer

3 (mandatory value)

3 = L2TP

For example:

Tunnel-Type = 3

65

Tunnel-Medium-Type

integer

1 (mandatory value)

1 = IP or IPv4

For example:

Tunnel-Medium-Type = 1

66

Tunnel-Client-Endpoint

string

Max. 19 bytes (untagged)

<dotted-decimal IP address used on LAC as L2TP src-ip>

For example:

Tunnel-Client-Endpoint = "203.0.113.1"

67

Tunnel-Server-Endpoint

string

Max. 19 bytes (untagged)

<dotted-decimal IP address used on LAC as L2TP dst-ip>

For example:

Tunnel-Server-Endpoint = "198.51.100.1"

68

Acct-Tunnel-Connection

string

253 chars

By default, the Call Serial Number is inserted.

Configured format:

(if the resulting string is longer than 253 characters, it is truncated)

acct-tunnel-connection-fmt ascii-spec

<ascii-spec> : <char-specification> <ascii-spec>

<char-specification> : <ascii-char> | <char-origin>

<ascii-char> : a printable ASCII character

<char-origin> : %<origin>

<origin> : n | s | S | t | T | c | C

n - Call Serial Number

s | S - Local (s) or Remote (S) Session Id

t | T - Local (t) or Remote (T) Tunnel Id

c | C - Local (c) or Remote (C) Connection Id

87

NAS-Port-Id

string

253 bytes

See [87] NAS-Port-Id attribute details for a detailed description of the attribute format.

For example:

NAS-Port-Id = "1/1/4:501.1001"

NAS-Port-Id = ‟LNS rtr-2#lip-203.0.113.1#rip- 198.51.100.1#ltid-11381#rtid-1285#lsid- 30067#rsid-19151#347”

NAS-Port-Id = ‟GRE rtr-11#lip-192.0.2.1#rip-172.16.1.1”

90

Tunnel-Client-Auth-ID

string

64 chars

For example:

Tunnel-Client-Auth-Id:0 = "LAC-1"

91

Tunnel-Server-Auth-ID

string

64 chars

For example:

Tunnel-Server-Auth-Id:0 = "LNS-1"

95

NAS-IPv6-Address

ipv6addr

16 bytes

# ipv6-address

For example:

NAS-IPv6-Address = 2001:db8::1

96

Framed-Interface-Id

ifid

8 bytes

For example:

Framed-Interface-Id 02:00:00:ff:fe:00:00:01

97

Framed-IPv6-Prefix

ipv6prefix

max. 16 bytes for prefix + 1 byte for length

PPPoE SLAAC wan-host <ipv6-prefix/prefix-length> with prefix-length 64

For example:

Framed-IPv6-Prefix 2001:db8:FFF3:1::/64

99

Framed-IPv6-Route

string

max. 17 Framed-IPv6-Route attributes

(16 managed routes and 1 DHCPv6 IA-PD host as managed route)

<ip-prefix>/<prefix-length> <space> :: <space> <metric> [<space> tag <space> <tag-value>] <space> pref <space> <preference-value> [<space>type pd-host]

The gateway address is always reported as "::", representing the wan host ip.

For DHCPv6 IA-PD hosts modeled as a managed route, the key word "type pd-host" is appended to the Framed-IPv6-Route attribute.

For example:

Framed-IPv6-Route = "2001:db8:1::/56 :: 0 pref 0" corresponds with a managed route with default metrics (metric=0, no tag, preference=0)

Framed-IPv6-Route = "2001:db8:1::/56 :: 10 tag 3 pref 100" corresponds with a managed route with metric=10, tag=3 and preference=100

Framed-IPv6-Route = "2001:db8:d2:10::/56 :: 0 pref 0 type pd-host" corresponds with a PD host modeled as managed route

123

Delegated-IPv6-Prefix

ipv6prefix

max. 16 bytes for prefix + 1 byte for length

<ipv6-prefix/prefix-length> with prefix-length [48 to 64]

For example:

Delegated-IPv6-Prefix 2001:DB8:173A:100::/56

26.10415.1

3GPP-IMSI

string

1 to 15 digits

3GPP vendor specific attribute as defined in 3GPP TS 29.061.

For example:

3GPP-IMSI = 001001123456789

26.3561.1

Agent-Circuit-Id

string

247 chars

format see also RFC4679 #Ethernet/DSL <Access-Node-Identifier><eth slot/port[:vlan-id]>

For example:

ethernet dslam1 slot 2 port 1 vlan 100 Agent-Circuit-Id = dslam1 eth 2/1:100

26.3561.2

Agent-Remote-Id

string

247 chars

format see also RFC4679

For example:

Agent-Remote-Id = MyRemoteId

26.3561.129

Actual-Data-Rate-Upstream

integer

4294967295

For example:

Actual-Data-Rate-Upstream = 1000000

26.3561.130

Actual-Data-Rate-Downstream

integer

4294967295

For example:

Actual-Data-Rate-Downstream = 5000000

26.3561.131

Minimum-Data-Rate-Upstream

integer

4294967295

For example:

Minimum-Data-Rate-Upstream = 1000

26.3561.132

Minimum-Data-Rate-Downstream

integer

4294967295

For example:

Minimum-Data-Rate-Downstream = 1000

26.3561.133

Attainable-Data-Rate-Upstream

integer

4294967295

For example:

Attainable-Data-Rate-Downstream = 1000

26.3561.134

Attainable-Data-Rate-Downstream

integer

4294967295

For example:

Minimum-Data-Rate-Upstream = 1000

26.3561.135

Maximum-Data-Rate-Upstream

integer

4294967295

For example:

Maximum-Data-Rate-Upstream = 1000

26.3561.136

Maximum-Data-Rate-Downstream

integer

4294967295

For example:

Maximum-Data-Rate-Downstream = 1000

26.3561.137

Minimum-Data-Rate-Upstream-Low-Power

integer

4294967295

For example:

Minimum-Data-Rate-Upstream-Low-Power = 1000

26.3561.138

Minimum-Data-Rate-Downstream-Low-Power

integer

4294967295

For example:

Minimum-Data-Rate-Downstream-Low-Power = 1000

26.3561.139

Maximum-Interleaving-Delay-Upstream

integer

4294967295

For example:

Maximum-Interleaving-Delay-Upstream = 10

26.3561.140

Actual-Interleaving-Delay-Upstream

integer

4294967295

For example:

Actual-Interleaving-Delay-Upstream = 10

26.3561.141

Maximum-Interleaving-Delay-Downstream

integer

4294967295

For example:

Maximum-Interleaving-Delay-Downstream = 10

26.3561.142

Actual-Interleaving-Delay-Downstream

integer

4294967295

For example:

Actual-Interleaving-Delay-Downstream = 10

26.3561.144

Access-Loop-Encapsulation

octets

3 bytes

<Data Link><Encaps-1><Encaps-2> <Data Link>: AAL5(0), Ethernet(1) <Encaps 1>: NotAvailable(0), Untagged Ethernet(1), Single-Tagged Ethernet(2) <Encaps 2>: Not Available(0), PPPoA LLC(1), PPPoA Null(2), IPoA LLC(3), IPoA Null(4), Ethernet over AAL5 LLC w FCS(5), Ethernet over AAL5 LLC without FCS(6), Ethernet over AAL5 Null w FCS(7), Ethernet over AAL5 Null without FCS(8)

For example:

Ethernet, Single-Tagged Ethernet, Not Available Access-Loop-Encapsulation = 0x010200

26.3561.254

IWF-Session

octets

len 0

For example:

IWF-Session

26.6527.11

Alc-Subsc-ID-Str

string

64 chars

For example:

Alc-Subsc-ID-Str = MySubscriberId

26.6527.12

Alc-Subsc-Prof-Str

string

32 chars

For example:

Alc-Subsc-Prof-Str = MySubProfile

26.6527.13

Alc-SLA-Prof-Str

string

32 chars

For example:

Alc-SLA-Prof-Str = MySlaProfile

26.6527.19

Alc-Acct-I-Inprof-Octets-64

octets

10 bytes/ attribute with max 31 attributes

<Q/P-selection 1 Byte><Queue-id|Policer-id 1 Byte><8 Byte value> where Q/P-selection : 00 = Queue counters, 80= Policer counters where Queue-id|Policer-id range <1 to 32>

For example:

# 500 bytes in profile traffic for ingress queue 2

Alc-Acct-I-Inprof-Octets-64 = 0x000200000000000001f4

# 1000 bytes in profile traffic for ingress policer 3

Alc-Acct-I-Inprof-Octets-64 = 0x800300000000000003e8

26.6527.20

Alc-Acct-I-Outprof-Octets-64

octets

10 bytes/ attribute with max 31 attributes

<Q/P-selection 1 Byte><Queue-id|Policer-id 1 Byte><8 Byte value> where Q/P-selection : 00 = Queue counters, 80= Policer counters where Queue-id|Policer-id range <1 to 32>

For example:

# 500 bytes out of profile traffic for ingress queue 2 Alc-Acct-I-Outprof-Octets-64 = 0x000200000000000001f4 # 1000 bytes out of profile traffic for ingress policer 3 Alc-Acct-I-Outprof-Octets-64 = 0x800300000000000003e8

26.6527.21

Alc-Acct-O-Inprof-Octets-64

octets

10 bytes/ attribute with max 8 attributes

<Q/P-selection 1 Byte><Queue-id|Policer-id 1 Byte><8 Byte value> where Q/P-selection : 00 = Queue counters, 80= Policer counters where Queue-id range <1 to 8> or Policer-id range <1 to 63>

For example:

# 500 bytes in profile traffic for egress queue 2

Alc-Acct-O-Inprof-Octets-64 = 0x000200000000000001f4

# 1000 bytes in profile traffic for egress policer 3

Alc-Acct-O-Inprof-Octets-64 = 0x800300000000000003e8

26.6527.22

Alc-Acct-O-Outprof-Octets-64

octets

10 bytes/ attribute with max 8 attributes

<Q/P-selection 1 Byte><Queue-id|Policer-id 1 Byte><8 Byte value> where Q/P-selection : 00 = Queue counters, 80= Policer counters where Queue-id range <1 to 8> or Policer-id range <1 to 63>

For example:

# 500 bytes out of profile traffic for egress queue 2

Alc-Acct-O-Outprof-Octets-64 = 0x000200000000000001f4

# 1000 bytes out of profile traffic for egress policer 3

Alc-Acct-O-Outprof-Octets-64 = 0x800300000000000003e8

26.6527.23

Alc-Acct-I-Inprof-Pkts-64

octets

10 bytes/ attribute with max 31 attributes

<Q/P-selection 1 Byte><Queue-id|Policer-id 1 Byte><8 Byte value> where Q/P-selection : 00 = Queue counters, 80= Policer counters where Queue-id|Policer-id range <1 to 32>

For example:

# 500 packets in profile traffic for ingress queue 2

Alc-Acct-I-Inprof-Pkts-64 = 0x000200000000000001f4

# 1000 packets in profile traffic for ingress policer 3

Alc-Acct-I-Inprof-Pkts-64 = 0x800300000000000003e8

26.6527.24

Alc-Acct-I-Outprof-Pkts-64

octets

10 bytes/ attribute with max 31 attributes

<Q/P-selection 1 Byte><Queue-id|Policer-id 1 Byte><8 Byte value> where Q/P-selection : 00 = Queue counters, 80= Policer counters where Queue-id|Policer-id range <1 to 32>

For example:

# 500 packets out profile traffic for ingress queue 2

Alc-Acct-I-Outprof-Pkts-64 = 0x000200000000000001f4

# 1000 packets out profile traffic for ingress policer 3

Alc-Acct-I-Outprof-Pkts-64 = 0x800300000000000003e8

26.6527.25

Alc-Acct-O-Inprof-Pkts-64

octets

10 bytes/ attribute with max 8 attributes

<Q/P-selection 1 Byte><Queue-id|Policer-id 1 Byte><8 Byte value> where Q/P-selection : 00 = Queue counters, 80= Policer counters where Queue-id range <1 to 8> or Policer-id range <1 to 63>

For example:

# 500 packets in profile traffic for egress queue 2

Alc-Acct-O-Inprof-Pkts-64 = 0x000200000000000001f4

# 1000 packets in profile traffic for egress policer 3

Alc-Acct-O-Inprof-Pkts-64 = 0x800300000000000003e8

26.6527.26

Alc-Acct-O-Outprof-Pkts-64

octets

10 bytes/ attribute with max 8 attributes

<Q/P-selection 1 Byte><Queue-id|Policer-id 1 Byte><8 Byte value> where Q/P-selection : 00 = Queue counters, 80= Policer counters where Queue-id range <1 to 8> or Policer-id range <1 to 63>

For example:

# 500 packets out profile traffic for egress queue 2

Alc-Acct-O-Outprof-Pkts-64 = 0x000200000000000001f4

# 1000 packets out profile traffic for egress policer 3

Alc-Acct-O-Outprof-Pkts-64 = 0x800300000000000003e8

26.6527.27

Alc-Client-Hardware-Addr

string

6 bytes

For example:

Alc-Client-Hardware-Addr = 00:00:00:00:00:01

26.6527.36

Alc-DHCP-Vendor-Class-Id

string

247 chars

For example:

Alc-DHCP-Vendor-Class-Id = My-DHCP-VendorClassId

26.6527.69

Alc-Acct-I-High-Octets-Drop_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 32>

For example:

INPUT_HIGH_OCTETS_DROP_64 [69] 10 0x00010000000000000000

26.6527.70

Alc-Acct-I-Low-Octets-Drop_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 32>

For example:

INPUT_LOW_OCTETS_DROP_64 [70] 10 0x00010000000000000000

26.6527.71

Alc-Acct-I-High-Pack-Drop_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 32>

For example:

INPUT_HIGH_PACK_DROP_64 [71] 10 0x00010000000000000000

26.6527.72

Alc-Acct-I-Low-Pack-Drop_64

octets

10 bytes

<Queue-id 2Bytes><8 Bytes value> where Queue-id range <1 to 32>

For example:

INPUT_LOW_PACK_DROP_64 [72] 10 0x00010000000000000000

26.6527.73

Alc-Acct-I-High-Octets-Offer_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 32>

For example:

INPUT_HIGH_OCTETS_OFFER_64 [73] 10 0x00010000000000000000

26.6527.74

Alc-Acct-I-Low-Octets-Offer_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 32>

For example:

INPUT_LOW_OCTETS_OFFER_64 [74] 10 0x00010000000000000000

26.6527.75

Alc-Acct-I-High-Pack-Offer_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 32>

For example:

INPUT_HIGH_PACK_OFFER_64 [75] 10 0x00010000000000000000

26.6527.76

Alc-Acct-I-Low-Pack-Offer_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 32>

For example:

INPUT_LOW_PACK_OFFER_64 [76] 10 0x00010000000000000000

26.6527.77

Alc-Acct-I-Unc-Octets-Offer_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 32>

For example:

INPUT_UNC_OCTETS_OFFER_64 [77] 10 0x00010000000000000000

26.6527.78

Alc-Acct-I-Unc-Pack-Offer_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 32>

For example:

INPUT_UNC_PACK_OFFER_64 [78] 10 0x00010000000000000000

26.6527.81

Alc-Acct-O-Inprof-Pack-Drop_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 8>

For example:

OUTPUT_INPROF_PACK_DROP_64 [81] 10 0x00010000000000000000

26.6527.82

Alc-Acct-O-Outprof-Pack-Drop_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 8>

For example:

OUTPUT_OUTPROF_PACK_DROP_64 [82] 10 0x00010000000000000000

26.6527.83

Alc-Acct-O-Inprof-Octs-Drop_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 8>

For example:

OUTPUT_INPROF_OCTS_DROP_64 [83] 10 0x00010000000000000000

26.6527.84

Alc-Acct-O-Outprof-Octs-Drop_64

octets

10 bytes

<Queue-id 2Bytes><8 Byte value> where Queue-id range <1 to 8>

For example:

OUTPUT_OUTPROF_OCTS_DROP_64 [84] 10 0x00010000000000000000

26.6527.96

Alc-Credit-Control-Quota

string

2 attributes

DSM only.

<volume-value> B|0|<category-name>

  • volume-value is the remaining volume in bytes.
  • category-name can be hard or soft.

For example, soft quota exhausted and 10MB hard quota remaining:

Alc-Credit-Control-Quota = 10000000B|0|hard

Alc-Credit-Control-Quota = 0|0|soft

26.6527.99

Alc-Ipv6-Address

ipv6addr

16 bytes

For example:

Alc-Ipv6-Address 2001:db8:FFF5::1

26.6527.100

Alc-Serv-Id

integer

2147483647 ID

DSM only.

For example:

Alc-Serv-Id = 100

26.6527.102

Alc-ToServer-Dhcp-Options

octets

multiple attributes

247 bytes / attribute

DSM only.

For example:

DHCPv4 Discover with three options:

Class-identifier-option (60) = DHCP-VendorClassId,

Agent-Circuit-Id (82-1) = circuit10

Agent-Remote-Id (82-2) = remote10

Alc-ToServer-Dhcp-Options = 350101

Alc-ToServer-Dhcp-Options = 3c12444843502d56656e646f72436c6173734964

Alc-ToServer-Dhcp-Options = 52150109636972637569743130020872656d6f74653130

26.6527.107

Alc-Acct-I-statmode

string

253 chars

<Q/P-selection 1 Byte><Queue-id | Policer-id 1 Byte><space><statmode-string>

Q/P-selection: 0x00 = Queue statmode, 0x80 = Policer statmode

Queue-id | Policer-id range <1 to 63>

stat-mode : configured stat-mode

For example:

# configure ingress policer 5 stat-mode offered-priority-no-cir INPUT_STATMODE [107] 30 0x8005 offered-priority-no-cir

26.6527.108

Alc-Acct-I-Hiprio-Octets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# ingress policer 5 INPUT_HIPRIO_OCTETS_64 [108] 10 0x80050000000000000000

26.6527.109

Alc-Acct-I-Lowprio-Octets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# ingress policer 5 INPUT_LOWPRIO_OCTETS_64 [109] 10 0x80050000000000000000

26.6527.110

Alc-Acct-O-Hiprio-Octets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# ingress policer 5 OUTPUT_HIPRIO_OCTETS_64 [110] 10 0x80050000000000000000

26.6527.111

Alc-Acct-O-Lowprio-Octets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# ingress policer 5 OUTPUT_LOWPRIO_OCTETS_64 [111] 10 0x80050000000000000000

26.6527.112

Alc-Acct-I-Hiprio-Packets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# ingress policer 5 INPUT_HIPRIO_PACKETS_64 [112] 10 0x80050000000000000000

26.6527.113

Alc-Acct-I-Lowprio-Packets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# ingress policer 5 INPUT_LOWPRIO_PACKETS_64 [113] 10 0x80050000000000000000

26.6527.114

Alc-Acct-O-Hiprio-Packets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# egress policer 1 OUTPUT_HIPRIO_PACKETS_64 [114] 10 0x80010000000000000000

26.6527.115

Alc-Acct-O-Lowprio-Packets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# egress policer 1 OUTPUT_LOWPRIO_PACKETS_64 [115] 10 0x80010000000000000000

26.6527.116

Alc-Acct-I-All-Octets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# egress policer 1 INPUT_ALL_OCTETS_64 [116] 10 0x80010000000000000000

26.6527.117

Alc-Acct-O-All-Octets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# egress policer 1 OUTPUT_ALL_OCTETS_64 [117] 10 0x80010000000000000000

26.6527.118

Alc-Acct-I-All-Packets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# ingress policer 3 INPUT_ALL_PACKETS_64 [118] 10 0x80030000000000000000

26.6527.119

Alc-Acct-O-All-Packets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1 to 63>

For example:

# egress policer 1 OUTPUT_ALL_PACKETS_64 [119] 10 0x80010000000000000000

26.6527.121

Alc-Nat-Port-Range

string

no limits

ESM: <public-ip> <space> <port- range> <space> router <space> <outside-routing-instance> <space> <nat-policy-name>

DSM: <public-ip> <space> <port- range>[,<port-range>]* <space> router <space> <outside-routing-instance>

For example:

ESM: a host with public pool address 198.51.100.248; port-range [37674..37723] in Base with nat-policy-name = nat-pol-1

Alc-Nat-Port-Range = "198.51.100.248 37674-37723 router base nat-pol-1"

DSM: a UE with public address 192.0.2.12 with two port-ranges 12500-12999 and 32000-32499 in router 3001

Alc-Nat-Port-Range = "192.0.2.12 12500-12999,32000-32499 router 3001"

26.6527.127

Alc-Acct-O-statmode

string

253 chars

<Q/P-selection 1 Byte><Queue-id|Policer-id 1 Byte><space><statmode-string>

Q/P-selection: 0x00 = Queue statmode, 0x80 = Policer statmode

Queue-id range <1 to 8> or Policer-id range <1 to 63>

stat-mode: configured stat-mode

For example:

# configure egress policer 5 stat-mode offered-limited-capped-cir

OUTPUT_STATMODE [127] 33 0x8001 offered-limited-capped-cir

26.6527.140

Alc-Nat-Outside-Serv-Id

integer

2147483647 ID

DSM only.

For example:

Alc-Nat-Outside-Serv-Id = 300

26.6527.141

Alc-Nat-Outside-Ip-Addr

ipaddr

4 bytes

DSM only.

For example:

Alc-Nat-Outside-Ip-Addr = 203.0.113.113

26.6527.146

Alc-Wlan-APN-Name

string

247 chars

The APN is directly reflected as present in the incoming GTP-C message.

For example:

Alc-Wlan-APN-Name = demo.mnc001.mcc001.gprs

26.6527.147

Alc-MsIsdn

string

9 to 15 digits

Textual representation of the MSISDN in decimal format.

For example:

Alc-MsIsdn = 13109976224

26.6527.148

Alc-RSSI

integer

32 bit value

For example:

Alc-RSSI = 30

26.6527.149

Alc-Num-Attached-UEs

integer

32 bit value

A number indicating how many UEs are active.

For example:

Alc-Num-Attached-Ues = 1

26.6527.163

Alc-Acct-Triggered-Reason

integer

4 bytes

See Accounting triggered reason for a description of Accounting Triggered Reason values.

For example:

ACCT TRIGGERED INTERIM REASON [163] 4 regular(1)

26.6527.175

Alc-DSL-Line-State

integer

4 bytes

1=showtime, 2-idle, 3=silent

For example:

Alc-DSL-Line-State = SHOWTIME

26.6527.176

Alc-DSL-Type

integer

4 bytes

0=other, 1=ADSL1, 2=ADSL2, 3=ADSL2PLUS, 4=VDSL1, 5=VDSL2, 6=SDSL

For example:

Alc-DSL-Type = VDSL2

26.6527.184

Alc-Wlan-Ue-Creation-Type

integer

values [0 to 1]

DSM only. Value in case of DSM is fixed to isa (1)

For example:

Alc-Wlan-Ue-Creation-Type = isa

26.6527.191

Alc-ToServer-Dhcp6-Options

octets

Multiple attributes

247 bytes / attribute

(truncated if DHCPv6 option is longer)

DSM only. One DHCPv6 option per RADIUS attribute. In case of DHCPv6 relay or LDRA this reflects the options as they appear in the outer packet.

For example: an LDRA message with following options:

  • Interface-Id = 00:00:00:00:00:05;1;0

  • Remote Identifier = alu00:02:00:00:00:19

  • Relay-Message containing:

    • Client Identifier

    • Server Identifier

    • IA_NA (2001:db8:2::1)

    • Elapsed Time

    • Option Request Options

Results in three attributes:

Alc-ToServer-Dhcp6-Options= 0012001530303a30303a30303a30303a30303a30353b313b6f

Alc-ToServer-Dhcp6-Options= 002500180000197f616c7530303a30323a30303a30303a30303a3139

Alc-ToServer-Dhcp6-Options= 0009006003e115820001000a000300010002000000190002000a000300010812ff0000000003002c000000010000070800000b400005001820010db800020000000000000000000100000e1000000e100000000000080002000000060006000100020003

26.6527.194

Alc-IPv6-Acct-Input-Packets

integer

4 bytes

For example:

Alc-IPv6-Acct-Input-Packets = 14511

26.6527.195

Alc-IPv6-Acct-Input-Octets

integer

4 bytes

For example:

Alc-IPv6-Acct-Input-Octets = 2932215

26.6527.196

Alc-IPv6-Acct-Input-GigaWords

integer

4 bytes

For example:

Alc-IPv6-Acct-Input-GigaWords = 1

26.6527.197

Alc-IPv6-Acct-Output-Packets

integer

4 bytes

For example:

Alc-IPv6-Acct-Output-Packets = 54122

26.6527.198

Alc-IPv6-Acct-Output-Octets

integer

4 bytes

For example:

Alc-IPv6-Acct-Output-Octets = 8521943

26.6527.199

Alc-IPv6-Acct-Output-Gigawords

integer

4 bytes

For example:

Alc-IPv6-Acct-Output-Gigawords = 2

26.6527.206

Alc-Wlan-SSID-VLAN

string

247 chars

Textual representation of the VLAN. If no vlan-tag was present, this attribute is not included.

For example:

Alc-Wlan-SSID-VLAN = ‟2173”

26.6527.226

Alc-Error-Code

integer

4 bytes

For example:

Alc-Error-Code = 202

26.6527.227

Alc-Error-Message

string

247 chars

For example:

Alc-Error-Message = "Service cleared by operator"

26.6527.228

Alc-Trigger-Acct-Interim

string

247 chars

Free formatted string that is echoed in the triggered interim update message.

For example:

Alc-Trigger-Acct-Interim = "CoA - Filter update"

26.6527.230

Alc-Acct-O-Exprof-Octets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1..63>

For example: # egress policer 1

OUTPUT EXCEEDPROF OCTETS 64 [230] 10 0x80010000000000000000

26.6527.231

Alc-Acct-O-Exprof-Packets_64

octets

10 bytes

<0x80><policer-id><8 byte value> where policer-id <1..63>

For example:

# egress policer 1

OUTPUT EXCEEDPROF PACKETS 64 [231] 10 0x80010000000000000000

26.6527.239

Alc-BRG-Num-Active-Sessions

integer

32 bits value

A counter indicating how many sessions are connected.

For example:

Alc-Brg-Num-Active-Sessions = 3

26.6527.240

Alc-Nat-Port-Range-Freed

string

No limits

<public-ip> <space> <port- range> <space> <outside-routing-instance> <space> <nat-policy-name>

For example:

a public pool with address 198.51.100.248; port-range [37674..37723] in Base, nat-policy name nat-pol-1

Alc-Nat-Port-Range = "198.51.100.248 37674-37723 router base nat-pol-1"

241.26.6527.9

Alc-Bridge-Id

integer

1 - 4294967294

For example:

Alc-Bridge-Id = 200

241.26.6527.10

Alc-Vxlan-VNI

integer

1 - 16777214

For example:

Alc-Vxlan-VNI =250

241.26.6527.14

Alc-RT

string

SR OS supported format

  • target:<ip-addr:comm-val>

  • target:<2byte-asnumber:ext-comm-val>

  • target:<4byte-asnumber:comm-val>

For example:

Alc-RT = "target:64496:200"

241.26.6527.15

Alc-RD

string

SR OS supported format

One of the following formats:

  • <ip-addr:comm-val>

  • <2byte-asnumber:ext-comm-val>

  • <4byte-asnumber:comm-val>

For example:

Alc-RD = ‟64496:510”

241.26.6527.19

Alc-Bonding-Id

string

1..32 chars

ID used to identify the bonding context.

For example:

Alc-Bonding-Id=home1

241.26.6527.23

Alc-Bonding-Active-Connection

integer

[1..2]

ID used to identify the connection.

Included for each connection active.

For example: e

Connection 1 and 2 active

Alc-Active-Connection+=1

Alc-Active-Connection+=2

241.26.6527.25

Alc-Steering-Profile

string

32 chars

Steering profile name.

For example:

Alc-Steering-Profile = ‟steering-profile-1”

241.26.6527.28

Alc-HLE-Device-Type

integer

1

Value: 1 = Device in the home

For example:

Alc-HLE-Device-Type = 1

241.26.6527.36

Alc-Bonding-Load-Balance-Stats

octets

10 bytes per attribute

First byte indicates which data is reported:

0x01 = egress packets

0x02 = egress octets

Second byte indicates the connection ID.

Remaining 8 bytes indicate the value as a 64-bit integer.

For example:

100 packets totaling 40000B over connection 1, 50 packets totaling 30000B over connection 2

Alc-Bonding-Load-Balance-Stats += 0x01010000000000000064

Alc-Bonding-Load-Balance-Stats += 0x01020000000000000032

Alc-Bonding-Load-Balance-Stats += 0x02010000000000009c40

Alc-Bonding-Load-Balance-Stats += 0x02020000000000007530

241.26.6527.47

Alc-SPI-Sharing-Id

string

247 chars

<SPI-sharing-type>[:<SPI sharing id>]

SPI sharing per SAP:

"SAP”

SPI sharing per session:

"PPP session:<PPP SPI sharing id>"

"IPoE session:<IPoE SPI sharing id>"

SPI sharing per group:

"group:<group id>"

For example:

Alc-SPI-Sharing-Id = "PsiPP session:17"

Alc-SPI-Sharing-Id = "group:100"

241.26.6527.48

Alc-Firewall-Info

string

247 chars

<service> <space> <firewall-policy-name>

For example:

a firewall-policy fw-pol-1 active in the base router

Alc-Firewall-Info = "router base fw-pol-1"

For example: a firewall-policy fw-pppoe active in Epipe 20:

Alc-Firewall-Info = "pppoe-service-id 20 fw-pppoe"

241.26.6527.56

Alc-Gtp-Bearer-Fteid

string

247 chars

rtr-<virtual router id>

#bid-<bearer-id>

#lip-<local ip address>

#rip-<peer ip address>

#lteid-<local teid>

#rteid-<remote teid>

For example:

Alc-Bearer-Fteid = "rtr-12#bid-5#lip-192.0.2.1#rip-192.0.2.2#lteid-4293918976#rteid-3"

241.26.6527.59

Alc-Xconnect-Tunnel-Home-Ipv6

ipv6addr

16 bytes

IPv6 address

For example:

Alc-Xconnect-Tunnel-Home-Ipv6 = 2001:db8::1

241.26.6527.63

Alc-Millisecond-Event-Timestamp

integer64

8 bytes

For example Jul 6 2012 17:28:23.123 UTC is reported as:

Alc-Millisecond-Event-Timestamp = 1341595703123

241.26.6527.64

Alc-GTP-Change-Detail

integer

[1..5]

Details GTP connection changes. Values:

1 - s1-release: the GTP-u connection was released by the eNodeB because it was idle. Not to be confused with a GTP-C session release which is indicated using Alc-Acct-Triggered-Reason GTP-Session-Released.

2 - attach: the GTP-u connection was re-attached after idling. Not to be confused with a GTP-C session re-attach which is indicated using Alc-Acct-Triggered-Reason GTP-Session-Attached.

3 - uli-change: a new ULI was received.

4 - teidu-change: the GTP-U peer TEID changed, for example, because of mobility or re-attach.

5 - teidc-change: the GTP-C peer TEID changed, usually indicating an MME change.

Example, GTP-U re-attach and GTP-U peer TEID changed:

Alc-GTP-Change-Detail = 2

Alc-GTP-Change-Detail = 4

241.26.6527.86

Alc-ISA-Event-Timestamp

integer

4 bytes

Number of seconds since January 1, 1970 00:00 UTC

For example:

Alc-ISA-Event-Timestamp = 1624459738

26.10415.20

3GPP-IMEISV

string

14 to 16 digits

3GPP vendor specific attribute as defined in TS 29.061

26.10415.22

3GPP-User-Location-Info

octets

247 bytes

3GPP vendor specific attribute as defined in TS 29.061

26.25053.2

Ruckus-Sta-RSSI

integer

32 bits value

For example: Ruckus-Sta-RSSI = 28

Table 5. Enhanced Subscriber Management accounting (applicability)
Attribute ID Attribute Name Acct Start Acct Stop Acct Interim-Update Acct On 1 Acct Off 1 Acct Reporting Level

1

User-Name

0-1

0-1

0-1

0

0

H->S->Q

4

NAS-IP-Address

0-1

0-1

0-1

0-1

0-1

HSQ

5

NAS-Port

0-1

0-1

0-1

0

0

H->S->Q

6

Service-Type

1

1

1

0

0

H->S->Q

7

Framed-Protocol

1

1

1

0

0

H->S->Q

8

Framed-IP-Address

0-1

0-1

0-1

0

0

H->S->Q

9

Framed-IP-Netmask

0-1

0-1

0-1

0

0

H->S->Q

22

Framed-Route

0+

0+

0+

0

0

H->S->Q

25

Class

0+

0+

0+

0

0

H->S->Q

30

Called-Station-Id

0-1

0-1

0-1

0

0

H->S->Q

31

Calling-Station-Id

0-1

0-1

0-1

0

0

H->S->Q

32

NAS-Identifier

0-1

0-1

0-1

1

1

HSQ

40

Acct-Status-Type

1

1

1

1

1

HSQ

41

Acct-Delay-Time

0-1

0-1

0-1

0-1

0-1

HSQ

42

Acct-Input-Octets

0

0-1

0-1

0

0

HSQ

43

Acct-Output-Octets

0

0-1

0-1

0

0

HSQ

44

Acct-Session-Id

1

1

1

1

1

HSQ

45

Acct-Authentic

0-1

0-1

0-1

1

1

H->S->Q

46

Acct-Session-Time

0-1

0-1

0-1

0

0

HSQ

47

Acct-Input-Packets

0

0-1

0-1

0

0

HSQ

48

Acct-Output-Packets

0

0-1

0-1

0

0

HSQ

49

Acct-Terminate-Cause

0

1

0

0

1

HSQ

50

Acct-Multi-Session-Id

0-1

0-1

0-1

0

0

HSQ

52

Acct-Input-Gigawords

0

0-1

0-1

0

0

HSQ

53

Acct-Output-Gigawords

0

0-1

0-1

0

0

HSQ

55

Event-Timestamp

1

1

1

1

1

HSQ

61

NAS-Port-Type

0-1

0-1

0-1

0

0

H->S->Q

64

Tunnel-Type

0-12

0-1

0-1

0

0

HSQ

65

Tunnel-Medium-Type

0-12

0-1

0-1

0

0

HSQ

66

Tunnel-Client-Endpoint

0-12

0-1

0-1

0

0

HSQ

67

Tunnel-Server-Endpoint

0-12

0-1

0-1

0

0

HSQ

68

Acct-Tunnel-Connection

0-12

0-1

0-1

0

0

HSQ

87

NAS-Port-Id

0-1

0-1

0-1

0

0

H->S->Q

90

Tunnel-Client-Auth-ID

0-12

0-1

0-1

0

0

HSQ

91

Tunnel-Server-Auth-ID

0-12

0-1

0-1

0

0

HSQ

95

NAS-IPv6-Address

0-1

0-1

0-1

0-1

0-1

HSQ

96

Framed-Interface-Id

0-1

0-1

0-1

0

0

H->S->Q

97

Framed-IPv6-Prefix

0-1

0-1

0-1

0

0

H->S->Q

99

Framed-IPv6-Route

0+

0+

0+

0

0

H->S->Q

123

Delegated-IPv6-Prefix

0-1

0-1

0-1

0

0

H->S->Q

26.3561.1

Agent-Circuit-Id

0-1

0-1

0-1

0

0

H->S->Q

26.3561.2

Agent-Remote-Id

0-1

0-1

0-1

0

0

H->S->Q

26.3561.129

Actual-Data-Rate-Upstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.130

Actual-Data-Rate-Downstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.131

Minimum-Data-Rate-Upstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.132

Minimum-Data-Rate-Downstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.133

Attainable-Data-Rate-Upstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.134

Attainable-Data-Rate-Downstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.135

Maximum-Data-Rate-Upstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.136

Maximum-Data-Rate-Downstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.137

Minimum-Data-Rate-Upstream-Low-Power

0-1

0-1

0-1

0

0

H->S->Q

26.3561.138

Minimum-Data-Rate-Downstream-Low-Power

0-1

0-1

0-1

0

0

H->S->Q

26.3561.139

Maximum-Interleaving-Delay-Upstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.140

Actual-Interleaving-Delay-Upstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.141

Maximum-Interleaving-Delay-Downstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.142

Actual-Interleaving-Delay-Downstream

0-1

0-1

0-1

0

0

H->S->Q

26.3561.144

Access-Loop-Encapsulation

0-1

0-1

0-1

0

0

H->S->Q

26.3561.254

IWF-Session

0-1

0-1

0-1

0

0

H->S->Q

26.6527.11

Alc-Subsc-ID-Str

0-1

0-1

0-1

0

0

HSQ

26.6527.12

Alc-Subsc-Prof-Str

0-1

0-1

0-1

0

0

HSQ

26.6527.13

Alc-SLA-Prof-Str

0-1

0-1

0-1

0

0

HSQ

26.6527.19

Alc-Acct-I-Inprof-Octets-64

0

0+

0+

0

0

HSQ

26.6527.20

Alc-Acct-I-Outprof-Octets-64

0

0+

0+

0

0

HSQ

26.6527.21

Alc-Acct-O-Inprof-Octets-64

0

0+

0+

0

0

HSQ

26.6527.22

Alc-Acct-O-Outprof-Octets-64

0

0+

0+

0

0

HSQ

26.6527.23

Alc-Acct-I-Inprof-Pkts-64

0

0+

0+

0

0

HSQ

26.6527.24

Alc-Acct-I-Outprof-Pkts-64

0

0+

0+

0

0

HSQ

26.6527.25

Alc-Acct-O-Inprof-Pkts-64

0

0+

0+

0

0

HSQ

26.6527.26

Alc-Acct-O-Outprof-Pkts-64

0

0+

0+

0

0

HSQ

26.6527.27

Alc-Client-Hardware-Addr

0-1

0-1

0-1

0

0

H->S->Q

26.6527.36

Alc-DHCP-Vendor-Class-Id

0-1

0-1

0-1

0

0

H->S->Q

26.6527.69

Alc-Acct-I-High-Octets-Drop_64

0

0+

0+

0

0

HSQ

26.6527.70

Alc-Acct-I-Low-Octets-Drop_64

0

0+

0+

0

0

HSQ

26.6527.71

Alc-Acct-I-High-Pack-Drop_64

0

0+

0+

0

0

HSQ

26.6527.72

Alc-Acct-I-Low-Pack-Drop_64

0

0+

0+

0

0

HSQ

26.6527.73

Alc-Acct-I-High-Octets-Offer_64

0

0+

0+

0

0

HSQ

26.6527.74

Alc-Acct-I-Low-Octets-Offer_64

0

0+

0+

0

0

HSQ

26.6527.75

Alc-Acct-I-High-Pack-Offer_64

0

0+

0+

0

0

HSQ

26.6527.76

Alc-Acct-I-Low-Pack-Offer_64

0

0+

0+

0

0

HSQ

26.6527.77

Alc-Acct-I-Unc-Octets-Offer_64

0

0+

0+

0

0

HSQ

26.6527.78

Alc-Acct-I-Unc-Pack-Offer_64

0

0+

0+

0

0

HSQ

26.6527.81

Alc-Acct-O-Inprof-Pack-Drop_64

0

0+

0+

0

0

HSQ

26.6527.82

Alc-Acct-O-Outprof-Pack-Drop_64

0

0+

0+

0

0

HSQ

26.6527.83

Alc-Acct-O-Inprof-Octs-Drop_64

0

0+

0+

0

0

HSQ

26.6527.84

Alc-Acct-O-Outprof-Octs-Drop_64

0

0+

0+

0

0

HSQ

26.6527.99

Alc-Ipv6-Address

0-1

0-1

0-1

0

0

H->S->Q

26.6527.107

Alc-Acct-I-statmode

0

0+

0+

0

0

HSQ

26.6527.108

Alc-Acct-I-Hiprio-Octets_64

0

0+

0+

0

0

HSQ

26.6527.109

Alc-Acct-I-Lowprio-Octets_64

0

0+

0+

0

0

HSQ

26.6527.110

Alc-Acct-O-Hiprio-Octets_64

0

0+

0+

0

0

HSQ

26.6527.111

Alc-Acct-O-Lowprio-Octets_64

0

0+

0+

0

0

HSQ

26.6527.112

Alc-Acct-I-Hiprio-Packets_64

0

0+

0+

0

0

HSQ

26.6527.113

Alc-Acct-I-Lowprio-Packets_64

0

0+

0+

0

0

HSQ

26.6527.114

Alc-Acct-O-Hiprio-Packets_64

0

0+

0+

0

0

HSQ

26.6527.115

Alc-Acct-O-Lowprio-Packets_64

0

0+

0+

0

0

HSQ

26.6527.116

Alc-Acct-I-All-Octets_64

0

0+

0+

0

0

HSQ

26.6527.117

Alc-Acct-O-All-Octets_64

0

0+

0+

0

0

HSQ

26.6527.118

Alc-Acct-I-All-Packets_64

0

0+

0+

0

0

HSQ

26.6527.119

Alc-Acct-O-All-Packets_64

0

0+

0+

0

0

HSQ

26.6527.121

Alc-Nat-Port-Range

0+

0+

0+

0

0

HSQ

26.6527.127

Alc-Acct-O-statmode

0

0+

0+

0

0

HSQ

26.6527.146

Alc-Wlan-APN-Name

0-1

0-1

0-1

0

0

SQ

26.6527.147

Alc-MsIsdn

0-1

0-1

0-1

0

0

SQ

26.6527.148

Alc-RSSI

0-1

0-1

0-1

0

0

HSQ

26.6527.149

Alc-Num-Attached-UEs

0-1

0-1

0-1

0

0

H->S->Q

26.6527.163

Alc-Acct-Triggered-Reason

0

0

0-1

0

0

HSQ

26.6527.175

Alc-DSL-Line-State

0-1

0-1

0-1

0

0

H->S->Q

26.6527.176

Alc-DSL-Type

0-1

0-1

0-1

0

0

H->S->Q

26.6527.194

Alc-IPv6-Acct-Input-Packets

0

0-1

0-1

0

0

HSQ

26.6527.195

Alc-IPv6-Acct-Input-Octets

0

0-1

0-1

0

0

HSQ

26.6527.196

Alc-IPv6-Acct-Input-GigaWords

0

0-1

0-1

0

0

HSQ

26.6527.197

Alc-IPv6-Acct-Output-Packets

0

0-1

0-1

0

0

HSQ

26.6527.198

Alc-IPv6-Acct-Output-Octets

0

0-1

0-1

0

0

HSQ

26.6527.199

Alc-IPv6-Acct-Output-Gigawords

0

0-1

0-1

0

0

HSQ

26.6527.206

Alc-Wlan-SSID-VLAN

0-1

0-1

0-1

0

0

H->S->Q

26.6527.226

Alc-Error-Code

0

0-1

0

0

0

HSQ

26.6527.227

Alc-Error-Message

0

0-1

0

0

0

HSQ

26.6527.228

Alc-Trigger-Acct-Interim

0

0

0-1

0

0

HSQ

26.6527.230

Alc-Acct-O-Exprof-Octets_64

0

0+

0+

0

0

HSQ

26.6527.231

Alc-Acct-O-Exprof-Packets_64

0

0+

0+

0

0

HSQ

26.6527.239

Alc-BRG-Num-Active-Sessions

0-1

0-1

0-1

0

0

H->S->Q

26.6527.240

Alc-Nat-Port-Range-Freed

0

0+

0+

0

0

HSQ

241.26.6527.9

Alc-Bridge-Id

0-1

0-1

0-1

0

0

H->S->Q

241.26.6527.10

Alc-Vxlan-VNI

0-1

0-1

0-1

0

0

H->S->Q

241.26.6527.14

Alc-RT

0-1

0-1

0-1

0

0

H->S->Q

241.26.6527.15

Alc-RD

0-1

0-1

0-1

0

0

H->S->Q

241.26.6527.19

Alc-Bonding-Id

0-1

0-1

0-1

0

0

H->S->Q

241.26.6527.23

Alc-Bonding-Active-Connection

0+

0

0+

0

0

H->S->Q

241.26.6527.25

Alc-Steering-Profile

0-1

0-1

0-1

0

0

HS

241.26.6527.28

Alc-HLE-Device-Type

0-1

0-1

0-1

0

0

H->S->Q

241.26.6527.36

Alc-Bonding-Load-Balance-Stats

0

0+

0+

0

0

H->S->Q

241.26.6527.47

Alc-SPI-Sharing-Id

0-1

0-1

0-1

0

0

HSQ

241.26.6527.48

Alc-Firewall-Info

0-1

0-1

0-1

0

0

HSQ

241.26.6527.56

Alc-Gtp-Bearer-Fteid

0-1

0-1

0-1

0

0

H->S->Q

241.26.6527.59

Alc-Xconnect-Tunnel-Home-Ipv6

0-1

0-1

0-1

0

0

H->S->Q

241.26.6527.64

Alc-GTP-Change-Detail

0

0

0+

0

0

HSQ

241.26.6527.86

Alc-ISA-Event-Timestamp

0

0-1

0-1

0

0

HSQ

26.10415.1

3GPP-IMSI

0-1

0-1

0-1

0

0

H>S>Q

26.10415.20

3GPP-IMEISV

0-1

0-1

0-1

0

0

SQ

26.10415.22

3GPP-User-Location-Info

0-1

0-1

0-1

0

0

H->S->Q

26.25053.2

Ruckus.Sta-RSSI

0-1

0-1

0-1

0

0

HSQ

DSM accounting

In Distributed Subscriber Management (DSM), a single accounting session per UE is started. A unique Accounting-Session-ID per UE is generated. An Acct-Multi-Session-Id is also generated but currently not used to link any accounting sessions.

Acct-Status-Type and Acct-Session-Id are always included by default. The presence of all other attributes is dictated by configuration (config>aaa>isa-radius-policy name acct-include-attributes). Unless otherwise stated in a note, the attribute description and limits are the same as for Enhanced Subscriber Management (ESM) Accounting (Enhanced Subscriber Management accounting (description) and Enhanced Subscriber Management accounting (limits)), Distributed Subscriber Management accounting (applicability) provides an overview of the applicability of the attributes in DSM accounting messages.

Accounting On and Accounting Off messages are generated when a server is enabled or disabled in an isa-radius-policy (config>aaa>isa-radius-policy name servers id>[no] shutdown). An accounting-On is also generated every 5 minutes for a RADIUS server that is unresponsive.

Table 6. Distributed Subscriber Management accounting (applicability)
Attribute ID Attribute name Acct start Acct stop Acct interim-update Acct on (*) Acct off (*)

1

User-Name

0-1

0-1

0-1

0

0

5

NAS-Port

0-1

0-1

0-1

1

1

8

Framed-IP-Address

0-1

0-1

0-1

0

0

9

Framed-IP-Netmask

0-1

0-1

0-1

0

0

25

Class

0+

0+

0+

0

0

30

Called-Station-Id

0-1

0-1

0-1

0-1

0-1

31

Calling-Station-Id

0-1

0-1

0-1

0

0

32

NAS-Identifier

0-1

0-1

0-1

0-1

0-1

40

Acct-Status-Type

1

1

1

1

1

41

Acct-Delay-Time

0-1

0-1

0-1

0

0

42

Acct-Input-Octets

0-1

0-1

0-1

0

0

43

Acct-Output-Octets

0-1

0-1

0-1

0

0

44

Acct-Session-Id

1

1

1

1

1

46

Acct-Session-Time

0-1

0-1

0-1

0-1

0-1

47

Acct-Input-Packets

0-1

0-1

0-1

0

0

48

Acct-Output-Packets

0-1

0-1

0-1

0

0

49

Acct-Terminate-Cause

0

0-1

0

0-1

0-1

50

Acct-Multi-Session-Id

0-1

0-1

0-1

0

0

52

Acct-Input-Gigawords

0-1

0-1

0-1

0

0

53

Acct-Output-Gigawords

0-1

0-1

0-1

0

0

55

Event-Timestamp

0-1

0-1

0-1

0-1

0-1

61

NAS-Port-Type

0-1

0-1

0-1

0

0

87

NAS-Port-Id

0-1

0-1

0-1

0

0

95

NAS-IPv6-Address

0-1

0-1

0-1

0-1

0-1

97

Framed-IPv6-Prefix

0-1

0-1

0-1

0

0

26.3561.1

Agent-Circuit-Id

0-1

0-1

0-1

0

0

26.3561.2

Agent-Remote-Id

0-1

0-1

0-1

0

0

26.6527.11

Alc-Subsc-ID-Str

0-1

0-1

0-1

0

0

26.6527.19

Alc-Acct-I-Inprof-Octets-64 3

0

0-1

0-1

0

0

26.6527.21

Alc-Acct-O-Inprof-Octets-643

0

0-1

0-1

0

0

26.6527.23

Alc-Acct-I-Inprof-Pkts-643

0

0-1

0-1

0

0

26.6527.25

Alc-Acct-O-Inprof-Pkts-643

0

0-1

0-1

0

0

26.6527.27

Alc-Client-Hardware-Addr

0-1

0-1

0-1

0

0

26.6527.36

Alc-DHCP-Vendor-Class-Id

0-1

0-1

0-1

0

0

26.6527.96

Alc-Credit-Control-Quota

0-1

0-1

0-1

0

0

26.6527.99

Alc-Ipv6-Address

0-1

0-1

0-1

0

0

26.6527.100

Alc-Serv-Id

0-1

0-1

0-1

0

0

26.6527.102

Alc-ToServer-Dhcp-Options

0+

0+

0+

0

0

26.6527.121

Alc-Nat-Port-Range

0+

0+

0+

0

0

26.6527.140

Alc-Nat-Outside-Serv-Id

0-1

0-1

0-1

0

0

26.6527.141

Alc-Nat-Outside-Ip-Addr

0-1

0-1

0-1

0

0

26.6527.148

Alc-RSSI

0-1

0-1

0-1

0

0

26.6527.163

Alc-Acct-Triggered-Reason

0

0

0-1

0

0

26.6527.184

Alc-Wlan-Ue-Creation-Type

0-1

0-1

0-1

0

0

26.6527.191

Alc-ToServer-Dhcp6-Options

0-1

0-1

0-1

0

0

26.6527.206

Alc-Wlan-SSID-VLAN

0-1

0-1

0-1

0

0

241.26.6527.59

Alc-Xconnect-Tunnel-Home-Ipv6

0-1

0-1

0-1

0

0

241.26.6527.63

Alc-Millisecond-Event-Timestamp

0-1

0-1

0-1

0

0

Subscriber service accounting

This section specifies the attributes for RADIUS accounting on subscriber service instances. The attributes included in the subscriber service accounting messages are identical to the attributes that are included in the associated parent subscriber session accounting (Host accounting mode for IPoE host and Session accounting mode for PPPoE and IPoE sessions). Volume counters are always reported in standard attributes. Differences for attribute content and additional attributes are detailed in Subscriber service accounting (description).

Table 7. Subscriber service accounting (description)
Attribute ID Attribute name Description

42

Acct-Input-Octets

octets received for this subscriber service instance. Only included if stats-type is set to volume and time.

43

Acct-Output-Octets

octets send for this subscriber service instance. Only included if stats-type is set to volume and time.

44

Acct-Session-Id

Unique generated hexadecimal number that represents the accounting session for this Subscriber Service instance.

47

Acct-Input-Packets

packets received for this subscriber service instance. Only included if stats-type is set to volume and time.

48

Acct-Output-Packets

packets send for this subscriber service instance. Only included if stats-type is set to volume and time.

50

Acct-Multi-Session-Id

Accounting session ID of the parent PPPoE/IPoE session (session acct-session-id) or IPoE host (host acct-session-id). The format (variable length description or fixed 22B hexadecimal number) is identical to the parent PPPoE/IPoE session or IPoE host and determined by session-id-format in the radius-accounting- policy (configure subscriber-mgmt radius-accounting-policy name session-id-format {number | description}).

52

Acct-Input-Gigawords

indicates how many times (one or more) the [42] Acct-Input-Octets counter has wrapped around 2^32 in the course of delivering this service. Only included if its value is different from zero and stats-type is set to volume and time.

53

Acct-Output-Gigawords

indicates how many times (one or more) the [42] Acct-Input-Octets counter has wrapped around 2^32 in the course of delivering this service. Only included if its value is different from zero and stats-type is set to volume and time.

26.6527.151

Alc-Sub-Serv-Activate

Activate a subscriber service. The attribute typically contains parameters as input for the Python script that populates the subscriber service data structure (sub_svc). The attribute is ignored if not used in Python. The parameters can cross an attribute boundary. The concatenation of all Alc-Sub-Serv-Activate attributes with the same tag in a single message is typically used as a unique subscriber service instance identifier (key). In subscriber service RADIUS accounting messages, the attribute is sent untagged and contains the subscriber service data structure sub_svc.name value used at service activation. Multiple attributes may be present if the total length does not fit a single attribute.

Table 8. Subscriber service accounting (limits)
Attribute ID Attribute name Type Limits SR OS format

42

Acct-Input-Octets

integer

4 bytes

For example:

Acct-Input-Octets = 5000

43

Acct-Output-Octets

integer

4 bytes

For example:

Acct-Output-Octets = 2000

44

Acct-Session-Id

string

22 bytes

For example:

# Acct-Session-Id = 24ADFF0000000950C5F138

Acct-Session-Id 0x32313238343633353932313032353132313133343039

47

Acct-Input-Packets

integer

4 bytes

4294967295 packets

For example:

Acct-Input-Packets = 15200

48

Acct-Output-Packets

integer

4 bytes

4294967295 packets

For example:

Acct-Output-Packets = 153537

50

Acct-Multi-Session-Id

string

22 bytes (number format)

max. 253 bytes (description format)

For example:

Acct-Multi-Session-Id = 24ADFF0000000750C8EB26

52

Acct-Input-Gigawords

integer

4 bytes

For example:

Acct-Input-Gigawords = 7

53

Acct-Output-Gigawords

integer

4 bytes

For example:

Acct-Output-Gigawords = 3

26.6527.151

Alc-Sub-Serv-Activate

string

multiple VSA's per tag per message

For example:

Alc-Sub-Serv-Activate;1 = rate-limit;1000;8000

Table 9. Subscriber service accounting (applicability)
Attribute ID Attribute name Acct start Acct stop Acct interim-update

42

Acct-Input-Octets

0

0-1

0-1

43

Acct-Output-Octets

0

0-1

0-1

44

Acct-Session-Id

1

1

1

47

Acct-Input-Packets

0

0-1

0-1

48

Acct-Output-Packets

0

0-1

0-1

50

Acct-Multi-Session-Id

1

1

1

52

Acct-Input-Gigawords

0

0-1

0-1

53

Acct-Output-Gigawords

0

0-1

0-1

26.6527.151

Alc-Sub-Serv-Activate

1

1

1

LSN accounting

Table 10. LSN accounting (description)
Attribute ID Attribute name Description

1

User-Name

Refers to the username reported in Accounting for subscriber-aware or subscriber-unaware Large Scale NAT (LSN) users. The reported format for subscriber-unaware users is LSN44@, DS-lite@ or NAT64@ followed by the user’s inside IPv4 or IPv6 address. The reported format and length for subscriber-aware users is configured and driven by configure router nat inside subscriber-identification and send when user-name is included under configure aaa isa-radius-policy name acct-include-attributes. This attribute has the same content as [26.6527.11] Alc-Subsc-ID-Str for subscriber-unaware Large Scale NAT users.

4

NAS-IP-Address

The identifying IP Address of the NAS requesting the Authentication or Accounting and maps to the IPv4 address from the system interface (configure router interface system address ip-address).

5

NAS-Port

Unique 32 bit encoded number [31 to 0] that holds the MS-ISA MDA used for LSN accounting. The following formatting is used [3 bits 31 to 29 value 000], [4 bits 28 to 25 value slot-ms-isa], [4 bits 24 to 21 value mda-nbr-ms-isa], [6 bits 20 to 15 000010], [15 bits 14 to 0 0000 0000 0000 0000].

8

Framed-IP-Address

Refers to the inside private IP address of the user (LSN44) and send when framed-ip-addr is included in configure aaa isa-radius-policy name acct-include-attributes.

30

Called-Station-Id

Holds information to which nat-group and nat-member the NAT user belongs. The format of this attribute is a string 00-00-00-00-NatGroup-NatMember. The command show isa nat-group holds the link between ms-isa mda, NatGroup and NatMember. Optionally sent when called-station-id is included under configure aaa isa-radius-policy name acct-include-attributes.

32

NAS-Identifier

A string (configure system name system-name) identifying the NAS originating the Authentication or Accounting requests and sent when nas-identifier is included for the corresponding application: configure subscriber-mgmt radius-accounting-policy (ESM accounting), configure aaa isa-radius-policy (LSN accounting, WLAN-GW) and configure aaa l2tp-accounting-policy (L2TP accounting).

40

Acct-Status-Type

Indicates the LSN Accounting-Request type.

Accounting On is sent on MS-ISA restart, when a radius-accounting-policy is added in an isa nat-group nat-group-id and when adding a server in the aaa isa-radius-policy name.

Accounting Off is sent when removing a server from the aaa isa-radius-policy name.

With start/stop accounting, an Accounting-Start is sent when a port-range-block is assigned to a user and an Accounting-Stop when the port-range-block is released into the pool.

With interim accounting, an Accounting-Start is sent when the first port-range-block is assigned to a user. An Accounting Interim Update is sent when additional port-range blocks are assigned or released. An Accounting-Stop is sent when the last port-range block is released.

42

Acct-Input-Octets

Indicates how many Layer 3 octets were sent to this NAT user over the course of this service being provided and sent together with [43] Acct-Output-Octets, [52] Acct-Input-Gigawords and [53] Acct-Output-Gigawords when octet-counters is included under configure aaa isa-radius-policy name acct-include-attributes.

43

Acct-Output-Octets

Indicates how many Layer 3 octets have been received from this nat user over the course of this service being provided and send together with [42] Acct-Input-Octets, [52] Acct-Input-Gigawords and [53] Acct-Output-Gigawords when octet-counters is included under configure aaa isa-radius-policy name acct-include-attributes.

44

Acct-Session-Id

This unique 16 bytes attribute has two different behaviors. If multi-session-id is not included under configure aaa isa-radius-policy name acct-include-attributes then multiple port-ranges for the same user are all reported with a common 16 bytes [44] Acct-Session-id for the different port-ranges and reported using start, interim and stop accounting messages and without attribute [50] Acct-Multi-Session-Id. If multi-session-id is configured under configure aaa isa-radius-policy name acct-include-attributes then multiple port-ranges for the same user are reported with different 16 bytes [44] Acct-Session-id using start and stop accounting messages with an additional common 16 bytes attribute [50] Acct-Multi-Session-Id. For an accounting-on and accounting-off the first 8 bytes from the 16 bytes are put to zero.

46

Acct-Session-Time

Reports the elapsed time in seconds the user has allocated a unique port-range in accounting start, interim or stop. For accounting-off it reports the elapsed time in second since the last accounting-on.

47

Acct-Input-Packets

Indicates how many packets have been send for this nat user over the course of this service being provided and send together with [48] Acct-Output-Packets when frame-counters is included under configure aaa isa-radius-policy name acct-include-attributes.

48

Acct-Output-Packets

Indicates how many packets have been received for this nat user over the course of this service being provided and send together with [47] Acct-Input-Packets when frame-counters is included under configure aaa isa-radius-policy name acct-include-attributes.

49

Acct-Terminate-Cause

Indicates why a specific NAT port-range is released in Acct-Stop messages. Cause host-Request is used If the last port-range for this NAT user is freed and cause port-unneeded is used when we release a port-range which is not the last one (multiple port-ranges) for this NAT user. Cause [10]Nas-request is reported in Accounting-Off and cause [11]Nas-reboot is reported in Accounting-on. This attribute is only sent when release-reason is included under configure aaa isa-radius-policy name acct-include-attributes.

50

Acct-Multi-Session-Id

This unique 16 bytes attribute has two different behaviors. If multi-session-id is not included under configure aaa isa-radius-policy name acct-include-attributes then multiple port-ranges for the same user are all reported with a common 16 bytes [44] Acct-Session-id for the different port-ranges and reported using start, interim and stop accounting messages and without attribute [50] Acct-Multi-Session-Id. If multi-session-id is included under configure aaa isa-radius-policy name acct-include-attributes then multiple port-ranges for the same user are reported with different 16 bytes [44] Acct-Session-id using start and stop accounting messages with an additional common 16 bytes attribute [50] Acct-Multi-Session-Id.

52

Acct-Input-Gigawords

Indicates how many times (zero or more) the [42] Acct-Input-Octets counter has wrapped around 2^32 in the course of delivering this service and send together with [42] Acct-Input-Octets, [43] Acct-Output-Octets and [53] Acct-Output-Gigawords when octet-counters is included under configure aaa isa-radius-policy name acct-include-attributes.

53

Acct-Output-Gigawords

Indicates how many times (zero or more) the [43] Acct-Output-Octets counter has wrapped around 2^32 in the course of delivering this service and send together with [42] Acct-Input-Octets, [43] Acct-Output-Octets and [52] Acct-Input-Gigawords when octet-counters is included under configure aaa isa-radius-policy name acct-include-attributes.

55

Event-Timestamp

Record the time that this event occurred on the NAS, in seconds since January 1, 1970 00:00 UTC and send when hardware-timestamp is included under configure aaa isa-radius-policy name acct-include-attributes.

97

Framed-IPv6-Prefix

Inside private IPv6 address of the user (NAT64,DSLITE) and send when framed-ipv6-prefix is included under configure aaa isa-radius-policy name acct-include-attributes.

26.6527.11

Alc-Subsc-ID-Str

The reported format is LSN44@, DS-lite@ and NAT64@ followed by the users inside IPv4 or IPv6 address and send when nat-subscriber-string is included under configure aaa isa-radius-policy name acct-include-attributes. This attribute has the same content as [1]User-Name for subscriber-unaware Large Scale NAT users.

26.6527.100

Alc-Serv-Id

Refers in the Accounting-Request to the inside service-id used for LSN subscribers using RADIUS LSN accounting (configure aaa isa-radius-policy name nat acct-include-attributes inside-service-id). The outside service-id is reported using [26.6527.140] Alc-Nat-Outside-Serv-Id.

26.6527.121

Alc-Nat-Port-Range

This attribute is used to report allocated or released NAT resources in LSN. The reported NAT resources include a public IPv4 address, public port ranges, and outside routing instance.

This attribute is included in accounting by configuring the port-range-block option under the configure aaa isa-radius-policy name acct-include-attributes CLI hierarchy.

26.6527.140

Alc-Nat-Outside-Serv-Id

Refers to the public outside service-id and send when outside-service-id is included under configure aaa isa-radius-policy name acct-include-attributes.

26.6527.141

Alc-Nat-Outside-Ip-Addr

Holds for the NAT user his public outside IPv4 address and send when outside-ip is included under configure aaa isa-radius-policy name acct-include-attributes. The content of this attribute is identical to the outside IPv4 address in [26.6527.121] Alc-Nat-Port-Range.

26.6527.163

Alc-Acct-Triggered-Reason

A reason attribute included in Acct-Interim messages to specify the reason for the interim update. Attribute is included in LSN accounting only when acct-include-attribute acct-trigger-reason is enabled in the isa-radius-policy.

Table 11. LSN accounting (limits)
Attribute ID Attribute name Type Limits SR OS format

1

User-Name

string

[32|64] chars

Subscriber unaware: LSN44@<ipaddr>, DS-lite@<ipv6addr> and NAT64@<ipv6addr>Subscriber aware: format and length depends on the subscriber-identification attribute configuration- attribute-type alc-sub-string max 32 chars- attribute-type user-name, class and station-id max 64 chars- attribute-type imsi and imei max 32 chars

For example:

# subscriber unaware: NAT64 host ipv6 address 2001:db8::1User-Name = NAT64@2001:0db8:0000:0000:0000:0000:0000:0001# subscriber aware:

NAS subscriber-id = private-user1 and subscriber-identification alc-sub-stringUser-Name = private-user1

4

NAS-IP-Address

ipaddr

4 bytes

For example:

# ip-address 10.1.1.1

NAS-IP-Address 0a010101

5

NAS-Port

integer

4 bytes

For example:

# MS-ISA MDA 1/2 # 1/2/nat-out-ip corresponds to [000] [slot 0001] [mda 0010] [nat-outip 00010] [000 0000 0000 0000]: value 37814272#

Note - nat-out-ip is translated value 2 (00010) and it represents the logical port on the ms-isa (show port 1/2 returns all virtual ports) NAS-Port = 37814272

8

Framed-IP-Address

ipaddr

4 bytes

For example:

# private inside ipv4address LSN44 user192.168.0.1

Framed-IP-Address = 192.168.0.1

30

Called-Station-Id

string

17 bytes

00-00-00-00-<natgroup>-<natmember>

For example:

# nat group 1 and nat member 1#

Called-Station-Id = 30302d30302d30302d30302d30312d30312dCalled-Station-Id = 00-00-00-00-01-01

32

NAS-Identifier

string

64 chars

For example:

NAS-Identifier = PE1-Antwerp

40

Acct-Status-Type

integer

4 bytes

1=Start, 2=Stop, 3=Interim Update, 7=Accounting-On, 8=Accounting-Off

42

Acct-Input-Octets

integer

4 bytes

For example:

Acct-Input-Octets = 5000

43

Acct-Output-Octets

integer

4 bytes

For example:

Acct-Output-Octets = 2000

44

Acct-Session-Id

string

32 bytes

No useful information can be extracted from the string.

For example:

# internal generated asid 32 Bytes/16 chars: 0x3466666434383332306232313436393738363238346262323339326462636232

Acct-Session-Id = 4ffd48320b21469786284bb2392dbcb2

46

Acct-Session-Time

integer

4 bytes 4294967295 seconds

For example:

Acct-Session-Time = 870

47

Acct-Input-Packets

integer

4 bytes 4294967295 packets

For example:

Acct-Input-Packets = 15200

48

Acct-Output-Packets

integer

4 bytes 4294967295 packets

For example:

Acct-Output-Packets = 153537

49

Acct-Terminate-Cause

integer

4 bytes

See also table Acct Terminate Cause 10=Nas-Request, 11=Nas-Reboot, 14=Port-Suspended, 18=Host-Request

For example:

Acct-Terminate-Cause = Port-unneeded

50

Acct-Multi-Session-Id

string

32 bytes

No useful information can be extracted from the string.

For example:

# internal generated asid 32 Bytes/16 chars: 0x3566666434383332306232313436393738363238346262323339326462636232 Acct-Multi-Session-Id = 5ffd48320b21469786284bb2392dbcb2

52

Acct-Input-Gigawords

integer

4 bytes

For example:

# no overflowAcct-Input-Gigawords = 0

53

Acct-Output-Gigawords

integer

4 bytes

For example:

# no overflowAcct-Output-Gigawords = 0

55

Event-Timestamp

date

4 bytes

For example:

# Jul 6 2012 17:28:23 CEST is reported as 4FF70417Event-Timestamp = 4FF70417

97

Framed-IPv6-Prefix

ipv6prefix

max. 16 bytes for prefix + 1 byte for length

private inside IPv6 address of NAT64 or DS-Lite user

For example:

Framed-IPv6-Prefix = 2001:db8::1/128

26.6527.11

Alc-Subsc-ID-Str

string

64 chars

LSN44@<ipaddr>, DS-lite@<ipv6addr> and NAT64@<ipv6addr>

For example:

Alc-Subsc-ID-Str = LSN44@192.168.0.1

Alc-Subsc-ID-Str = DS-Lite@2001:0000:0000:0000:0000:0000:0000:0001

Alc-Subsc-ID-Str = NAT64@2002:0000:0000:0000:0000:0000:0000:0001

26.6527.100

Alc-Serv-Id

integer

2147483647 ID

VPRN service ID or 0 (zero) when inside service is the Base routing instance.

For example:

inside VPRN service 100:

Alc-Serv-Id = 100

26.6527.121

Alc-Nat-Port-Range

string

no limits

<public-ip> <space> <port-range> <space> router <space> <outside-routing-instance> <space> <nat-policy-name>

For example:

a host with public pool address 198.51.100.248; port-range [37674 to 37723] in Base with nat-policy-name = nat-pol-1

Alc-Nat-Port-Range = ‟198.51.100.248 37674-37723 router base nat-pol-1”

26.6527.140

Alc-Nat-Outside-Serv-Id

integer

2147483647 ID

VPRN service ID or 0 (zero) when outside service is the Base routing instance.

For example:

outside VPRN service 200:

Alc-Nat-Outside-Serv-Id = 200

26.6527.141

Alc-Nat-Outside-Ip-Addr

ipaddr

4 bytes

For example:

Alc-Nat-Outside-Ip-Addr = 198.51.100.248

26.6527.163

Alc-Acct-Triggered-Reason

integer

4 bytes

See Accounting triggered reason for a description of Accounting Triggered Reason values.

For example:

ACCT TRIGGERED INTERIM REASON [163] 4 Nat-Free (19)

Table 12. LSN accounting (applicability)
Attribute ID Attribute name Acct start Acct stop Acct interim-update Acct on Acct off

1

User-Name

0-1

0-1

0-1

0

0

4

NAS-IP-Address

1

1

1

1

1

5

NAS-Port

1

1

1

1

1

8

Framed-IP-Address

0-1

0-1

0-1

0

0

30

Called-Station-Id

0-1

0-1

0-1

0-1

0-1

32

NAS-Identifier

0-1

0-1

0-1

0-1

0-1

40

Acct-Status-Type

1

1

1

1

1

42

Acct-Input-Octets

0

0-1

0-1

0

0

43

Acct-Output-Octets

0

0-1

0-1

0

0

44

Acct-Session-Id

1

1

1

1

1

46

Acct-Session-Time

1

1

1

1

1

47

Acct-Input-Packets

0-1

0-1

0-1

0

0

48

Acct-Output-Packets

0-1

0-1

0-1

0

0

49

Acct-Terminate-Cause

0

0-1

0

0-1

0-1

50

Acct-Multi-Session-Id

0-1

0-1

0

0

0

52

Acct-Input-Gigawords

0

0-1

0-1

0

0

53

Acct-Output-Gigawords

0

0-1

0-1

0

0

55

Event-Timestamp

0-1

0-1

0-1

0-1

0-1

97

Framed-IPv6-Prefix

0-1

0-1

0-1

0

0

26.6527.11

Alc-Subsc-ID-Str

0-1

0-1

0-1

0

0

26.6527.100

Alc-Serv-Id

0-1

0-1

0-1

0

0

26.6527.121

Alc-Nat-Port-Range

0-1

0-1

0-1

0

0

26.6527.140

Alc-Nat-Outside-Serv-Id

0-1

0-1

0-1

0

0

26.6527.141

Alc-Nat-Outside-Ip-Addr

0-1

0-1

0-1

0

0

26.6527.163

Alc-Acct-Triggered-Reason

0

0

0-1

0

0

L2TP tunnel accounting

Table 13. L2TP tunnel accounting (description)
Attribute ID Attribute name Description

1

User-Name

Refers to the PPPoE username

4

NAS-IP-Address

The identifying IP Address of the NAS requesting the Authentication or Accounting. Included when the RADIUS server is reachable using IPv4.

The address is determined by the routing instance through which the RADIUS server can be reached:

‟Management” — The active IPv4 address in the Boot Options File (bof address ipv4-address)

‟Base” or ‟VPRN” — The IPv4 address of the system interface (configure router interface system address address).

The address can be overwritten with the configured source-address (configure aaa radius-server-policy policy-name servers source-address ip-address).

5

NAS-Port

The physical access-circuit on the NAS which is used for the Authentication or Accounting of the user. The format of this attribute is configurable on the NAS as a fixed 32 bit value or a parameterized 32 bit value. The parameters can be a combination of outer and inner vlan ID, slot number, MDA number, port number, lag-id, pw-id, pxc-id, pxc-subport and fixed bit values (zero or one) but cannot exceed 32 bits. The format can be configured for following applications: configure aaa l2tp-accounting-policy name include-radius-attribute nas-port, configure router l2tp cisco-nas-port, configure service vprn service-id l2tp cisco-nas-port, configure subscriber-mgmt authentication-policy name include-radius-attribute nas-port, configure subscriber-mgmt radius-accounting-policy name include-radius-attribute nas-port.

6

Service-Type

The type of service the PPPoE user has requested, or the type of service to be provided for the PPPoE user. Optional in RADIUS-Accept and CoA. Treated as a session setup failure if different from Framed-User.

31

Calling-Station-Id

Includes the hostname and sap-id.

Send when calling-station-id is included in configure aaa l2tp-accounting-policy policy-name include-radius-attribute calling-station-id

32

NAS-Identifier

A string (configure system name system-name) identifying the NAS originating the Authentication or Accounting requests and sent when nas-identifier is included for the corresponding application: configure aaa l2tp-accounting-policy (L2TP accounting).

41

Acct-Delay-Time

Indicates how many seconds the client has been trying to send this accounting record for. This attribute is included with value 0 in all initial accounting messages. Attribute is omitted in accounting using configure subscriber-mgmt radius-accounting-policy name include-radius-attribute no acct-delay-time.

42

Acct-Input-Octets

Tunnel-link and Tunnel level accounting uses the ESM accounting statistics. For Tunnel Link Stop it reports the input bytes for this user over the course of this service being provided. For Tunnel Stop this attribute represent an aggregate of input bytes of all sessions that belong(ed) to this tunnel over the course of this service being provided. Attribute [52] Acct-Output-Gigawords indicates how many times (if greater than zero) the [42] Acct-Input-Octets counter has wrapped around 2^32 in the course of delivering this service.

43

Acct-Output-Octets

Tunnel-link and Tunnel level accounting uses the ESM accounting statistics. For Tunnel Link Stop it reports the output bytes for this user over the course of this service being provided. For Tunnel Stop this attribute represent an aggregate of output bytes of all sessions that belong(ed) to this tunnel over the course of this service being provided. Attribute [53] Acct-Output-Gigawords indicates how many times (if bigger than zero) the [43] Acct-Output-Octets counter has wrapped around 2^32 in the course of delivering this service.

44

Acct-Session-Id

Is a unique generated number and maps for the Tunnel-link stop to the accounting-session-id of the PPPoE session (show service id service id ppp session detail). For Tunnel-stop accounting it is longer and a concatenation of start-time and connection-id with delimiter. The start-time equals to the node uptime reported in Timeticks (nd:hh:mm:ss:ts) and value/6000 gives the uptime in minutes. The connection-id equals {tunnel-id * 65536} and the tunnel-id maps to L2TP AVP 9 Assigned Tunnel Id.

46

Acct-Session-Time

Reports the elapsed time in seconds over the course of this service (L2TP session or L2TP tunnel) being provided.

47

Acct-Input-Packets

Tunnel-link and Tunnel level accounting uses the ESM accounting statistics. For Tunnel Link Stop it reports the input packets for this user over the course of this service being provided. For Tunnel Stop this attribute represent an aggregate of input packets of all sessions that belong/belonged to this tunnel over the course of this service being provided.

48

Acct-Output-Packets

Tunnel-link and Tunnel level accounting uses the ESM accounting statistics. For Tunnel Link Stop it reports the output packets for this user over the course of this service being provided. For Tunnel Stop this attribute represent an aggregate of output packets of all sessions that belong/belonged to this tunnel over the course of this service being provided.

49

Acct-Terminate-Cause

Indicates how the L2TP session or L2TP tunnel was terminated.

52

Acct-Input-Gigawords

Indicates how many times (zero or more) the [42] Acct-Input-Octets counter has wrapped around 2^32 in the course of delivering this service.

53

Acct-Output-Gigawords

Indicates how many times (zero or more) the [43] Acct-Output-Octets counter has wrapped around 2^32 in the course of delivering this service.

55

Event-Timestamp

Record the time that this event occurred on the NAS, in seconds since January 1, 1970 00:00 UTC

61

NAS-Port-Type

The type of the physical port of the NAS which is authenticating the user and value automatically determined from subscriber SAP encapsulation. It can be overruled by configuration. Included only if include-radius-attribute nas-port-type is added per application: configure aaa l2tp-accounting-policy (L2TP accounting). Checked for correctness if returned in CoA.

64

Tunnel-Type

The tunneling protocols to be used (in the case of a tunnel initiator) or the tunneling protocol in use (in the case of a tunnel terminator). This attribute is mandatory on LAC Access-Accept and needs to be L2TP. The same attribute is included on LNS in the Access-Request and Acct-Request if configure subscriber-mgmt authentication-policy | radius-accounting-policy policy name include-radius-attribute tunnel-server-attrs is enabled on LNS. For L2TP Tunnel/Link Accounting this attribute is always included on LAC and LNS.

65

Tunnel-Medium-Type

Which transport medium to use when creating a tunnel for those protocols (such as L2TP) that can operate over multiple transports. This attribute is mandatory on LAC Access-Accept and needs to be IP or IPv4. The same attribute is included on LNS in the Access-Request and Acct-Request if configure subscriber-mgmt authentication-policy|radius-accounting-policy policy name include-radius-attribute tunnel-server-attrs is enabled on LNS. For L2TP Tunnel/Link Accounting this attribute is always included on LAC and LNS.

66

Tunnel-Client-Endpoint

The dotted-decimal IP address of the initiator end of the tunnel. Preconfigured values are used when attribute is omitted (configure router/service vprn service-id l2tp local-address). If omitted in Access Accept on LAC and no local-address configured, then the address is taken from the interface with name system. This attribute is included on LNS in the Access-Request and Acct-Request only if configure subscriber-mgmt authentication-policy|radius-accounting-policy policy name include-radius-attribute tunnel-server-attrs is enabled on LNS. For L2TP Tunnel/Link Accounting this attribute is always included on LAC and LNS as untagged.

67

Tunnel-Server-Endpoint

The dotted-decimal IP address of the server end of the tunnel and is on the LAC the dest-ip for all L2TP packets for that tunnel.

68

Acct-Tunnel-Connection

Indicates the identifier assigned to the tunnel session. For Tunnel start/stop it is a concatenation, without delimiter, of LAC-tunnel-id (4 bytes) and LNS-tunnel-id (4 bytes) were the LAC-tunnel-id maps to the hex value of L2TP AVP 9 AssignedTunnelId from SCCRQ and LNS-tunnel-id maps to the hex value L2TP AVP 9 AssignedTunnelId in SCCRP. Unknown tunnel-ids (Tunnel Reject and Tunnel Link Reject) are reported as 0000 or ffff. For Tunnel Link Start/Stop it maps to the integer Call Serial Number from ICRQ L2TP AVP 15 Call Serial Number.

The default format of the attribute can be changed with configure aaa l2tp-accounting-policy policy-name acct-tunnel-connection-fmt ascii-spec.

82

Tunnel-Assignment-ID

Indicates to the tunnel initiator the particular tunnel to which a session is to be assigned. Some tunneling protocols, such as PPTP and L2TP, allow for sessions between the same two tunnel endpoints to be multiplexed over the same tunnel and also for a specific session to use its own dedicated tunnel.

86

Acct-Tunnel-Packets-Lost

Indicates the number of packets dropped and uses the ESM accounting statistics for this. For Tunnel Link Stop it reports an aggregate of the dropped input and output packets for this user over the course of this service being provided. For Tunnel Stop this attribute represent an aggregate of input and output dropped packets of all sessions that belong/belonged to this tunnel over the course of this service being provided.

87

NAS-Port-Id

LAC: a text string identifying the physical access circuit (slot/mda/port/outer-vlan.inner-vlan) of the user that requested the Authentication and, or Accounting. The physical port on LAC can have an optional prefix-string (8 characters maximum) and suffix-string (64 characters maximum) added (configure aaa l2tp-accounting-policy policy-name include-radius-attribute nas-port-id prefix-string string suffix(circuit-id | remote-id)). LNS: a text string identifying the logical access circuit of the user that requested the Authentication or Accounting. This logical access circuit is a fixed concatenation (delimiter number) of routing instance, tunnel-server-endpoint, tunnel-client-endpoint, local-tunnel-id, remote-tunnel-id, local-session-id, remote-session-id and call sequence number.

90

Tunnel-Client-Auth-ID

Used during the authentication phase of tunnel establishment and copied by the LAC in L2TP SCCRQ AVP 7 Host Name. Reported in L2TP Tunnel/Link accounting when length is different from zero. The value with tag 0 is used as default for the tunnels where the value is not specified. Preconfigured values are used when the attribute is omitted (configure router/service vprn service-id l2tp local-name). The Node system-name is copied in AVP Host Name if this attribute is omitted and no local-name is configured.

91

Tunnel-Server-Auth-ID

Used during the authentication phase of tunnel establishment and reported in L2TP Tunnel/Link accounting when length is different from zero. For authentication the value of this attribute is compared with the value of AVP 7 Host Name from the received LNS SCCRP. Authentication from LAC point of view passes if both attributes are the same. This authentication check is not performed if the RADIUS attribute is omitted.

95

NAS-IPv6-Address

The identifying IP address of the NAS requesting the Authentication or Accounting. Included when the RADIUS server is reachable using IPv6.

The address is determined by the routing instance through which the RADIUS server can be reached:

‟Management” — The active IPv6 address in the Boot Options File (bof address ipv6-address)

‟Base” or ‟VPRN” — The IPv6 address of the system interface (configure router interface system ipv6 address ipv6-address).

The address can be overwritten with the configured ipv6-source-address (configure aaa radius-server-policy policy-name servers ipv6-source-address ipv6-address).

Table 14. L2TP tunnel accounting (limits)
Attribute ID Attribute name Type Limits SR OS format

1

User-Name

string

253 bytes

Format depends on authentication method and configuration.

For example:

User-Name user1@domain1.com

4

NAS-IP-Address

ipaddr

4 bytes

# ip-address

For example:

NAS-IP-Address= 192.0.2.1

5

NAS-Port

integer

4 bytes

nas-port <binary-spec>

<binary-spec>=<bit-specification><binary-spec>

<bit-specification> = 0 | 1 | <bit-origin>

<bit-origin> = *<number-of-bits><origin> <number-of-bits> = [1 to 32]

<origin> =

s: slot number

m: MDA number

p: port number, lag-id, pw-id or pxc-id

o: outer VLAN ID

i: inner VLAN ID

c: pxc-subport (a=0, b=1)

Only the lower bits of the specified origin are included if the number of bits assigned for that origin is not enough to hold its maximum value. For example, when specifying 10 bits for an outer VLAN ID (*10o), then VLAN 3000 (binary 1011 1011 1000) would be reported as 952 (binary 11 1011 1000)

For example : configured nas-port *12o*10i*3s*2m*5p for SAP 2/2/4:221.7 corresponds to 000011011101

0000000111 010 10 00100

NAS-Port = 231742788

6

Service-Type

integer

2 (mandatory value)

PPPoE and PPPoL2TP hosts only

For example:

Service-Type = Framed-User

31

Calling-Station-Id

string

253 chars

For example:

Calling-Station-Id = "router-1 1/1/4:1200.10"

32

NAS-Identifier

string

64 chars

For example:

NAS-Identifier = PE1-Antwerp

41

Acct-Delay-Time

integer

4294967295 seconds

For example:

# initial accounting start Acct-Delay-Time = 0# no ack and retry after 5 seconds Acct-Delay-Time = 5

42

Acct-Input-Octets

integer

4 bytes

For example:

Acct-Input-Octets = 5000

43

Acct-Output-Octets

integer

4 bytes

For example:

Acct-Output-Octets = 2000

44

Acct-Session-Id

string

[17|22] bytes

Tunnel number format: <uptime><.><connection-id>Tunnel-link number format: corresponds to PPPoE session ASID (No useful information can be extracted from the string).

For example:

# for tunnel accountingAcct-Session-Id = 18120579.84213760# for tunnel-link accountingAcct-Session-Id = 241AFF0000029B4FD5C03E

46

Acct-Session-Time

integer

4 bytes

42949672 seconds

The attribute value wraps after approximately 497 days

For example:

Acct-Session-Time = 870

47

Acct-Input-Packets

integer

4 bytes 4294967295 packets

For example:

Acct-Input-Packets = 213

48

Acct-Output-Packets

integer

4 bytes 4294967295 packets

For example:

Acct-Output-Packets = 214

49

Acct-Terminate-Cause

integer

4 bytes

See also table Acct Terminate Cause 1=User-Request, 2=Lost-Carrier, 9=NAS-Error, 10=NAS-Request, 11=NAS-Reboot, 15=Service-Unavailable

For example:

Acct-Terminate-Cause = NAS-Request

52

Acct-Input-Gigawords

integer

4 bytes

For example:

# no overflowAcct-Input-Gigawords = 0

53

Acct-Output-Gigawords

integer

4 bytes

For example:

# no overflowAcct-Output-Gigawords = 0

55

Event-Timestamp

date

4 bytes

For example:

# Jul 6 2012 17:28:23 CEST is reported as 4FF70417Event-Timestamp = 4FF70417

61

NAS-Port-Type

integer

4 bytes Values [0 to 255]

Values as defined in rfc-2865 and rfc-4603For LNS, the value is set to virtual (5)

For example:

NAS-Port-Type = PPPoEoQinQ (34)

64

Tunnel-Type

integer

3 (mandatory value)

Mandatory 3=L2TP

For example:

Tunnel-Type = L2TP

65

Tunnel-Medium-Type

integer

1 (mandatory value)

Mandatory 1=IP or IPv4

For example:

Tunnel-Medium-Type = IP

66

Tunnel-Client-Endpoint

string

19 or 20 bytes (untagged/tagged)

<Tag field><dotted-decimal IP address used on LAC as L2TP src-ip> If Tag field is greater than 0x1F, it is interpreted as the first byte of the following string field

For example:

# untagged Tunnel-Client-Endpoint = 3139382e35312e3130302e31Tunnel-Client-Endpoint = 198.51.100.1# tagged 0 Tunnel-Client-Endpoint = 003139382e35312e3130302e31Tunnel-Client-Endpoint:0 = 198.51.100.1# tagged 1 Tunnel-Client-Endpoint = 013139382e35312e3130302e31Tunnel-Client-Endpoint:1 = 198.51.100.1

67

Tunnel-Server-Endpoint

string

19 or 20 bytes (untagged/tagged)

<Tag field><dotted-decimal IP address used on LAC as L2TP dst-ip> If Tag field is greater than 0x1F, it is interpreted as the first byte of the following string field

For example:

# tagged 1 Tunnel-Server-Endpoint = 013230332e302e3131332e31Tunnel-Server-Endpoint:1 = 203.0.113.1

68

Acct-Tunnel-Connection

string

[4|8] bytes

Default format:

tunnel-start/stop : 8 Byte value representing the lac + lns tunnel-id converted in hexadecimallink-start/stop: maps to the AVP 15 call Serial Number from ICRQ (32 bit)

Configured format:

(if the resulting string is longer than 253 characters, it is truncated)

acct-tunnel-connection-fmt ascii-spec

<ascii-spec> : <char-specification> <ascii-spec>

<char-specification> : <ascii-char>|<char-origin>

<ascii-char> : a printable ASCII character

<char-origin> : %<origin>

<origin> : n | s | S | t | T | c | C

n - Call Serial Number

s | S - Local (s) or Remote (S) Session Id

t | T - Local (t) or Remote (T) Tunnel Id

c | C - Local (c) or Remote (C) Connection Id

82

Tunnel-Assignment-ID

string

32 chars

For example:

Tunnel-Assignment-ID = Tunnel-1

86

Acct-Tunnel-Packets-Lost

integer

4 bytes

Sum of all dropped packets on ingress and egress.

For example:

Acct-Tunnel-Packets-Lost = 748

87

NAS-Port-Id

string

no limits

See [87] NAS-Port-Id attribute details for a detailed description of the attribute format.

For example:

LAC: 1/1/4:120.10

LNS: rtr-2#lip- 3.3.3.3#rip-1.1.1.1#ltid-11381#rtid-1285#lsid- 30067#rsid-19151#347

90

Tunnel-Client-Auth-ID

string

64 chars

For example:

Tunnel-Client-Auth-Id:0 = LAC-Antwerp-1

91

Tunnel-Server-Auth-ID

string

64 chars

For example:

Tunnel-Server-Auth-ID:0 = LNS-Antwerp-1

95

NAS-IPv6-Address

ipv6addr

16 bytes

# ipv6-address

For example:

NAS-IPv6-Address = 2001:db8::1

Table 15. L2TP tunnel accounting (applicability)
Attribute ID Attribute name Acct tunnel-start Acct tunnel-stop Acct tunnel-reject Acct tunnel-link-start Acct tunnel-link-stop Acct tunnel-link-reject

1

User-Name

0

0

0

1

1

1

4

NAS-IP-Address

0-1

0-1

0-1

0-1

0-1

0-1

5

NAS-Port

0

0

0

0-1

0-1

0-1

6

Service-Type

0

0

0

1

1

1

31

Calling-Station-Id

0-1

0-1

0-1

0-1

0-1

0-1

32

NAS-Identifier

0-1

0-1

0-1

0-1

0-1

0-1

41

Acct-Delay-Time

1

1

1

1

1

1

42

Acct-Input-Octets

0

1

0

0

1

0

43

Acct-Output-Octets

0

1

0

0

1

0

44

Acct-Session-Id

1

1

1

1

1

1

46

Acct-Session-Time

0

1

0

0

1

0

47

Acct-Input-Packets

0

1

0

0

1

0

48

Acct-Output-Packets

0

1

0

0

1

0

49

Acct-Terminate-Cause

0

1

1

0

1

1

52

Acct-Input-Gigawords

0

0-1

0

0

0-1

0

53

Acct-Output-Gigawords

0

0-1

0

0

0-1

0

55

Event-Timestamp

1

1

1

1

1

1

61

NAS-Port-Type

0

0

0

0-1

0-1

0-1

64

Tunnel-Type

1

1

1

1

1

1

65

Tunnel-Medium-Type

1

1

1

1

1

1

66

Tunnel-Client-Endpoint

1

1

1

1

1

1

67

Tunnel-Server-Endpoint

1

1

1

1

1

1

68

Acct-Tunnel-Connection

1

1

1

1

1

0

82

Tunnel-Assignment-ID

1

1

1

1

1

1

86

Acct-Tunnel-Packets-Lost

0

1

0

0

1

0

87

NAS-Port-Id

0

0

0

0-1

0-1

0-1

90

Tunnel-Client-Auth-ID

1

1

1

1

1

1

91

Tunnel-Server-Auth-ID

1

1

0

1

1

1

95

NAS-IPv6-Address

0-1

0-1

0-1

0-1

0-1

0-1

Application Assurance (AA) accounting

Table 16. Application Assurance accounting (description)
Attribute ID Attribute name Description

1

User-Name

The AA-subscriber reported in AA Accounting statistics and included in Start, Interim and Stop Accounting messages.

4

NAS-IP-Address

The identifying IP Address of the NAS requesting the Accounting and maps to the IPv4 address from the system interface (configure router interface system address ip-address). Allows to monitor node redundancy activity switch.

32

NAS-Identifier

A string (configure system name system-name) identifying the NAS originating the AA Accounting requests. It is sent in all accounting messages. Allows to monitor node redundancy activity switch.

40

Acct-Status-Type

Indicates AA Acct request type. Acct On is sent each time a RADIUS accounting policy (configure application-assurance radius-accounting-policy rad-acct-plcy-name) is enabled under a partition (configure application-assurance group aa-group-id:partition-id statistics aa-sub radius-accounting-policy rad-acct-plcy-name) or after a node reboot. An Acct Start is sent for each new AA-subscriber created under a partition were radius accounting is enabled. An Acct Interim is sent every configured interval time (configure application-assurance radius-accounting-policy rad-acct-plcy-name interim-update-interval minutes) for each AA-subscriber under a partition with the radius-accounting policy applied. An Acct Stop is sent at AA-subscriber removal. An application-profile change or an Application-Service-Options [ASO] override against a subscriber does not trigger Acct Start/Stop messages and does not affect the AA RADIUS Acct session.

44

Acct-Session-Id

The unique value per node used to identify the AA subscriber accounting session. Reported in accounting Start, Stop and Interim Updates messages. Its value is automatically derived from the subscriber ID string ([26.6527.11] Alc-Subsc-ID-Str) and the AA subscriber type, that guarantees to preserve the subscriber session ID after ISA card redundancy activity switch or after a node redundancy activity switch (in AARP context). An activity switch does not modify the session ID, but can be detected if needed due to the [26.6527.156] Alc-AA-Group-Partition-Isa-Id or the [32] NAS-Identifier. The AA RADIUS Acct session is independent from the ESM RADIUS Acct session. An AA Acct Off is sent when accounting stats is disabled (removing the RADIUS accounting policy).

49

Acct-Terminate-Cause

Indicates how the session was terminated.

55

Event-Timestamp

Records the time that this event occurred on the NAS, in seconds, since January 1, 1970 00:00 UTC.

26.6527.11

Alc-Subsc-ID-Str

AA-subscriber string name, used together with the AA-subscriber type to construct the [44] Acct-Session-Id. Sent in all Acct Start, Interim Updates and Stop messages.

If Application Assurance per subscriber MAC is enabled, then the MAC address is appended, with a '-' as a separator between sub ID and MAC. If the sub ID is more than 19 characters, it's truncated to 19 characters and '+' is used as a separator between the sub ID and MAC to indicate truncation.

26.6527.19

Alc-Acct-I-Inprof-Octets-64

Identifies a charging group, app-group, application or sub-aggregate and its corresponding total from-sub admitted bytes. Reports cumulative volume of preconfigured AA-subscriber charging group, app-group or application since the start of the session (as described in RFC 2689) in Acct Interim Update or Stop messages.

26.6527.21

Alc-Acct-O-Inprof-Octets-64

Identifies a charging group, app-group, application or sub-aggregate and its corresponding total to-sub admitted bytes. Reports cumulative volume of preconfigured AA-subscriber charging group, app-group or application since the start of the session (as described in RFC 2689) in Acct Interim Update or Acct Stop messages.

26.6527.23

Alc-Acct-I-Inprof-Pkts-64

Identifies a charging group, app-group or application and its corresponding total from-sub admitted packets. Reports cumulative volume of preconfigured AA-subscriber charging group, app-group or application since the start of the session (as described in RFC 2689) in Acct Interim Update or Acct Stop messages.

26.6527.25

Alc-Acct-O-Inprof-Pkts-64

Identifies a charging group, app-group or application and its corresponding total to-sub admitted packets. Reports cumulative volume of preconfigured AA-subscriber charging group, app-group or application since the start of the session (as described in RFC 2689) in Acct Interim Update or Acct Stop messages.

26.6527.45

Alc-App-Prof-Str

Designates the AA-subscriber current application profile. Sent in all Acct Start, Interim Update and Stop messages.

26.6527.156

Alc-AA-Group-Partition-Isa-Id

Designates the AA Group/partition and the ISA card assigned to the AA-subscriber reported in the Accounting Statistics. Sent in all Acct requests. The ISA ID allows to monitor ISA card switch over.

26.6527.157

Alc-AA-Peer-Identifier

Specifies Application-Assurance RADIUS Peer Information and used by the PCRF to autodiscover redundant AA nodes. When AA Seen IP (Seen-IP transit subscriber notification provides RADIUS Accounting Start notification of the IP addresses and location of active subscribers within a parent AA service) is used together with AARP (removal of routing asymmetry when using redundant transit-aa-nodes), for example, having two redundant transit 7750 SR nodes, PCRF pushes a CoA create message to both 7750 SR nodes. This is achieved by adding the peer-identifier information in the original Accounting-start sent by the primary 7750 SR.

Table 17. Application Assurance accounting (limits)
Attribute ID Attribute name Type Limits SR OS format

1

User-Name

string

32 chars

# format varies with the aa-sub type

For example:

# sap formataa-sub: 1/1/6:61.2# spoke-sdp formataa-sub : 4:100# esm or transit formataa-sub: user1@domain1.com

4

NAS-IP-Address

ipaddr

4 bytes

For example:

# ip-address 10.1.1.1NAS-IP-Address 0a010101

32

NAS-Identifier

string

64 chars

For example: N

AS-Identifier = PE1-Antwerp

40

Acct-Status-Type

integer

4

1=Start, 2=Stop, 3=Interim Update, 7=Accounting-On, 8=Accounting-Off

44

Acct-Session-Id

string

22 bytes

<subscriber-type>|<Alc-Subsc-ID-str>where <subscriber-type> = esm, esm-mac or transit

For example:

Acct-Session-Id = esm|ipoe_sub_08

49

Acct-Terminate-Cause

integer

4 bytes

# Supported causes: 1=User-Request, 2=Lost-Carrier, 3=Lost-Service, 4=Idle-Timeout, 5=Session-Timeout, 6=Admin-Reset, 8=Port-Error, 10=NAS-Request, 15=Service-Unavailable# See table Acct Terminate Cause for complete overview

For example:

Acct-Terminate-Cause = User-Request

55

Event-Timestamp

date

4 bytes

For example:

# Jul 6 2012 17:28:23 CEST is reported as 4FF70417Event-Timestamp = 4FF70417

26.6527.11

Alc-Subsc-ID-Str

string

32 char

<aa-subscriber text name>

For example:

Scope = subscriber:

Alc-Subsc-ID-Str = ipoe_sub_08

Scope = mac

Alc-Subsc-ID-Str = ipoe_sub_08-000102030405

Scope = mac, with subId = "ipoe_sub_012345678901234" truncated to 19 chars:

Alc-Subsc-ID-Str = ipoe_sub_0123456789+000102030405

26.6527.19

Alc-Acct-I-Inprof-Octets-64

octets

10 bytes

<Type of second byte 1 Byte><export-id 1 Byte><8 Byte value>

Where:

<Type of second byte> = 0x40 indicates byte 2 is AA charging-group export-id

<Type of second byte> = 0x50 indicates byte 2 is AA app-group export-id

<Type of second byte> = 0x60 indicates byte 2 is AA application export-id

<Type of second byte> = 0x70 indicates byte 2 is sub-aggregate export-id (=1)

<export-id> =<1 to 255>

For example:

500 bytes reported in CG id 2

Alc-Acct- I-Inprof-Octets-64 = 0x400200000000000001f4

26.6527.21

Alc-Acct-O-Inprof-Octets-64

octets

10 bytes

<Type of second byte 1 Byte><export-id 1 Byte><8 Byte value>

Where:

<Type of second byte> = 0x40 indicates byte 2 is AA charging-group export-id

<Type of second byte> = 0x50 indicates byte 2 is AA app-group export-id

<Type of second byte> = 0x60 indicates byte 2 is AA application export-id

<Type of second byte> = 0x70 indicates byte 2 is sub-aggregate export-id (=1)

<export-id> = <1 to 255>

For example:

Alc-Acct-O-Inprof-Octets-64 = 0x40020000000000651d26

26.6527.23

Alc-Acct-I-Inprof-Pkts-64

octets

10 bytes

<Type of second byte 1 Byte ><export-id 1 Byte><8 Byte value>

Where

<Type of second byte> = 0x40 indicates byte 2 is AA charging-group export-id

<Type of second byte> = 0x50 indicates byte 2 is AA app-group export-id

<Type of second byte> = 0x60 indicates byte 2 is AA application export-id

<export-id> = <1…255>

For example:

Alc-Acct-I-Inprof-Pkts-64 = 0x4002000000001acae3e7

26.6527.25

Alc-Acct-O-Inprof-Pkts-64

octets

10 bytes

<Type of second byte 1 Byte ><export-id 1 Byte><8 Byte value>

Where

<Type of second byte > =0x40 indicates byte 2 is AA charging-group export-id

<Type of second byte> = 0x50 indicates byte 2 is AA app-group export-id

<Type of second byte> = 0x60 indicates byte 2 is AA application export-id

< export-id> = <1 to 255>

For example:

Alc-Acct-O-Inprof-Pkts-64 = 0x400200000000004368c4

26.6527.45

Alc-App-Prof-Str

string

16 char

For example:

Alc-App-Prof-Str = MyAppProfile

26.6527.156

Alc-AA-Group-Partition-Isa-Id

string

no limits

<Group ID>:<Partition ID>:<ISA slot>/<ISA MDA>

For example:

Alc-AA-Group-Partition-Isa-Id = 2:4:3/2

26.6527.157

Alc-AA-Peer-Identifier

string

no limits

<AARP ID>@<Peer IP address>@<Peer Port-id>

For example:

# system-ip 10.1.1.2 remote redundant transit-aa-node Alc-AA-Peer-Identifier = 200@10.1.1.2@1/1/1/4:200

Table 18. Application Assurance accounting (applicability)
Attribute ID Attribute name Acct start Acct stop Acct interim-update Acct on Acct off

1

User-Name

1

1

1

0

0

4

NAS-IP-Address

1

1

1

1

1

32

NAS-Identifier

1

1

1

1

1

40

Acct-Status-Type

1

1

1

1

1

44

Acct-Session-Id

1

1

1

0

0

49

Acct-Terminate-Cause

0

0-1

0

0

0

55

Event-Timestamp

1

1

1

1

1

26.6527.11

Alc-Subsc-ID-Str

1

1

1

0

0

26.6527.19

Alc-Acct-I-Inprof-Octets-64

0

0-1

0-1

0

0

26.6527.21

Alc-Acct-O-Inprof-Octets-64

0

0-1

0-1

0

0

26.6527.23

Alc-Acct-I-Inprof-Pkts-64

0

0-1

0-1

0

0

26.6527.25

Alc-Acct-O-Inprof-Pkts-64

0

0-1

0-1

0

0

26.6527.45

Alc-App-Prof-Str

1

1

1

0

0

26.6527.156

Alc-AA-Group-Partition-Isa-Id

1

1

1

1

1

26.6527.157

Alc-AA-Peer-Identifier

0-1

0

0

0

0

Dynamic data service accounting

This section specifies the attributes for RADIUS accounting on dynamic data service SAPs. The attributes for RADIUS accounting of the associated control channel is identical as the ESM accounting case (see ESM accounting.

Table 19. Dynamic data service accounting (description)
Attribute ID Attribute name Description

1

User-Name

Dynamic data services associated with an ESM control channel:

  • The RADIUS username from the Dynamic Data Service Control Channel associated with this Dynamic Data Service SAP accounting session

Dynamic data services associated with a dynamic service data trigger:

  • The dynamic data services sap-id

4

NAS-IP-Address

The identifying IP Address of the NAS requesting the Authentication or Accounting. Included when the RADIUS server is reachable using IPv4.

The address is determined by the routing instance through which the RADIUS server can be reached:

‟Management” — The active IPv4 address in the Boot Options File (bof address ipv4-address)

‟Base” or ‟VPRN” — The IPv4 address of the system interface (configure router interface system address address).

The address can be overwritten with the configured source-address (configure aaa radius-server-policy policy-name servers source-address ip-address)

25

Class

(Dynamic Data Services associated with an ESM control channel only)

The Class attributes from the Dynamic Data Service Control Channel associated with this Dynamic Data Service SAP accounting session

32

NAS-Identifier

A string (configure system name system-name) identifying the NAS originating the Accounting requests.

40

Acct-Status-Type

Indicates whether this Accounting-Request marks the beginning of the user service (Start) or the end (Stop) or reports interim updates.

41

Acct-Delay-Time

Indicates how many seconds the client has been trying to send this accounting record for. This attribute is included with value 0 in all initial accounting messages.

44

Acct-Session-Id

Unique generated hexadecimal number that represents the accounting session for this Dynamic Data Service SAP.

46

Acct-Session-Time

The Acct-Session-Time time is started when the corresponding dynamic data service sap is created. The Acct-Session-Time is stopped when the corresponding dynamic data service SAP is deleted. When the SAP is orphaned (not deleted in the teardown function call), the session time stops after the teardown script is executed. If an accounting stop is sent as a result of a failure scenario, the Acct-Session-Time is zero.

49

Acct-Terminate-Cause

Indicates how the accounting session was terminated.

50

Acct-Multi-Session-Id

Dynamic data services associated with and ESM control channel:

  • Accounting session ID of the associated Control Channel (session acct-session-id for PPPoE or IPoE sessions and host acct-session-id for IPoE hosts)

Dynamic data services associated with a dynamic service data trigger:

  • Accounting session ID of the associated dynamic services data trigger (send in Access-Request in case of RADIUS authentication)

55

Event-Timestamp

Record the time that this event occurred on the NAS, in seconds since January 1, 1970 00:00 UTC

87

NAS-Port-Id

The Dynamic Data Service SAP where this accounting session is started for

95

NAS-IPv6-Address

The identifying IP Address of the NAS requesting the Authentication or Accounting. Included when the RADIUS server is reachable using IPv6.

The address is determined by the routing instance through which the RADIUS server can be reached:

‟Management” — The active IPv6 address in the Boot Options File (bof address ipv6-address)

‟Base” or ‟VPRN”— The IPv6 address of the system interface (configure router interface system ipv6 address ipv6-address).

The address can be overwritten with the configured ipv6-source-address (configure aaa radius-server-policy policy-name servers ipv6-source-address ipv6-address)

26.3561.1

Agent-Circuit-Id

(Dynamic Data Services associated with an ESM control channel only)

The Agent-Circuit-Id attribute from the Dynamic Data Service Control Channel associated with this Dynamic Data Service SAP accounting session

26.3561.2

Agent-Remote-Id

(Dynamic Data Services associated with an ESM control channel only)

The Agent-Remote-Id attribute from the Dynamic Data Service Control Channel associated with this Dynamic Data Service SAP accounting session

26.6527.165

Alc-Dyn-Serv-Script-Params

Parameters as input to the Dynamic Data Service Python script. The parameters can cross an attribute boundary. The concatenation of all Alc-Dyn-Serv-Script-Params attributes with the same tag in a single message must be formatted as function-key dictionary where the function-key specifies which Python functions are called and dictionary contains the actual parameters in a Python dictionary structure format.

In dynamic service RADIUS accounting messages, the attribute is sent untagged and contains the last received Alc-Dyn-Serv-Script-Params value in an Access-Accept or CoA message for this dynamic service. Multiple attributes may be present if the total length does not fit a single attribute.

Table 20. Dynamic data service accounting (limits)
Attribute ID Attribute name Type Limits SR OS format

1

User-Name

string

253 chars

For dynamic data services associated with an ESM control channel, the format depends on authentication method and configuration.

For dynamic data services associated with a dynamic service data trigger, the format is fixed to the dynamic services sap-id.

For example:

User-Name user1@domain1.com

4

NAS-IP-Address

ipaddr

4 bytes

# ip-address

For example:

NAS-IP-Address ‟192.0.2.1”

25

Class

octets

Up to 6 attributes. Max. value length for each attribute is 253 chars

For example:

Class = ‟This is a Class attribute”

32

NAS-Identifier

string

64 chars

For example:

NAS-Identifier = router-1

40

Acct-Status-Type

integer

4

1=Start, 2=Stop, 3=Interim Update, 7=Accounting-On, 8=Accounting-Off, 9=Tunnel-Start, 10=Tunnel-Stop, 11=Tunnel-Reject, 12=Tunnel-Link-Start, 13=Tunnel-Link-Stop, 14=Tunnel-Link-Reject, 15=Failed

41

Acct-Delay-Time

integer

4294967295 seconds

For example:

# initial accounting start Acct-Delay-Time = 0# no ack and retry after 5 secondsAcct-Delay-Time = 5

44

Acct-Session-Id

string

22 bytes

For example:

# Acct-Session-Id = 24ADFF0000000950C5F138 Acct-Session-Id 0x32313238343633353932313032353132313133343039

46

Acct-Session-Time

integer

42949672 seconds

The attribute value wraps after approximately 497 days

For example:

Acct-Session-Time = 870

49

Acct-Terminate-Cause

integer

4 bytes

Supported causes: 1=User-Request, 2=Lost-Carrier, 3=Lost-Service, 4=Idle-Timeout, 5=Session-Timeout, 6=Admin-Reset, 8=Port-Error, 10=NAS-Request, 15=Service-Unavailable See also table Acct Terminate Cause for complete overview

For example:

Acct-Terminate-Cause = User-Request

50

Acct-Multi-Session-Id

string

22 bytes

For example:

Acct-Multi-Session-Id = 24ADFF0000000250C8EA5E

55

Event-Timestamp

date

4 bytes

For example:

# Jul 6 2012 17:28:23 CEST is reported as 4FF70417Event-Timestamp = 4FF70417

87

NAS-Port-Id

string

253 bytes

Ethernet SAPs: <slot>/<mda>/<port>:<vlan>.<vlan>

For example:

NAS-Port-Id = 1/1/4:50:100

95

NAS-IPv6-Address

ipv6addr

16 bytes

# ipv6-address

For example:

NAS-IPv6-Address = 2001:db8::1

26.3561.1

Agent-Circuit-Id

string

247 chars

Format, see also RFC 4679 # Ethernet/DSL <Access-Node-Identifier><eth slot/port[:vlan-id]>

For example:

ethernet dslam1 slot 2 port 1 vlan 100Agent-Circuit-Id = dslam1 eth 2/1:100

26.3561.2

Agent-Remote-Id

string

247 chars

format see also RFC 4679

For example:

Agent-Remote-Id = MyRemoteId

26.6527.165

Alc-Dyn-Serv-Script-Params

string

multiple VSAs per tag per message. Max length of concatenated strings per tag = 1000 bytes

The script parameters may be continued across attribute boundaries. The concatenated string must have following format: ‟function-key”=<dictionary> where ‟function-key” specifies which Python functions are used and <dictionary> contains the actual parameters in a Python dictionary structure format.

For example:

Alc-Dyn-Serv-Script-Params:1 = ‟data_svc_1 = { 'as_id' : '100', 'comm_id' : '200', 'if_name' : 'itf1', 'ipv4_address' : '192.168.1.1', 'egr_ip_filter' : '100' , 'routes' : [{'to' : '172.16.1.0/24', 'next-hop' : '192.168.2.2'}, {'to' : '172.16.2.0/24', 'next-hop' : '192.168.2.2'}]}

Table 21. Dynamic data service accounting (applicability)
Attribute ID Attribute name Acct start Acct stop Acct interim-update

1

User-Name

1

1

1

4

NAS-IP-Address

0-1

0-1

0-1

25

Class

0+

0+

0+

32

NAS-Identifier

1

1

1

40

Acct-Status-Type

1

1

1

41

Acct-Delay-Time

1

1

1

44

Acct-Session-Id

1

1

1

46

Acct-Session-Time

0

1

1

49

Acct-Terminate-Cause

0

1

0

50

Acct-Multi-Session-Id

1

1

1

55

Event-Timestamp

1

1

1

87

NAS-Port-Id

1

1

1

95

NAS-IPv6-Address

0-1

0-1

0-1

26.3561.1

Agent-Circuit-Id

0-1

0-1

0-1

26.3561.2

Agent-Remote-Id

0-1

0-1

0-1

26.6527.165

Alc-Dyn-Serv-Script-Params

1+

1+

1+

CLI user access accounting

Table 22. CLI user access accounting (description)
Attribute ID Attribute name Description

1

User-Name

The name of user requesting user-Authentication, Authorization, Accounting. Usernames longer the allowed maximum Limit are treated as an authentication failure.

4

NAS-IP-Address

The identifying IP Address of the NAS requesting the Authentication or Accounting. Included when the RADIUS server is reachable using IPv4.

The address is determined by the routing instance through which the RADIUS server can be reached:

‟Management” — The active IPv4 address in the Boot Options File (bof address ipv4-address)

‟Base” — The IPv4 address of the system interface (configure router interface system address address). The address can be overwritten with the configured source-address (configure system security source-address application radius ip-int-name | ip-address)

31

Calling-Station-Id

The IP address (coded in hex) from the user that requests Authentication, Authorization, Accounting.

44

Acct-Session-Id

A unique number generated per authenticated user and reported in all accounting messages. Used to correlate CLI commands (accounting data) from the same user.

61

NAS-Port-Type

Mandatory included as type Virtual(5).

95

NAS-IPv6-Address

The identifying IP Address of the NAS requesting the Authentication or Accounting. Included when the RADIUS server is reachable using IPv6.

The address is determined by the routing instance through which the RADIUS server can be reached:

‟Management” — The active IPv6 address in the Boot Options File (bof address ipv6-address)

‟Base” — The IPv6 address of the system interface (configure router interface system ipv6 address ipv6-address). The address can be overwritten with the configured ipv6-source-address (configure system security source-address application6 radius ipv6-address)

26.6527.6

Timetra-Cmd

A command string, subtree command string or a list of command strings as scope for the match condition for user authorization. Multiple command strings in the same attribute are delimited with the; character. Additional command strings are encoded in multiple attributes. If the maximum number of command strings is violated, or if a string is too long, processing the input is stopped but authorization continues, so if the RADIUS server is configured to have five command strings of which the third is too long, only the first two entries are used and the rest are ignored. Each [26.6527.6] Timetra-Cmd attribute is followed in sequence by a [26.6527.7] Timetra-Action. (A missing Timetra-Action results in a deny.)

Note - For each authenticated RADIUS user a temporary profile with name [1]User-Name is always created (show system security profile) and executed as last profile. This temporary profile is built from the mandatory attribute [26.6527.5]Timetra-Default-Action and optional attributes [26.6527.6] Timetra-Cmd, [26.6527.7] Timetra-Action.

Table 23. CLI user access accounting (limits)
Attribute ID Attribute name Type Limits SR OS format

1

User-Name

string

16 chars

For example:

User-Name = ‟admin”

4

NAS-IP-Address

ipaddr

4 bytes

For example:

NAS-IP-Address= ‟192.0.2.1”

31

Calling-Station-Id

string

64 bytes

# users ip address

For example:

Calling-Station-Id= ‟192.0.2.2” or

Calling-Station-Id= ‟2001:db8 to 2”

44

Acct-Session-Id

string

22 bytes

For example:

Acct-Session-Id = ‟2128463592102512113409”

61

NAS-Port-Type

integer

4 bytes

value 5 fixed

Fixed set to value virtual (5)

For example:

NAS-Port-Type 00000005

95

NAS-IPv6-Address

ipv6addr

16 bytes

For example:

NAS-IPv6-Address = 2001:db8::1

26.6527.6

Timetra-Cmd

string

25 attributes

247 chars/attribute

For example:

Timetra-Cmd += configure router isis;show subscriber-mgmt sub-profile

Timetra-Cmd += show router

Table 24. CLI user access accounting (applicability)
Attribute ID Attribute name Acct start Acct stop

1

User-Name

1

1

4

NAS-IP-Address

0-1

0-1

31

Calling-Station-Id

1

1

44

Acct-Session-Id

1

1

61

NAS-Port-Type

1

1

95

NAS-IPv6-Address

0-1

0-1

26.6527.6

Timetra-Cmd

1

1

IPsec accounting

This section provides details for the RADIUS attributes used in IPsec accounting.

Table 25. IPsec accounting (description)
Attribute ID Attribute name Description

1

User-Name

For IKEv1 remote-access tunnel, this represents the xauth username.

For IKEv2 remote-access tunnel, this represents the identity of the peer; the value of User-Name is the received IDi in IKEv2 message.

4

NAS-IP-Address

The identifying IP Address of the NAS requesting the Accounting.

The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute nas-ip-addr.

8

Framed-IP- Address

The IPv4 address to be assigned to IKEv1 or IKEv2 remote-access tunnel client using configuration payload: INTERNAL_IP4_ADDRESS. This attribute is reflected in RADIUS accounting request packet for IKEv2 tunnel. The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute framed-ip-addr.

30

Called-Station-Id

The local gateway address of IKEv2 remote-access tunnel. The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute called-station-id.

31

Calling-Station-Id

The peer's address and port of IKEv2 remote-access tunnel.

The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute calling-station-id.

32

NAS-Identifier

A string (configure system name system-name) identifying the NAS originating the Accounting requests.

The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute nas-identifier.

44

Acct-Session-Id

A unique identifier representing an IKEv2 remote-access tunnel session that is authenticated. Same Acct-Session-Id is included in both access- request and accounting-request.

46

Acct-Session-Time

This attribute represents the tunnel's lifetime in seconds. It is included in an Accounting-Stop packet.

87

Nas-Port-Id

The public SAP ID of IKEv2 remote-access tunnel. The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute nas-port-id.

97

Framed-IPv6-Prefix

The IPv6 address to be assigned to IKEv2 remote-access tunnel client using IKEv2 configuration payload: INTERNAL_IP6_ADDRESS. The prefix and prefix-length of Framed-IPv6-Prefix are conveyed in the corresponding part of INTERNAL_IP6_ADDRESS. The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute framed-ipv6-prefix.

241.26.6527.41

Alc-Acct-IPsec-Bidir-Kibibytes

(IKEv2 RA tunnel only) The number of kilobytes of bidirectional (encryption + decryption) traffic passed over the IPsec tunnel.

The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute acct-stats.

241.26.6527.42

Alc-Acct-IPsec-Encrypted-Kibibytes

(IKEv2 RA tunnel only) The number of kilobytes of encrypted traffic passed over the IPsec tunnel.

The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute acct-stats.

241.26.6527.43

Alc-Acct-IPsec-Decrypted-Kibibytes

(IKEv2 RA tunnel only) The number of kilobytes of decrypted traffic passed over the IPsec tunnel.

The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute acct-stats.

241.26.6527.44

Alc-Acct-IPsec-Bidir-Packets

(IKEv2 RA tunnel only) The number of packets of bidirectional (encryption + decryption) passed over the IPsec tunnel.

The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute acct-stats.

241.26.6527.45

Alc-Acct-IPsec-Encrypted-Packets

(IKEv2 RA tunnel only) The number of encrypted packets passed over the IPsec tunnel.

The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute acct-stats.

241.26.6527.46

Alc-Acct-IPsec-Decrypted-Packets

(IKEv2 RA tunnel only) The number of decrypted packets passed over the IPsec tunnel.

The attribute can be included or excluded with configure ipsec radius-accounting-policy name include-radius-attribute acct-stats.

Table 26. IPsec accounting (limits)
Attribute ID Attribute name Type Limits SR OS format

1

User-Name

string

253 bytes

Format depends on IDi format.

For example:

User-Name = "user1@domain1.com"

4

NAS-IP-Address

ipaddr

4 bytes

For example:

NAS-IP-Address=192.0.2.1

8

Framed-IP-Address

ipaddr

4 bytes

For example:

Framed-IP-Address = 192.168.10.100

30

Called-Station-Id

string

253 bytes

local gateway address of IKEv2 remote-access tunnel

For example:

Called-Station-Id = "172.16.100.1"

31

Calling-Station-Id

string

253 bytes

peer-address:port

For example:

Calling-Station-Id = "192.168.5.100:500"

32

NAS-Identifier

string

64 char

For example:

NAS-Identifier = "pe1"

44

Acct-Session-Id

string

147 bytes

local_gw_ip-remote_ip:remote_port-time_stamp

For example:

Acct-Session-Id =

172.16.100.1-192.168.5.100:500-1365016423

46

Acct-Session-Time

integer

4 bytes

4294967295

seconds

For example:

Acct-Session-Time = 870

87

Nas-Port-Id

string

44 bytes

For example:

Nas-Port-Id = "tunnel-1.public:100"

97

Framed-IPv6-Prefix

ipv6prefix

max. 16 bytes for prefix + 1 byte for length

For example:

Framed-IPv6-Prefix =

2001:DB8:CAFE:1::100/128

241.26.6527.41

Alc-Acct-IPsec-Bidir- Kibibytes

integer64

8 bytes

For example:

Alc-Acct-IPsec-Bidir-Kibibytes = 2000

241.26.6527.42

Alc-Acct-IPsec- Encrypted-Kibibytes

integer64

8 bytes

For example:

Alc-Acct-IPsec-Encrypted-Kibibytes

= 1000

241.26.6527.43

Alc-Acct-IPsec- Decrypted-Kibibytes

integer64

8 bytes