If you create a replica with an id that starts with 0, say 010 or 020, dsconf replication mon will be unable to capture the Max CSN and the script will fail.

2.4.5.x

1. Setup a MMR between two nodes
2. Set the replica id to 010 and 020
3. After initializing the nodes run a dsconf backend replication montior

 dsconf userroot replication monitor
Supplier: M3 (ds3.redhat.example.com:389)
-----------------------------------------
Replica Root: dc=redhat,dc=example,dc=com
Replica ID: 0300
Replica Status: Online
Max CSN: 00000000000000000000Status For Agreement: "example-agreement-supplier3-to-supplier4" (ds4.redhat.example.com:389)
Replica Enabled: on
Update In Progress: FALSE
Last Update Start: 20241030184845Z
Last Update End: 20241030184845Z
Number Of Changes Sent: 300:2/0 
Number Of Changes Skipped: None
Last Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
Last Init Start: 20241030184620Z
Last Init End: 20241030184623Z
Last Init Status: Error (0) Total update succeeded
Reap Active: 0
Replication Status: Not in Synchronization: supplier (67227f8d0000012c0000) consumer (Unavailable) State (green) Reason (error (0) replica acquired successfully: incremental update succeeded)
Replication Lag Time: unavailableSupplier: M4 (ds4.redhat.example.com:389)
-----------------------------------------
Replica Root: dc=redhat,dc=example,dc=com
Replica ID: 0400
Replica Status: Online
Max CSN: 00000000000000000000Status For Agreement: "example-agreement-supplier4-to-supplier3" (ds3.redhat.example.com:389)
Replica Enabled: on
Update In Progress: FALSE
Last Update Start: 20241030184845Z
Last Update End: 20241030184845Z
Number Of Changes Sent: 0
Number Of Changes Skipped: None
Last Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
Last Init Start: 20241030184648Z
Last Init End: 20241030184651Z
Last Init Status: Error (0) Total update succeeded
Reap Active: 0
Replication Status: Not in Synchronization: supplier (Unknown) consumer (Unknown) State (green) Reason (error (0) replica acquired successfully: incremental update succeeded)
Replication Lag Time: unavailable

 dsconf userroot replication monitor
Supplier: M3 (ds3.redhat.example.com:389)
-----------------------------------------
Replica Root: dc=redhat,dc=example,dc=com
Replica ID: 300
Replica Status: Online
Max CSN: 672280ac0000012c0000Status For Agreement: "example-agreement-supplier3-to-supplier4" (ds4.redhat.example.com:389)
Replica Enabled: on
Update In Progress: FALSE
Last Update Start: 20241030185409Z
Last Update End: 20241030185409Z
Number Of Changes Sent: 300:3/0 
Number Of Changes Skipped: None
Last Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
Last Init Start: 20241030185322Z
Last Init End: 20241030185324Z
Last Init Status: Error (0) Total update succeeded
Reap Active: 0
Replication Status: In Synchronization
Replication Lag Time: 00:00:00Supplier: M4 (ds4.redhat.example.com:389)
-----------------------------------------
Replica Root: dc=redhat,dc=example,dc=com
Replica ID: 400
Replica Status: Online
Max CSN: 672280d1000001900000Status For Agreement: "example-agreement-supplier4-to-supplier3" (ds3.redhat.example.com:389)
Replica Enabled: on
Update In Progress: FALSE
Last Update Start: 20241030185409Z
Last Update End: 20241030185409Z
Number Of Changes Sent: 400:1/0 
Number Of Changes Skipped: None
Last Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
Last Init Start: 20241030185341Z
Last Init End: 20241030185344Z
Last Init Status: Error (0) Total update succeeded
Reap Active: 0
Replication Status: In Synchronization
Replication Lag Time: 00:00:00