Enhance error handling when TL-chip encounters KHT memory parity error. With the enhancement, when KHT memory parity error is detected, the content of the memory will be corrected using software shadow copy.

Reply packets of TWAMP probes from TWAMP server were getting dropped when physical interface at server is configured as the target address in Twamp client config. Issue was because of packet checksum calculations were getting altered because of platform Endianness issue. To fix the issue, Endianness of packet data is taken care of before sending data to network and when received at host. Issue is seen with vMX platform setup only.

Kernel crash might be seen due to integer wrapping around in case of 64 bit architecture.

In a situation which BGP is being used in combination with interface's rfp-check; deleted routes may see delay in propagation of BGP withdrawn messages.

FPC might restart while issuing "write coredump" from fpc shell.

With a 100G CFP2 MIC installed in a MPC6E FPC. If the FPC fails to initialize the MIC, it is very likely that the FPC will get into boot loop.

With RSVP refresh reduction feature enabled (using RSVP aggregate messages), when changing the knob "no-load-balance-label-capability" to "load-balance-label-capability" on the egress router, the Entropy Label Capability (ELC) for the egress router would not being propagated towards the ingress.
As a workaround, we can execute "clear rsvp session" on the ingress router or wait for 3 refresh cycles (takes approximately 100s with default RSVP refresh config).

Continuously flapping interfaces on a FPC in a router which has approximately 56,000 routes; a FPC may restart unexpectedly

When a dynamic tunnel changes its state to down via configuration change, Routing Protocol process (RPD) may restart unexpectedly.

On MX platform, when MPC experiences a FATAL error, it gets reported to the chassisd daemon. Based on the action that is defined for a FATAL error, the chassisd will take subsequent action for the FATAL error. By default, the action for FATAL error is to reset the MPC. When the MPC reports FATAL error, chassisd will send offline message and will power off the MPC upon the ACK reception. However, if MPC is in busy state for any reason, the ACK doesn't come in time and hence there would be a delay in bringing down the MPC. The fix ensures to bring down the MPC in time upon FATAL error.

If container LSP name and the suffix together are more than 60 characters in length, rpd process might crash during extensive split merge conditions. Its always advisable to keep them less than 60 characters. The member lsp name is coined in the following manner:
<container-name> - <suffix-name> - <member-count>
The LSP name can have upto 64 characters. After putting together the container name, suffix, member-count (could go up to 2 digits), and the 2 hyphens, it should not exceed 64. It is important that container-name and suffix together should not exceed 60 characters. A commit check will be added to throw warning if the name is more than supported character long.

Changing VSTP configuration to MSTP configuration in one commit can result in service impact for some of the VLANS. Therefore it is advisable to do the configuration change in two steps. First deactivate VSTP and then activate MSTP. Same should be followed for MSTP to VSTP mode change.

During sib yanking test (pulling a sib out without offline), it is possible that traffic may be dropped resulting in an overall reduction in traffic throughput.

Due to software bug on chassisd, backup CB temperature information is missing on cli command 'show chassis environment cb' if it's replaced once.

A vmcore may be seen if there are 65000 pfestats requests in a short amount of time (70-90 seconds).

When two line-cards are taken offline back to back (without delay between issuing the line-card offline command) we are hitting the issue described in the PR (some planes goes to check state). This issue could be prevented by giving a 1 second delay between the offline commands. Workaround would be to offline and online the planes which are in Check state.

CLI commit warning is replaced by syslog warning message when limited-ifl-scaling knob is configured. Warning message text remains the same.

PTX5000 router: Commit fails after adding member links of the same speed from the QSFP28 PIC to an existing AE bundle created using a Universal PIC.

In very rare chances, a stream drain error message (error code 0x2104ce) might get triggered by frequent interface flap or by port speed changes on the new PTX QSFP PICs. This causes traffic to be dropped. To fix the problem, restart the FPC.

Adding keyword 'fast-filter-lookup' to existing filters of an input or output filter list may result in failure to pass traffic. To avoid this issue, the filter list should first be deactivated then the filters updated with a the keyword 'fast-filter-lookup; then the filter list activated.

This issue will be seen only when there are huge number of routes having different BGP NHs pointing to the same AS. Depending on the number of routes pointing to AS paths and also the difference in BGP NHs in the routes can shoot up the SRRD CPU consumption. In the real network this issue might not be seen often, as the number of AS paths will be huge and the routes referring these AS paths will be usually distributed among the AS paths. Even if the routes are pointing to the same AS, the impact would be lesser than the one seen in this PR.

If the no-cell-share knob under the chassis stanza is activated on MPC3,MPC4,MPC5 or MPC6 cards, the PFE is only able to forward about 62Gbps versus ~130Gbps and causing high level of fabric queue drops.

In certain FPC cases, the CM switch setting is not set correctly with 15.1F5.15 and will trigger loopback wedge error messages.

You can now assign user FC/DSCP classification value to inline jflow export packets to collector. This provide a way to differentiate collector traffic from normal transit traffic.

When polling SNMP counters for Trio-Only firewall filters, MIB2D_RTSLIB_READ_FAILURE cosmetic error messages might get reported in syslog.