Reliability: OD Master & Replica, or IP-based failover?

I have an Xserve that serves approx. 60 users and around 200GB of shared files. The primary Xserve is the OD master for my workgroup, and the backup Xserve is an OD replica.
I'm new to OS X Server (but not client), so I don't know what happens in the event of, say, the OD master dying. Do client login/access requests automatically get answered by the OD replica? The reason I'm asking this is I'm trying to decide between using two separate servers with an OD master & replica relationship, or using IP-based failover where the backup server would effectively "pretend" to be the primary server in case of a problem.
But with IP-based failover, I don't know if the backup server will automatically know to become an OD master or not. Or, perhaps, the OD integration is completely separate; and I can choose to use IP-based failover and do OD replication whichever way I want to. Does anyone have concrete info?

If your OD Master fails the OD Replica will automatically start handling authentication requests so for the most part you're covered (at least users can still log in).
As noted in that .pdf, though, the replica doesn't allow changes to the directory other than password changes for users with Open Directory passwords.
The main issue is how long your master is going to be down, and the relative pain of promoting the replica to be a master.
For various reasons there is no automatic promote-to-master function because most failures of the master are temporary (e.g. a simple reboot after a software update).
For the failover question I would use IP failover for any services that don't have their own failover mechanism. In all cases you need to write failover scripts to startup whatever processes you need your standby machine to take over. In the case of OD there is a built-in, automatic failover process so I would use that. The only exception to that would be if you wanted the replica to become a master server should the master fail, but I can't think of any circumstance where that would be the case.

Similar Messages

Multi-master replicated environment

hi,
what does it mean multi-master replicated environment? How could i benefit from it?
thanks in advance.

Hello,
This is the environment in which inserts, updates and deletes on objects
in any nodes, included in the environment will be replicated to remaining
nodes which are defined to be part of the replicated environment.
Sinces changes to any node are replicated to all other nodes, they all work
as Master, which gives it the name, Master-2-Master and also advanced replication.
Tahir.

Repairing OD Master/replica tress.

We had an issue with our OD Master and it's 11 replicas.
Apple Support said:
1. Export Users, User Groups, Computers and Computer Groups from the OD Master.
2. Downgrade the Replicas to stand-alone.
3. Downgrade the Master to stand-alone.
4. Promote the OD back to a OD Master.
5. Import the Users, User Groups, Computers and Computer Groups from the export files.
6. Promote the previous replicas from stand-alone to replicas again.
Did all of that, and the import went fine.
However: now all the Home Directory servers are not providing home directory information back to the OD Master.
The Home Directory servers are looking at the local replica for authentication.
The OD Master lists the replicas in it's logs.
And, of course, students/staff will be back Monday and will want to get to their home directories.

Recovering from a corrupted Open Directory Master/Replica system.
1. Export from ODM 'Users' (except your directory admin), 'Groups', 'Computers', 'Computer Groups'.
2. Degrade the OD Replicas, one at a time, to stand-alone.
3. Degrade the OD Master to stand-alone.
4. Restart the OD Master server.
5. Upgrade the OD Master from Stand-alone to OD Master.
6. Upgrade the OD Replicas, one at a time, from Stand-alone to OD Replica.
Rebind remote server to appropriate authentication server (OD Replica)
1. At the server, go to 'System Preferences' - 'Accounts' and unlock the panel with the local server admin login.
2. Click 'Login Options'.
3. Click the 'Edit' button next to 'Network Account Server'.
4. Click 'Open Directory Utility'.
5. Highlight 'LDAPv3' then click the pencil icon.
6. Highlight the configuration and click 'Delete', then click 'Okay' to unbind.
7. Enter the OD Directory Administrator name and password. (This will fail, but it is okay.)
8. Click 'Ok' to forcibly remove the configuration.
9. Click 'Ok'.
10. WHile LPADv3 is still highlighted, click the pencil icon again.
11. Click 'New'.
12. Enter the fully qualified name of the local OD Replica and click 'Continue'.
13. Enter the fully qualified name of the local server, the OD Directory Administrator Login and Password. Click 'Continue'.
14. Enter the local server administrator login and password.
15. Click 'Overwrite'.
16. Click 'Ok', then click 'Ok'. Quit Directory Utility. Close 'System Preferences'.
Reconnecting Home Directory Automounts.
1. At the local server, start 'Server Manager' and select 'File Sharing'.
2. Click 'Share Points' and select the Home Directory item.
3. Click the 'Share Point' option in the lower window.
4. Deslect 'Enable Automount'. Enter the OD Master Directory Administrator Login and Password and click 'Ok'.
5. Click 'Save'.
6. Select 'Enable Automount'. Ensure that the next window is pointing to the local OD Replica and click 'Ok'.
7. Click 'Save'. After clicking 'Save' you can edit the 'Protocol Options' to your preferences.
Restablish the users, groups, computers and computer groups.
1. Open 'Workgroup Manager' on the OD Master.
2. Import Users
3. Import User Groups
4. Import Computers. When importing Computers ensure that the 'ignore record' is selected.
5. Import Computer Groups.
After users have been imported, you can mass assigne them to their appropriate Home Directory location.

