Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Enabling Export of Subscriber Statistics and Queue Statistics for Dynamic Interfaces and Interface-Sets

Understanding Enabling Export of Subscriber Statistics and Queue Statistics for Dynamic Interfaces and Interface-Sets

You can use subscriber statistics and queue statistics for dynamic interfaces and interface-sets to support remote analytics and monitor Juniper devices that operate as a Broadband Network Gateway (BNG). Using these statistics, you can model and condition traffic flows in a subscriber access network.

About Subscriber and Queue Statistics

Subscriber statistics include the per-IP protocol family (IPv4 or IPv6) packet information (receive and transmitted packets and bytes) for a subscriber interface. They will only include subscriber data forwarded by the system. Filtered and dropped packets and control traffic are factored out and not delivered.

ON-CHANGE subscription support for interface meta-data sends asynchronous notifications when interfaces are created and deleted. After an initial baseline of delivering create notifications for all existing interfaces, only notifications for interfaces that are being created or deleted are sent to an external collector.

Use queue statistics to determine oversubscription levels, the mix of forwarding-class traffic, or traffic rates for a given CoS-enabled interface or interface-set.

Enabling Export of Statistics

To receive statistics, you enable both meta-data and statistical data for export on your Juniper device through the Junos CLI. Meta-data for the interface is provided because the interface key is a dynamic integer, a session identifier (SID), which conveys no context to an external server. The meta-data provides more tangible context (such as the user name, a profile name VLAN tags, etc.) to the SID. An external collector associates the statistical data to a persistent reference.

A subscription for both statistical data and meta-data can be made from the external collector (in Figure 1, the JTI collector). In this way, the two streams are “merged” and a correlation is made between the statistical data and the meta-data. The dynamic SID is matched with the more permanent attributes such as user name and location.

Figure 1: JTI Collector “Merging” Sensor DataJTI Collector “Merging” Sensor Data

Enable Export of Subscriber Statistics and Queue Statistics

You can enable the telemetry export of subscriber statistics and queue statistics for dynamic interfaces and interface-sets. After you enable telemetry for these statistics, they are eligible for export to one or more collectors using a remote procedure call (gRPC) subscription.

Use these statistics to model and condition traffic flows in a subscriber access network and to provide subscriber statistics information (accurate accounting).

To enable the export of subscriber statistics and associated interface meta-data:

  1. Enable export of interface meta-data and subscriber statistics:
  2. Enable the logical demultiplexing (demux) interface in a dynamic profile to export subscriber accurate statistics:

To enable export of interface meta-data and queue statistics for dynamic interfaces:

  1. Enable export of interface meta-data and interface queue statistics. Use the profile variable $junos-interface-name.

    Note:

    the profile variables $junos-interface-name and $junos-interface-set-name are generated from the corresponding device, unit and interface-set elements in the interfaces stanza at profile instantiation time. Using these derived variables is a convenient way to configure telemetry behavior for the interface or interface-set without the need to mimic the specific configuration in the interfaces stanza.

  2. To override the default internal queue-stats collection interval of 900 seconds or the default queue export filter (all queues, 0-7), add the rate and queues statements.

To enable export of interface-set meta-data and queue statistics for dynamic interface-sets:

  1. Enable export of interface-set meta-data and interface-set queue statistics. Use the profile variable $junos-interface-set-name.

    Note:

    the profile variables $junos-interface-name and $junos-interface-set-name are generated from the corresponding device, unit and interface-set elements in the interfaces stanza at profile instantiation time. Using these derived variables is a convenient way to configure telemetry behavior for the interface or interface-set without the need to mimic the specific configuration in the interfaces stanza.

  2. To override the default internal queue-stats collection interval of 900 seconds or the default queue export filter (all queues, 0-7), add the rate and queues statements.

After telemetry export is enabled, meta-data and statistics can be streamed to external collectors subscribing to the available resource paths.

Use the resource paths from gRPC Sensors for Subscriber Statistics and Queue Statistics for Dynamic Interfaces and Interface-Sets (Junos Telemetry Interface) for your gRPC subscription.

Guidelines for Exporting Subscriber Statistics and Queue Statistics for Dynamic Interfaces and Interface-Sets

You can use subscriber statistics and queue statistics for dynamic interfaces and interface-sets to support remote analytics and monitoring on MX Series routers that operate as a Broadband Network Gateway (BNG).

