Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Enable Subscriber and Service Accounting for BNG CUPS Telemetry

Junos Telemetry streams accounting statistics on the Juniper® BNG CUPS (Broadband Network Gateway Control and User Plane Separation) Controller by subscribing to the subscriber sensor. The statistics information includes actual subscriber transit statistics, firewall filter statistics, and subscriber metadata.

Use the following configuration statements to enable telemetry support for subscriber metadata:
  1. Specify the subscriber-info configuration statement to enable streaming of subscriber metadata to an external telemetry server when the subscriber logs into or logs out of the device under test (DUT).
    set dynamic-profiles CLIENT-PROFILE telemetry subscriber-info
  2. Specify the subscriber-statistics option to allow periodic streaming of subscriber accounting statistics such as input packets/octets and output packets/octets to an external telemetry server.
    set dynamic-profiles CLIENT-PROFILE telemetry subscriber-info subscriber-statistics
  3. Specify the service-statistics option to allow periodic streaming of firewall filter statistics for IPv4 and IPv6 filters to an external telemetry server.
    set dynamic-profiles FILTER-PROFILE telemetry subscriber-info service-statistics

    The subscriber-info hierarchy level contains the configuration commands to enable telemetry for subscriber and service statistics. These commands were previously under the dynamic-profiles hierarchy.

Use the following command to check the sensor subscription:

The following table describes the sensor subscription path and their data models:

Table 1: Data models and sensor subscription paths

Data Exported

Sensor Path

Usage Group

Data Model

Subscriber information

/junos/system/subscriber-management/cups/cp-instances/cp- instance/subscribers/subscriber-info

interface-information group

Uses the data model as in Integrated BNG, except data streamed is CP specific.

There are additional fields added to the interface-information group:

PeerSid – This field gives the session ID on the user plane.

User-plane:port – This field gives the user plane name and port on which the session has come up.

SGRP Name– This field gives the SGRP (subscriber group) name of the session.

Device ID– This field gives the device ID of the session.

Subscriber statistics

 /junos/system/subscriber-management/cups/cp-instances/cp-instance/subscribers/accounting-statistics

actual-transit-statistics group

The data model remains same as subscriber-statistics in integrated BNG, except for the sensor subscription path.

Service statistics

/junos/system/subscriber-management/cups/cp-instances/cp-instance/subscribers/service-statistics

service-filter-statistics group

The data model remains same as service-statistics in integrated BNG, except for the sensor subscription path.

Junos Telemetry exports all the above sensor data to an external collector through telemetry for each control plane.

The configuration hierarchy for the dynamic-profiles statement is as follows.

Note:

The subscriber-info configuration statement is mandatory under telemetry. Within the subscriber-info statement, there are two optional configurations: service-statistics and subscriber-statistics.

Related Documentation