The routing protocol process (rpd) tried to register with the dynamic configuration subsystem and failed.
The problem related to this syslog message is described in the following sections:
The following messages are reported in the log messages file:
ethernet-link-fault-management (PID 4393) exited with status=255
ethernet-link-fault-management (PID 31449) started
RPD_DYN_CFG_REGISTER_FAILED: Dynamic config registration failed: Invalid argument
RPD_PPM_WRITE_ERROR: ppm_send: write error on pipe to ppmd (Broken pipe)
performing a "rpdc -D bfdd stop" command for user root
System core files may also be generated. The core file will be listed in the output of the show system core-dumps command. For example:
-rw------- 1 root field 2637036 Nov 11 02:26 /var/tmp/rpd.core-tarball.1.tgz
-rw-rw---- 1 root field 2314991 Nov 4 22:51 /var/tmp/rpd.core.0.gz
This error message is not expected to appear under normal circumstances. If you encounter it, please carefully note any other symptoms that you encounter that seem related to the message, then contact your technical support engineer to discuss the possible causes.
Examine the following output to help determine the cause of this message:
show log messages
Perform these steps:
- Open a case with your technical support representative to investigate the issue further.
- If there was a core file generated, upload the core-file to the Juniper FTP site under that case for analysis.