Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Network Management and Monitoring

  • SFlow OpenConfig translation and telemetry enhancement (PTX10008)—We’ve extended the sFlow OpenConfig translation and telemetry functionality. When you configure the first path in an OpenConfig container, all the associated OpenConfig default settings for that container are automatically enabled. The default values are available in the openconfig-sampling-sflow.yang DM.

    This functionality simplifies the configuration process by ensuring that all necessary defaults are in place without requiring additional manual configuration.

    The default sample size is 128 bytes but you can also set an explicit sample size. You can verify the sample size using the run show sflow command.

    [See OpenConfig User Guide.]

  • Sflow support for filter-based UDP and GRE tunnel de-encapsulation (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Use sFlow to monitor ingress and egress traffic profiles for filter-based GRE and UDP tunnel de-encapsulation. sFlow support for UDP tunnel de-encapsulation enhances network monitoring with statistical sampling of network packets through firewall filters. This feature supports IPv4, IPv6, and MPLS payloads, where de-encapsulation and firewall actions are enabled on the ingress side. Key functionalities include de-encapsulation action mapping for preserving payload headers, handling VRF configuration for accurate packet lookup, and determining sample content based on packet structure. The device supports a sampling rate of up to 35,000 samples per second.

    The behavior of sFlow for UDP de-encapsulation is consistent with that of GRE de-encapsulation, providing a unified approach to monitoring across different tunneling methods.

  • Chunked framing support in NETCONF sessions (PTX10008)—Junos devices support the chunked framing mechanism for messages in a NETCONF session. Chunked framing is a standardized framing mechanism that ensures that character sequences within XML elements are not misinterpreted as message boundaries. If you enable RFC 6242 compliance, and both peers advertise the :base:1.1 capability, the NETCONF session uses chunked framing for the remainder of the session. Otherwise, the NETCONF session uses the character sequence ]]>]]> as the message separator.

    [See Configure RFC-Compliant NETCONF Sessions.]

  • Ingress and egress sFlow support for L2 traffic (PTX10001-36MR, PTX10004, PTX10008, PTX10016)— Use sFlow to monitor ingress or egress data and control traffic forwarded through L2 logical interfaces associated with a bridge domain (BD). This feature supports both enterprise and service provider style L2 configurations.

    [See sFlow Technology Overview.]