mixed tree and -625 error in DSRepair

[br...@nospam.com]

I have a NW 5.1 server with DSRepair 10250.37, DS 8.85. This box has the
master of Root, the only partition. It is a secondary time server. The
other two boxes are NW 4.11 with SP9. One of them is the Single reference
server. Both 4.11 boxes have R/W replicas. Recently I have been getting
abends on the 5.1 server which runs ZFD 3.2. The abend log keeps showing
errors in DS.NLM. Based on a TID I turned on IPX checksumming on the 5.1
server. In addition I updated the DS.NLM on the NW 4.11 boxes to 6.21
last week. This morning during my weekly health checks I saw that on the
5.1 server it shows a -625 error communicating with itself! This is in
the Time synchronization option of DSRepair. The error is "could not
retrieve synchronization status" and "could not retrieve ds status" with
both giving a -625 error. No other errors show and the time sync is fine
on the other servers. Also timesync debug screen shows no errors. The
synchronization status shows all servers synching also.

I wonder if the 6.21 ds.nlm is the issue. I tried turning off the ipx
checksumming but haven't restarted the server yet.

Any suggestions appreciated.

Thanks,
Bruce

[Andrew C Taubman]

Sounds like you purely have a problem with timesync, not DS at all. Make the
5.1 server the Single ref time server, the 4.11s all secondaries, and
restart timesync.nlm on the NW 5.1 server.

Which was the checksumming TID? I'm not aware that's ever necessary. You
might try fds885b.exe to resolve the DS abends.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.

[br...@nospam.com]

The TID for the checksumming suggestion is:
http://support.novell.com/cgi-bin/search/searchtid.cgi?/2934127.htm

As for timesync I haven't yet changed it. My issue is that the error is
new(months of running with the timesync that way) and the errors are only
in the time synchronization screen of dsrepair, on the server that is
listed as having the -625 error. Seems unusual to have a server report
itself as having a 625 error with no other errors in DSTRACE or timesync
debug screen. The one TID with the error messages I am seeing in DSRepair
doesn't seem to apply since the changes were only on the 4.11 servers.

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10050844.htm

Thanks for the ideas. I will try some more things.

Bruce

[Andrew C Taubman]

That TID is from 1998, and documents that the problem is resolved in DS
6.03. I'm sure you have a later version than that. Undo the checksumming
change you made, it is not necessary and may cause you other unsuspected
problems.

[br...@nospamme.com]

It was the checksumming setting that caused it. Based on the TID and how
it was wording I was trying to "reduce" the possibility of a corrupted
packet being the cause. After turning back to default the server abended
later in the day. Not sure about using the beta ds patch, may open an
incident if this becomes worse.

Thanks!
Bruce

[Andrew C Taubman]

>Not sure about using the beta ds patch, may open an incident if this
becomes worse.

They will just suggest using the same patch.