Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Resolved Issues: 22.1R1

Flow-Based and Packet-Based Processing

  • On SRX Series devices using Unified Policies with IPv6, when attempting to reject certain dynamic-applications a flowd core file might be generated. PR1601806

  • Cleartext fragments are not processed by flow. PR1620803

General Routing

  • When using log templates with Unified Policies, logs were not generated in a predictable manner. A new construct has been added that allows you to define a default log profile using the set security log profile name default-profile command can be used to improve this behavior when multiple log profiles are defined. PR1570105

  • The pkid process might generate core files during auto-re-enrollment of CMPv2 certificates. PR1580442

  • Getting UNKNOWN instead of HTTP-PROXY for application and UNKNOWN instead of GOOGLE-GEN in RT-FLOW close messages These messages can be seen in the RT-flow close log and these are due to JDPI not engaged for the session. This might affect the app identification for the web-proxy session traffic. PR1588139

  • When combining log profiles and unified policies RT_FLOW_SESSION_DENY logs were not being generated corrected. PR1594587

  • High CPU utilization might be seen when Jflow sampling is configured on vSRX HA setup. PR1604775

  • For apps getting classified on first packet, the volume update syslog are not getting generated. PR1613516

  • The interface speed is limited to 1G on vSRX 2.0 even the speed is set as more than 1G. PR1617397

  • Assert core file might be seen when the application goes to no path selected state. PR1617506

  • During SaaS probing, due to race condition between APP entry addition and session processing, this core is seen. PR1622787

  • Running DNS on all SRX Series devices, a memory leak on Packet Forwarding Engine might occur. PR1624655

  • The application package installation might fail with error in SRX Series devices. PR1626589

  • vSRX3.0 on VMware ESXi versions 7.0u2 or 7.0u3 with i40e SR-IOV, the traffic stopped after reboot. PR1627481

  • Resource errors in show interfaces extensive command output. PR1629986

  • Signature package update might fail and the appid process might stop on SRX Series devices. PR1632205

  • The pfe process might pause on SRX Series devices. PR1642914

Infrastructure

  • The failover process might become slow in a vSRX cluster if the gstatd process stops running. PR1626423

Interfaces and Chassis

  • Static route might not work on vSRX. PR1613430

Intrusion Detection and Prevention (IDP)

  • Device is paused while checking the show security idp attack attack-list policy combine-policy command. PR1616782

J-Web

  • J-Web might only allow certain types of interfaces to be added in a routing instance. PR1637917

Routing Policy and Firewall Filters

  • After policy configuration commit with source tenant and destination services id field set as 0 due to this Incoming traffic processed by first policy. PR1617026

  • Policy re-match extensive is not working for SVR traffic. PR1618717

Routing Protocols

  • The rpd process might generate core file due to memory corruption. PR1599751

  • Memory leak in global data shm process might lead to traffic outage. PR1626704

VPNs

  • Unable to set DynamoDB in HSM module. PR1599069

  • The process kmd might stop if the ike gateway is configured with two IP address. PR1626830

  • Issue in certificate based VPN tunnels initiation while using GCP KMS. PR1628722