12-11-2005 02:26 PM - edited 03-13-2019 11:31 AM
Hi,
After a complete reinstall of both pub & sub using BARS I keep getting this error every 30 minutes. Below event is a paste from the publisher although the subsriber is showing it aswell.
Event Type: Warning
Event Source: DCDirectory
Event Category: Directory Operation
Event ID: 7879
Date: 12/12/2005
Time: 8:06:38 PM
User: N/A
Computer: <publisher>
Description:
(DSA REPLICATION(17) Proc 1056, Sev 14)
We have received an error from our partner DSA which suggests
a configuration problem with our shadowing agreement, or an
inconsistency with the configuration on the remote server.
Shadowing agreement slot index 1
Agreement id 1
Role (consumer/supplier) Supplier
Partner DSA AE_Title /o=cisco.com/cn=DCDSERVER/cn=<subscriber>
Shadow problem returned Invalid Agreement ID
Also, i am not able to logon in the CCM Administration pages on the subscriber.
I did a password synch check and there are some question marks on the sub side (see attach).
Thanks a lot for any insight!
Peter
Running CCM 4.1(3)SR2, OS 2000.2.7SR8.
12-11-2005 02:49 PM
12-11-2005 03:54 PM
I can sucessfully logon into DC Directory on the Pub.
When logging into the DCD on the subscriber with username "Directory Manager" and password identically used on the pub I receive the following error:
"DCD09360020: Failed to write policy information to DSA".
After clicking OK DCD opens and see cisco.com structure.
12-11-2005 05:12 PM
Also, when failing over to the subscriber, phones are not able to register with it.
Replication test by creating a dummy phone works perfectly.
Am I experiencing an issue on LDAP access in DCD?
12-11-2005 05:19 PM
Aha... first problem noticed.
It appears that BARS 4.0.8 only has set my host file back in original state while it left my lmhost untouched.
In the meantime I rebooted both Pub & Sub. I am still unable to logon into the ccm admin page on the subscriber - also phones are not able to register with the sub when failing over. :-(
12-11-2005 06:34 PM
Now I am unable to start CCM service, tftp, etc...
"Service could not be started because it timed out".
Also after a reboot of the subscriber; the event viewer says "CCM restarting in 60000 seconds, tftp restarting in ...".
What is going on here?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: