The RPD_DYN_CFG_PROCESSING_FAILED message is reported in the system message file whenever the routing protocols process (RPD) receives a failure response when it attempts to process dynamic configuration.
Currently, subscriber access DHCP configuration with dynamic profiles is only supported on MX-series routers. However, dynamic profiles for use with PPP client access can be defined for MX-series routers, or the M120 and M320 systems. Therefore any of these systems can use dynamic configurations in JunOS.
The problem related to this syslog message is described in the following sections:
The RPD_DYN_CFG_PROCESSING_FAILED message is logged each time RPD tries to process dynamic configuration and the processing fails.
When the RPD_DYN_CFG_PROCESSING_FAILED event occurs, messages similar to the following are reported:
RPD_DYN_CFG_PROCESSING_FAILED: Module failed to process dynamic configuration
Some example messages:
RPD_DYN_CFG_PROCESSING_FAILED: Module IGMP failed to process dynamic configuration RPD_DYN_CFG_PROCESSING_FAILED: Module options failed to process dynamic configuration RPD_DYN_CFG_PROCESSING_FAILED: Module IGMP failed to process dynamic configuration RPD_IGMP_DYN_CFG_SES_ID_MISMATCH: Dynamic configuration entry for interface pp0.1181 with session id 8086 found an existing entry with a different session id of 8079. RPD_DYN_CFG_PROCESSING_FAILED: Module options failed to process dynamic configuration dyn_prof_notification_handler: request_id = 8992040, result = 1 from rpd daemon: options failed to process dynamic config
The message includes the module that reported the error.
The cause of this message may be a mis-configuration of dhcp, may be a software issue within the rpd process or may be another event on the router.
Examine the following output to help determine the cause of this message:
show log messages show log rdd show configuration
Look for any related events that occurred at or just before the RPD_DYN_CFG_PROCESSING_FAILED message. See if any other events may have caused this message, such as a commit. If so, the failure to process dynamic configuration changes may be due to that one type of event occurring.
Review the dhcp configuration. If multiple dhcp client sessions will exist on a single VLAN, the aggregate-clients option must be specified under the dhcp-relay stanza. If it is not, this message will be generated.
Perform these steps:
- If aggregate-clients is needed but not configured, add the aggregate-clients option to the configuration. See aggregate clients for more information on this command.