An internal routing protocol daemon check has failed, and the process generated a core-dump file.
The problem related to this syslog message is described in the following sections:
Messages similar to the following are reported in the system log, and the device generates a core-dump.
rpd: RPD_ASSERT_SOFT: Soft assertion failed rpd: file "../../../../../src/junos/usr.sbin/rpd/rt/rt_table.c", line 4885: "rt_notbest_sanity: Path selection failure on 10.0.75.0/24, recovering...", daemon continued running
The routing protocol daemon (rpd) will continue to run, and no outage may experienced.
The source code for the routing protocol process (rpd) includes internal self-consistency checks. A check failed at the indicated line number in the indicated source file, but the instance of rpd that was using the indicated binary and had the indicated process ID (PID) continued running. The process created a diagnostic core-dump.
Review the output of show log messages. The events prior to (and immediately following) the RPD_ASSERT_SOFT might help indicating the source of the failure.
Look for any core-dumps associated with the soft assertion of rpd with the CLI command: show system core-dumps
Please contact a technical support representative to investigate the issue further.
Review the output of the show system core-dumps command to identify the core file associated with the error.
Be prepared to load the core file to the Juniper FTP server.
The following link provides instructions for loading the core file to the Juniper FTP server: https://www.juniper.net/customers/csc/help/upload_files.jsp