Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Partition Synchronization Status?

Status
Not open for further replies.

CaptKirk

IS-IT--Management
Feb 16, 2002
28
US
Running Netware 6.5, receiving this warning message ...

NLSLSP.NLM warning: Unable to write license usage information to NDS. Check "[ROOT]" partition synchronization status. Service will continue.

Question: How do I Check the "[ROOT]" partition synchronization status? And what do I do to fix the problem?

Thanks.
 
Probably the thing to start with is check time sync and replica sync, both on the main menu in DSREPAIR.

Usually you will find errors there that help you solve your problem or lead you to another deeper problem.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
I found the time sync OK.

The Replica Sync shows server Curly -603 Remote.

Larry is Master Replica and dated 5/19/04.
Curly is Read/Write Replica and dated 8/30/04, today's date.

When I ran "Synchronize the replica on all servers" from Curly it said:
.Curly.WarrenCentral.MSD Read/Write Host
.Larry.Seeger.MSD Master -601

What do I do next?

Thanks,

 
ok let me get this right

on larry - if at Larry:
you type time and rtn
it thinks it's may
if yes then you need to fix his time

how are you getting the time -
you can set time manual (be careful) - type
set time 08/30/04
and for time it's set time 19:30

but you want to check what type of time setup you have
my preference here would be curly would go to ntp source so in monitor time - conf source on and a single and point to probably bigtimeonnet:123
then larry as a secondary pointing to curly

check the settings in monitor for both these - it's better if it changes the time rather than manully and getting it wrong - setting into the future - is awful to fix
#
 
I think you have some serious problems. 603 generally means the replica is sending data. 601 means object not found.

Can you check the replica synch on the server holding the master replica of root and see what errors you get.

Also, I suspect that if you look at the partition tables, you'll see that there are replicas that are not in the "ON" state. DSREPAIR - ADVANCED OPTIONS -- Replica and Partition operations -- (select the partition ) -- View Replica ring.

Not really sure how to tell you to proceed just because there are a lot of possibilities.

I would suggest that you do not do anything in DSREPAIR unless you know exactly what the outcome is, and open a call with Novell if you aren't sure. You can really make things worse if you're not careful.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top