Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Services Applications

  • Inline active flow monitoring multiple BGP next hop support (MX240, MX480, MX960, MX2010, and MX2020)—Starting in Junos OS Release 24.2R1, we have added support for reporting an accurate BGP next-hop address for the load-balanced traffic over multiple BGP peers in the ingress direction. Prior to this release, we reported the first address in a list of BGP next hops. To contain this accurate BGP next-hop address, we use the IPv4 BGP Nexthop Address (IE 18) field in the IPv4 and MPLS-IPv4 templates and the IPv6 BGP Nexthop Address (IE 63) field in the IPv6 and MPLS-IPv6 templates, for both the IPFIX and the version 9 formats. To configure this feature, include the multi-bgp-path statement at the [edit services flow-monitoring (version-ipfix | version9) template] hierarchy level. For IPv6 and MPLS-IPv6 flows, you also need to configure the ipv6-extended-attrib statement at the [edit chassis fpc slot-number inline-services flow-table-size] hierarchy level. When this feature is enabled, the fragmentIdentification (IE 54) field reports a value of 0.

    [See Understand Inline Active Flow Monitoring, ipv6-extended-attrib, and multi-bgp-path.]

  • Inline active flow monitoring support for a demux0 interface mapped to an underlying Aggregated Ethernet (AE) interface, for core facing interfaces only (MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX)—Starting in Junos OS Release 24.2R1, we support configuring inline active flow monitoring for a demux0 interface mapped to an underlying AE interface, but for only the mpls-template of family mpls and for protocol family ccc. (No ip4-template or ipv6-template support.) Existing maximum flow scale on the linecard is supported.

    Demux0 is a single interface under which you can map an AE interface. In turn, this AE interface hosts multiple child logical interfaces. The flow record reports the SNMP ID of the underlying AE logical interface as the egress interface. Demux0 logical interfaces are not supported on the reserved unit numbers 16383 and 32767; for example, demux0.16383 and demux0.32767 are not supported.

    [See Understand Inline Active Flow Monitoring.]

  • RPM and TWAMP hardware-timestamp and RTT meansurement support for tests over a Layer 3 VPN PE-to-PE configuration (MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—Starting in Junos OS Release 24.2R1, you can now configure hardware timestamping on PEs in a Layer 3 VPN PE-to-PE configuration that uses the line cards MPC1 through MPC11E, LC480, LC2101, LC2103, and LC2301. You can also receive round-trip time (RTT) measurements using these line cards across platforms (MPC7 and MPC10).

    [See Understanding Using Probes for Real-Time Performance Monitoring on M, T, ACX, MX, and PTX Series Routers, EX and QFX Switches and Configure TWAMP on ACX, MX, M, T, and PTX Series Routers, EX4300 Series, EX9200 Series, and QFX10000 Series Switches.]

  • Support for Inline IPsec (MX304 )—Starting in Junos OS Release 24.2R1, MX304 supports inline IPsec. The IPsec architecture provides a security suite for the IPv4 and IPv6 network layers. The suite provides such functionality as authentication of origin, data integrity, confidentiality, replay protection, and nonrepudiation of source. In addition to IPsec, the Junos OS also supports the IKE, which defines mechanisms for key generation and exchange, and manages security associations (SAs).

    See IPsec Overview.