Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Network Management and Monitoring

  • Operational command RPCs support returning JSON and XML output in minified format in NETCONF sessions (ACX1000, ACX1100, ACX2100, ACX4000, ACX5048, ACX5096, ACX5448, EX2300, EX3400, EX4300, EX4400-24P, EX4400-24T, EX4400-48F, EX4400-48P, EX4400-48T, EX4600, EX4650, EX9200, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, PTX1000, PTX5000, PTX10001, PTX10002, PTX10008, PTX10016, QFX5100, QFX5110, QFX5120, QFX5200, QFX5210, QFX10002, QFX10002-60C, QFX10008, QFX10016, SRX550HM, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800, vMX, and vSRX)—Starting in Junos OS Release 21.1R1, operational command RPCs, including the <get-configuration> RPC, support the format="json-minified" and format="xml-minified" attributes in NETCONF sessions to return JSON or XML output in minified format. Minified format removes any characters that are not required for computer processing—for example, unnecessary spaces, tabs, and newlines. Minified format decreases the size of the data, and as a result, can reduce transport costs as well as data delivery and processing times.

    [See Specifying the Output Format for Operational Information Requests in a NETCONF Session.]

  • HMAC-SHA-2 authentication protocol support for users of SNMPv3 USM (MX Series and SRX Series)—Starting in Junos OS Release 21.1R1, you can configure HMAC-SHA-2 authentication protocols for users of the SNMPv3 user-based security model (USM) with the following new CLI configuration statements:

    • authentication-sha224
    • authentication-sha256
    • authentication-sha384
    • authentication-sha512

    We’ve introduced these statements for local-engine users at [edit snmp v3 usm local-engine user username] and for remote-engine users at [set snmp v3 usm remote-engine engine-id user user-name].

    [See authentication-sha224, authentication-sha256, authentication-sha348, and authentication-sha512.]

  • Log profiles and templates for customized logging (cSRX, SRX300, SRX320, SRX340, SRX345, SRX380, SRX550HM, SRX1500, SRX4100, SRX4200, SRX4600, SRX5800, and vSRX)—Starting in Junos OS Release 21.1R1, you can configure log profiles and log templates for a policy. Use the configuration statement profile to select a log profile for a policy at the [edit security log profile] hierarchy level, and use the configuration statement template to select a predefined log template for a policy at the [edit security log profile profile-name template] hierarchy level. From this release, you can track the application tracking logs using the set security application-tracking log-session-create, set security application tracking log-session-close, set security application-tracking session-update-interval, set security application-tracking no-volume-updates, and set services application-identification no-application statistics commands. Unified threat management (UTM) features also support the log profiles and templates for customized logging.

    [See profile (security), application-tracking, application-identification, and show security log profile.]