Solution:
Junos Software service Release version 16.1R3-S5 is now available.
The following are incremental changes in 16.1R3-S5.
| PR Number | Synopsis | Description |
|---|---|---|
| 1209308 | tcp_timer_keep: Dropping socket connection when remote VPLS PE comes up |
In some rare scenarios remote VPLS PE coming up might cause TCP keepalive timeouts on the local sockets between the master RE and the FPCs (e.g. ppmd <-> PPManager connection): kernel: tcp_timer_keep: Dropping socket connection due to keepalive timer expiration Local(0x80000001:6011) Foreign(0x80000015:36678) kernel: tcp_timer_keep: Dropping socket connection due to keepalive |
| 1231167 | MPC2E-NG/MPC3E-NG core-dump with specific MIC due to tight loop of PCIe critical exceptions | On MX platform with MPC2E-3D-NG/MPC2E-3D-NG-Q/MPC3E-3D-NG/MPC3E-3D-NG-Q line card, if the FPC-MIC link failure happens, the bridge may keep sending register messages in an infinite loop, which would cause continuous PCI exceptions, the MPC might crash and traffic forwarding might be affected. This is a rare issue, it is hard to reproduce. |
| 1241801 | The rpd might crash on backup RE when changing l2circuit neighbor in NSR scenario | With NSR enabled and a Layer 2 circuit configured, an rpd crash might be observed on the backup Routing Engine when you change the Layer 2 circuit neighbor and then commit the changes. The issue does not exist if NSR is not enabled. |
| 1251556 | KRT queue stuck on RE causing RIB and FIB to go out of sync | From Junos 16.1R1 and later, there is a rpd problem sending route update messages to the kernel. The KRT queue used to send the messages can get into a state where no more messages can be sent to the kernel. This causes the RIB and FIB to get out of |
| 1256736 | IRP interrupt "INTR: throttle 3630sec PECHIP[2]:pe.irp.intr.status:ap0_trap(0): (Count:3434)" would be observed for every hour under certain conditions. | While processing lookup results, IRP block would raise an interrupt upon detecting an error condition. The interrupt would be active until the trapcode error is read. Under certain conditions, software is not reading this trapcode error upon IRP interrupt. This issue causes the following syslog message to be generated: fpc5 |
| 1258472 | The rpd might crash during the next-hop change if unicast reverse-path- forwarding (uRPF) is used | In a very rare cases, if the unicast reverse path forwarding (uRPF) is used, the rpd might crash and the core file might be generated during the next-hop change. |
| 1259579 | Rpd memory leak is observed in NG-MVPN environment | Rpd memory leak is seen when NG-MVPN type 6 and type 7 route adds/deletes/changes. The leak is 36 byte block size on Junos versions prior to 15.1, and 44 byte block size on Junos versions 15.1 or higher. |
| 1276748 | RPD core: Assertion failed rpd[6255]: file src/junos/usr.sbin/rpd/rsvp/rsvp_enh_lp.c", line 4928: "rsvp_enh_lp_supported_psb_type(psb) | RPD core: Assertion failed rpd[6255]: file src/junos/usr.sbin/rpd/rsvp/rsvp_enh_lp.c", line 4928: "rsvp_enh_lp_supported_psb_type(psb) |
| 1280809 | RPD core generation when a memory is allocated twice | Under a rare circumstance show task command of any type might cause a double free of a data structure resulting in a rpd coredump. |
| 1282672 | Rpd might crash due to a certain chain of events in BGP-LU protection scenario | In BGP-LU protection scenario with the statement per-prefix-label configured, rpd might crash due to a certain chain of events that if receiving a BGP route with the indirect next-hop firstly and later receiving another BGP route with the direct next-hop (which has the same prefix with the route received early) |
| 1290789 | The rpd crashes due to LDP defect during NSR-enabled RE switchover | The rpd will generate core file, if it involves an Label Distribution Protocol (LDP) egress route, which is stitched to a Border Gateway Protocol (BGP) route via the "ldp egress-policy" configuration. |
No comments:
Post a Comment