Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Packet Forwarding Engine and Routing Engine sensor support with JTI (QFX5210)—Starting in Junos OS Release 21.1R1, you can use Junos telemetry interface (JTI) with remote procedure call (gRPC) services to export Packet Forwarding Engine statistics and Routing Engine statistics from QFX5210 switches to an outside collector. These statistics can also be exported through UDP (native) sensors.

    The supported Packet Forwarding Engine sensors are:

    • Sensor for CPU (microkernel) memory (resource path /junos/system/linecard/cpu/memory/)
    • Sensor for firewall filter statistics (resource path /junos/system/linecard/firewall/)
    • Sensor for physical interface traffic (resource path /junos/system/linecard/interface/)
    • Sensor for logical interface traffic (resource path /junos/system/linecard/interface/logical/usage/)
    • Sensor for software-polled queue-monitoring statistics (resource path /junos/system/linecard/qmon-sw/)

    The supported Routing Engine sensors are:

    • Sensor for LACP state export (resource path /lacp/)
    • Sensor for chassis environmentals export (resource path /junos/system/components/component/)
    • Sensor for chassis components export (resource path /components/)
    • Sensor for LLDP statistics export (resource path /lldp/interfaces/interface[name='name’]/)
    • Sensor for BGP peer information export (resource path /network-instances/networkinstance/protocols/protocol/bgp/)
    • Sensor for RPD task memory utilization export (resource path /junos/task-memoryinformation/)
    • Sensor network discovery ARP table state (resource path /arp-information/)
    • Sensor for network discovery NDP table state (resource path /nd6-information/)

    [See Understanding OpenConfig and gRPC on Junos Telemetry Interface.]

  • VCP interchassis link port statistics and optimized queue statistics for aggregated Ethernet bundle support with JTI (MX5, MX10, MX40, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX100016, and vMX)—Starting in Junos OS Release 21.1R1, you can use Junos telemetry interface (JTI) with remote procedure call (gRPC) services to export Virtual Chassis port (VCP) interchassis link statistics and queue statistics. A Virtual Chassis operator can subscribe to supported sensors to monitor the health of MX-VC interchassis links and be able to diagnose and solve issues that may arise when links become unhealthy. This feature also optimizes queue statistics collection, limiting the data and statistical polling to queues that are part of an interface set for which there is an active telemetry subscription. Doing so reduces resources and creates a more stable operating environment.

    The supported new sensors are:

    • Virtual Chassis port sensor, which provides interchassis links basic error and operational state for the interface (resource path /junos/system/mxvc/members/member[memberID=<ID>]/virtual-chassis-ports/virtual-chassis-port[vcp-interface-name=<vcp-interface-port-string>]). This sensor collects the same data displayed when using the operational mode command show interfaces vcp-x/x/x extensive and show virtual-chassis vc-port.
    • Virtual Chassis heartbeat sensor, which provides insight into the overall link health of the Virtual Chassis system (resource path /junos/system/mxvc/members/member[memberID=<ID>]/heartbeat). The Virtual Chassis heartbeat sensor, when active, periodically sends and receives information between the chassis to keep track of the connection state. This sensor collects the same data displayed when using the operational mode command show virtual-chassis heartbeat detail.
    • Virtual Chassis high/low DDoS queue statistics sensor (resource path /junos/system/mxvc/members/member[memberID=<ID>]/ddos-protocols/ddos-protocol[packetType=<packet_type>]/). This sensor tracks high and low statistics used in distributed denial-of-service (DDoS) protection. This sensor is available on the global primary chassis. No sensor output is collected for a backup chassis. This sensor collects the same data displayed when using the operational mode command show ddos-protection protocols virtual-chassis statistics terse.

    • Timestamp sensor (resource path /junos/system/subscriber-management/dynamic-interfaces/interface-sets/queue-statistics/interface-set[container-index=<container-index>]/fpcs/fpc[slot=<slot>]/last-update-time and /junos/system/subscriber-management/dynamic-interfaces/interfaces/queue-statistics/interface[sid=<session-identifier>]/fpcs/fpc[slot=<slot>]/last-update-time ). The timestamp sensor keeps track of when the FPC calculated the queue statistics for a given FPC leg. This provides a better way to track the validity of the data and is a basis for more accurate rate calculations.

    The enhanced sensors are:

    • Per-subscriber queue statistics sensor (resource path /junos/system/subscriber-management/dynamic-interfaces/interfaces/queue-statistics/interface[sid=<session-identifier>]/fpcs/fpc[slot=<slot>]/queues/queue[queue-no=<queue-index>] and /junos/system/subscriber-management/dynamic-interfaces/interface-sets/queue-statistics/interface-set[container-index=<container-index>]/fpcs/fpc[slot=<slot>]/queues/queue[queue-no=<queue-index>] ). This sensor can include the additional leafs current-polling-interfaces and current-polling-interface-sets. When you provide a corresponding index (SID for interface or container ID for interface set), polling for queue statistics is enabled only for that corresponding index. If no index is specified, polling all indexes queue statistics is enabled.

    [See Junos Telemetry Interface User Guide.]

  • Optimized chassis sensor support with JTI (MX2010 and MX2020 with MPC11E and MPC9E line cards)—Starting in Junos OS Release 21.1R1, you can use Junos telemetry interface (JTI) with remote procedure call (gRPC) services to export additional chassis sensors from an MX2010 or MX2020 router to an outside collector.

    For network debugging, there are system-generated logs and SNMP traps available. However, some parameters, such as power entry module (PEM) voltage and PEM supply failure, have not been available in telemetry. We've now introduced these additional system parameters through chassis sensors that support messages logged as part of the SNMP traps for a field-replaceable unit (FRU), fan, PEM, or plane.

    Use the resource path /components/component/properties/property in subscriptions for these additional chassis sensors:
    • power-supply-failed
    • chassisd-pem-breaker-trip
    • chassisd-pem-voltage
    • fan-blower-removed
    • pem-not-powered
    • chassisd-zone-blowers-speed-type
    • chassisd-zone-blowers-speed
    • temprature-back-to-normal
    • over-temprature
    • fru-failed
    • plane-fru-check
    • plane-online

    [See Junos Telemetry Interface User Guide.]