Before enabling export of subscriber statistics and queue statistics for dynamic interfaces and interface-sets, consider the following limitations:

  • On MX Series routers supporting the Modular Port Concentrator 2 (MPC2), a slow internal refresh cycle for queue statistics can occur. This cycle can be lengthy at full line card scale. If the subscription frequency is higher than the internal refresh cycle, exported data may appear stale across reporting intervals.

  • The unified in-service software upgrade (ISSU) feature enables you to upgrade your device between two different Junos OS releases with no disruption on the control plane and with minimal disruption of traffic. Dynamic interfaces and Interface-sets created prior to ISSU and prior to Junos OS Release 18.4R1 do not support telemetry for subscriber and queue statistics.

  • The subscription frequency should be larger than the time to export telemetry. If the volume of data cannot be exported before the next reporting interval, the export continues to completion and the next reporting interval will immediately start. in such instances, continuous streaming results–behavior that may not be wanted.

  • Multiple sensors from the dynamic-interfces sub-tree may be subscribed to simultaneously. As streaming of these sensors for the sub-tree is supported by a single Junos component, you should expect the time to export the sensor data for each subscription to extend.

  • Juniper advises to enable export only for active queues. To do this, include the queues statement at the [[edit dynamic-profiles profile-name telemetryqueue-statistics $junos-interface-name] or [[edit dynamic-profiles profile-name telemetry queue-statistics $junos-interface-set-name] hierarchy level. Exporting data for active queues only reduces the amount of data to export for each reporting interval.

gRPC Sensors for Subscriber Statistics and Queue Statistics for Dynamic Interfaces and Interface-Sets (Junos Telemetry Interface)

Starting with Junos OS Release 18.4R1, MX Series routers are supported.

You can use subscriber statistics and queue statistics for dynamic interfaces and interface-sets to support remote analytics and monitoring on Juniper devices that operate as a Broadband Network Gateway (BNG). Using these statistics, you can model and condition traffic flows in a subscriber access network.

Figure 2 shows the structure of the sensors or resource paths used for subscription to the external collector. The resource paths are a combination of both meta-data and statistical data.

Figure 2: Structure of SensorsStructure of Sensors

For statistics delivery through a gRPC subscription, include one or more resource paths from Table 1 in the subscription. For statistics delivered through gRPC, you will also need to install some additional software enable statistics to be exported on your Juniper device through the Junos CLI. For more information, see Enable Export of Subscriber Statistics and Queue Statistics. For more information about creating a subscription, see Configure a NETCONF Proxy Telemetry Sensor in Junos.

Table 1: gRPC Sensors

resource path

Description

/junos/system/subscriber-management/dynamic-interfaces/interface-sets/meta-data/interface-set[container-id='container-id-value']/

Sensor for subscriber interface-set information.

This sensor is supported on MX Series routers starting with Junos OS Release 18.4R1.

ON-CHANGE streaming is supported.

The following end paths are supported:

  • cos-egress-tcp-name-The egress traffic control profile associated with this interface-set.

  • cos-egress-tcp-remainder-name-The egress remainder traffic control profile associated with this interface-set.

  • interface-set-name-The name of the interface-set as supplied by AAA or as constructed by the topology relationship (ACI string or interface stacking).

  • interface-set-type-The type of interface-set (determines structure of interface-set-name).

  • device-name-The name of the underlying device or port (e.g. ge-1/0/0 or ae1). This leaf is empty if the interface-set-type is not a physical interface-set type.

  • stag-The outer VLAN tag. The value is 0 if interface-set-type is not a VLAN type.

  • ctag-The inner VLAN tag. The value is 0 if interface-set-type is not a VLAN type.

/junos/system/subscriber-management/dynamic-interfaces/interfaces/meta-data/interface[sid='sid-value']/

Sensor for subscriber interface information.

ON-CHANGE streaming is supported.

The following end paths are supported:

  • interface-index-The system assigned interface index for the interface.

  • session-type-The type of client session (e.g VLAN, DHCP, PPPoE).

  • user-name-The login name for this interface and session.

  • profile-name-The name of the client profile used to create the interface.

  • underlying-interface-name-The name of the associated underlying interface.

  • cvlan-tag-The innermost VLAN tag value associated with the interface.

  • svlan-tag-The outermost VLAN tag value associated with the interface.

/junos/system/subscriber-management/dynamic-interfaces/interfaces/subscriber-statistics/interface[sid='sid-value']/

Sensor for actual accounting statistics for dynamic subscriber interfaces.

The following end paths are supported:

  • ip-in-packets-The number of actual transit IPv4 & IPv6 packets received by the interface.

  • ip-out-packets-The number of actual transit IPv4 & IPv6 packets sent to the interface.

  • ip-in-bytes-The number of actual transit IPv4 & IPv6 bytes received by the interface.

  • ip-out-bytes-The number of actual transit IPv4 & IPv6 bytes received by the interface.

  • ipv6-in-packets-The number of actual transit IPv6 packets received by the interface.

  • ipv6-out-packets-The number of actual transit IPv6 packets sent to the interface.

  • ipv6-in-bytes-The number of actual transit IPv6 bytes received by the interface.

  • ipv6-out-bytes-The number of actual transit IPv6 bytes sent to the interface.

/junos/system/subscriber-management/dynamic-interfaces/interfaces/queue-statistics/interface[sid='sid-value']/fpcs/fpc[slot=’slot-value’]/queues/queue/[queue-no=’queue-no-value’]/

Sensor for queue statistics for dynamic interfaces.

The following end paths are supported:

  • transmitted-packets-The number of actual transit IPv4 & IPv6 packets received by the interface.

  • transmitted-bytes-Total bytes enqueued for this queue.

  • dropped-packets-Total packets dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

  • dropped-bytes-Total bytes dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

/junos/system/subscriber-management/dynamic-interfaces/interface-sets/queue-statistics/interface-set[container-id='container-id-value']/fpcs/fpc[slot=’slot-value’]/queues/queue/[queue-no=’queue-no-value’]/

Sensor for queue statistics for dynamic interface-sets.

The following end paths are supported:

  • transmitted-packets-The number of actual transit IPv4 & IPv6 packets received by the interface.

  • transmitted-bytes-Total bytes enqueued for this queue.

  • dropped-packets-Total packets dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

  • dropped-bytes-Total bytes dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

Release History Table
Release
Description
18.4R1
Starting with Junos OS Release 18.4R1, MX Series routers are supported.