Sponsored Content
Operating Systems AIX IBM TDS/SDS (LDAP) - can I mix endianness among servers in an instance ? Post 303039487 by maraixadm on Monday 7th of October 2019 06:07:12 PM
Old 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

HP-UX 10.2 servers interoperability with IBM mass storage devices

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

Is no LDAP unusual for 40+ solaris servers?

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

IBM Servers Documentation

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

executable problems with shell script in IBM servers

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

Mix LDAP and LOCAL user on 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
PMNAMEINDOM(3)						     Library Functions Manual						    PMNAMEINDOM(3)

NAME
pmNameInDom - translate an instance identifier into an instance name C SYNOPSIS
#include <pcp/pmapi.h> int pmNameInDom(pmInDom indom, int inst, char **name); cc ... -lpcp DESCRIPTION
For the instance domain indom, in the current Performance Metrics Application Programming Interface (PMAPI) context, locate the instance with the internal instance identifier given by inst, and return the full external instance identification via name. The value for the instance domain indom is typically extracted from a pmDesc structure, following a call to pmLookupDesc(3) for a particu- lar performance metric. The space for the value of name will have been allocated in pmNameInDom with malloc(3C), and it is the responsibility of the caller to free(3C) the space when it is no longer required. pmNameInDom returns zero on success. SEE ALSO
PMAPI(3), pmGetConfig(3), pmGetInDom(3), pmLookupInDom(3), pmNameInDomArchive(3), pcp.conf(5) and pcp.env(5). DIAGNOSTICS
PM_ERR_INDOM indom is not a valid instance domain identifier PM_ERR_INST The instance identifier inst is not known for the instance domain indom in the current PMAPI context Performance Co-Pilot PCP PMNAMEINDOM(3)
All times are GMT -4. The time now is 11:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy