What's Changed
Learn about what changed in this release for vSRX.
Chassis Cluster
-
With vSRX 3.0 in Layer 2 chassis cluster mode, use the VirtIO type interface as a redundant Ethernet (reth) interface child to automatically utilize the reth's virtual MAC address. This setup ensures that during a failover, the device does not need to update the child MAC address, enhancing failover efficiency and reducing downtime.
Identity Management
-
For push-to-identity-management to successfully push the authentication entry to JIMS, you must configure JIMS and verify that JIMS status is online.
[See push-to-identity-management and Configure JIMS in Junos.]
User Interface and Configuration
-
The
xmlns:junosattribute includes the complete software version string (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX and vSRX)—Thexmlns:junosnamespace string in XML RPC replies includes the complete software version release number, which is identical to the version emitted by theshow versioncommand. In earlier releases, thexmlns:junosstring includes only partial software version information. -
Access privileges for request support information command (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series Firewalls, and vSRX Virtual Firewall)—The
request support informationcommand is designed to generate system information for troubleshooting and debugging purposes. Users with the specific access privilegesmaintenance,view, andview-configurationcan execute request support information command. -
Changes to the
show system storagecommand output (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—We've updated theshow system storagecommand 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.]
VPNs
-
Default installation of junos-ike package on additional platforms (SRX1500, SRX4100, SRX4200, SRX4600, and vSRx3.0)—The
junos-ikepackage is installed by default on SRX1500, SRX4100, SRX4200, SRX4600, and vSRX3.0 firewalls, ensuring the default support for <codeph>iked</codeph> process for IPsec VPN service. This aligns with the existing default installation of the package on SRX5000 line with Routing Engine 3 (SRX5K-SPC3 with RE3). You can delete thejunos-ikepackage using the commandrequest system software delete junos-ike. This runs thekmdprocess on these firewalls, allowing flexible management of your security infrastructure.