Junos Telemetry

Enhance VLAN/MAC statistics support for streaming telemetry (EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48MXP, EX4400-48XP, EX4400-48P, EX4400-48T, EX4650, EX4650-48Y-VC, EX9204, EX9208, EX9214, QFX5120-48Y, QFX5120-48Y-VC)You can enhance the granularity of streaming telemetry by subscribing to specific xpaths of leaf nodes using Yang state models generated from ODL files. This subscription-based model provides precise and efficient data collection compared to the traditional RPC mechanism. Note that this solution supports only periodic streaming of telemetry data.

For more information, see Junos YANG Data Model Explorer.

Sensor support for secure and dynamic packet capture (EX2300, EX2300-C, EX2300-MP, and EX2300-VC) —EX2300, EX2300-C, EX2300-MP, and EX2300-VC devices support secure and dynamic packet capture. You can use this feature to capture packets from a device and send them over a secure channel to an external telemetry collector (in the cloud) for monitoring and analysis. Network professionals use real-time packet capture data to troubleshoot complex issues, including network and performance degradation, as well as poor end-user experience.

For secure packet capture, the maximum packet size that can be captured is 512 bytes, including the packet header and the data within. To use secure packet capture, include the /junos/system/linecard/ packet-capture resource path using a Junos RPC call.

• For ingress packet capture, include the packet-capture option in the existing firewall filter configuration as follows:

  [edit firewall family family-name filter filter-name term matchterm then packet-capture]

  Use this configuration to send packet capture sensor data to the collector. Remove the packet-capture configuration after the data is sent to the collector. After the capture is done, ingress packets with the filter match conditions are trapped to the CPU. The trapped packets then go to the collector over a secure channel in JTI-specified format in key-value pairs through Remote Procedure Call (gRPC) transport.

• For egress packet capture on physical interfaces (ge-*, xe-*, mge-*, and et-*), include "packet-capture-telemetry," "egress," and "interface <interface-name>" at the [edit forwarding-options] hierarchy level.

  For example:

  set forwarding-options packet-capture-telemetry egress interface ge-0/0/0

  set forwarding-options packet-capture-telemetry egress interface ge-0/0/10

You can add multiple interfaces on the device for egress packet capture. When configured, host-bound egress packets are captured from the interface and sent to the collector. As with the ingress configuration, remove the configuration when packet capture is not required.

For dynamic packet capture, subscribe to the resource path /junos/system/linecard/packet-capture The device starts capturing the first "N" collector-bound packets for each physical interface present on the device when it transitions from the DOWN state to the UP state. The device then sends the packets securely to a collector.

By default, "N" is set as 50. For each interface, 50 ingress and 50 egress packets are captured. The data is captured from a Packet Forwarding Engine sensor and encoded using the Google Protocol Buffer format. The data is then sent over a secure channel using SSL encryption.

The collector receives the following packet attributes: 

For more information, see Junos YANG Data Model Explorer and Supported gRPC and gNMI Sensors.