10-07-2019
IBM TDS/SDS (LDAP) - can I mix endianness among servers in an instance ?
I'd like to add some x/linux-based servers to my current AIX-based TDS/SDS server community. Reading the Fine Install Guide (rtfig ?) I believe this may be covered by the section "Upgrade an instance of a previous version to a different computer" i.e. I'm going to install latest/greatest SDS on a new server image, then bring in the instance data from one of my current servers.
The chart in that section of the Install Guide indicates this is only possible among systems with the same endianness.
Is it possible to have Intel & power servers cooperating on the same directory ? If so, can someone pls point me to doc on how to get there ?
Much appreciated !
[edit:] more reading. I see in the section "creating a copy of an existing instance" the same requirement that only data from a source with the same endianness as the target can be used.
So: can I create an instance copy without data, then (quiesce replication and suspend my servers and) dump the directory to an LDIF, and load the new instance from that instead of from a backup ? Then ensuring that replication is prepared on the new copy and then spinning up the whole pile ? The crux being that by importing the data as text rather than binary, I avoid the fact that handling of endianness/network byte order is missing from the deploy tools ?
Same question as above though, crudely, does replication handle network byte order correctly and swap data nice between different endiannesses ?
Last edited by maraixadm; 10-08-2019 at 12:28 AM..
5 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone have succesfully interconnected HP-UX 10.2 HP 9000 K370 servers with A6885A HBA's, with an IBM Fastt storage server? I need to replace integrate both platforms. Interoperability matrices from manufacturers do not certified such integration. Thanks for anybody's help. (0 Replies)
Discussion started by: raltmannr
0 Replies
2. UNIX for Dummies Questions & Answers
I am the new jr admin on a solaris team (2 people). We have over 40 solaris servers (v8 and v9) yet no LDAP to manage it all. Is this unusual?
So, if we need to add a new user, we have to add him 40x.
Thanks in advance
~R (1 Reply)
Discussion started by: abstractrick
1 Replies
3. AIX
Hello dear friends, I wanrt to document our servers configuration but have no Idea which softweare should I use for documenting server environment.. maybe anyone can suggest me which software should I use.. thanks in Advance (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies
4. AIX
We have a java stand alone application running currently on sun Solaris system. The java application runs on Jdk 1.4.
We are reshooting this java application to new Ibm servers.
There are 10 unix scripts for this application. All scripts works well except one shell script,
This shell... (2 Replies)
Discussion started by: poojagupta
2 Replies
5. AIX
Hello,
I'm currently trying to mix local and LDAP users on an AIX 7.1.
I've triied many things.
My LDAP Server in on a CentOS - OpenLDAP (which works fine with linux).
I'm currently stuck on AIX at how to declare LDAP AND Local users.
Here's what i did :
/usr/sbin/mksecldap -c -h 'ldap03'... (15 Replies)
Discussion started by: AIX_user_324891
15 Replies
LEARN ABOUT CENTOS
ipa-csreplica-manage
ipa-csreplica-manage(1) IPA Manual Pages ipa-csreplica-manage(1)
NAME
ipa-csreplica-manage - Manage an IPA CS replica
SYNOPSIS
ipa-csreplica-manage [OPTION]... [connect|disconnect|del|list|re-initialize|force-sync]
DESCRIPTION
Manages the CA replication agreements of an IPA server.
connect [SERVER_A] <SERVER_B>
- Adds a new replication agreement between SERVER_A/localhost and SERVER_B
disconnect [SERVER_A] <SERVER_B>
- Removes a replication agreement between SERVER_A/localhost and SERVER_B
del <SERVER>
- Removes all replication agreements and data about SERVER
list [SERVER]
- Lists all the servers or the list of agreements of SERVER
re-initialize
- Forces a full re-initialization of the IPA CA server retrieving data from the server specified with the --from option
force-sync
- Immediately flush any data to be replicated from a server specified with the --from option
The connect and disconnect options are used to manage the replication topology. When a replica is created it is only connected with the
master that created it. The connect option may be used to connect it to other existing replicas.
The disconnect option cannot be used to remove the last link of a replica. To remove a replica from the topology use the del option.
If a replica is deleted and then re-added within a short time-frame then the 389-ds instance on the master that created it should be
restarted before re-installing the replica. The master will have the old service principals cached which will cause replication to fail.
OPTIONS
-H HOST, --host=HOST
The IPA server to manage. The default is the machine on which the command is run Not honoured by the re-initialize command.
-p DM_PASSWORD, --password=DM_PASSWORD
The Directory Manager password to use for authentication
-v, --verbose
Provide additional information
-f, --force
Ignore some types of errors
--from=SERVER
The server to pull the data from, used by the re-initialize and force-sync commands.
EXAMPLES
List a server's replication agreements.
# ipa-csreplica-manage list srv1.example.com
srv2.example.com
srv3.example.com
Re-initialize a replica:
# ipa-csreplica-manage re-initialize --from srv2.example.com
This will re-initialize the data on the server where you execute the command, retrieving the data from the srv2.example.com replica
Add a new replication agreement:
# ipa-csreplica-manage connect srv2.example.com srv4.example.com
Remove an existing replication agreement:
# ipa-csreplica-manage disconnect srv1.example.com srv3.example.com
Completely remove a replica:
# ipa-csreplica-manage del srv4.example.com
Using connect/disconnect you can manage the replication topology.
EXIT STATUS
0 if the command was successful
1 if an error occurred
IPA
Jul 14 2011 ipa-csreplica-manage(1)