LAN-based Failover & intermittent drop issues

Have 2 PIX535s each at remote sites configured for LAN-based failover. There is a VLAN("abc")designed for failover, but in that same VLAN are servers.
My setup is as follows:
PIX535 connects to a DMZ switch using 4 connections: the Inside intf & 3 other intfs.
On that same DMZ switch connects my core switch on the inside network. The core switch is the Root Bridge for the said VLAN ("abc"). It trunks this VLAN, along with others, to the DMZ switch.
On that same DMZ switch are a number of servers that are in this vlan ("abc").
When I configure one of the PIX interfaces to be in this same VLAN and be used for LAN-based failover I get intermittently lose of connectivity to different servers at different times. Its never any one particular server.
When I use another PIX interface, still connecting to this same DMZ switch, but in another VLAN ("xyz"), for LAN-based failover, I dont get any problems.
This other PIX interface is also being used for State failover. The idea is to have two separate interfaces, one each for LAN-based & State failover.
What could be the possible cause of this intermittent loss of connectivity to the servers in VLAN "abc" when I switch LAN-based failover to the PIX interface that connects to a VLAN "abc" port on the DMZ switch.

Following link may help you
http://www.cisco.com/warp/public/110/failover.html#lanbasedfailover

Hi, We have enterprise agreement and we are entittled to use master collection package. Based on thi

hi,
We have enterprise agreement and we are entittled to use master collection package. Based on this we want to upgrade to flash builder 4.7. please let us know how can we do it and how to obtain the keys.
-Anamika

Same here, we used to have serials through the development partner portal, but FB 4.7 doesn't show up there.
As we are out of beta/trials, and don't want to use a 32bit version, would it be possible to have any information about that?

Configure OD master/replica behind a NAT

I have 4 servers 2 of them in public IP (the master is one of them) and the other in the public IP sync ok, but the two others that are behind a NAT in a DMZ with a PUBLIC-IP to private-IP configured, when they are promoting to replicas, the process runs until the end but suddenly the replica refuses to become a replica and return to the previous state, looking into the master logs, it looks like the replica send their true IP (192.168.1.4) to the master and not the IP that it has so I believe that this is part of the problem, I have a well-know DNS working in the master, but not on the replicas, and they point to the master as their DNS.
Any ideas ?

Hi
Promote the Replica to OD Master. Demote the old Master to Standalone and then Promote to Replica. For OD Master & Replica relationships to be successful they must all be the same OS version:
http://manuals.info.apple.com/enUS/Open_Directory_Admin_v10.5_3rdEd.pdf
Page 57 onwards.
Tony

NCP traffic to Master Replica server

I am doing packet traces during login and not finding a single NCP packet to my Master Replica server.
I see the NCP connection packets to my Replica server and any other servers I connect to through login or agents installed (ZCM, Contextless login, etc).
I think I am having redundancy issues and I am trying to resolve them.
This is a Windows 7 workstation with Client 2sp1 ir9. I do have SLP configured with the DA as my Master Replica server. I also have LDAP contextless login configured but those settings do not have the Replica server as the configured server.
I was wondering if anyone can tell me if a client is not suppose to send NCP traffic to the Master Replica server on to the Replica servers. Thanks!

