What's Changed

EVPN-VXLAN tracing configuration]--The set services trace evpn-vxlan configuration invokes a built-in commit script to generate tracing configurations for troubleshooting EVPN-VXLAN in multiple modules and hierarchies.

[See trace (EVPN-VXLAN).]

• Peer PE device peer-id value can only be 1 or 2.

• You are required to configure the loopback subnet addresses for each peer PE device using the new loopback-subnet peer1-subnet and loopback peer2-subnet options at the edit services evpn device-attribute hierarchy level. The commit script uses these values for each peer PE device's loopback subnet instead of deriving those values on each PE device. The loopback-subnet option at the edit services evpn device-attribute hierarchy level has been deprecated.

• If you configure the no-policy-and-routing-options-config option, you must configure a policy statement called EXPORT-LO0 that the default underlay configuration requires, or configure the new no-underlay-config option and include your own underlay configuration.

• The commit script generates "notice" messages instead of "error" messages for configuration errors so you can better handle edit services evpn configuration issues.

• The commit script includes the element names you configure (such as IRB instance names and server names) in description statements in the generated configuration.

This feature also now includes a few new options so you have more flexibility to customize the generated configuration:

• no-underlay-config at the edit services evpn hierarchy level—To provide your own underlay peering configuration.

• mtu overlay-mtu and mtu underlay-mtu options at the edit services evpn global-parameters hierarchy level—To change the default assigned MTU size for underlay or overlay packets.

[See Easy EVPN LAG Configuration.]

Change in options and generated configuration for the EZ-LAG configuration IRB subnet-address statement—With the EZ-LAG subnet-address inet or subnet-address inet6 options at the edit services evpn evpn-vxlan irb irb-instance hierarchy, you can now specify multiple IRB subnet addresses in a single statement using the list syntax addr1 addr2 ?. Also, in the generated configuration for IRB interfaces, the commit script now includes default router-advertisement statements at the edit protocols hierarchy level for that IRB interface.

[See subnet-address (Easy EVPN LAG Configuration).]

Changes to Aggregate Level Policer at FPC (EX9208)—The summation of newly added sub-policers HELLO and UNCLS for DDOS protocols OSPF, OSPFv3, and RSVP result in the correct reporting of counters at the FPC level, for e.g. packet drops. Earlier, you could configure the OSPF, OSPFv3, and RSVP aggregate policer at the FPC level directly.

You can use the following CLI statements to configure the burst and bandwidth values for OSPF, OSPFv3, and RSVP.

• set system ddos-protection protocols ospf ospf-hello burst size bandwidth packets-per-second
• set system ddos-protection protocols ospf ospf-uncls burst 10000 bandwidth 10000
• set system ddos-protection protocols ospfv3v6 ospfv3v6-hello burst 10000 bandwidth 10000
• set system ddos-protection protocols ospfv3v6 ospfv3v6-uncls burst 10000 bandwidth 10000
• set system ddos-protection protocols rsvp rsvp-hello burst 10000 bandwidth 10000
• set system ddos-protection protocols rsvp rsvp-uncls burst 10000 bandwidth 10000

[See Protocols (DDOS).]

Support extended for Default No VSTP Flooding (EX Series and QFX Series)-When a switch receives an incoming VSTP PDU, it is sent to the PFE host path where it is re-injected over the VLAN, which might cause VSTP flooding. No VSTP (VLAN Spanning Tree Protocol) Flooding, allows the packets to be dropped at the PFE host path and does not allow flooding or re-injection to the VLAN. "No VSTP Flooding" is implemented by default.

VSTP flooding can be enabled using set switch-options vstp-flooding command.

[See Configuring VSTP.]

Activation of SFP-10GBASE-T for 1G speed simultaneously with other 1G SFPs-If you want to use SFP-10GBASE-T at 1G speed, use a separate quad of ports. Do not mix with other 1G SFPs because SFP-10GBASE-T deactivates other ports with a different 1G SFP module.

Change in the XML tags displayed for the show virtual-network-functions command in JDM (Junos node slicing)]-To align the XML tags displayed for the show virtual-network-functions gnf-name | display xml with the new XML validation logic, we have replaced the underscores (_) in the output with hyphens (-). This change is applicable to any RPC that previously had underscores in the XML tag name.

Ability to commit extension-service file configuration when application file is unavailable—When you set the optional option at the edit system extension extension-service application file file-name hierarchy level, the operating system can commit the configuration even if the file is not available at the /var/db/scripts/jet file path.

See file (JET).

XML output tags changed for request-commit-server-pause and request-commit-server-start (ACX Series, EX Series, MX Series, QFX Series, SRX Series, and vSRX)—We've changed the XML output for the request system commit server pause command (request-commit-server-pause RPC) and the request system commit server start command (request-commit-server-start RPC). The root element is <commit-server-operation> instead of <commit-server-information>, and the <output> tag is renamed to <message>.

NETCONF <copy-config> operations support a file:// URI for copy to file operations (ACX Series, EX Series, MX Series, QFX Series, SRX Series, and vSRX)—The NETCONF <copy-config> operation supports using a file:// URI when <url> is the target and specifies the absolute path of a local file.

[See <copy-config>.]

ephemeral-db-support statement required to configure MSTP, RSTP, and VSTP in the ephemeral configuration database (ACX Series, EX Series, and QFX Series)—To configure Multiple Spanning Tree Protocol (MSTP), Rapid Spanning Tree Protocol (RSTP), or VLAN Spanning Tree Protocol (VSTP) in the ephemeral configuration database, you must first configure the ephemeral-db-support statement at the [edit protocols layer2-control] hierarchy level in the static configuration database.

[See Enable and Configure Instances of the Ephemeral Configuration Database.]

After this change IS-IS export policies support setting the down bit configuring the "set-down-bit" action in an export policy term.

Information about users editing system configuration-- The show system configuration database status command displays information from the Junos OS configuration database that describes the users currently editing the system configuration.

Output for request system software status | display xml validate has a tag mismatch error (all platforms)--The output contains the error message CRITICAL ERROR: Root tag 'package-status' is either not defined in ODL or does not have 'flag root' set. Please check. Rendering may not work properly. We have removed the improperly defined package-status tag and replaced it with a new child tag package-status-message.

Viewing files with the file compare files command requires users to have maintenance permission]-The file compare files command in Junos OS and Junos OS Evolved requires a user to have a login class with maintenance permission.

[See Login Classes Overview.]