PR Number |
Synopsis |
Category: EX2300/3400 platform |
1477165 |
EX3400 me0 interface might remain down
|
The me0 interface of EX3400 does not come up when connected to 100m speed interface. |
PR Number |
Synopsis |
Category: MX10008/16 Platform |
1420571 |
"show chassis power" output status doesn't seem right and there are also similar error messages in the syslog after turn off / on power feed
|
After changing the power feed(s), either turn off or turn on, show chassis power outputs do not match real condition and there are also incorrect Syslog information recorded. |
1420571 |
"show chassis power" output status doesn't seem right and there are also similar error messages in the syslog after turn off / on power feed
|
After changing the power feed(s), either turn off or turn on, show chassis power outputs do not match real condition and there are also incorrect Syslog information recorded. |
PR Number |
Synopsis |
Category: ACX Services feature |
1479710 |
dcpfe core when disabling/enabling macsec via Toby scripts
|
dcpfe core when disabling/enabling macsec via Toby scripts |
PR Number |
Synopsis |
Category: Border Gateway Protocol |
1473351 |
Removing cluster from BGP group might cause prolonged convergence time
|
Cluster removal from BGP group might lead to a state where each subsequent change to BGP configuration will trigger import policy reevaluation causing prolonged convergence time of several minutes. This might result in a traffic loss. |
1487691 |
High CPU utilization might be observed when the outgoing BGP updates are sending slowly
|
On all Junos platforms with BGP scenario, the rpd process might go into high CPU utilization if there are a few BGP peers that are sending the updates slowly. The high CPU utilization of the BGP IO thread (bgpio, it is part of the rpd daemon) happens when the outgoing BGP update queue is full. This defect could cause a slow BGP network convergence problem. (See also https://kb.juniper.net/TSB17725) |
PR Number |
Synopsis |
Category: Class of Service |
1472083 |
Unexpected traffic loss might be discovered in certain conditions under fusion scenario
|
On MX platform with enhanced queuing MPC under fusion scenario, EP (Extended Port) hosted on multiple CPs (Cascade Port) which are from different PFEs on the same FPC. Unexpected traffic loss might be observed if a CoS policy with the knob "rate-limit" is applied. |
PR Number |
Synopsis |
Category: DNX platform MPLS FRR features |
1485444 |
ACX5448 L2VPN with interface ethernet-ccc input-vlan-map/output-vlan-map can cause traffic blackhole
|
On the ACX5448 platform, l2vpn application with ethernet-ccc input-vlan-map/output-vlan-map can experience traffic blackhole while the control plane is still up. This issue is a software defect introduced by changes made via PR1456624 in the ethernet-ccc ingress interface. This software defect adds an internal vlan tag to all packets. As a result, customers' desired vlan-tag was not added in ccc->mpls direction. Causing the remote PE -- expecting vlan-tagged traffic -- to drop these packets due to vlan mismatch. |
PR Number |
Synopsis |
Category: Express PFE Services including JTI, TOE, HostPath, Jflow |
1379227 |
PTX10008: error logs seen when flows are sample through aggregate bundles when jflow sampling enabled
|
When you sample flows which the ingress and egress interfaces are of "aggregate" type on PTX10000s and QFX10000s, you may see syslog info messages about "expr_get_local_pfe_child_ifl" and "flowtb_get_cpu_header_fields". Even though these messages are non-impact messages, they will crowd syslog files and syslog servers. |
PR Number |
Synopsis |
Category: Express PFE L3 Multicast |
1389569 |
BFD flaps are seen on PTX or QFX10K platforms with inline BFD
|
With inline-BFD configured on the PTX or QFX10000 platforms, BFD sessions might flap continuously. |
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: Security platform jweb support |
1431298 |
Junos OS: Path traversal vulnerability in J-Web
|
A path traversal vulnerability in the Juniper Networks Junos OS device may allow an authenticated J-web user to read files with 'world' readable permission and delete files with 'world' writeable permission. Refer to https://kb.juniper.net/JSA10985 for more information. |
PR Number |
Synopsis |
Category: FreeBSD Kernel Infrastructure |
1439906 |
FPC might reboot if jlock hog occurs on all Junos VM based platforms
|
On a JUNOS VM using TSC clocking from the host system, "jlock hog" messages may be seen. This may lead to FPCs reboot. |
1454950 |
EX switches might not come up properly upon reboot
|
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
|
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: 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: Resource Reservation Protocol |
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: MX10003/MX204 Platform SW - Chassisd s/w defects |
1449067 |
FPC might reboot during off-lining PIC 0 on MX204 platform
|
On MX204 platform with 4XQSFP28 PIC, off-lining PIC 0 might result in FPC reload. |
PR Number |
Synopsis |
Category: Trio pfe qos software |
1430878 |
With CNH for 6PE, MPLS EXP rewrite rule for non-VPN IPv4 over MPLS traffic might not work
|
On platforms that use Trio PFE (MX/EX9200/T4000), when Chained Composite Next-Hop for 6PE is configured, Class of Service MPLS EXP rewrite rule for non-VPN IPv4 over MPLS traffic ('protocol mpls-inet-both-non-vpn') may not work when a BGP 6PE route using the same MPLS LSP (same BGP next-hop) exists. This happens after the MPLS LSP next-hop is re-programmed, e.g. due to the network convergence. |
PR Number |
Synopsis |
Category: PTX/QFX10002/8/16 specific software components |
1412318 |
hostname does not update at FPC shell after system configuration change on CLI
|
On PTX platform, hostname does not update at FPC shell after host name change unless FPC reboot. |