Support Support Downloads Knowledge Base Service Request Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

18.1R3-S9: Software Release Notification for JUNOS Software Version 18.1R3-S9

0

0

Article ID: TSB17708 TECHNICAL_BULLETINS Last Updated: 13 Jan 2020Version: 1.0
Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, MX, PTX, QFX, SRX, NFX, VMX, VRR, Network Agent
Alert Description:
Junos Software Service Release version 18.1R3-S9 is now available for download from the Junos software download site
Download Junos Software Service Release:
  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts
Solution:

unos Software service Release version 18.1R3-S9 is now available.

18.1R3-S9 - List of Open issues

PR Number Synopsis Category:QFX Multichassis Link Aggregrate
1454764 Flooding of ARP reply unicast packets for switch VRRP MAC address through every port in VLAN
 
A QFX switch may send out ARP reply unicast packets as a result of an ARP request sent for the device's VRRP MAC address.
PR Number Synopsis Category:JUNOS Network App Infrastructure (for ping, traceroute, etc)
1463622 The cosmetic error messages of NTP time synchronization might be seen during device booting
 
In NTP with the boot-server scenario, when the router or switch boots, the NTP daemon will send a ntpdate request to poll the configured NTP boot-server to determine the local date and time. If the ntpdate is not be activated correctly while the device booting, the ntpdate might not work successfully. Then some cosmetic error messages of time synchronization might be seen, but there is no impact with time update since ntp daemon will update the time eventually.


18.1R3-S9 - List of Fixed issues

PR Number Synopsis Category:L2NG RTG feature
1461293 MAC addresses learned on RTG may not be aged out after aging time
 
MAC addresses learned on redundant trunk group (RTG) might not be aged out after aging time if the source interface is configured as RTG.
PR Number Synopsis Category:EX4300 Control Plane
1461434 ERP might not revert back to IDLE state after reload/reboot of multiple switches
 
On EX4300 platforms configured with ERP, after multiple devices reboot/restart at the same time, ERP might not revert back to the IDLE state. This issue might be seen in situations where the ERP node-id is not configured manually and after the restart, the default node-id (switch base MAC address) might get reset to 00:00:00:00:00:00, effectively causing multiple devices to have the same node-id.
PR Number Synopsis Category:EX4300 PFE
1413700 Untagged traffic is single-tagged in Q-in-Q scenario on EX4300 platforms
 
On EX4300 platforms except for EX4300-48MP, untagged traffic over S-VLAN is forwarded with a single tag (S-VLAN tag) instead of double tags (native-VLAN and S-VLAN tag).
1448607 NSSU cause a traffic loss again after the backup to master transitions
 
In specific topology (VC uplink with VRRP and downlink client-side has a LAG), while doing NSSU on EX4300 VC, traffic loss might be observed again after the backup to master transitions.
1459210 The OSPF neighbor might go down when mDNS/PTP traffic is received at a rate higher than 1400pps
 
On EX4300 platforms, the OSPF (Open Shortest Path First) hello packets might be dropped when mDNS/PTP (multicast DNS / Precision Time Protocol) traffic is received at a rate higher than 1400pps. The issue results in OSPF neighbor down and traffic loss is seen.
1470424 The switch might not be able to learn MAC address with dot1x and interface-mac-limit configured
 
On Junos platforms, if dot1x and interface-mac-limit are configured, when sending traffic continuously to the interfaces, the switch might not be able to learn MAC address. Hence traffic drop might be seen.
PR Number Synopsis Category:EX4300 Platform
1405262 EX4300 : Alarm with removal of PEM (Power supply)
 
EX4300 : When PEM (Power supply) is removed, Alarm was not generated. With this fix, Alarm will be generated and ALM LED will be illuminated with yellow.
1461983 Traffic loss may be observed longer than 20 seconds when performing NSSU on EX4300 VC
 
In the EX4300 virtual-chassis scenario, when performing NSSU (nonstop software upgrade) on EX4300 VC, due to master relationship switchover, traffic loss may be observed longer than 20 seconds.
PR Number Synopsis Category:Marvell based EX PFE L3
1462106 Error messages related to soft reset of port due to queue buffers being stuck could be seen on EX-4600-EX-4300 VC
 
Error messages related to soft reset of port due to queue buffers being stuck could be seen on EX-4600-EX-4300 VC
PR Number Synopsis Category:EX9200 Control Plane
1452738 The l2ald and eventd are hogging 100% after issued "clear ethernet-switching table"
 
The l2ald and eventd processes are hogging 100% after issued "clear ethernet-switching table" and also the continuous syslog errors "l2ald[18605]: L2ALD_IPC_MESSAGE_INVALID: Invalid message received (message type 0, subtype 0): null message" are observed.
PR Number Synopsis Category:EX2300/3400 PFE
1465526 [EX2300] FXPC Core is seen after mastership election based on user's priority
 
 
PR Number Synopsis Category:EX2300/3400 platform
1428627 The phone-home feature does not work because the date is wrong
 
If an EX2300 or EX3400 device is kept powered off for a long time, when powering it on, the time is set incorrectly either to epoch or to a time in future. This can cause failure of phone-home zero touch provisioning since it relies on certificates to set up secure connection to the phone-home server.
PR Number Synopsis Category:DC PFE QoS
1466770 Slow packet drops might be seen on QFX5000 platforms
 
The issue observed on QFX5000 platforms when there are any packets on the port before its buffer configuration is completed after the reboot. This issue is very rare and the window could be just few milli seconds.
PR Number Synopsis Category:QFX Multichassis Link Aggregrate
1465077 The traffic might be forwarded to wrong interfaces in MC-LAG scenario
 
On EX/QFX platforms with MultiChassis Link Aggregation Group (MC-LAG) configured, if the interface media of MC-LAG is changed from MultiProtocol Label Switching (MPLS) to Dense Wavelength Division Multiplexing (DWDM), the traffic might be forwarded to wrong interfaces and get dropped.
PR Number Synopsis Category:QFX Access control list
1379718 Host destined packets with filter log action might not reach to the routing engine if log/syslog is enabled.
 
On EX4300/EX4600/QFX Series switches except for QFX10k, if host destined packets (that is, the destination address belongs to the device) come from the interface with ingress filter of log/syslog action (for example, 'filter <> term <> then log/syslog'), such packets should not be dropped and reach the Routing Engine.
1429543 The traffic with destination UDP port 520 (RIP) or 521 (RIPng) gets dropped on QFX5000/EX4600 platforms
 
On QFX5000/EX4600 platforms, the received traffic will be dropped if the destination UDP port is 520/521 though the device runs pure layer 2 swithcing.
PR Number Synopsis Category:QFX PFE CoS
1432078 Shaping does not work after the reboot if "shaping-rate" is configured.
 
On QFX5110, QFX5100 and EX4600 platforms, if "shaping-rate" is configured, the shaping feature might not work after a reboot. The service might be impacted as the traffic cannot be rate limited.
PR Number Synopsis Category:QFX PFE L2
1434687 JDI-RCT: EVPN-VXLAN NON-COLLAPSED: JTASK and multimove depth failed errors seen after HALT
 
QFX5100/5110 interface driver may not be initialized correctly. This causes errors when the system is halted. There is no impact to the system's operation.
1437577 Physical layer and MAC/ARP learning might not work for copper base SFP-T on QFX5100/QFX5110/EX4600
 
On QFX5100/QFX5110/EX4600 platforms, if copper base SFP-T is used, it might not get up on physical layer and the MAC/ARP learning might not work if it gets up. The PR fixes both layer-1 and layer-2 issues in this scenario.
1447333 Packet might be dropped on QFX5100/QFX5200/EX4600
 
On QFX5100/QFX5200/EX4600, in Junos 18.1 release, if there are multiple layer 3 sub interfaces on multiple interfaces, packet might be dropped when multiple layer 3 subinterface config added and rollbacks happens.
1467763 The fxpc.core might be seen when committing the configuration all together, e.g., after the reboot
 
On EX2300/3400/4300/4600 and QFX Series switches except for QFX10k, if committing the configuration all together (e.g., after the reboot), the fxpc/PFE core dump might be found. In the Virtual Chassis scenario, the VC members might be splitted because the VC ports might not be created in time.
1469596 Ingress traffic might be blackholed if underlying interfaces flap in EVPN/VXLAN scenario
 
On QFX5000 platforms with Ethernet Virtual Private Network (EVPN) and Virtual Extensible LAN (VXLAN) scenario, if there is the underlying interface flaps for the core network side, all the ingress traffic might be backholed by the VXLAN Tunnel Endpoint (VTEP) due to this issue.
PR Number Synopsis Category:QFX L3 data-plane/forwarding
1367439 Invalid VRRP mastership election on QFX5110-VC peers
 
In some specific scenarios, the configuration of bpdu-block-on-edge might cause both QFX5110 to claim as VRRP masters.
1367439 Invalid VRRP mastership election on QFX5110-VC peers
 
In some specific scenarios, the configuration of bpdu-block-on-edge might cause both QFX5110 to claim as VRRP masters.
1444845 CRC errors might be seen on QFX5100-VC
 
In QFX5100 Virtual Chassis(VC) scenario, if the VC connections are disconnected for any reason, like rebooting the switch or pulling out the optical module, the CRC errors and packets loss might be seen when the VC connections resume working again. Due to the VCP ports are not getting initialized properly.
1455547 The coredump might occur during adding/removing EVPN Type-5 routing instance
 
On QFX platforms, the coredump might occur during adding/removing EVPN Type-5 routing instance. The EVPN route would be corrupted and traffic/service impact appears if hitting the issue.
PR Number Synopsis Category:QFX PFE MPLS
1477301 The traffic may be lost over QFX5100 switch acting as a transit PHP node in the MPLS network
 
In the MPLS network, the packets may get dropped by egress node if the packets go through the QFX5100 switch acting as a transit PHP (penultimate-hop popping) node.
PR Number Synopsis Category:Accounting Profile
1452363 The pfed might crash and not be able to come up on the PTX or TVP platforms
 
The flow label statistics are retrieved periodically by pfed for PTX or TVP platforms, if the statistics reply becomes very big number, the pfed might crash hence affecting traffic.
PR Number Synopsis Category:ACX Interfaces IFD, IFL, vlans, and BRCM init
1284590 ACX5k MacDrainTimeOut and bcm_port_update failed: Internal error
 
On ACX5K, the buffer is corrupted on port 0 (*/*/0) and error message MACDRAINTIMEOUT and dcbcm_check_stuck_buffers are observed, which could eventually lead to port 0 (*/*/0) flapping.
1382166 Host bound traffic might be affected and lt interface can go down in ACX
 
Host bound traffic might be affected and lt interface can go down in ACX
PR Number Synopsis Category:ACX MPLS
1449681 l2circuit with a "backup-neighbor" (hot-standby) configured may stop forwarding traffic after failovers
 
On ACX platforms, if the "backup-neighbor" is configured with the "hot-standby" parameter, then l2circuit may stop passing traffic if the master path is down and back up again (l2circuit switchovers from the master path to the backup path, then moves back from the backup path to the master path)
PR Number Synopsis Category:ACX GE, 10GE, PoE, IDT framers
1439384 interface on ACX1100 remains down when using SFP-1FE-FX (740-021487)
 
Interface with SFP-1FE-FX transceiver optic (740-021487) will not come UP on ACX routers.
PR Number Synopsis Category:common or misc area for SRX product
1430941 Unable to launch J-Web when the device is upgraded through USB image.
 
On SRX5000 series, when the device is upgraded through USB image, J-Web is not available and needs to be installed through "request system software add optional://jweb-srx".
PR Number Synopsis Category:MIBs related to BBE
1470664 SNMP interface-mib stops working for PPPoE clients
 
SNMP interface-mib stops working for PPPoE clients. In this scenario SNMP works fine for standard queries on the MX router, but for subscriber statistics always returns value of zero.
PR Number Synopsis Category:Bi Directional Forwarding Detection (BFD)
1432440 In BFD and GR enabled scenario, BFD DOWN packets are not being sent immediately after BFD failure
 
In both GR helper and GR restarter scenarios, BFD down packets are not immediately sent. It might cause an issue where BGP session down is notified before BFD DOWN.
1448649 JUNOS BFD sessions with authentication flaps after a certain time
 
In the scenario where BFD session authentication is configured, after a certain period of time, BFD sessions flaps may be seen, this will cause the neighbor to be down.
PR Number Synopsis Category:Border Gateway Protocol
1371045 TCP sessions might be taken down during RE switchover
 
On MX10K platforms enabled with Graceful Routing Engine Switchover (GRES) and Non Stop Routing (NSR), if the router runs with Transmission Control Protocol (TCP) based routing protocol (e.g. Border Gateway Protocol, BGP), and establishes TCP sessions with the remote peers, the execution of RE switchover might cause few TCP sessions being taken down and re-connected. Due to this issue, the TCP session re-connection will impact the related routing protocol session and therefore impact the traffic. This is a timing issue.
1371045 TCP sessions might be taken down during RE switchover
 
On MX10K platforms enabled with Graceful Routing Engine Switchover (GRES) and Non Stop Routing (NSR), if the router runs with Transmission Control Protocol (TCP) based routing protocol (e.g. Border Gateway Protocol, BGP), and establishes TCP sessions with the remote peers, the execution of RE switchover might cause few TCP sessions being taken down and re-connected. Due to this issue, the TCP session re-connection will impact the related routing protocol session and therefore impact the traffic. This is a timing issue.
1454951 Rpd might crash when multipath is in use
 
If multipath is enabled, in some certain conditions, the rpd core might be seen while secondary route resolution.
PR Number Synopsis Category:Cassis pfe microcode software
1464820 MPC5E/6E might crash due to internal thread hogging the CPU
 
PR 1382182 (which is fixed in 16.2R3 17.1R3 17.3R3-S3 17.3R4 17.4R2-S3 17.4R3 18.1R3-S2 18.1R4 18.2R2 18.2X75-D40 18.3R2 18.4R1 19.1R1) introduced an improper code which could cause an internal thread to hog the CPU and eventually result in the MPC crash. It is a timing issue and affects MPC5E/6E.
PR Number Synopsis Category:Virtual-chassis platform/chassisd infrastructure PRs for MX
1391011 Interim accounting updates might not be sent for subscribers after Junos OS selective update
 
On MX/MXVC platforms enabled with enhanced subscriber management, if Graceful Routing Engine Switchover (GRES) and Nonstop active Routing (NSR) are disabled, when the chassisd process is going to restart (which is resulted from Junos Selective Update), the system will make the transition of Routing Engine (RE) mastership from master to standby before the chassisd process restart. Due to this issue, the new standby RE didn't reboot as expected, which causes the pfed process being passive for 15 minutes. During the 15 minutes, all the interim accounting update will not sent for all the subscribers who login during this time range.
PR Number Synopsis Category:MX Platform SW - UI management
1453533 Alarm was not sent to syslog on MX10003 platform
 
On the MX10003 platform, the alarmd wont write the alarm messages to the syslog.
1453533 Alarm was not sent to syslog on MX10003 platform
 
On the MX10003 platform, the alarmd wont write the alarm messages to the syslog.
1457657 The chassisd process and all FPCs may restart after RE switchover
 
The chassisd process and all FPCs may restart after RE switchover if the knob "master-only" is enabled.
PR Number Synopsis Category:Class of Service
1428144 The host-inbound packets might be dropped if configuring host-outbound FC
 
On all Junos platforms, if class-of-service host-outbound-traffic forwarding-class is configured and the FC (Forwarding Class) is with an implicit/explicit discard action in the firewall filter, the kernel might classify the host-inbound traffic to the same FC and being discarded.
PR Number Synopsis Category:Device Configuration Daemon
1445370 VRRP-V6 state is flapping with init and idle states after configuring vlan-tagging
 
VRRP-V6 state is flapping with init and idle states after configuring vlan-tagging
1475634 Commit error is not thrown when member link is added to multiple aggregation group with different interface specific options
 
Commit error is not thrown when member link was added to multiple aggregation group with different interface specific options. When member interface added to bundle with both ether and gig-ether interface specific options, gig-ether option takes precedence over ether options.
PR Number Synopsis Category:Firewall Filter
1452435 Commit error and dfwd coredump might be observed when applying a firewall filter with action "then traffic-class" or "then dscp"
 
Commit failure with error might be seen and the dfwd crashes when applying a firewall filter with action "then traffic-class" or "then dscp" to an interface.
1473093 Traffic might not be forwarded into the right queue but the default queue when VPLS traffic has three or more VLAN tags with VLAN priority 5
 
On the MX platform with MPC line card (except DPC line card) used, if an input firewall filter is configured at the ingress VPLS interface, the packet with a VLAN priority of 5 with three or more VLAN tags might be forwarded into the wrong queue. When this occurs, it might cause traffic loss due to congestion as all traffic is forwarded into the default queue.
PR Number Synopsis Category:dhcpd daemon
1425206 The jdhcpd might consume 100% CPU and crash if dhcp-security is configured
 
The issue is limited to DB related to MAC-MOVE scenario. When dhcp-security is configured, if multiple IPv4 and IPv6 client's MAC-MOVE happens, the jdhcpd might consume 100% CPU and jdhcpd will crash afterwards.
1474097 DHCP-server : radius given mask being reversed. Seems to me big/small endian conversion issue on PPC based REs
 
DHCP-server : radius given mask being reversed. Seems to me big/small endian conversion issue on PPC based REs. This is occurring because of big/small endian platform data format conversion.
PR Number Synopsis Category:Covers Application classification workflows apart from custo
1463159 A core file will be generated when perform an ISSU on SRX platforms
 
When APPID is enabled and perform an ISSU on SRX devices, it might cause traffic impact and generate core-dump file.
PR Number Synopsis Category:JUNOS Dynamic Profile Configuration Infrastructure
1188434 UID may not release properly in some scenarious after service session deactivation
 
When same UID objects are used in both inet and inet6 services of the same subscriber session, deactivation the first session cause conditions which avoid releasing UID entry after deactivation second service session. This leads to having stale UID entry and can cause subscriber's connection problem in the future when UID pool would be completely exhausted. The probability of hitting the issue increases if amount subscriber to amount of unique services ratio is aproaching 1 (i.e. when almost every subscriber has a service with unique servie objects).
1379482 The subinfo process might crash with core file if flapping all the subscribers
 
On MX platforms with large scaled number of subscribers login, if flapping all the subscribers and executing the command "show subscriber summary port", the subinfo process might crash.
PR Number Synopsis Category:dynamic dcd prs
1470622 Executing commit might hang up due to stuck dcd process
 
