What's Changed
Learn about what changed in this release for MX Series routers.
General Routing
-
Changes to default behavior under forwarding-table (MX Series)—The
ecmp-fast-reroute
andindirect-next-hop-change-acknowledgements
commands are enabled by default under the [edit routing-options forwarding-table
] hierarchy. You can verify these defaults by running theshow configuration routing-options forwarding-table
command in the operational mode.[See ecmp-fast-reroute .]
-
SSH key options for user account credentials. You can configure key-options <key-options> option at the set system login user <user> authentication [ssh-rsa|ssh-ecdsa|ssh-ed25519] <ssh key> hierarchy level.
[See login.]
-
Deprecation of jnxLEDTable—The jnxLEDTable table is no longer supported.
-
The
show subscribers extensive client-type dhcp | display xml validate
command has now been updated to display correct output instead of theDuplicate data element
error message. -
SFP Optics LOS alarms (MX Series)— SFP Optics don't support Tx laser disabled alarm, Tx loss of signal functionality alarm, and Rx loss of signal alarm as diagnostics output.
-
G.8275.1 profile configuration with PTP, SyncE, and hybrid mode (Junos)]— On all Junos platforms, when configuring the G.8275.1 profile, it is mandatory to configure Precision Time Protocol (PTP), Synchronous Ethernet (SyncE), and hybrid mode. Earlier, the system would not raise a commit error even if the required hybrid and SyncE configurations were missing while configuring G.8275.1 profile. However, going forward you will not be able to configure the G.8275.1 profile without configuring PTP, SyncE and hybrid mode to be compliant with the ITU-T standards.
[See G.8275.1 Telecom Profile.]
-
Extension of traceoptions support for VLANs in IGMP/MLD snooping—The
traceoptions
option is supported under theedit routing-instance protocols igmp-snooping vlan
andedit routing-instance protocols mld-snooping vlan
hierarchy.traceoptions
can be enabled for both specific and all vlans.[See (IGMP Snooping) and vlan (MLD Snooping).]
Subscriber Access Management
-
You can configure VLAN termination cause codes to specify RADIUS attribute values for different termination scenarios on JUNOS MX platforms supporting the Layer-2 Bitstream Access (L2BSA) feature. You can diagnose and manage network issues effectively by understanding the specific reasons for VLAN termination. Ensure that the correct termination cause codes are sent by validating configuration and testing scenarios to correctly interpret network events. When a subscriber logs out, the system occasionally sends an incorrect termination cause value to RADIUS. The subscriber VLAN "Account-Terminate-Cause" in "Acct-Stop" message for different L2BSA subscriber logout error scenarios is modified to display correct reasons for termination.
[See VLAN Termination Causes and Code Values and show network-access aaa terminate-code.]
User Interface and Configuration
-
Access privileges for request support information command (ACX Series, EX Series, MX Series, QFX Series, SRX Series Firewalls, and vSRX Virtual Firewall)—The
request support information
command is designed to generate system information for troubleshooting and debugging purposes. Users with the specific access privilegesmaintenance
,view
andview-configuration
can execute request support information command. -
Changes to the
show system storage
command output (ACX Series, EX Series, MX Series, QFX Series, and SRX Series)—We've updated theshow system storage
command output to include only true (physical) storage and exclude any host/hypervisor level storage. In earlier releases, the output also includes a container/jail storage, which does not have a separate storage of its own.[See show system storage.]