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

Use subscriber and queue statistics for dynamic interfaces and interface-sets to support remote analytics and monitoring.

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

• On devices supporting the Modular Port Concentrator 2 (MPC2), a slow internal refresh cycle for queue statistics can occur. This refresh cycle can be lengthy at full line-card scale. 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 lets you upgrade devices between two different Junos OS releases with no control-plane disruption and minimal traffic disruption.

• The subscription frequency must exceed the time required to export telemetry. If the volume of data can't be exported before the next reporting interval, the export continues to completion, and the next reporting interval immediately starts. In such scenarios, continuous streaming results—behavior that might not be wanted.

• Multiple sensors from the dynamic-interfaces sub-tree can be subscribed to simultaneously. Because a single Junos component supports streaming of these sub-tree sensors, the time to export the sensor data for each subscription might extend.

• Enable export only for active queues. To enable export only for active queues, 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. This approach reduces the volume of data for each reporting interval.