When dynamic DHCP sessions are existing in the device, if multiple commits in parallel are performed, the commit might hang up.
PR Number Synopsis Category:Ethernet OAM (LFM)
1465608 Need two knobs for EOAM CFM interoperability between MX10003 and Ciena CPE
 
Customer need two knobs for EOAM CFM interoperability between MX10003 and Ciena CPE Two knobs: 1. primary-vid - this allows interop with Ciena CPE - which is used at evert tower site to est. EOAM CFM session 2. enhanced-cfm-mode - provides required scale needed for EOAM for CBH and METROE services
PR Number Synopsis Category:EVPN Layer-2 Forwarding
1396597 A few minutes of traffic loss might be observed during recovery from link failure
 
On EVPN-VXLAN Multi-homing environment, when interface state is changed, a few minutes traffic loss might be observed during recovery from link failure. It happens in this configuration scenario where large (such as, a few hundreds) sub-interface style configurations and ESI are configured in one IFD (Pysical interface), then any change in the IFL (Logical interface) might result in programming all IFLs which share the same ESI, and then multiple updates would be sent to the kernel. At last the l2ald (Layer 2 Address Learning Daemon) would be very busy and it causes a few minutes delay programming of flooding for VTEP interface, and during this period the traffic would be dropped.
PR Number Synopsis Category:EX Chassis Interface Handling
1441035 The ports of the EX device might stay in up state even if the EX46XX/QFX51XX series device is rebooted
 
With DAC cable used between EX46XX/QFX51XX series device and EX device, during rebooting the EX46XX/QFX51XX series device, the ports on EX device might still stay up.
PR Number Synopsis Category:Express PFE FW Features
1448778 Egress sampling for sflow might stop working for more than 8 interfaces on PTX platforms
 
On PTX platforms, if sflow is configured on more than 8 interfaces, egress sampling might stop working due to this issue.
PR Number Synopsis Category:Express PFE L2 fwding Features
1442587 The PMTUD might not work for both IPv4 and IPv6 if the ingress L3 interface is an irb
 
Path MTU Discovery (PMTUD) is a standardized technique for determining the maximum transmission unit (MTU) size on the network path between two IP hosts, usually with the goal of avoiding IP fragmentation. On QFX10K platforms, the PMTUD might not work for both IPv4 and IPv6 if the ingress L3 interface is an irb. The corresponding ICMP Fragmentation Needed packet to the sender might be dropped silently, then PMTUD fails. This issue has service impact.
1446291 On QFX10K platforms removing EVPN-VXLAN L3 Gateway on the IRB interface from spine switches might cause black holing of traffic
 
On QFX10000 platforms and EVPN-VXLAN (spine-leaf) scenario, the QFX10000 spine switches are configured with VXLAN Layer3 gateway (utilizing the virtual-gateway) on an IRB interface, if enabling and then subsequently remove the VXLAN L3 gateway on this IRB interface on one or some of these spine switches, traffic drop might be observed. If all virtual-gateways are configured with an unique v4 or v6 mac-address, this issue would not happen. This is also the workaround.
PR Number Synopsis Category:Enhanced Broadband Edge support for firewall
1463420 The subscribers might not pass traffic after doing some changes to the dynamic-profiles filter
 
On MX platform, with enhanced subscriber enabled, if doing some changes to a dynamic-profiles filter, the subscribers built on the filter might no longer forward traffic.
PR Number Synopsis Category:PTX Express ASIC interface
1412126 PTX interface stays down after maintenance
 
on PTX3000/PTX5000 linecard (QSFP28-100GBASE-LR4) interface may stay down after software upgrade. Issue is usually observed on links connected to another vendors equipment.
PR Number Synopsis Category:Libjtask for RPD tasks, scheduler, timers, memory, and slip
1463368 JDI-RCT:ACX/AMX:MemLeak:Backport jemalloc profiling CLI support to all releases where jemalloc is present.
 
Backport jemalloc profiling CLI support to all releases where jemalloc is present.
PR Number Synopsis Category:Inline NAT PRs for defect & enhancement requests
1446267 The static route for NAT might never come up if switchover the service interface which has NAT and GR configuration
 
On MX platform, when switchover a service interface that has NAT and GR configuration, the static route for NAT might never come up.
PR Number Synopsis Category:Kernel software for AE/AS/Container
1412215 Packet drop might be seen if native VLAN is configured along with flexible VLAN tagging
 
When the native VLAN is configured along with the flexible VLAN tagging on a L3 subinterface, untagged packets might be dropped on that L3 subinterface.
PR Number Synopsis Category:Optical Transport Interface
1467712 "MIC Error code: 0x1b0002" alarm might not be cleared for MIC on MPC5E when the voltage has returned to normal
 
The voltage high alarm might not be cleared when voltage level comes back to normal for MIC on MPC5.
PR Number Synopsis Category:ISIS routing protocol
1455432 The rpd might crash continuously due to memory corruption in ISIS setup
 
With ISIS configured and in a very rare case, memory corruption may occur, this may cause rpd crash continuously.
PR Number Synopsis Category:jdhcpd daemon
1459925 DHCP packet might not be processed correctly if DHCP option 82 is configured
 
In Dynamic Host Configuration Protocol (DHCP) scenario, an zero length sub-option of the option 82 in DHCP DISCOVER message might not be processed correctly causing other DHCP options from DHCP DISCOVER message to be mis-processed as well. This issue has service impact.
PR Number Synopsis Category:Adresses ALG issues found in JSF
1474942 The flowd/srxpfe process might crash when an ALG creates gate with incorrect protocol value
 
On SRX chassis clusters, when an ALG creates gate with incorrect protocol value, the flowd/srxpfe process might crash on one node. This issue might happen in the situation that an ALG receives a corrupted RTO message on secondary node. It might affect the traffic.
PR Number Synopsis Category:Adresses NAT/NATLIB issues found in JSF
1471932 The flowd/srxpfe process might crash when traffic is processed by both ALGs and NAT
 
The flowd/srxpfe process might crash when traffic is processed by both ALGs and NAT.
PR Number Synopsis Category:To track issues related to jsf tcp proxy
1467351 The jbuf process usage may increase up to 99 percent after Junos OS upgrade.
 
