Table of Contents
Navigation
Back up to About Overview [+] Expand All
[-] Collapse All
Download This Guide
Known Issues
The following problems currently exist in Juniper Networks branch SRX Series Services Gateways and J Series Services Routers. The identifier following the description is the tracking number in the Juniper Networks Problem Report (PR) tracking system.
 | Note: For the latest, most complete information about outstanding and resolved issues with the Junos OS software, see the Juniper Networks online software defect search application at https://www.juniper.net/prsearch. |
Access Point Network
- On branch SRX Series devices with AX411, the SRX devices are unable to communicate with AX411 WLAN devices. PR1173837
Chassis Cluster
- On branch SRX Series devices in a chassis cluster, the clear interface stats command does not work when any of the nodes in a chassis cluster are down. PR550641
- On SRX Series devices in a chassis clusters, the PIC might go offline on one of the nodes due to RG0 failover caused by rebooting the device. PR933248
Class of Service (CoS)
- On branch SRX Series devices, you cannot apply CoS rewrite rules based on AppQoS. PR782050
- On branch SRX Series devices in chassis clusters Z mode, the traffic rate-limited displays a deviation in the traffic forwarding rate. PR779368
- On SRX240H and SRX240H2 devices, because of a system performance limitation, some queues of CoS might not get enough packets when the traffic is high. PR1061350
Flow-based and Packet-based Processing
- On branch SRX Series devices, when data flowsets are exported after AS configuration changes, the changes to srcAS and dstAS values are not reflected immediately in the exported flows. PR864416
- On branch SRX Series devices, when sampling is enabled, the template-refresh-rate and option-refresh-rate options takes into account a default value of 60 seconds, if packets are configured without any value for seconds. PR865413
- On SRX220H2 device, the TCP connection rate might drop by 15 percent. PR898217
- On SRX Series devices, in a rare condition, memory might be overwritten on Jtree, which causes the flowd process crash. PR1158276
- On branch SRX Series devices, flowd_octeon_hm core several times on both the nodes. PR1193835
- On SRX550M device, the maximum-sessions value is not displayed correctly. PR977169
Hardware
- On SRX550 device, the USB modem is not supported due to hardware limitation. PR856058
- On SRX650 device, when using SRX-SFP-1GE-LX optics with Sumitomo part number SCP6G44-J8-ANE or SCP6G44-J7-ANE, the SFP will not work. After reboot the following message appears on the console: twsi0: Device timeout on unit 1. This specific type of SFP should not be used on SRX650. On other platforms this SFP works fine. PR1118061
Interfaces
- On SRX Series devices, the loop back CLI configurations shdsl-options for pt interface is not working as expected. PR798180
- On SRX Series devices, the SHDSL media and statistics counters are not incrementing after the introduction of micro-interruption to the line. The counters are also not cleared even after explicitly using the clear command. PR810334
- On branch SRX Series devices, packet loss is seen initially for 15 seconds after the GRE tunnel is brought up over the VDSL interface. PR821330
- On SRX210 and SRX220 devices, when the baseboard port or the 1XGE Mini-PIM port over IRB is configured to receive joins for any valid multicast address x.1.1.1, the multicast address is not recognized and it is not present in the PIM join or IGMP group. PR873909
- On branch SRX Series devices, if flexible-vlan-tagging is configured on the underlying interface of a PPPoE interface, then the native-vlan will not be supported on this interface. Traffic sent out from the logical interface which is an underlying interface of PPPoE and native-vlan is configured will wrongly contain the VLAN tag. PR987068
- On branch SRX Series devices, the vrf-table-label statement is currently supported only on physical interfaces. This statement is not supported over aggregated interfaces or VLAN interfaces. PR1137159
- On branch SRX Series devices, the IP address count per logical interface has been enhanced to support up to eight IP addresses when sending GARP packets. PR1153410
Intrusion Detection and Prevention (IDP)
- On SRX Series devices, in the output of the show services application-identification application-system-cache command, the application-system-cache table for P2P encrypted traffic is incorrectly marked as Encrypted: No instead of Encrypted:Yes. PR704023
Platform and Infrastructure
- On branch SRX Series devices, the maximum MTU supported on the 1XGE Mini-PIM card is 9010 bytes for both optical and copper small form-factor pluggable transceiver (SFP). If a 1XGE Mini-PIM card is configured with a value greater than 9010, the earlier committed value takes effect, but no error message is displayed in the CLI. However, the log captures the failure to set the configured MTU value. PR825691
- On branch SRX Series devices, when reverse path forwarding (RPF) is enabled along with real-time performance monitoring (RPM), the device changes to db prompt and loses the reach ability when you delete some configurations. PR869528
- On branch SRX Series devices, IP Monitoring supports only point to point interface, you cannot configure the interface with point to multi-point encapsulation mode such as ether-over-atm-llc as next hop. PR956174
- On branch SRX Series devices, when using RPM IP Monitoring, when you disable an interface which is used as a backup, the backup route will not be removed. PR957027
- On SRX650 device, traffic might be dropped intermittently due to high CPU usage on RE. PR1170231
- On SRX Series devices, if there are two or more IP Monitoring configured, and they operate the same IP prefix, then unexpected behavior with IP Monitoring might occur, such as false negative. PR1192668
Routing Policy and Firewall Filters
- On branch SRX Series devices, the feed-server option is not supported. PR899426
Switching
- On SRX650 device in chassis cluster, when the fabric link is disabled manually by using the CLI, the secondary node remains in the secondary mode. As a result, in the active/active mode, the Z-traffic is dropped even when the secondary node is up and the fabric link status is down. PR839193
Unified Threat Management (UTM)
- On SRX650 device, after installing advance services such as UTM and IDP, the corresponding bit of the NVRAM environment variable will be set. This bit is used to decide if the advance service should be enabled or not. PR943672
- On SRX550 and SRX650 devices with Sophos Antivirus (SAV) configured, some files whose size is larger than the max-content-size might not go into fallback state. Instead, some protocols do not predeclare the content size. PR1005086
VPNs
- On branch SRX Series devices in HA mode, VPN-monitoring with optimized option is configured and traffic goes through the IPsec tunnel. The VPN-monitoring status will be displayed as down after RG0 failover. PR1203723
