Marcus Tornberg Super Contributor.
Super Contributor.
462 views

eDirectory synchronization 601 Remote

Hello!

I have some problem with my eDirectory replication. Running ndsrepair -E reveals 601 remote. I have logged in to each server using iMonitor, and I can see the other servers and the "Driver Set" partition fine.

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: srvfile1.O=servers.PROD-TREE
Repair utility for NetIQ eDirectory 9.0 - 9.1 v40101.31
DS Version 40101.29 Tree name: PROD-TREE
Server name: .srvfile1.servers

Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 67249 bytes.

Preparing Log File "/var/opt/novell/eDirectory/log/ndsrepair.log"
Please Wait...
Collecting replica synchronization status
Start: Saturday, April 27, 2019 10:37:26 PM Local Time
Retrieve replica status

Partition: .Driver Set.servers
Replica on server: .srvfile9.servers
Replica: .srvfile9.servers 04-26-2019 12:04:20
Server: CN=srvfile4.O=servers 04-27-2019 22:36:48 -601 Remote
Object: CN=Driver Set.O=servers
Replica on server: .srvfile6.servers
Replica: .srvfile6.servers 04-27-2019 21:48:03
Replica on server: .srvfile1.servers
Replica: .srvfile1.servers 04-27-2019 21:20:54
Server: CN=srvfile4.O=servers 04-27-2019 22:36:28 -601 Remote
Object: CN=Driver Set.O=servers
Replica on server: .srvfile2.servers
Replica: .srvfile2.servers 04-27-2019 21:48:03
Replica on server: .srvfile4.servers
Replica: .srvfile4.servers 04-10-2019 19:44:41
Server: CN=srvfile1.O=servers 04-27-2019 22:36:48 -601 Remote
Object: CN=Driver Set.O=servers
Server: CN=srvfile9.O=servers 04-27-2019 22:36:48 -601 Remote
Object: CN=Driver Set.O=servers
All servers synchronized up to time: 04-10-2019 19:44:41 Warning

Partition: .[Root].
Replica on server: .srvfile9.servers
Replica: .srvfile9.servers 04-27-2019 22:37:20
Replica on server: .srvfile4.servers
Replica: .srvfile4.servers 04-27-2019 22:37:26
Replica on server: .srvfile6.servers
Replica: .srvfile6.servers 04-27-2019 22:37:22
Replica on server: .srvfile1.servers
Replica: .srvfile1.servers 04-27-2019 22:37:22
Replica on server: .srvfile2.servers
Replica: .srvfile2.servers 04-27-2019 22:37:22
All servers synchronized up to time: 04-27-2019 22:37:20
Finish: Saturday, April 27, 2019 10:37:26 PM Local Time

Total errors: 4
NDSRepair process completed.

Any ideas on how to proceed?

Best regards
Marcus
Labels (1)
0 Likes
3 Replies
AutomaticReply Absent Member.
Absent Member.

Re: eDirectory synchronization 601 Remote

marcus,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit https://www.microfocus.com/support-and-services and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.microfocus.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.microfocus.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.microfocus.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Micro Focus Forums Team
http://forums.microfocus.com



0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: eDirectory synchronization 601 Remote

marcus_jonsson;2498924 wrote:
Hello!

I have some problem with my eDirectory replication. Running ndsrepair -E reveals 601 remote. I have logged in to each server using iMonitor, and I can see the other servers and the "Driver Set" partition fine.

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: srvfile1.O=servers.PROD-TREE
Repair utility for NetIQ eDirectory 9.0 - 9.1 v40101.31
DS Version 40101.29 Tree name: PROD-TREE
Server name: .srvfile1.servers

Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 67249 bytes.

Preparing Log File "/var/opt/novell/eDirectory/log/ndsrepair.log"
Please Wait...
Collecting replica synchronization status
Start: Saturday, April 27, 2019 10:37:26 PM Local Time
Retrieve replica status

Partition: .Driver Set.servers
Replica on server: .srvfile9.servers
Replica: .srvfile9.servers 04-26-2019 12:04:20
Server: CN=srvfile4.O=servers 04-27-2019 22:36:48 -601 Remote
Object: CN=Driver Set.O=servers
Replica on server: .srvfile6.servers
Replica: .srvfile6.servers 04-27-2019 21:48:03
Replica on server: .srvfile1.servers
Replica: .srvfile1.servers 04-27-2019 21:20:54
Server: CN=srvfile4.O=servers 04-27-2019 22:36:28 -601 Remote
Object: CN=Driver Set.O=servers
Replica on server: .srvfile2.servers
Replica: .srvfile2.servers 04-27-2019 21:48:03
Replica on server: .srvfile4.servers
Replica: .srvfile4.servers 04-10-2019 19:44:41
Server: CN=srvfile1.O=servers 04-27-2019 22:36:48 -601 Remote
Object: CN=Driver Set.O=servers
Server: CN=srvfile9.O=servers 04-27-2019 22:36:48 -601 Remote
Object: CN=Driver Set.O=servers
All servers synchronized up to time: 04-10-2019 19:44:41 Warning

Partition: .[Root].
Replica on server: .srvfile9.servers
Replica: .srvfile9.servers 04-27-2019 22:37:20
Replica on server: .srvfile4.servers
Replica: .srvfile4.servers 04-27-2019 22:37:26
Replica on server: .srvfile6.servers
Replica: .srvfile6.servers 04-27-2019 22:37:22
Replica on server: .srvfile1.servers
Replica: .srvfile1.servers 04-27-2019 22:37:22
Replica on server: .srvfile2.servers
Replica: .srvfile2.servers 04-27-2019 22:37:22
All servers synchronized up to time: 04-27-2019 22:37:20
Finish: Saturday, April 27, 2019 10:37:26 PM Local Time

