| PR Number |
Synopsis |
Description |
| 1298561 |
MPC stops forwarding traffic upon using service queue-monitoring application or once using ddos flow-detection
|
If the application ddos flow-detection(SFCD) or QMON (set services analytics resource-profiles bla queue-monitoring) are configured, local packet forwarding context memory could get overwritten and corrupting the dispatch cookie causing permanent forwarding issue.
|
| 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 (i.e., the destination address belongs to the device) come from the interface with ingress filter of log/syslog action (e.g., 'filter <> term <> then log/syslog'), such packets should not be dropped and reach the routing engine.
|
| 1398128 |
The alarm might be seen if the PEM's serial number starts with "1F1"
|
On ACX/EX/QFX/SRX platforms, if the PEM's serial number starts with "1F1", the alarm "Minor FPC PEM Temp Sensor Failed" might be seen.
|
| 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.
|
| 1423171 |
The interface can not get up when the remote-connected interface only supports 100M in QFX5100 VC setup
|
If QFX5100-48T is not the master in VC/VCF scenario, the interface can not get up when the remote-connected interface with auto-negotiation configured only supports 100M.
|
| 1434980 |
PFE memory leak might be seen if MLPPP links are flapped
|
On all Trio-based platforms, MLPPP links flap continuously might result in PFE memory exhaustion. Furthermore, the PFE crash might be seen due to running out of memory.
|
| 1439073 |
Interfaces configured with flexible-vlan-tagging might loss connectivity
|
On QFX5000 series platform and related products (like ACX5K and EX4600), a port configured in service provider style (flexible-vlan-tagging) might lose connectivity over the native VLAN when additional tagged VLANs are added to it. The impact is that all the hosts' traffic over the designated native VLAN might be dropped.
|
| 1443353 |
The cfmd process might crash after a restart on Junos 17.1R1 and above
|
On MX platforms running Junos 17.1R1 and above, when enhanced-ip mode and CFM centralized mode ("no-aggregate-delegate-processing" konb is configured for CFM) are used , after a cfmd restart (e.g. device cold start/restart, RE switchover), the cfmd process might crash and could not run anymore.
|