Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Services Applications

  • Support for displaying the timestamp in syslog (MX Series routers with MS-MPC, MS-MIC, and MX-SPC3)—Starting in Junos OS Release 21.1R1, you can enable system log (syslog) timestamps in local system timestamp format or UTC format.

    On routers with MS-MPC, you can override the default UTC timestamp to local system timestamp format by configuring the new statement, syslog-local-system-timestamp, at the edit interfaces ms-interface\ams-interfaceservices-options hierarchy level.

    On routers with MX-SPC3 cards, you can override the default local system timestamp in syslog to UTC format by configuring the existing statement,utc-timestamp, at the edit interfaces vms-interface\ams-interfaceservices-options hierarchy level or at the [edit services service-set-namesyslog hierarchy level.

    For the routers with MX-SPC3 cards, starting in Release 21.1R1 you can configure the utc-timestamp statement at the edit interfaces vms-interface\ams-interfaceservices-options hierarchy level. In earlier releases, we support this statement at the [edit services service-set-namesyslog hierarchy level.

    [See syslog (Services Service Set).]

  • Enhancements to DNS sinkhole feature (MX240, MX480, and MX960 routers with MS-MPC and MX-SPC3)—Starting in Junos OS Release 21.1R1 as part of the DNS sinkhole feature enhancements, you can:

    • Configure new actions for a DNS request for a disallowed domain-alert, accept, drop, and drop-no-log.
    • Configure domain names and actions for multiple tenants such that domain feeds can be managed on a per tenant basis.
    • Configure hierarchical domain feed management per profile, dns-filter-template or dns-filter-term.
    • Exempt domain feeds at the IP, subnet, or CIDR level.

    [See DNS Request Filtering for Disallowed Website Domains.]

  • TWAMP Light IPv4 support (MX Series, PTX Series)—Starting in Junos OS Release 21.1R1, we support the Two-Way Active Measurement Protocol (TWAMP) Light, as defined in Appendix I of RFC 5357. TWAMP Light is a stateless version of TWAMP, where test parameters are predefined instead of negotiated. All test packets received by the server on a test port are reflected back and forgotten right away.

    [See twamp.]

  • Support for RFC 2544-based benchmarking tests (SRX300, SRX320, SRX340, SRX345, SRX380, and SRX550HM)—Starting in Junos OS Release 21.1R1, we support only the Layer 3 reflector function for these tests, with the following limitations:

    • family inet option; no other families are supported

    • IPv4 source and destination addresses for the tests

    RFC 2544 tests measure and demonstrate the service-level agreement (SLA) parameters before service activation. You can use the tests to measure throughput, latency, frame loss rate, and the number of back-to-back frames. [See Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, MX, and SRX Series Routers .]

  • Support for the any firewall filter family and the Layer 2 firewall filter families for inline monitoring services (MX Series)—Starting in Junos OS Release 21.1R1, you can configure the any, bridge, ccc, mpls, or vpls family firewall filter with the term action inline-monitoring-instance inline-monitoring-instance-name.

    [See Inline Monitoring Services Configuration .]

  • Support for inline active flow monitoring (PTX10008 and PTX10016)—Starting in Junos OS Release 21.1R1, we support inline active flow monitoring for the PTX10K-LC1105 line card. Inline active flow monitoring supports version 9 and IPFIX flow collection templates. Both the IPFIX and the version 9 templates are supported for IPv4, IPv6, and MPLS, and use UDP as the transport protocol.

    [See Configuring Inline Active Flow Monitoring on PTX Series Routers .]