After an incorrect use of the route-distinguisher, RPD could crash causing traffic disruption.

This is a day 1 Junos behavior and is documented in Junos CLI Reference - route-distinguisher-id

Our documentation explicitly indicates that to avoid a conflict in the two route distinguisher values, you must ensure that the first half of the route distinguisher obtained by configuring the route-distinguisher statement is different from the first half of the route distinguisher obtained by configuring the route-distinguisher-id statement

If in your config you have for example the following route-distinguisher-id under routing-options :

root@labdevice> show configuration routing-options      
route-distinguisher-id 172.16.0.18;

And under the routing-instance vrf, you attempted to configure a static RD:

+  route-distinguisher 172.16.0.18:29; >>> must avoid using the same octet as the one defined under routing-options route-distinguisher-id

As per documentation to avoid further issues the first half should be different, not the same as configured under route-distinguisher-id.

After commit. the Junos messages could throw the following errors informing the bad address and potential core dumps will be generated.

rpd[PID]: UI_CONFIGURATION_ERROR: Process: rpd, path: [edit routing-instances test], statement: route-distinguisher, routing-instance test has duplicate route-distinguisher 172.16.0.18:29: as routing-instance mgmt-test

rpd[PID]: JTASK_ABORT: abort rpd[PID] version 22.2R3.15 built by builder on 2023-03-22 15:55:35 UTC: Bad address

Recommendation to follow the juniper documentation to assign rd values which avoid duplicate rd values.

Junos CLI Reference - route-distinguisher-id