The daemon jbuf usage may get a high level after Junos upgrade, resulting in jbuf warning logs and possible jbuf exhaustion, which might eventually cause traffic loss.
PR Number Synopsis Category:Flow Module
1462825 The tunnel packets might be dropped because gr0.0 or st0.0 interface is wrongly calculated after a GRE or VPN route change.
 
On SRX Series device, MTU is wrongly calculated in a gr0.0 or st0.0 interface after a GRE or VPN route change. If the command do-not-fragment is configured and the packet is bigger than the MTU, the packet might be dropped.
PR Number Synopsis Category:JSR Infrastructure
1450545 Traffic loss might occur when there are around 80,000 routes in FIB.
 
On SRX1500 platform, when there are around 800K routes in forwarding information base (FIB), traffic loss might occur and abnormal error messages of some CLI commands would appear due to lack of memory on packet forwarding engine (PFE). This issue has traffic impact.
PR Number Synopsis Category:Firewall Policy
1458639 The NSD process might get stuck and cause problems.
 
On all SRXs that have policy counter configured, there is a potential risk where the network-security daemon (NSD) on the RE could not communicate with its PFE counterpart (NSD-PFE) after either a HA failover, control link down, or PFE restart. At that point, it could no longer respond to network-security related commands and will not be able to complete coldsync for a newly joined node in HA environment.
PR Number Synopsis Category:IPSEC/IKE VPN
1428029 The kmd process stops and generates a core file after running the show security ipsec traffic-selector command.
 
In IPsec scenario, the kmd process might crash when executing the command "show security ipsec traffic-selector source-address <> destination-address <> interface-name <>" with the IP string exceeds 12 characters (e.g. 100.100.100.100 has 15 characters, 12 of the IP address and 3 dots). IPsec VPN tunnel will go down during the kmd process crash and traffic loss might be seen.
PR Number Synopsis Category:Security platform jweb support
1464110 IPv6 address objects containing a,b,c,d,e can't be configured via J-Web
 
When configuring IPv6 address objects under Configure>Security>Objects>Zone Addresses>Addresses/Address-sets via J-web, address objects containing a,b,c,d,e can't be configured. The issue might impact IPv6 service deployment. Please configure address objects containing a,b,c,d,e via CLI command to avoid this issue.
PR Number Synopsis Category:issues related to RPD sensors including LSP
1449837 Changing the hostname will trigger lsp on -change notification, not an adjacency on-change notification. Also, currently ISIS is sending host-name instead of system-id in OC paths.
 
Currently ISIS is sending system host-name instead of system-id in OC paths in lsdb or Adjacency xpaths in periodic streaming and on-change notification.
PR Number Synopsis Category:Layer 2 Circuit issues
1464194 The l2circuit connections might be stuck in OL state after changing the l2circuit community and flapping the primary LSP path
 
In l2circuit scenario with community configured, when the community for l2circuit is changed from X to Y to go via a different LSP, the l2circuit connections might be stuck in "OL" state if there is a flap in the primary LSP path.
PR Number Synopsis Category:Layer 2 Control Module
1431355 The l2cpd process might crash and generate a core dump when interfaces are flapping
 
If there are any conditional groups in the system, the l2cpd process might crash and generate a core dump when interfaces are flapping and the lldp neighbors are available. It might cause the dot1x process to fail and all the ports have a short interruption at the time of process crash.
1469635 Memory leak on l2cpd process might lead to l2cpd crash
 
On all Junos platforms with l2cpd (Layer-2 control protocols) daemon, committing configuration changes which are processed by l2cpd (e.g., flexible-vlan-tagging, stacked-vlan-tagging, vlan-tagging, family ethernet-switching) might cause marginally memory leak. Committing the l2cpd processed configuration changes in a successive manner might cause the memory resource exhaustion (Some operations have the same effect as the committing action, e.g., bouncing a vlan-tagged interface in a successive way). Eventually, it could result in the l2cpd process crash.
PR Number Synopsis Category:Layer2 forwarding on EX/NTF/PTX/QFX
1468732 MAC address might not be learned on a new extended port after VMotion in Junos Fusion Data Center environment
 
In Junos Fusion Data Center environment, when a VM is moved from one satellite port to another using VMotion, MAC address of VM might not move to new satellite port in Aggregate Device's switching table.
PR Number Synopsis Category:Multicast Routing
1443713 PIM (S,G) joins can cause MSDP to incorrectly announce source active messages in some cases
 
In the event of a network running: 1) a first-hop PIM router also being a rendez-vous point (RP); and 2) anycast RP in conjunction with MSDP; and 3) any-source multicast; and 4) a PIM last-hop router sending an (S,G) join when there is no traffic in the network matching the source and group, the first-hop RP will incorrectly send MSDP source-active messages to other MSDP peers. In other cases such as when the RP is not the first-hop PIM router, the traffic source needs to originate packets before the RP would originate MSDP source-active messages.
PR Number Synopsis Category:Multicast for L3VPNs
1469028 The rpd might crash when "link-protection" is added/deleted from LSP for MVPN ingress replication selective provider tunnel
 
In MVPN scenario with ingress replication selective provider tunnel used, if the knob "link-protection" is added/deleted from the LSP for MVPN, rpd crash might be seen. The reason is that when link-protection is deleted, the ingress tunnel is not deleted, and when link link-protection is added back, it tries to add same tunnel, hence the rpd asserts as same tunnel exists. Finally the rpd core might be seen.
PR Number Synopsis Category:FreeBSD Kernel Infrastructure
1425608 The kernel crashes when removing mounted USB while a file is being copied to it
 
If you pulled out a USB from the system while files are being copied, the kernel will panic and the system will restart.
1427233 The duplex status of management interface might not be updated in the output of show command
 
On all Junos platforms that are upgraded to Junos OS Release 15.1 onward, when the duplex setting is changed on the management interface (for example, fxp0/em0), the duplex status of the management interface might not be updated in the output of the "show interface <>".
1442376 EX2300 platforms might stop forwarding traffic or responding to console
 
On EX2300/EX2300-C platforms, if Junos OS is with FreeBSD kernel version 11 with the build date on or after 2019-02-12, the switch might stop forwarding traffic or responding to console. A reboot is required to restore the service.
1450093 EX4300 : CLI config "on-disk-failure" is not supported
 
