IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Error while loading replcredentials.ldif file - SDS6.4 V

    Posted 04/04/22 09:30 AM
    Hi All,

    I am creating the replication agreements between the 1st and 3rd server. So in one of the step where I am adding the replcreds.ldif file to the 3rd server which is new server and while executing ldapadd command I am seeing a message saying already file exists. However I did not execute this step earlier and also I am seeing the details in ibmslapd.conf file. So where can I check the details of replcreds.file?

    Thanks in Advance
    Srinivasa

    ------------------------------
    Kalyan
    ------------------------------


  • 2.  RE: Error while loading replcredentials.ldif file - SDS6.4 V

    Posted 04/05/22 03:26 AM
    I am creating the replication agreements between the 1st and 3rd server. So in one of the step where I am adding the replcreds.ldif file to the 3rd server which is new server and while executing ldapadd command I am not seeing a message saying already file exists. However I did not execute this step earlier and also I am seeing the details in ibmslapd.conf file. So where can I check the details of replcreds.file?

    ------------------------------
    Kalyan
    ------------------------------



  • 3.  RE: Error while loading replcredentials.ldif file - SDS6.4 V

    Posted 04/05/22 09:30 AM
    Hello Kalyan,

    It might be the case that a few entries got added with idsldapadd command and then it got stuck.

    Did you try replication between servers 2 and 3 before and during that some entries got replicated to server 3? Just guessing the possibilities. 

    It is difficult to tell the exact cause of this issue before knowing the exact steps executed to do this setup.

    If you want to know the details of entries you may try the following command and check the replication topology details - 
    #idsldapsearch -h <system name> -p <ITDS port> -D <adminDN> -w <adminDNpwd> -b <replication context> -s sub objectclass=ibm-repl*

    Thanks!



    ------------------------------
    Umesh Sanjay Torawane
    ------------------------------



  • 4.  RE: Error while loading replcredentials.ldif file - SDS6.4 V

    Posted 04/06/22 03:26 AM
    Hi Umesh,

    Thanks for your inputs.

    After adding repladmin entry the issue got resolved. But when I am adding entries of DR server to the Prod server and creating the replication agreements the entries are not getting added to the prod server ibmslapd.conf file. Below is the error which I am seeing when I am executing the idsldapadd command.

    While adding the enteries in ldif file one of the method is set 1. Could this be the cause of the issue when setting up the multi threaded servers?
    ibmreplicamethod: 1 

    ibm-replicaGroup=default,O=SAMPLE
    bm-replicamethod: 2


    Error Message: No Such Object

    Thanks.
    Kalyan

    ------------------------------
    Kalyan
    ------------------------------



  • 5.  RE: Error while loading replcredentials.ldif file - SDS6.4 V

    Posted 04/08/22 05:49 AM
    Hi Kalyan,

    You should consider opening a case with IBM support to resolve these issues if the commands are failing and resulting in error messages like No Such Object.

    But I can definitely give you input on multi-threaded replication -

    Multi-threaded replication has demanding requirements:
    • A high update rate
    • No downlevel servers
    • Common AES salt and synchronization if encryption is AES and passwords are updated often
    • Available servers and reliable network
    • Data consistency is not critical
    • All replication schedules are immediate
    • Multiprocessor machines

    I would like to compare multi-threaded replication with the UDP protocol: if something is lost, it's just discarded.  Normal replication is like the TCP protocol: there's constant software checking to see if there's been a problem with the updates, so none of them are ever lost. 

    We generally recommend NOT using multi-threaded replication ("MTR") because you can quickly get out of sync between your servers if you do use this.  If you do use MTR, you really need to be very good at remediating replication issues on your own.  You will be out of sync fairly often and that will be expected.  You will have to have a process for: 

     1) Quickly putting servers back in sync 

    2) Remediating entries that get out of sync manually 

     Most folks don't have that and so we recommend not using MTR.

    Thanks!



    ------------------------------
    Umesh Sanjay Torawane
    IAM Consultant
    IBM Expert Labs
    copenhagen
    51639030
    ------------------------------