Originally Posted by ataubman
That's not a valid timesync configuration. On the server NDSMASTER load monitor - server parameters - time and change PRIMARY to SINGLE in two places. Then check Configured Sources, it should be turned On and pointed to the IP address of the same NTP server that all the linux boxes in that tree are fgetting their time from (the whole tree must get time from the same place).
You didn't post the Report Sync Status part ...
I made the change you asked for and the IP address has always been the same as the OES boxes. All of our Netware servers get their time from NDSMASTER and NDSMASTER gets it from 10.16.231.237 which is where the OES servers are pointing directly. Is that configuration OK?
NetWare 1602.00 Directory Services Repair 20506.01, DS 20506.07
Log file for server ".NDSMASTER.FCPS" in tree "FCPS"
Start: Monday, December 12, 2011 1:24:17 pm Local Time
Retrieve replica status
Partition: .SBO.FCPS
Replica: .sbostorage.SBO.FCPS 12-12-2011 13:23:41
Replica: .sbo2.SBO.FCPS 12-12-2011 13:23:42
Replica: .ZENWORKS.SBO.FCPS 12-12-2011 13:23:41
Replica: .SBO1.SBO.FCPS 12-12-2011 13:23:41
Replica: .NDSREPLICA.FCPS 12-12-2011 13:23:49
Replica: .NDSMASTER.FCPS 12-12-2011 13:23:47
All servers synchronized up to time: 12-12-2011 13:23:41
Partition: .APR.FCPS
Replica: .APR_INST.APR.FCPS 12-12-2011 13:24:13
Replica: .NDSREPLICA.FCPS 12-12-2011 13:24:10
Replica: .NDSMASTER.FCPS 12-12-2011 13:24:10
All servers synchronized up to time: 12-12-2011 13:24:10
Partition: .BHE.FCPS
Replica: .BHE_INST.BHE.FCPS 12-12-2011 13:09:50
Replica: .NDSREPLICA.FCPS 12-12-2011 13:10:00
Replica: .NDSMASTER.FCPS 12-12-2011 13:09:57
All servers synchronized up to time: 12-12-2011 13:09:50
Partition: .BMS.FCPS
Replica: .NDSREPLICA.FCPS 12-12-2011 13:23:47
Replica: .NDSMASTER.FCPS 12-12-2011 13:23:47
Replica: .BYRD_MS.BMS.FCPS 12-12-2011 13:23:46
All servers synchronized up to time: 12-12-2011 13:23:46
Partition: .DJH.FCPS
Replica: .DJH1.DJH.FCPS 12-12-2011 13:23:58
Replica: .NDSREPLICA.FCPS 12-12-2011 13:24:09
Replica: .NDSMASTER.FCPS 12-12-2011 13:24:10
All servers synchronized up to time: 12-12-2011 13:23:58
Partition: .FCGOV1.FCPS
Replica: .NDSREPLICA.FCPS 12-12-2011 13:14:04
Replica: .NDSMASTER.FCPS 12-12-2011 13:15:05
All servers synchronized up to time: 12-12-2011 13:14:04
Partition: .FCM.FCPS
Replica: .FCM_3.FCM.FCPS 12-12-2011 13:24:11
Replica: .NDSREPLICA.FCPS 12-12-2011 13:23:48
Replica: .NDSMASTER.FCPS 12-12-2011 13:23:47
All servers synchronized up to time: 12-12-2011 13:23:47
Partition: .GBE.FCPS
Replica: .GBES_INST.GBE.FCPS 12-12-2011 13:24:01
Replica: .NDSREPLICA.FCPS 12-12-2011 13:24:09
Replica: .NDSMASTER.FCPS 12-12-2011 13:24:10
All servers synchronized up to time: 12-12-2011 13:24:01
Partition: .Groupwis.FCPS
Replica: .NDSREPLICA.FCPS 12-12-2011 12:55:18
Replica: .NDSMASTER.FCPS 12-12-2011 12:55:50
All servers synchronized up to time: 12-12-2011 12:55:18
Partition: .IHE.FCPS
Replica: .IHE_INST.IHE.FCPS 12-12-2011 13:23:28
Replica: .NDSREPLICA.FCPS 12-12-2011 13:23:28
Replica: .NDSMASTER.FCPS 12-12-2011 13:23:37
All servers synchronized up to time: 12-12-2011 13:23:28
Partition: .JDC.FCPS
Replica: .JDC2.JDC.FCPS 12-12-2011 13:17:16
Replica: .NDSREPLICA.FCPS 12-12-2011 13:17:16
Replica: .NDSMASTER.FCPS 12-12-2011 13:17:18
All servers synchronized up to time: 12-12-2011 13:17:16
Partition: .JWM.FCPS
Replica: .INST.JWM.FCPS 12-12-2011 13:23:49
Replica: .NDSREPLICA.FCPS 12-12-2011 13:23:58
Replica: .NDSMASTER.FCPS 12-12-2011 13:23:59
All servers synchronized up to time: 12-12-2011 13:23:49
Partition: .MAINT.FCPS
Replica: .MAINT2.MAINT.FCPS 12-12-2011 13:24:10
Replica: .NDSREPLICA.FCPS 12-12-2011 13:11:19
Replica: .NDSMASTER.FCPS 12-12-2011 13:24:09
All servers synchronized up to time: 12-12-2011 13:11:19
Partition: .MES.FCPS
Replica: .MES_INST.MES.FCPS 12-12-2011 13:24:04
Replica: .NDSREPLICA.FCPS 12-12-2011 13:24:00
Replica: .NDSMASTER.FCPS 12-12-2011 13:24:09
All servers synchronized up to time: 12-12-2011 13:24:00
Partition: .NREP.FCPS
Replica: .NREP1.NREP.FCPS 12-12-2011 13:01:39
Replica: .NDSREPLICA.FCPS 12-12-2011 13:01:39
Replica: .NDSMASTER.FCPS 12-12-2011 13:01:57
All servers synchronized up to time: 12-12-2011 13:01:39
Partition: .OES.FCPS
Replica: .OES_INST.OES.FCPS 12-12-2011 13:20:53
Replica: .NDSREPLICA.FCPS 12-12-2011 13:21:03
Replica: .NDSMASTER.FCPS 12-12-2011 13:21:02
All servers synchronized up to time: 12-12-2011 13:20:53
Partition: .RBE.FCPS
Replica: .RBE_INST.RBE.FCPS 12-12-2011 13:24:03
Replica: .NDSREPLICA.FCPS 12-12-2011 13:24:10
Replica: .NDSMASTER.FCPS 12-12-2011 13:24:09
All servers synchronized up to time: 12-12-2011 13:24:03
Partition: .REA.FCPS
Replica: .REAMS2.REA.FCPS 12-12-2011 13:23:41
Replica: .NDSREPLICA.FCPS 12-12-2011 13:23:48
Replica: .NDSMASTER.FCPS 12-12-2011 13:23:48
All servers synchronized up to time: 12-12-2011 13:23:41
Partition: .SES.FCPS
Replica: .SES_INST.SES.FCPS 12-12-2011 13:23:43
Replica: .NDSREPLICA.FCPS 12-12-2011 13:23:50
Replica: .NDSMASTER.FCPS 12-12-2011 13:23:48
All servers synchronized up to time: 12-12-2011 13:23:43
Partition: .SLP.FCPS
Replica: .NDSREPLICA.FCPS 12-12-2011 13:24:00
Replica: .NDSMASTER.FCPS 12-12-2011 13:24:10
All servers synchronized up to time: 12-12-2011 13:24:00
Partition: .GME.FCPS
Replica: .GME_INST.GME.FCPS 12-12-2011 13:23:54
Replica: .NDSREPLICA.FCPS 12-12-2011 13:24:00
Replica: .NDSMASTER.FCPS 12-12-2011 13:23:59
All servers synchronized up to time: 12-12-2011 13:23:54
Partition: .Transp.FCPS
Replica: .TRANS1.Transp.FCPS 12-12-2011 13:18:12
Replica: .NDSREPLICA.FCPS 12-12-2011 13:18:16
Replica: .NDSMASTER.FCPS 12-12-2011 13:18:09
All servers synchronized up to time: 12-12-2011 13:18:09
Partition: .JWH.FCPS
Replica: .jwhstore.JWH.FCPS 12-12-2011 13:24:09
Replica: .wood1.JWH.FCPS 12-12-2011 13:24:14
Replica: .JWHS_MSTR.JWH.FCPS 12-12-2011 13:24:09
Replica: .NDSREPLICA.FCPS 12-12-2011 12:54:37
Replica: .NDSMASTER.FCPS 12-12-2011 12:54:34
Replica: .JWHS_LIB.JWH.FCPS 12-12-2011 13:24:08
All servers synchronized up to time: 12-12-2011 12:54:34
Partition: .SHS.FCPS
Replica: .shsstore.SHS.FCPS 12-12-2011 13:22:41
Replica: .warrior1.SHS.FCPS 12-12-2011 13:22:41
Replica: .SHS_MSTR.SHS.FCPS 12-12-2011 13:22:41
Replica: .NDSREPLICA.FCPS 12-12-2011 13:06:46
Replica: .NDSMASTER.FCPS 12-12-2011 13:06:50
Replica: .SHS_LIBRARY.SHS.FCPS 12-12-2011 13:22:40
All servers synchronized up to time: 12-12-2011 13:06:46
Partition: .AES.FCPS
Replica: .AES_INST.AES.FCPS 12-12-2011 13:23:55
Replica: .NDSREPLICA.FCPS 12-12-2011 13:24:00
Replica: .NDSMASTER.FCPS 12-12-2011 13:23:58
All servers synchronized up to time: 12-12-2011 13:23:55
Partition: .MHS.FCPS
Replica: .pioneer1.MHS.FCPS 12-12-2011 13:24:16
Replica: .mhsstore.MHS.FCPS 12-12-2011 13:24:15
Replica: .NDSREPLICA.FCPS 12-12-2011 13:17:31
Replica: .NDSMASTER.FCPS 12-12-2011 13:17:36
Replica: .MHS_MASTER.MHS.FCPS 12-12-2011 13:24:16
Replica: .MHS_LIB.MHS.FCPS 12-12-2011 13:24:15
All servers synchronized up to time: 12-12-2011 13:17:31
Partition: .[Root].
Replica: .NDSREPLICA.FCPS 12-12-2011 13:24:10
Replica: .NDSMASTER.FCPS 12-12-2011 13:24:10
All servers synchronized up to time: 12-12-2011 13:24:10
Partition: .EES.FCPS
Replica: .EES_INST.EES.FCPS 12-12-2011 13:19:10
Replica: .NDSREPLICA.FCPS 12-12-2011 13:19:21
Replica: .NDSMASTER.FCPS 12-12-2011 13:19:11
All servers synchronized up to time: 12-12-2011 13:19:10
Finish: Monday, December 12, 2011 1:24:18 pm Local Time
*** END ***
NetWare 1602.00 Directory Services Repair 20506.01, DS 20506.07
Log file for server ".NDSMASTER.FCPS" in tree "FCPS"
Time synchronization and server status information
Start: Monday, December 12, 2011 1:28:49 pm Local Time
---------------------------+---------+---------+-----------+--------+-------
DS.NLM Replica Time Time is Time
Server name Version Depth Source in sync +/-
---------------------------+---------+---------+-----------+--------+-------
.groupwise.FCPS 20501.00 -1 Non-NetWare Yes 0
.BOARDMAIL.SBO.FCPS 20504.13 -1 Secondary Yes 0
.EES_INST.EES.FCPS 20219.15 2 Secondary Yes 0
.pioneer1.MHS.FCPS 20605.00 2 Non-NetWare Yes 0
.mhsstore.MHS.FCPS 20605.00 2 Non-NetWare Yes 0
.MHS_MASTER.MHS.FCPS 20219.15 2 Secondary Yes 0
.MHS_LIB.MHS.FCPS 20219.15 2 Secondary Yes 0
.AES_INST.AES.FCPS 20219.15 2 Secondary Yes 0
.shsstore.SHS.FCPS 20605.00 2 Non-NetWare Yes 0
.warrior1.SHS.FCPS 20605.00 2 Non-NetWare Yes 0
.SHS_MSTR.SHS.FCPS 20219.15 2 Secondary Yes 0
.SHS_LIBRARY.SHS.FCPS 20219.15 2 Secondary Yes 0
.jwhstore.JWH.FCPS 20603.06 2 Non-NetWare Yes 0
.wood1.JWH.FCPS 20605.00 2 Non-NetWare No - 9
.JWHS_MSTR.JWH.FCPS 20219.15 2 Secondary Yes 0
.JWHS_LIB.JWH.FCPS 20219.15 2 Secondary Yes 0
.TRANS1.Transp.FCPS 20219.15 2 Secondary Yes 0
.GME_INST.GME.FCPS 20219.15 2 Secondary Yes 0
.SES_INST.SES.FCPS 20219.15 2 Secondary Yes 0
.REAMS2.REA.FCPS 20219.15 2 Secondary Yes 0
.RBE_INST.RBE.FCPS 20219.15 2 Secondary Yes 0
.OES_INST.OES.FCPS 20219.15 2 Secondary Yes 0
.NREP1.NREP.FCPS 20219.15 2 Secondary Yes 0
.MES_INST.MES.FCPS 20219.15 2 Secondary Yes 0
.MAINT2.MAINT.FCPS 20217.06 2 Secondary Yes 0
.INST.JWM.FCPS 20219.15 2 Secondary Yes 0
.JDC2.JDC.FCPS 20219.15 2 Secondary Yes 0
.IHE_INST.IHE.FCPS 20219.15 2 Secondary Yes 0
.GBES_INST.GBE.FCPS 20219.15 2 Secondary Yes 0
.FCM_3.FCM.FCPS 20219.15 2 Secondary Yes 0
.DJH1.DJH.FCPS 20219.15 2 Secondary Yes 0
.BYRD_MS.BMS.FCPS 20219.15 2 Secondary Yes 0
.BHE_INST.BHE.FCPS 20219.15 2 Secondary Yes 0
.APR_INST.APR.FCPS 20219.15 2 Secondary Yes 0
.sbostorage.SBO.FCPS 20605.00 2 Non-NetWare Yes 0
.sbo2.SBO.FCPS 20604.10 2 Non-NetWare Yes 0
.ZENWORKS.SBO.FCPS 20219.15 2 Secondary Yes 0
.SBO1.SBO.FCPS 20219.15 2 Secondary Yes 0
.NDSREPLICA.FCPS 20506.07 0 Secondary Yes 0
.NDSMASTER.FCPS 20506.07 0 Single Yes 0
---------------------------+---------+---------+-----------+--------+-------

Multi-Master replica busy

I have a multi-master ldap server(5.1 service pack 2, build number:2003.028.2338). There are about 56k users in 1st server and 45k on the 2nd server when count the users in the 2 servers. Plus, I have a pure consumer which is working fine with the replica from 1st server.
But when activated replication between two multi-master machines, the secondary server got the error message like below. And the replica process is very slow and the cost CPU always 40% and up. Can anyone please help me with this issue? What the replica process suppose to do? Why the replica is slow? What happens if the replication queue is about 11k entries? How can I speed up the replica?
Thanks in advance for your help.
===error log====
[29/Sep/2003:12:52:05 -0400] NSMMReplicationPlugin - Warning: timed out waiting 600 seconds for add operation result from replica 10.30.250.146:389
[29/Sep/2003:12:52:05 -0400] NSMMReplicationPlugin - Failed to replay change (uniqueid e1181801-1dd111b2-8003d8a4-aa1f9c2b, CSN 3f729278000300030000) to replica "cn=PRI-2-SEC-USER-01, cn=replica, cn="o=sso", cn=mapping tree, cn=config (host 10.30.250.146, port 389)": Connection lost. Will retry later.
[29/Sep/2003:12:52:05 -0400] NSMMReplicationPlugin - Warning: unable to send endReplication extended operation to consumer "cn=PRI-2-SEC-USER-01, cn=replica, cn="o=sso", cn=mapping tree, cn=config (host 10.30.250.146, port 389)" - error 2
[29/Sep/2003:13:07:18 -0400] NSMMReplicationPlugin - Warning: timed out waiting 600 seconds for add operation result from replica 10.30.250.146:389
[29/Sep/2003:13:07:18 -0400] NSMMReplicationPlugin - Failed to replay change (uniqueid e1181804-1dd111b2-8003d8a4-aa1f9c2b, CSN 3f729293000200030000) to replica "cn=PRI-2-SEC-USER-01, cn=replica, cn="o=sso", cn=mapping tree, cn=config (host 10.30.250.146, port 389)": Connection lost. Will retry later.
[29/Sep/2003:13:07:19 -0400] NSMMReplicationPlugin - Warning: unable to send endReplication extended operation to consumer "cn=PRI-2-SEC-USER-01, cn=replica, cn="o=sso", cn=mapping tree, cn=config (host 10.30.250.146, port 389)" - error 2
[29/Sep/2003:13:27:32 -0400] NSMMReplicationPlugin - Warning: timed out waiting 600 seconds for add operation result from replica 10.30.250.146:389
===access log===
[29/Sep/2003:13:59:42 -0400] conn=292 op=1 RESULT err=0 tag=101 nentries=1 etime=0
[29/Sep/2003:13:59:43 -0400] conn=292 op=2 SRCH base="cn=config" scope=0 filter="(|(objectClass=*)(objectClass=ldapsuben
try))" attrs="nsslapd-instancedir nsslapd-security"
[29/Sep/2003:13:59:43 -0400] conn=292 op=2 RESULT err=0 tag=101 nentries=1 etime=0
[29/Sep/2003:13:59:43 -0400] conn=292 op=3 SRCH base="cn=options,cn=features,cn=config" scope=1 filter="(objectClass=dir
ectoryServerFeature)" attrs=ALL
[29/Sep/2003:13:59:43 -0400] conn=292 op=3 RESULT err=0 tag=101 nentries=0 etime=0
[29/Sep/2003:13:59:48 -0400] conn=292 op=4 SRCH base="cn=config" scope=0 filter="(|(objectClass=*)(objectClass=ldapsuben
try))" attrs="nsslapd-security"
[29/Sep/2003:13:59:48 -0400] conn=292 op=4 RESULT err=0 tag=101 nentries=1 etime=0
[29/Sep/2003:13:59:48 -0400] conn=292 op=5 SRCH base="cn=config" scope=0 filter="(|(objectClass=*)(objectClass=ldapsuben
try))" attrs="nsslapd-port nsslapd-secureport nsslapd-lastmod nsslapd-readonly nsslapd-schemacheck nsslapd-referral"
[29/Sep/2003:13:59:48 -0400] conn=292 op=5 RESULT err=0 tag=101 nentries=1 etime=0
[29/Sep/2003:13:59:51 -0400] conn=292 op=6 SRCH base="cn=replication, cn=config" scope=0 filter="(|(objectClass=*)(objec
tClass=ldapsubentry))" attrs=ALL
[29/Sep/2003:13:59:51 -0400] conn=292 op=6 RESULT err=0 tag=101 nentries=1 etime=0
[29/Sep/2003:13:59:51 -0400] conn=292 op=7 SRCH base="cn=replication,cn=config" scope=2 filter="(objectClass=*)" attrs=ALL

I have had a similar problem. and it was due to that I recreated a new replication agreement which pointed to a different server with the same id. Or to the same server with a different ID.
The solution provided by sun was to remove the reference to the old replicas in the dse.ldif and restart but it didn't work out. not even by ldapmodify on the replicas dn.
I had to reinstall...

DPM 2012 R2 Consistency Check (Replica Inconsistent) Error for Failover Cluster

I have a SCDPM 2012 R2 instance running against a Windows Server 2012 R2 Failover Cluster on the network.
However, any new/migrated Roles/Virtual machines that I add under an existing protection group always gives me an error saying that the replica is inconsistent.
I've verified the following :
1. All windows updates are applied on the cluster hosts & the DPM server.
2. The VSS and DPMRA services are running on the hosts & DPM server.
3. The Windows Server Backup feature has been installed on all the machines as well.
4. The short term storage disks attached to the DPM server are LUNs and there is enough free space on those.
What else am I missing that could be causing the Replica to be inconsistent - considering that these are new VMs on the hosts themselves - is there a way to force a fresh replica to be created?

Do not remove any of the providers they come with the system. There is just something wrong with that VM, your trying to backup, as it could take the initial replica creation.
Check all of the following
1) Make sure you have enough C drive space on the guest - need space to create a snapshot
2) Check the vssadmin list wirters for any errors
If none of the above, rerun the consistency check when no other backup is running. Check the Application log on the host for any vss failures
Ensure you have all the DPM hotfixes - I am compiling a list since i've been thru many DPM issues.
Great product when you get it going but like any product there are bumps in the road :)
ANNCEX

Grant Master field group control based on authorization - hide fields

Hi,
The Grant Master field group control settings are based on grant type settings. So you can hide fields and tabs etc based on the grant's lifecycle status.
Does anyone know if this can be configured based on authorization objects / authorization roles?
We wish certain fields to be hidden in all life cycle statuses for all general users, but for central finance users we wish those fields to be visible.
There is a customizing transaction GMS103 in the SPRO/IMG path
IMG > Public Sector Management > Grants Management > Grantee Management > Master Data > Grant > GM Grant Control : Field group for Authorizations
The documentation for this transaction says:
GM Grant Control: Field Group for Authorizations
It is possible to group fields together for authorization purposes. Use this step to specify such groups in Grants Management (GM).
Standard settings
We deliver the groups you can enter here, as standard.
Activities
Choose New Entries and enter the ID for the group you want to add. When you save, the system displays the longer description for the group.
Further notes
Authorization to a group allows access to all the fields in the group for users with the appropriate authorization. Only allow access to those you know need it for the whole group.
This table is empty on our system. Has anyone used this part of the customizing and can they let me know how it links into the basis roles / authorizations etc.
Thanks
Paul Abrahamson

I found this authorization object F_GMGT_FDG
The documentation for the authorization object states:
Definition
With this authorization object, you can define authorizations for individual field groups in grants management maintenance. You thereby define which fields in grant master maintenance can be maintained or viewed by a user.
Notes
This authorization is optional. You do not have to assign authorization if there are no field groups that require special protection and consequently no field groups requiring authorization were defined in Customizing.
Defined fields
The object consists of the fields "Field group" and "Activity":
Field group
Here you define which field groups require authorization.
Activity
Here you define which activities are permitted:
02 = Change
03 = Display
* = All activities
Procedure
Proceed as follows if you want to use this authorization:
1. Determine the field groups of the fields that you want to protect.
2. In Customizing, define that these field groups require authorization.
3. For each field group, define the authorization that you wish to assign to selected users.
4. Assign this authorization using the corresponding profile.
I'll try this out and update this message again later

Master Details form (LOV based on Detail Column of Join Condition)

I have created a master detail form where user_id is joining master and details.
I have created one dynamic lov based on child user_id in detail block to diplay all user who works under current user.
Problem : When i want to select Insert detail action in detail block the dynamic lov should read the user_id which is going to be inserted when you press Save button. Means as its not getting populated till one click on save button my lov is not getting refereshed.
Please advice what should i do.
Thanks
Bakulesh

I solved myself by modifing some guru's script from this forum little bit. I am adding here for feedback or use to any.
htp.p('<script language="JavaScript1.3">
function getMstFieldValue(form,fieldName)
var objName = "";
var tmp = "";
var dAction = "";
var sel_idx = 0;
var cnt = 0;
var instance = 0;
var slicedName;
var fillData = new Array();
var blkname;
for(var i = 0; i < form.length; i++)
slicedName = form.elements.name.split(".");
tmp = slicedName[2];
instance = parseInt(slicedName[3],10);
blkname = slicedName[1];
//alert("Fld "+tmp+" blk "+blkname+ " instance "+instance);
if (!tmp)
continue;
objName = tmp;
if (objName == fieldName && blkname == "MASTER_BLOCK")
return form.elements[i].value;
function setDetFieldValue(form,fieldName,value)
var objName = "";
var tmp = "";
var dAction = "";
var sel_idx = 0;
var cnt = 0;
var instance = 0;
var slicedName;
var fillData = new Array();
var blkname;
for(var i = 0; i < form.length; i++)
slicedName = form.elements[i].name.split(".");
tmp = slicedName[2];
instance = parseInt(slicedName[3],10);
blkname = slicedName[1];
//alert("Fld "+tmp+" blk "+blkname+ " instance "+instance);
if (!tmp)
continue;
objName = tmp;
if (objName == fieldName && blkname == "DETAIL_BLOCK")
form.elements[i].value = value;
</script>');
thanks
Bakulesh

OS/hw based failover cluster for WebLogic Server 9.2 Standard Edition

Hi
Is it possible to run WebLogic Server 9.2 SE on OS/hardware based cluster?
I want to get an simple failover environment on a cluster of 2 nodes (active-passive).
Oracle Database can be run in such scenario with one license with a limit of up time for passive instance.
Is it the same with WLS licences?
Regards
WD

The problem doesn't look like it has anything to do with wappers per se. The stack indicates that the JVM died when the persistent store tried to invoke a standard Java synchronize operation. JVM crashes need to be analyzed by a JVM expert, so I second the suggestion to solicit help from JVM experts and/or filing a case with customer support. In the mean-time, you can probably work-around the issue by either (A) ensuring you have a recent version of the JVM installed, or (B) temporarily switching to the Sun JVM.
Regards,
tom
Edited by: TomB on Sep 17, 2010 2:33 PM

Kerberized NFS home folders without being an OD Master/Replica?

Does an OS X server have to be either an OD Master or Replica in order to Kerberize NFS?
I'm trying to run kerberized NFS home folders from a file server that is joined to our OD, but is not a replica of it, and it's not working. The clients log in OK, but say "The home folder for user "x" isn't located in the usual place or can't be accessed."
If I open a Terminal at this point and cd into /Network/Servers/servername/path/to/home, then I can see the NFS mount point which appears to be owned by the user logged in, but I can't cd into the mount point, I get "Permission denied".
Any suggestions?
All clients and servers are 10.6.4.

Yup, this is actually really easy in Mac OS X Leopard. Before you do this, make sure that any local version of the account has been removed from the client computer. Open up the Workgroup manager and go to the user that you want to add the client side home folder for, go to Home, and add a new entry with "/Users/<username>" as the path and click ok. I click Create Home Now just to make sure, I don't know if this is required.
I THINK this is all you have to do, although I do have my clients managed though a Computer Group list that is set to always manage the Login window to show all network users. Obviously only users with their local folder on a particular computer will be able to see their items. This method works great in an environment where users always use the same computer, but because the folder isn't being stored on the server you can't use this method where users will be using multiple computers.

OD Master replicating to nonexistent server.

Hey All,
Thank You for reading and I hope that I can get some help on this forum. Just to let you know, I have been reading extensivly on my problems and really need some help with the following issues. I will first state the problems as precisely as I can, and then tell you what I have done (if anything), later.
I have a Mac Mini server running 10.6.5 server (.5 updated a few weeks ago). This server is running AFP, DNS, Open Directory, Print and SMB. It is also running VMWare, and a CRM called ACT!. This vmware is on bridged mode, because it does share it's ACT! database with the other PC's on the network. This is necessary in our work environment, as the clients are PC's. We also have a Airport Extreme router running NAT and Port Forwarding for external management and it is on bridged mode (b/c of Verizon). All the PC's are running Windows XP Professional. All is wireless.
1. My largest problem is that the PC's are flaky when it comes to binding to my OD Master server. Just to let you know, DNS resolutions are working. On top of this, the OD Master seems to be replicating to the vmware ip addresses. I think this may be a source of the problem and I have gone into WGM and removed ALL instances of the ip addresses. I have restarted and still found it to be replicating to those numbers. Can any of you help me remove this problem, as I think this is a root to the issue.
2. My screen sharing no longer works. It is enabled in system preferences but it won't work in/out house. No clue why.
3. I cannot wire my server to the router, but I can wire the clients to the router. Would this help or not?
I have been calling Apple like no tomorrow, but little help has come my way. I have destroyed and rebuilt this OD server several times. There are no replicas (due to the size of the infrastructure). I would like to setup a simple OD server where users from PC's can authenticate and mount their respective folders to edit. If any of you are familiar with VMWare, is there a way to circumvent/destroy those interfaces vmnet1 and vmnet8 without losing access to the internet? My client is dependent on VMWare to work as ACT! stores her entire business career. I am a fast responder and desperately in need of answers!
Thank You,
Syed Zaidi
Message was edited by: syedzaidi.nyc

Anyone here to help me?

Change Master Agent for Cluster-Based Agent -- OEM 11.1.0.1

        We had a 6 node RAC cluster and a cluster-based management agent installed to monitor.
        Node 6 was the Master agent.
       Now node 6 is not part of the cluster.
    I am getting metric collection for the cluster.
I cluster configuration in OEM shows Master agent as node 6. I only have 3 nodes now.
How do I update the master agent or the cluster.
Thanks,
Silver

On the clustef homepage in OEM there is a link called properties under the name of the cluster. Click the link it will shlw the true master node. What I have seen in the pasf what can rsolve the issue is bounce the agent on that master node. You can also try a clear state. You can also use the configuration for the cluster database to make sure the old instance has been remove from OEM.

Reliability: OD Master & Replica, or IP-based failover?

Similar Messages

Maybe you are looking for