On an EX4300 switch, the CLI configuration "set chassis routing-engine on-disk-failure disk-failure-action (reboot | halt)" is not supported.
1454950 mgd error found during Junos 18.4R2.7 boot up and Junos did not work as expect
 
Packet Forwarding Engine sometimes does not come up after system reboot.Timeout is required to handle the fifo tx/rx error. Debug sysctls are been removed. Mutex been added to handle to race condition.
1469400 Member of virtual chassis might reboot because of lack of watchdog patting
 
In virtual-chassis scenario on EX3400, if watchdog pat did not happen within stipulated time, member (master or backup or linecard) of virtual chassis might reboot automatically with "0x2:watchdog" as reboots reason.
PR Number Synopsis Category:Kernel socket data replication issues for protocols that use
1472519 The kernel might crash and vmcore might be observed after configuration change is committed
 
The kernel might crash and vmcore might be observed after configuration change is committed.
PR Number Synopsis Category:TCP/UDP transport layer
1437257 The BGP session might flap after performing RE switchover simultaneously on both end of BGP peers
 
On all Junos platforms with GRES enabled, if BGP is configured with NSR and MD5 authentication in logical-systems, the BGP sessions might flap after performing Routing-Engine switchover simultaneously on both end of BGP peers.
PR Number Synopsis Category:OSPF routing protocol
1444728 The rpd crash might be seen after configuring OSPF nssa area-range and summaries
 
In the scenario of running OSPF, if nssa area-range and summaries are configured, the rpd crash may occur and traffic may be lost.
PR Number Synopsis Category:Protocol Independant Multicast
1427720 Multicast traffic might be lost for around 30 seconds during RE switchover
 
On MVPN supported platform with PIM enabled, when multiple lo0.* interfaces are configured with the same IP address, and lo0.0 belongs to master routing instance and all the other lo0.* interfaces belong to another routing instance, around 30 seconds multicast traffic loss might be seen during RE switchover.
PR Number Synopsis Category:Periodic Packet Management Daemon
1448670 The connection between ppmd(RE) and ppman(FPC) might get lost due to session timeout
 
Under certain circumstances such as JUNOS VM freeze at the Routing Engine, ppmd to ppman connection might be closed if the session timeout is greater than 3 seconds in either direction. This might lead to flapping of distributed ppm protocol adjacency such as lacp/mBFD.
PR Number Synopsis Category:PTP related issues.
1408178 QFX5k : Transit traffic loss when one of LAG child interfaces deleted or deactivated
 
Traffic does not pass through LAG interface on QFX5k once deleted or deactivated one of child interfaces though LAG interface is UP state. At that time, invalid vlan tag will be added to traffic.
PR Number Synopsis Category:Interface related issues. Port up/down, stats, CMLC , serdes
1423496 Ports may get incorrectly chanalized if they are 10G already and they are channelized to 10G again
 
On all junos platforms with channelizing ports on FPCs, if a 40G port which are channelized to 10G ports already (eg:xe-2/0/16:0) are being channelized to 10G again, they may get incorrectly channelized.
1440062 The EX4600/QFX5100 VC might not come up after replacing VC port fiber connection with DAC cable
 
On the EX4600/QFX5100 virtual chassis scenario, the VC may split after replacing VC port fiber connection with DAC cable.
1449406 CRC error might be seen on the VCPs of the QFX5100 VC
 
In QFX5100 VC (Virtual Chassis) scenario, CRC (Cyclic Redundancy Check) error might be seen on the VCPs (Virtual Chassis Port) when the VCPs are "BCM84328 PHY" ports. The CRC error indicates there is data corrupt, the issue might reduce the system performance. The issue can be avoided by using non-"BCM84328 PHY" ports as VCPs to build the VC.
1449406 CRC error might be seen on the VCPs of the QFX5100 VC
 
In QFX5100 VC (Virtual Chassis) scenario, CRC (Cyclic Redundancy Check) error might be seen on the VCPs (Virtual Chassis Port) when the VCPs are "BCM84328 PHY" ports. The CRC error indicates there is data corrupt, the issue might reduce the system performance. The issue can be avoided by using non-"BCM84328 PHY" ports as VCPs to build the VC.
PR Number Synopsis Category:QFX Platform related (SYSLOG/ALARMS/miscellaneous)
1419732 "show interface" indicates "Media type: Fiber" on QFX5100-48T running "QFX 5e Series" image.
 
"show interface" indicates "Media type: Fiber" on QFX5100-48T running "QFX 5e Series" image. This is a display issue. Physical interface: xe-0/0/0, Enabled, Physical link is Down Interface index: 650, SNMP ifIndex: 515 Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Link-mode: Auto, Speed: Auto, BPDU Error: None, Loop Detect PDU Error: None, Ethernet-Switching Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Disabled, Remote fault: Offline, Media type: Fiber <<<<<< Here!! Should be "Copper" Device flags : Present Running Down Interface flags: Hardware-Down SNMP-Traps Internal: 0x4000 Link flags : None
1422958 QFX5100-48T 10G interface might be auto-negotiated at 1G speed instead of 10G
 
QFX5100-48T 10G interface might be auto-negotiated at 1G speed instead of 10G after peer device reboot. This issue will cause link down and impact customer service.
1454527 Dcpfe should crash because usage of data is not NULL terminated on QFX5K
 
The dcpfe crash is due to usage of data which is not NULL terminated on QFX5K.
1465183 PEM is not present spontaneously on QFX5210
 
On QFX5210 platforms, due to a firmware issue on the power supplies (PEMs) of the switch, the routing engine may spontaneously misread the status registers of a power supply. This produces erroneous messages of PEM not present. Although the power supply is present and can deliver power, the system may then deactivate the power supply believing it not to be present.
1466810 EPR iCRC errors in QFX10000 series platforms might cause protocols down
 
EPR iCRC errors in QFX10000 series platforms might cause protocols down. FPC will be in wedged state and will not pass traffic on that PFE if hitting this issue. EPR iCRC errors are normal and caused by transient hardware conditions. EPR iCRC errors are not expected to impact the protocols, and only one CRC failed packet will be dropped. But due to incorrect handling of this error, it affects protocols and causes FPC wedge.
1471216 The speed 10m might not be configured on the GE interface
 
On QFX5100 and EX4300 mixed-mode Virtual Chassis, the speed 10m might not be configured on the GE interface.
PR Number Synopsis Category:QFX platform optics related issues
1458363 Intermittent LAG interface flaps might be seen on QFX platforms
 
On QFX platforms with Link Aggregation Group (LAG) interface, if periodic "SFP diagnostic" is configured with short interval (e.g. test sfp periodic diagnostic-interval 3), the LAG interfaces might have intermittent flaps and therefore bring service impact due to this issue.
PR Number Synopsis Category:QFX access control list
1464883 QFX5100-24Q: not able to apply dscp rewrite to firewall filter to a Layer 3 subinterface (e.g. xe-0/0/0.100)
 
When you try to apply a firewall filter that contains a "then dscp" action to a Layer 3 inet subinterface, you will get an error when trying to commit. Applying the same filter to an IRB interface succeeds as does applying the same filter to a Layer 3 subinterface on QFX5100-48S.
PR Number Synopsis Category:QFX PFE Class of Services
1468033 Ingress drops to be included at CLI from interface statistics and added to InDiscards
 
In QFX5000 platforms, as Ingress buffer drops (InDiscards) field is not presented the output of "show interfaces extensive x-x/x/x". This change added ingress buffer drops counters.
1472223 The shaping of COS does not work after reboot
 
On EX/QFX Series platforms, the shaping of CoS does not work after reboot when the shaping rate is configured with an absolute value. The line rate of traffic is sent out and no shaping occurs. This issue has traffic or service impact.
PR Number Synopsis Category:DHCP related Issues
1459499 JDI-_QFX5200_-REGRESSION-SWITCHING-QFX5200: dhcpv6 LDRA relay bounded count is not as expected after dchp configured
 
On qfx5k platforms dhcp6 security with LDRA option is not supported. When ldra is configured, ldra filter to punt packets to host path is conflicting with system default dhcpv6 relay filter, hence packets are not punted to host path.
PR Number Synopsis Category:Filters
1462594 The fxpc process might core-dump when changing MTU in a VXLAN scenario with firewall filters applied on QFX5K platforms
 
On the QFX5K VC/VCF platform with firewall filters applied on VXLAN enabled interface, the fxpc process might crash when changing MTU for the interface.
PR Number Synopsis Category:for all ipv6 related issues
1459759 The fxpc process might crash due to several BGP IPV6 session flaps
 
On QFX5100 and EX4600 platforms, the fxpc (packet forwarding engine manager) process might crash when multiple BGP IPV6 sessions (for instance around 500) are flapped and then restored at the same time.
PR Number Synopsis Category:QFX L2 PFE
1474545 Continuous error log messages might be raised on QFX5K platforms in EVPN/VXLAN scenario
 
In EVPN-VXLAN scenario, when an SP style interface is configured both with native-vlan-id and LLDP on QFX5000 platforms, continuous log messages might be observed.
PR Number Synopsis Category:QFX L3 data-plane/forwarding
1456336 Link up delay and traffic drop might be seen on mixed SP L2/L3 and EP L2 type configs
 
This PR includes three issues. First one: When Layer3 IFL (logical interface) is configured first and then Layer2 IFL is configured, MAC move might not happen. Second one: On Vxlan setup with large number of child interfaces, link up delay is seen. Third one: In case of VLAN setup with Enterprise/Service Provider L2 and L3 type configs, when all the configs are done in single commit statement then the traffic might not be forwarded.
PR Number Synopsis Category:QFX MPLS PFE
1469998 If continuous interface flaps at ingress/egress of PE devices, IP routed packets might be looped on the MPLS PHP node
 
On QFX5K platform, when MPLS node-link-protection is configured on all nodes (PE and P device), the IP routed packets might be looped on the MPLS PHP node (P device) if continuous interface flaps at ingress/egress of PE devices.
PR Number Synopsis Category:QFX EVPN / VxLAN
1463939 JDI-RCT : QFX 5100 VC/VCF : Observing Error BRCM-VIRTUAL,brcm_vxlan_walk_svp(),6916:Failed to find L2-iff for ifl: while cleanup Evpan-VxLAN configs with Mini-PDT base configurations
 
On QFX5100, Error BRCM-VIRTUAL,brcm_vxlan_walk_svp(),6916:Failed to find L2-iff for ifl: may come while cleanup Evpn-VxLAN configs. These are harmless messages.
PR Number Synopsis Category:QFX VC Infrastructure
1465196 A 10G interface might not come up on QFX5100-48T switches or negotiate at speed 1G when connected with Broadcom 57800-T daughter card
 
On QFX5100-48T, the 10G interface might not come up or negotiate at the speed of 1G with Broadcom 10G 57800-T daughter card. In the issue state, speed will be set to 1G which might make the interface down and result in traffic impact.
PR Number Synopsis Category:QFX VCCP
1454343 Master FPC might come up in master state again after reboot instead of backup
 
In QFX5110-32Q VC with 100G VCP links, if the master switch with the lowest MAC address reboot, it might come up in the master state again instead of backup. This can have outage around ten minutes and packets loss.
PR Number Synopsis Category:KRT Queue issues within RPD
1386475 The rpd process might end up with stuck krt queue entries in a VRF scenario
 
In rare cases, if using vrf configurations along with a static default route to em0 or fxp0, the interface flaps may result in rpd end up with krt queue stuck.
PR Number Synopsis Category:RPD Next-hop issues including indirect, CNH, and MCNH
1441550 The rpd may crash or consume 100% of CPU after flapping routes
 
When flapping the existed flood nexthop type routes, it may cause rpd crash or consume 100% of CPU. This issue may cause routing protocols sessions/neighbors flap or traffic loss.
PR Number Synopsis Category:RPD policy options
1451025 The rpd might crash after RE switchover when prefix-list is configured
 
On all Junos platforms, when two prefix-lists are configured one after another, and the first prefix-list contains apply-path whereas the second prefix-list does not contain apply-path, after RE switchover, rpd might crash on new master RE.
1453439 Routes resolution might be inconsistent if any route resolving over the multipath route
 
On all Junos platforms, any route resolving over the multipath routes, one scenario is BGP over BGP. After the metric value of any PNH (refers to the second PNH and using it to performing the second time next-hop resolving) changes, meanwhile, if the hash-selection changes happened, it might result in routes resolution inconsistency. Traffic drops could be observed if the packages are still forwarding to the old PNH (Protocol Next Hop). Any recursive resolving multipath scenario might trigger this issue.
1476530 Support for dynamic-tunnels on SRX-Series devices was mistakenly removed
 
