| PR Number |
Synopsis |
Description |
| 1115686 |
RPD memory leak caused by repeated RSVP RSB (reservation state block) deletes |
When an RSVP path is deleted (because
of LSP deletion or switch-over to new path) RSB (Reservation state
block) data structure has to be deleted to free up memory. When RSB
deletion is performed, LSP attribute object in RSB is not deleted by
RPD. This causes build up of RPD memory usage over a period of time
(memory leak). Build up of RPD memory is proportional to the frequency
of RSB deletes. |
| 1265548 |
Traffic drop on MPC with "Link sanity checks" and "Cell underflow" errors |
When certain hardware transient
failures occur on an MQ-chip based MPC, traffic might be dropped on the
MPC, and syslog errors "Link sanity checks" and "Cell underflow" are
reported. There is no major alarm or self-healing mechanism for this
condition. |
| 1275766 |
The rpd may crash in LDP L2circuit scenario |
In an L2 circuit scenario, while
processing an advertisement of LDP signaled L2 circuit, it gets stale
binded because of the corrupted LDP structure. As a result, the rpd
crashes. |
| 1278153 |
After bfdd restart seen issue with ng mvpn and l2vpn route exchange causing mVPN and vpls traffic drop |
bfd daemon kill or restart on PE
router is causing issue with ng mvpn and l2vpn route exchange and result
is traffic drop. Work around is to clear bgp neighbor on router
reflector. |
| 1293014 |
traffic drop during NSR switchover for RSVP P2MP provider tunnels used by MVPN |
When next-generation MVPN is
configured with RSVP provider tunnels and NSR is used, then the egress
router for the tunnel might not correctly replicate some of the tunnel
state to the backup Routing Engine, leading to temporary traffic loss
during NSR failover for the affected tunnels. |
| 1298175 |
L2TP subscribers might get stuck in terminating state during login. |
Layer 2 Tunneling Protocol (L2TP) and
L2TP access concentrator (LAC) subscribers might get stuck in
terminating state because of the race condition during login. |
| 1298612 |
MX platforms may display false positive CB alarm "PMBus Device Fail". |
MX platforms may display false positive CB alarm "PMBus Device Fail". |
| 1299580 |
The traffic in P2MP tunnel might be lost when NG-MVPN uses RSVP-TE |
In the case of NG-MVPN
(Next-Generation Multicast VPN) and RSVP-TE (Resource Reservation
Protocol Traffic Engineering) are configured at the same time, the
traffic in P2MP tunnel might be lost if NG-MVPN has more than one
routing instances on router. |
| 1300716 |
Interfaces might go down when PFE encounters "TOE::FATAL ERROR" |
Interfaces might go down when PFE
(Packet Forwarding Engine) encounters "TOE::FATAL ERROR" (TOE is a
module in PFE, the fatal error can be caused either by software issue or
hardware issues like memory parity errors or others). Please reboot the
line card to recover the service when hitting the issue. |
| 1300989 |
Condition based policy fails to take action even though condition is matched |
When the policy condition
configurations are used in export policy in BGP add-path scenario,
condition based policy fails to take action even though condition is
matched. |
| 1303459 |
Fan speed changes frequently on MX Series after an upgrade to JUNOS software with the change introduced by PR:1244375 |
On routers with XM-chip based line
cards (e.g., MX platform with MPC3E/4E/5E/6E/2E-NG/3E-NG), log messages
might report fan speed changes between full and normal speed
continuously, due to XM-chip reaches a temperature threshold. |
| 1305284 |
Dfwd might crash during execution of "show firewall templates-in-use" command |
In a subscriber-management
environment, dfwd process might crash during execution of "show firewall
templates-in-use" command if a CLI session disconnects before the
complete output of this command is received. |
| 1306930 |
The RSVP node-hello packet might not work correctly after the next-hop for remote destination is changed |
An unexpected error such as an RSVP
authentication failure, or an RSVP node-hello packet is rejected when
the next-hop for remote node's loopback is changed. |
| 1309288 |
PFE error messages are flooding as
"expr_sensor_update_cntr_to_sid_tree" after delete and rollback
"protocols isis source-packet-routing node-segment " |
This problem would occur when we do
delete and rollback protocols isis source-packet-routing node-segment.
This could lead to router streaming incorrect counter values for SR
stats |
| 1312117 |
The rpd process might crash if LDP updates the label for BGP route |
When LDP egress-policy is configured
for the BGP route and a label is received for a BGP route in inet.0
table from LDP, if BGP receives a new label for the same BGP route
matching the LDP egress-policy, rpd might crash because of updating the
new label. |
| 1312336 |
PEM alarms and I2C Failures are observed on MX240/MX480/MX960/EX92/SRX5K series |
On MX240/MX480/MX960/EX92/SRX5K series, PEM alarms and I2C Failures with PCF8584 are observed. |
| 1315009 |
The L2TP LAC might drop packets that have incorrect payload length while sending packets to the LNS |
On all MX-Series platform, if the
Point-to-Point Protocol over Ethernet (PPPoE) subscribers runs on Layer 2
Tunneling Protocol (L2TP) Access Concentrator (LAC) over dual-tagged
VLAN and auto-sensed VLANs, all the packets that are being sent to the
L2TP Network Server (LNS) might be dropped, because the LAC Ethernet
pads the PPPoE packets with larger size. |
| 1315207 |
Service Interim Missing for Random Users in JSRC scenario |
Service Interim Missing for Random Users in JSRC scenario |
| 1315577 |
MX10003 : Despite of having all AC low PEM alarm is raised. |
Alarm is raised if Mixed AC PEMs are
present. Changed the criteria to check whether mixed AC is present.If
the PEM is AC(HIGH) first bit of pem_voltage is set and if it is AC(LOW)
second bit of pem_voltage is set.So if both first and second bit is set
then MIXED AC is present |
| 1316192 |
The FAN speed might frequently keep changing between normal and full for MX platform |
On MX platform with MPC cards, frequent FAN speed change might be seen. |
| 1317011 |
Log messages "L2ALM Trying peer/master connection, status 26" is showed on SRX device |
Fix for internal L2ALM connection on
SRX5K between IOC cards and RE. It will prevent repeating of following
log message "L2ALM Trying peer/master connection, status 26." |
| 1317019 |
The PPPOE subscribers might encounter connection failure during login |
In Point-to-Point Protocol over
Ethernet (PPPOE) subscriber environment, If one subscriber logs in with
incorrect radius attribute(such as Framed-IP-Address,
Framed-IPv6-Prefix, Delegated-IPv6-Prefix attribute is logically 0;
Framed-IP-Address = 255.255.255.254) and then logs out, all the
subscribers on the same Packet Forwarding Engine (PFE) might not be able
to reconnect. |
| 1317023 |
lsdb entry cleanup may cause rpd crash, if loop free alternative is configured |
When isis database is cleaned, rpd
crash may be observed if loop free alternative is configured. isis
database can be cleaned even when isis is deactivated. |
| 1317132 |
The policy configuration might not be evaluated if policy expression is changed |
If Border Gateway Protocol (BGP)
import policy is configured with a policy expression, the configuration
might not be evaluated after the policy expression is changed later. |
| 1317223 |
The output from "show configuration <> | display json" might not be properly enclosed in double quotes |
If the output from "show configuration
<> | display json" contains alpha-numeric (like 10m, 512k etc) or
wildcard (like <*>), and the alpha-numeric or wildcard represents
a number, they might not be enclosed in double quotes. |
| 1317536 |
The rpd might crash after the primary link failure of link protection |
If there are some LSPs for which a
router has make link protection available and when primary link failure
is caused by FPC restart, this core may occur. |
| 1317542 |
Multicast traffic is not forwarded on the newly added P2MP branch/receiver |
Multicast traffic is not forwarded on
the newly added P2MP branch/receiver due to Multicast indirect NH and
alternate forwarding NH (snooping route) go out of sync after receiver
is leaving the group. |
| 1317623 |
The inactive route cannot be installed
in multipath next-hop after disabling and enabling the next-hop
interface in L3VPN scenario |
In some circumstances, a route from a BGP peer in a VRF may have an incorrect multipath attribute. |
| 1318476 |
The rpd might crash when the link flaps on an adjacent router |
The rpd (Routing Protocol Process) might crash during heavy next hops churn. |
| 1318528 |
The daemon bbe-smgd may crash after performing GRES |
In subscriber management scenario with
Point-to-Point Protocol over Ethernet (PPPoE) configured, bbe-smgd may
crash if performing graceful routing engine switchover (GRES) during
PPPoE subscribers login. This is a timing issue and only part of the
subscribers may get synced to the standby RE in this case. |
| 1318677 |
FPC crash on configuration change for PFE sensors |
On receiving a configuration change
for PFE sensors in the middle of a reap cycle there is a chance that the
PFE might crash due to invalid data access. This is a timing issue and
related to the length of time it takes to reap the sensors. |
| 1319338 |
ISIS might choose a sub-optimal path after the metric change in ECMP links |
On a busy system when ISIS interface
metric configuration is changed for ECMP links, ISIS might choose a
sub-optimal path instead of the best path. The issue will clear itself
if a full LSP (Link State PDU) re-generation (e.g. LSP refresh is
triggered because of LSP aged or clear ISIS database) happens. |
| 1320254 |
2-3 secs packets loss is seen every 5 mins on Junos Fusion |
On Junos Fusion Enterprise/Provider
Edge platforms with feature dot1.x is configured, if the FPC has no
interface as cascade port on Aggregation Devices (ADs), 2-3 secs packets
loss might be seen every 5 minutes. |
| 1320585 |
Move XQ_CMERROR_XR_CORRECTABLE_ECC_ERR to minor and re-classify remaining XQCHIP CMERROR from FATAL to MAJOR |
The default severity of the
correctable ECC errors on MX Series routers with MPC2E NG Q, MPC3E NG Q,
or MPC5E has been changed from Fatal to Major. This helps in avoiding
instances of line card restart caused by Fatal errors, thereby
preventing any potential operational impacts for users. |
| 1320880 |
PPP inline keepalive does not work fine as expected when CPE aborts the subscriber session |
For DSL (Digital subscriber line)
subscribers such as PPPoE (Point-to-Point Protocol over Ethernet), when a
CPE (customer premises equipment) device is administratively powered
off, the BRAS (Broadband Remote Access Server) terminates the subscriber
as expected upon the expiry of configured PPP LCP (Link Control
Protocol) keapalive value. However, in a scaled scenario, a few
subscriber sessions remain active even the keepalive has expired, due to
which the same CPE (client) cannot reconnect unless the former sessions
are cleared/deleted from the server or the client waits for extended
amount of time to make sure the server internally clears those sessions. |
| 1321122 |
The traffic with more than 2 VLAN tags might be incorrectly rewritten and sent out |
On MX with MPC1E/MPC2E/MPC 3D 16x
10GE/MPC3E/MP4E, EX9200 switch or T4000 with type 5 card, if the
interface is configured with input-vlan-map option, then the traffic
with more than 2 VLAN tags might be incorrectly rewritten and sent out,
then it will cause the traffic to be dropped. |
| 1321952 |
The rpd might crash due to memory leak in RSVP scenario |
When make-before-break (MBB) such as
re-optimization, auto-bandwidth and interoperate with older releases
happens in RSVP scenario, the rpd might crash. |
| 1323256 |
Commands "show chassis environment pem" and "show chassis power" do not show 'input voltage' correctly. |
On SRX5K devices, DC PEM is used on
the box, the output of "show chassis environment pem" and "show chassis
power" commands do not show DC input value correctly. |
| 1325271 |
MPC cards might drop traffic under high temperature |
When some specific MPC cards
(MPC3E/4E/5E/6E/2E-NG/3E-NG) work under high temperature (around 67C or
higher), XM-DDR3 memory refresh interval will be reduced and hence DDR
bandwidth and Packet Forwarding Engine (PFE) forwarding capacity will be
reduced. As a result, traffic might get dropped. |
| 1326584 |
On SRX5400, SRX5600, and SRX5800
devices, SPC2 XLP stops processing packets in the ingress direction
after repeated RSI collections. |
SRX5400/5600/5800 platforms using
SRX5K-SPC-4-15-320 (SPCII) may encounter a XLP buffer leak during
Request Support Information (RSI) data collections, which resulting in
intermittent packet loss or complete loss of ingress packets. |
| 1326899 |
The rpd process might crash
continuously on both REs when "backup-spf-options
remote-backup-calculation" is configured in ISIS protocol |
If the knob "backup-spf-options
remote-backup-calculation" is being used for remote loop-free alternate
(LFA) backup path in Intermediate system to Intermediate system (ISIS)
protocol and some routes have both IP and label-switched path (LSP)
backups, the rpd process might crash continuously on both master Routing
Engine (RE) and backup RE. |
| 1327723 |
The MAC might not be learnt on MX Trio-based card due to the negative value of the bridge MAC table limit counter |
The MAC might not be learnt on MX Trio-based card due to the negative value of the bridge MAC table limit counter. |
| 1327724 |
The packet might get dropped in LSR if
MPLS pseudowire payload does not have control word and its destination
MAC starts with '4' |
When the label-switching router (LSR)
works on MX Series with MPCs/MICs platforms or vMX and LSR carries MPLS
pseudowire (such as l2circuit(LDP based)/l2vpn(BGP based)/VPLS) traffic,
the packet might get dropped if the MPLS pseudowire payload does not
have control word and its destination MAC starts with '4'. |
| 1327904 |
Multiple next-hops may not be installed for IBGP multipath route after IGP route update |
Multiple next-hops may not be
installed for an internal BGP(IBGP) route received from a
multipath-enabled peer when an active IBGP route from a
non-multipath-enabled peer is changed to a new active route from a
multipath-enabled peer due to interior gateway protocol(IGP) route
update. |
| 1328570 |
Directories and files under
/var/db/scripts lose execution permission or directory 'jet' is missing
under /var/db/scripts causing "error: Invalid directory: No such file or
directory" error during commit |
On MX10003, MX150, MX204,
MX240/480/960 with RE-S-X6-64G, MX2010/MX2020 with REMX2K-X8-64G,
PTX1000, PTX10008, PTX10016, QFX10000, QFX5200, SRX1500, SRX4100,
SRX4200 platforms: execution is denied when running automation script
stored in Junos automation folder(/var/db/scripts) or directory 'jet' is
missing under /var/db/scripts causing "error: Invalid directory: No
such file or directory" error during commit. |
| 1329013 |
With BGP/LDP/ISIS configurations, deleted ISIS routes may still be visible in RIB |
With BGP/LDP/ISIS configurations,
deleted ISIS routes may still be present in the RIB The PR does not
affect or have any impact on route selection or other functionality of
RPD. Just that deleted ISIS routes don't get removed with specific
configurations. |
| 1330150 |
Not all CSURQ replied |
Not all CSURQ messages are replied in case the number of sessions addressed in CSURQ is more than about 107. |
| 1331185 |
The dcd process might crash due to memory leak and causing commit failure |
In some situations, like multiple
commit in a short time with scaled configuration, dcd memory leak might
occur. This could cause commit to fail. |
| 1332153 |
Router hits db prompt at netisr_process_workstream_proto |
Due to an issue with a lock protected
variable of netisr queue and if rate limiting also kicks in, the count
of remaining packets in netisr queue becomes wrong. This leads to kernel
crash or db prompt. |
| 1333265 |
The subinfo process might crash and it might cause the PPPOE subscribers to get disconnected |
On MX-Series platforms with a
Point-to-Point over Ethernet (PPPoE) subscriber environment, in order to
increase overall system performance of subscriber accessing, after
optimizing the Session Database (SDB) using Short Term Storage (STS)
cache, the subinfo process might crash and might cause the SDB of MX
subscriber to experience a down event. As a result, the PPPOE
subscribers might get disconnected from the MX. |
| 1333380 |
The log messages file is filled with message "node*.fpc*.pic* Status:1000 from if_np for ifl_copnfig op:2 for ifl :104" |
On all SRX Series devices running with
Junos OS Release 17.4R1 or onwards, the log messages file is filled
with message "node*.fpc*.pic* Status:1000 from if_np for ifl_copnfig
op:2 for ifl :104" and "node*.fpc*.pic* IFL: Error:1000 while changing
IFL 104 index to UP". |
| 1335319 |
BGP sessions get stuck in active state after remote end (Cisco) restart the device |
In BGP (Border Gateway Protocol)
environment, BGP sessions get stuck in active state after remote Cisco
router restart or update the device. |
| 1335486 |
Log "No Port is enabled for FPC# on node0" genereated every 5 seconds. |
Since 12.3X48-D55 on SRX5K, the below
unnecessary log is observed in chassisd log every 5 seconds. "No Port is
enabled for FPC# on node0" The log is removed in 12.3X48-D70 &
15.1X49-D140. |
| 1335914 |
The rpd process memory leak is observed upon any changes in VPLS configuration like deleting/re-adding VPLS interfaces |
In Virtual private LAN service (VPLS)
scenarios, any changes in VPLS configuration like deleting/re-adding
VPLS instances or deleting/re-adding VPLS interfaces might cause the rpd
process memory leak. The memory leak rate is 14 bytes per VPLS
interface. |
| 1336207 |
PTX device may get to abnormal state due to the malfunction of the protection mechanism for F-Label |
On 16.1 onwards, PTX device may get to
abnormal state due to F-Label exhaustion. The protection mechanism for
warning and protecting F-Label exhaustion malfunctions on these releases
after network churn. |
| 1336946 |
Configuring "lldp neighbour-port-info-display port-id" doesn't take any effect |
When configuring ""lldp
neighbour-port-info-display port-id", supposedly we should see
interface's name on "Port's Info" when we do "show lldp neighbor", but
it does not take effect on certain software versions. |
| 1340264 |
The MX10003 MPC off-line button is not effective |
Off-line button to bring an MPC off-line does not work. |
| 1340612 |
PTX FPC Link down after router reboot or flap |
In a rare case on PECHIP based PTX FPCs DFE tuning can end up with port staying down |
| 1341336 |
The rpd crash might occur when receiving BGP updates |
From Junos 16.1R1 onwards, there might
be a mismatch in the length of BGP update message between BGP main
thread and I/O thread when receiving BGP updates. If this issue happens,
rpd crash might be seen. |
| 1342481 |
The rpd may crash when BGP flaps |
When EBGP peer connections with
labeled-unicast capability flap if a newly received label information is
the same as an existing route, the Routing Protocole Daemon may restart
unexpectedly. |
| 1344732 |
PTX1008: 30-Port Coherent Line Card (DWDM-lC) does not come up |
Applicable to only 17.4R1-S2: PTX1008 30-Port Coherent Line Card (DWDM-LC) will not come up in the release 17.4R1-S2 |
| 1345275 |
SRX1500 devices may encounter a failure accessing SSD drive |
SRX1500 devices may encounter a loss
in reading/writing access to SSD drive due to an incorrect calculation
error during read/write operations with SSD firmware version 560ABBF0. |
| 1345365 |
[ EX9208] / [ 17.4R1.16 ] Dot1x Re-authentication issue |
During the authentication process the
VOIP phone mac is added to both data and voice VLAN. Later the VOIP
phone will be sending tagged frames out over voice VLAN only. Now the
mac entry in the data VLAN will get Age out and that process will
trigger the delete of that MAC in data VLAN. DOT1x process was not
comparing the MAC state learnt on both the data and voice VLAN and later
when re-authentication triggered it finds MAC Ageout and clears the
dot1x session. This is a bug and will be fixed in the next release. |
| 1345519 |
The rpd might crash if the IRB interface and routing instance are deleted together in the same committing |
On all MX Series platform with
Ethernet VPN (EVPN) scenario, the rpd might crash if the Integrated
Routing and Bridging (IRB) interface and routing instance are deleted
together in the same committing operation. |
| 1345882 |
Summit 3RU: MAC address of multiple interfaces are found to be duplicate. |
Duplicate MAC address seen on interfaces on different PIC |
| 1346054 |
Summit: Routing engine Model changed from JNP10003-RE1 to RE-S-1600x8 |
There is a change in RE model for
MX10003 and MX204, these changes will be shown in show chassis hardware
and show chassis routing-engine. |
| 1347250 |
When in hadrware-assited-pm-mode and pm config is scale, deativate eth-oam can lead to fpc crash |
When eth-oam is deactivated with scale
PM config (under hardware-assited-pm-mode), the FPC can become unstable
and can lead to FPC core |
| 1348089 |
EVPN-VXLAN: MX: Output policing action does not work on irb interfaces for VNIs |
Output policing action for EVPN VXLAN may not be applied to an interface despite configuration on the irb interface. |
| 1348607 |
The rpd might crash while restart routing or deactivate ISIS |
In Intermediate System-to-Intermediate
System (ISIS) segment routing environment with the mapping-server
feature enabled, rpd might crash while restart routing or deactivate
ISIS configuration. The rpd will recovery itself. |
| 1348753 |
Chassisd memory leak issue on MX10003 and MX204 platform and it would cause eventual RE switchover and crash. |
Chassisd process running on MX10003
and MX204 platform will be leaking memory. Memory leak happens as long
as chassisd is working and there is no way to stop leaking. This would
cause eventual RE switchover and chassisd crash. |
| 1349228 |
The mspmand process might crash when executing "show services nat deterministic-nat nat-port-block" command |
With Network Address Translation (NAT)
configured on MS-MPC/MS-MIC, if a NAT rule is configured with multiple
terms and the first term has 'no-translation' type configured, executing
'show services nat deterministic-nat nat-port-block' command might
cause the mspmand process crash. |
| 1351203 |
pfed process consuming 80-90% cpu running subscriber management on PPC based routers |
pfed process consumes high cpu on PPC based routers running subscriber management. This includes MX5-MX80 and MX104. |
| 1353111 |
"Chassis Manager Daemon - chassisd" memory leak |
Memory leak in chassisd |
