| PR Number |
Synopsis |
Category: EX2300/3400 platform |
| 1477165 |
EX3400 me0 interface might remain down
Product-Group=junos |
The me0 interface of EX3400 does not come up when connected to 100m speed interface. |
| PR Number |
Synopsis |
Category: NFX Series Platform Software |
| 1458554 |
Static MAC address getting replaced by random MAC.
Product-Group=junosvae |
In 19.2R1, the device will not take the statically assigned MAC address from the CLI configuration. This is fixed in junos:19.2R2 junos:19.3R3 junos:19.4R2 junos:20.1R1. This issue was caused by an issue with the intel drivers. |
| 1459885 |
VMhost mapping changes for a particular NIC should be done by first deleting the vmost mapping and then configuring the new mapping
Product-Group=junosvae |
On NFX150 devices, when you need to change the vmhost mappings of a particular NIC or NICs, you must delete the existing vmhost mapping and commit the configuration. Now you can configure the new mappings for the respective NICs. You cannot change the NIC vmhost mappings in the same commit to delete and add a new mapping to the heth NICs. |
| 1478456 |
NFX350: VNF Instantiation using XMl with interfaces mapped to VF doesn't work.
Product-Group=junosvae |
If a VNF is spawned using XML and the XML has interfaces with mapping to Virtual functions then the VNF will not come up. |
| PR Number |
Synopsis |
Category: QFX ISSUE PFE related |
| 1472183 |
ISSU will not be supported for QFX5K for some versions
Product-Group=junos |
On QFX5K platforms, during unified ISSU from previous releases to some Junos OS Release (19.2R1-S1, 19.4R1 and so on.), dcpfe will crash continuously and hence ISSU will not work. |
| PR Number |
Synopsis |
Category: QFX PFE L2 |
| 1467466 |
Few MAC addresses might be missing from MAC table in software on QFX5k platform.
Product-Group=junos |
On QFX5k platform, if Packet Forwarding Engine process is restarted manually or device reboot occurs, some MAC address(es) might not be seen on software MAC table but MAC address will be present in hardware table. |
| PR Number |
Synopsis |
Category: This is for Hw & Sw issues which are special for SPC3 car |
| 1479001 |
When SRX5K-SPC3s or MX-SPC3s are installed in slots 0 or 1 in a SRX5800 or MX960 chassis, EMI radiated emissions are observed to be higher than regulatory compliance requirements
Product-Group=junos |
When SRX5K-SPC3s or MX-SPC3s are installed in slots 0 or 1 in a SRX5800 or MX960 chassis, EMI radiated emissions are observed to be higher than regulatory compliance requirements |
| PR Number |
Synopsis |
Category: Border Gateway Protocol |
| 1487691 |
High CPU utilization might be observed when the outgoing BGP updates are sending slowly
Product-Group=junos |
On all Junos platforms with the BGP routing protocols, the rpd process might go into a high CPU utilization causing slow network convergence. If a BGP peer is receiving and processing BGP updates slowly, this may cause the BGP output queue of the sending BGP peer to be full. When the queue is full it causes high CPU utilization of the BGP IO thread (bgpio, it is part of the rpd daemon) on the sending BGP peer. This defect could cause network-wide slow BGP network convergence. (See also https://kb.juniper.net/TSB17725) |
| PR Number |
Synopsis |
Category: MX Platform SW - FRU Management |
| 1463169 |
The RE switchover may not be triggered when the primary CB clock failure
Product-Group=junos |
On the specific Junos platforms, the RE switchover may not be triggered when the primary CB clock failure is detected. The primary CB with faulty clock can't operate normally and this issue may cause fabric plane failure. |
| PR Number |
Synopsis |
Category: L2NG Access Security feature |
| 1478375 |
The process dhcpd may crash in a Junos Fusion environment
Product-Group=junos |
On EX92XX platforms with the DHCP snooping configured, if a peer receives DHCPv6 packets from the server without the "client-id" option present, and it is syncing packets to the other side at that time, then the process dhcpd crash may be observed. |
| PR Number |
Synopsis |
Category: OpenSSH and related subsystems |
| 1475255 |
EVO: sftp does not connect properly: "Received message too long" error
Product-Group=junos |
Due to issues with the way ssh subsystems are handled, SFTP (services ssh secure-ftp) does not function properly under Evo |
| PR Number |
Synopsis |
Category: Express PFE L2 fwding Features |
| 1474876 |
The input-vlan-map/output-vlan-map might not work properly in L2circuit local-switching scenario
Product-Group=junos |
On PTX1K/PTX10K platforms, in L2circuit local-switching scenario, when vlan-ccc encapsulation is configured with input-vlan-map/output-vlan-map, all traffic passing through might have unexpected vlan manipulation (vlan tag push/pop/swap). |
| PR Number |
Synopsis |
Category: Platform infra to support jvision |
| 1479642 |
JDI_TPTX_REG_Observe the core "mib2d.core-tarball" verifying the onchange functionality.
Product-Group=junos |
mib2d will core while deleting channelised interfaces. |
| PR Number |
Synopsis |
Category: Layer 2 Control Module |
| 1478157 |
"show evpn statistics instance" command gets stuck on multihomed scenario.
Product-Group=junos |
"show evpn statistics instance" command gets stuck on multihomed scenario. The command shall give proper output but will not terminate and only time out. Ctrl+C can be used to exit the command immediately. |
| PR Number |
Synopsis |
Category: Label Distribution Protocol |
| 1474204 |
LDP/BFD sessions are not coming up in scaled setup
Product-Group=junos |
On MPC10/MPC11 line card, the LDP/BFD sessions are dropped when the fast-lookup-filter has a default term with only accept as action and it is attached to the lo0 interface. |
| PR Number |
Synopsis |
Category: mc-ae interface |
| 1479012 |
MC-AE interface may be shown as unknown status if adding the sub-interface as part of the VLAN on the peer MC-AE node
Product-Group=junos |
If adding the sub-interface as part of the VLAN on the peer MC-AE node while its corresponding MC-AE interface is still not configured to be part of the VLAN, the status of the MC-AE interface might be shown as unknown. It might have an impact on the traffic as the colour of the MC-AE interface could not be updated correctly. |
| PR Number |
Synopsis |
Category: FreeBSD Kernel Infrastructure |
| 1442376 |
EX2300 platforms might stop forwarding traffic or responding to console
Product-Group=junos |
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. |
| 1454950 |
EX switches might not come up properly upon reboot
Product-Group=junos |
EX switches might not come up properly upon reboot due to the date not been set up |
| 1469400 |
EX3400 might reboot because of lack of watchdog patting
Product-Group=junos |
On EX3400, if watchdog pat did not happen within stipulated time and it might reboot automatically with "0x2:watchdog" as reboot reason. |
| PR Number |
Synopsis |
Category: OSPF routing protocol |
| 1452118 |
The TI-LFA backup path for adj-sid is broken in OSPF
Product-Group=junos |
The TI-LFA (Topology-Independent Loop-Free Alternate) backup path for adj-sid is broken in OSPF where the shortest path to the node opposite the adj-sid is not the one hop path over the interface indicated by the adj-sid. If the backup path is broken when the primary path fails, it will cause traffic loss. |
| PR Number |
Synopsis |
Category: Filters |
| 1472206 |
QFX5K: Egress PACL size will be half in 19.4R1
Product-Group=junos |
Because of change in new SDK, egress filter's slice usage will be double and these will be only 512 entries in Junos OS Release 19.4R1. This will be fixed in R2. |
| 1472206 |
QFX5K: Egress PACL size will be half in 19.4R1
Product-Group=junosvae |
Because of change in new SDK, egress filter's slice usage will be double and these will be only 512 entries in Junos OS Release 19.4R1. This will be fixed in R2. |
| PR Number |
Synopsis |
Category: QFX L2 PFE |
| 1475430 |
There might be traffic drop on QFX5110/5120 switches acting as leaf switch in a multicast environment with VxLAN
Product-Group=junos |
In a multicast environment where IGMP-snooping is enabled with VxLAN and QFX5110/5120 switches act as leaf switch, there might be traffic drop as the switch might fail to forward the traffic to Assisted Replicator (AR-replicator)/Spines when BGP is flapped on Spine switch. This is a rare issue noticed when the route installation messages are received out-of-order on leaf switch. |
| PR Number |
Synopsis |
Category: Trio pfe bridging, learning, stp, oam, irb software |
| 1467764 |
The Layer-2 traffic over ae interfaces sent from one member to another is corrupted on MX-VC setup
Product-Group=junos |
On MX-VC setup with bridge-domains configured, if ae interface is used within bridge-domain, and if the ingress ae and egress ae interface host in different VC members, the Layer-2 traffic over ae sent from one member to another is getting corrupted. |