Support for dynamic-tunnels on SRX-Series devices was mistakenly removed.
PR Number Synopsis Category:RPD route tables, resolver, routing instances, static routes
1459384 The rpd memory leak might be observed on backup routing engine due to BGP flap
 
In a BGP scenario when certain routes are flapping frequently, it could lead to rpd memory leak on backup Routing Engine. The rpd might crash and restart once the rpd runs out of memory for certain junos releases.
PR Number Synopsis Category:show route table commands, tracing, and syslog facilities
1442542 EVENT UpDown interface logs are partially collected in syslog messages
 
When multiple interfaces UpDown event happens, a number of interfaces are not logged the event but partial logs are recorded in messages file.
PR Number Synopsis Category:multicast source distribution protocol
1454244 The rpd memory might leak in a certain MSDP scenario
 
In the Multicast Source Discovery Protocol (MSDP) scenario, where the router acts as both Rendezvous Point (RP) and First Hop Router (FHR), connecting to another RP in its AS with a logical loop topology, due to this special setup, it might cause a source-active (SA) message continuously to loop and eventually causes the rpd memory leak.
PR Number Synopsis Category:Resource Reservation Protocol
1471281 The rpd crash might be seen after doing some commit operations which could affect RSVP ingress routes
 
On all platforms with BGP PIC configured, if doing some commit operations where RSVP ingress routes are affected, the rpd crash might be seen.
1476773 RSVP LSPs might not come up in scaled network with very high number of LSPs if NSR is used on transit router
 
If NSR is enabled on transit router with scaled RSVP LSPs, RESV message might not be sent from transit router because the path messages replication on master RE does not complete in time. Hence RSVP LSPs might not come up with traffic impact.
PR Number Synopsis Category:RPM and TWAMP
1333190 [RIO NPI-TWAMP]: Test sessions packets are dropped on server when DF bit is set to 1
 
When TWAMP test session packets from TWAMP client are received by TWAMP server with DF bit set(1), TWAMP server is dropping the packets and TWAMP test session are not established.
PR Number Synopsis Category:IPSEC functionality on M/MX/T ser
1477483 On NATT scenario the IKE Version 2 IPsec tunnel might flap if the tunnel initiator is not behind NAT
 
On MX platforms with MS-MPC/MS-MIC card installed and NATT scenario, when the IPsec tunnel initiator is not behind NAT, it might cause IPsec tunnel flapping. It happens in IKEv2 scenario.
PR Number Synopsis Category:Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1396785 The MS-MPC might core when mspmand receives a non-syn packet of TCP
 
On MX Series platforms and when MS-MPC line card is used, if the ms/ams-interface is not configured and mspmand (Multiservices PIC management daemon) receives a non-synchronized packet of TCP, the MS-MPC might crash due to some NULL pointer issues of the global configuration variable.
1459306 The traffic might be stuck on MS-MPC/MS-MIC with sessions receiving huge number of affinity packets
 
On MX platforms with MS-MPC/MS-MIC, if there are sessions receiving huge number of affinity packets (e.g. thousands of packets), the service interface might be brought down by the prolonged flow-control, and the mspmand process crash might happen. In this case, the traffic will be stuck due to this issue.
PR Number Synopsis Category:SFW, CGNAT on MS-MIC/MS-MPC (XLP)
1425405 The mspmand process might crash and restart with a mspmand core file created after doing a commit change to deactivate and activate service-set
 
On MX-Series platforms with NAT pool PBA (Port Block Allocation) configuration, the mspmand process might crash and restart with a mspmand core file created if a NAT pool PBA configuration is changed. The impact is that it might cause a service traffic loss.
PR Number Synopsis Category:platform related PRs on SRX branch platforms
1468430 Tail drop on all ports is observed when any switch-side egress port gets congested.
 
On the SRX300 line of devices with Mini-PIM installed, tail-drop might happen on all ports when the serial egress port gets congested.
PR Number Synopsis Category:SRX-1RU platfom datapath SW defects
1462610 Srxpfe/flowd process might crash if changing the sampling configuration
 
On all SRX platforms, if Jflow is configured and there is a sampling configuration change, the srxpfe/flowd process might crash. This is a corner issue. It might cause traffic loss.
PR Number Synopsis Category:Trio pfe l3 forwarding issues
1444186 GRE packets which are larger than MTU get dropped on MX204 platforms when sampling is enabled on the egress interface
 
On MX204 platforms, if GRE packet length exceeds MTU of gr interface and the egress interface is configured with sampling, it might cause GRE packet to be dropped because the reassembled packet's checksum is incorrect.
PR Number Synopsis Category:Configuration management, ffp, load action
1426341 Switch may unable to commit baseline config after zeroize
 
When the OpenConfig package is used (The OpenConfig package became part of image itself from 18.3, prior to 18.3 OpenConfig package is a seperate add-on package), the following switches (EX2200, EX3200, EX3300, EX4200, EX4300, EX4500, EX4550, EX4600, QFX3000, QFX3100, QFX3500, QFX3600, QFX5100) may unable to commit baseline config after zeroize.
PR Number Synopsis Category:UI Infrastructure - mgd, DAX API, DDL/ODL
1423229 While commiting huge configuration, customer is seeing the error "error: mustd trace init failed"
 
"error: mustd trace init failed" during configuration commit.
1464439 The CPU utilization on mgd daemon might be stuck at 100% after the netconf session is interrupted by flapping interface
 
If a netconf session is initiated over inband connection, the CPU utilization on mgd daemon might be stuck at 100% after the netconf session which is executing an RPC call for some commands gets interrupted by flapping interface. There is no impact observed to control-plane or forwarding-plane, the subsequent netconf session will continue to function.
PR Number Synopsis Category: PTX/QFX 10000 platform
1464119 FPC might restart during run time on PTX10K/QFX10K platforms
 
On PTX10K/QFX10K platforms, FPC might restart if there is some corruption in BCM (Broadcom) switch (a small internal ethernet switch, instead of PFE engine) inside the FPC. It is a timing issue. The reason is that the PCIe speed configuration for BCM switch is not correct. And this issue is resolved in some FPC U-boot versions.
Modification History:
First publication date 2020-01-13
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Security Alerts and Vulnerabilities

Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search