Total errors: 4
NDSRepair process completed.

Any ideas on how to proceed?

Best regards
Marcus


Hi Marcus,
Do you have "real" (R/W) replicas of your DriverSet partition on your servers (CN=srvfile4.O=servers, CN=srvfile1.O=servers, CN=srvfile9.O=servers)?

I think, that all these servers have replicas of [root] partition and nothing for DriverSet partition (only subordinate).
Subordinate reference replicas, therefore, don't provide fault tolerance. They are internal pointers that are generated to contain enough information for eDirectory to resolve object names across partition boundaries.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: eDirectory synchronization 601 Remote

al b <al_b@no-mx.forums.microfocus.com> wrote:
>

marcus_jonsson;2498924 Wrote:
> Hello!
>>
>> I have some problem with my eDirectory replication. Running ndsrepair -E

> reveals 601 remote. I have logged in to each server using iMonitor, and
> I can see the other servers and the "Driver Set" partition fine.
>>
>> [1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:

> srvfile1.O=servers.PROD-TREE
>> Repair utility for NetIQ eDirectory 9.0 - 9.1 v40101.31
>> DS Version 40101.29 Tree name: PROD-TREE
>> Server name: .srvfile1.servers
>>
>> Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 67249 bytes.
>>
>> Preparing Log File "/var/opt/novell/eDirectory/log/ndsrepair.log"
>> Please Wait...
>> Collecting replica synchronization status
>> Start: Saturday, April 27, 2019 10:37:26 PM Local Time
>> Retrieve replica status
>>
>> Partition: .Driver Set.servers
>> Replica on server: .srvfile9.servers
>> Replica: .srvfile9.servers 04-26-2019 12:04:20
>> Server: CN=srvfile4.O=servers 04-27-2019 22:36:48 -601

> Remote
>> Object: CN=Driver Set.O=servers
>> Replica on server: .srvfile6.servers
>> Replica: .srvfile6.servers 04-27-2019 21:48:03
>> Replica on server: .srvfile1.servers
>> Replica: .srvfile1.servers 04-27-2019 21:20:54
>> Server: CN=srvfile4.O=servers 04-27-2019 22:36:28 -601

> Remote
>> Object: CN=Driver Set.O=servers
>> Replica on server: .srvfile2.servers
>> Replica: .srvfile2.servers 04-27-2019 21:48:03
>> Replica on server: .srvfile4.servers
>> Replica: .srvfile4.servers 04-10-2019 19:44:41
>> Server: CN=srvfile1.O=servers 04-27-2019 22:36:48 -601

> Remote
>> Object: CN=Driver Set.O=servers
>> Server: CN=srvfile9.O=servers 04-27-2019 22:36:48 -601

> Remote
>> Object: CN=Driver Set.O=servers
>> All servers synchronized up to time: 04-10-2019 19:44:41

> Warning
>>
>> Partition: .[Root].
>> Replica on server: .srvfile9.servers
>> Replica: .srvfile9.servers 04-27-2019 22:37:20
>> Replica on server: .srvfile4.servers
>> Replica: .srvfile4.servers 04-27-2019 22:37:26
>> Replica on server: .srvfile6.servers
>> Replica: .srvfile6.servers 04-27-2019 22:37:22
>> Replica on server: .srvfile1.servers
>> Replica: .srvfile1.servers 04-27-2019 22:37:22
>> Replica on server: .srvfile2.servers
>> Replica: .srvfile2.servers 04-27-2019 22:37:22
>> All servers synchronized up to time: 04-27-2019 22:37:20
>> Finish: Saturday, April 27, 2019 10:37:26 PM Local Time
>>
>> Total errors: 4
>> NDSRepair process completed.
>>
>> Any ideas on how to proceed?
>>
>> Best regards
>> Marcus

>
> Hi Marcus,
> Do you have "real" (R/W) replicas of your DriverSet partition on your

servers (CN=srvfile4.O=servers, CN=srvfile1.O=servers,
CN=srvfile9.O=servers)?
>
> I think, that all these servers have replicas of [root] partition and

nothing for DriverSet partition (only subordinate).
>> Subordinate reference replicas, therefore, don't provide fault

> tolerance. They are internal pointers that are generated to contain
> enough information for eDirectory to resolve object names across
> partition boundaries.



--
If you find this post helpful, please show your appreciation by clicking
on the star below :cool:
------------------------------------------------------------------------
al_b's Profile: https://forums.novell.com/member.php?userid=12514
View this thread: https://forums.novell.com/showthread.php?t=512085

>


Hi.

This is all servers in this small tree. The driver set partition is master
on srvfile9 and r/w on srvfile1 and srvfile4. Other two servers are
subordinate.

But I had to resolve this issue last weekend. I ended up with a xk2 on
srvfile4, cleaning up the tree and add srvfile4 to the tree again.

There is surely some other way to solve this, but this issue caused some
critical errors in the OES environment. One example would be that the
clients authenticated to srvfile4 would not be mapped to file shares on
srvfile1. Changing the Novell client to srvfile1 instead of srvfile4 made
the issue go away. But it was never an option to change all clients to
srvfile1, srvfile4 needed to work.

Still curious on what 601 means in this context? 601 is generally object
not found. But what object and on what server?

I guess I will never find out for sure as this issue is resolved. But I
feel I solved the issue by nuking instead of finding out what the cause
was. Kind of like deleting and recreating a user instead of checking and
fixing login disabled, expiration time or similar.

Also xk2 according to the above statement also made all drivers (IDM) to
loose their security equals. The IDM server in this case was srvfile9.

Best regards
Marcus

--
Best regards
Marcus
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.