Telemetry Data Collection on the IPFIX Mediator for Export to an IPFIX Collector
Starting in Junos OS Release 18.4R1, the input-jti-ipfix plug-in for the IPFIX service agent collects telemetry data from the local Junos Telemetry Interface (JTI) on a BNG configured as an IPFIX mediator. The output-ipfix plug-in translates the gRPC data received from a nonconfigurable set of well-defined sensor types into specific IPFIX records. You configure a record group for the input plug-in that consists of one or more of the predefined IPFIX records. Each record is associated with a specific set of telemetry sensors on the BNG, as listed in Table 1.
IPFIX Record Name |
Sensors Collected by the Record |
|---|---|
address-pool-utilization |
/junos/system/subscriber-management/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance/pools/pool/ |
chassis-inventory |
/components/component[name=’Routing EngineX’]/properties/property[name='fru-model-number'] /components/component[name='FPCx']/properties/property[name='fru-model-number'] /components/component[name='Routing Engine0']/state/id /components/component[name=’FPCx’]/state/id /components/component[name='Routing EngineX']/properties/property[name='hardware-rev']/ /components/component[name=’FPCx’]/properties/property[name='hardware-rev']/ /components/component[name='FPCx']/properties/property[name='software-rev']/ |
chassis-power |
/components/component[name='Chassis']/properties/property[name='power-system-capacity']/ /components/component[name='Chassis']/properties/property[name='power-system-remaining']/ |
dhcpv4-server-statistics |
/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/server/statistics/ |
interface-meta-data |
/junos/system/subscriber-management/dynamic-interfaces/interfaces/meta-data/interface |
interface-queue-statistics |
/junos/system/subscriber-management/dynamic-interfaces/interfaces/queue-statistics/interface |
port-statistics |
/interfaces/interface/state/counters/ |
resource-utilization |
/components/component[name='Routing Engine0']/properties/property[name='memory-dram-used']/ /components/component[name='Routing Engine1']/properties/property[name='memory-dram-used']/ /components/component[name='Routing Engine0']/properties/property[name='memory-dram-installed']/ /components/component[name='Routing Engine1']/properties/property[name='memory-dram-installed']/ /components/component[name='FPCx']/properties/property[name='memory-utilization-heap']/ /components/component[name='Routing Engine0']/properties/property[name='memory-utilization-buffer']/ /components/component[name='Routing Engine1']/properties/property[name='memory-utilization-buffer']/ /components/component[name=’FPCx’]/properties/property[name='memory-utilization-buffer']/ /components/component[name='Routing Engine0']/properties/property[name='cpu-utilization-idle']/ /components/component[name='Routing Engine1']/properties/property[name='cpu-utilization-idle']/ |
subscriber-statistics |
/junos/system/subscriber-management/dynamic-interfaces/interfaces/subscriber-statistics/interface |
thermal |
/components/component[name='Chassis']/properties/property[name='temperature-ambient'] /components/component[name='RoutingEngine0']/properties/property[name='temperature']/state/value /components/component[name='RoutingEngine1']/properties/property[name='temperature']/state/value /components/component[name=FPCx]/properties/property[name='temperature-exhaust-x']/state/value |
uptime |
/components/component[name=’FPCx']/properties/property[name='uptime']/ |
We recommend that you configure the interface-metadata record whenever you configure the interface-queue-statistics record. The metadata information is essential for understanding
details about the subscriber whose queue statistics are being collected.
You can configure the frequency with which data is collected and reported to an IPFIX collector. The reporting interval has a default value, but some telemetry data, such as subscriber statistics, is more dynamic than other data, such as chassis temperature. A shorter reporting interval may be more useful for the more dynamic data. You can configure the reporting interval for the record group, but not for individual records.
The template IDs for the translated gRPC data are drawn from the same template ID space as the IPFIX mediator. Template IDs in the range 256 though 400 are reserved for the translation of telemetry data.
For more information about sensors, see Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).
For detailed information about the Juniper Telemetry Interface, see Junos Telemetry Interface User Guide.
Benefits of Telemetry Data Collection
Leverages the IPFIX mediation structure to collect data about hardware, resources, and user statistics for better remote management of the BNG and subscribers.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.