IBM TDS/SDS (LDAP) - can I mix endianness among servers in an instance ? Post: 303039487

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

10-07-2019

Registered User

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..

maraixadm

View Public Profile for maraixadm

Find all posts by maraixadm

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.

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

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

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...

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'...

LEARN ABOUT CENTOS

radrelay

RADRELAY(8)							 FreeRADIUS Daemon						       RADRELAY(8)

NAME

       radrelay -- Deprecated command.

DESCRIPTION

       The  functions  of  radrelay have been added to radiusd.  One benefit is that one instance of radiusd can read multiple detail files, among
       others.

       The rlm_sql_log module does something similar, but for SQL queries.  See it's man page for details.

REPLICATION FOR BACKUPS

       Many sites run multiple radius servers; at least one primary and one backup server. When the primary goes down, most NASes detect that  and
       switch to the backup server.

       That  will  cause your accounting packets to go the the backup server - and some NASes don't even switch back to the primary server when it
       comes back up.

       The result is that accounting records are missed, and/or the administrator must jump through hoops in order to combine the different detail
       files  from  multiple servers. It also means that the session database ("radutmp", used for radwho and simultaneous use detection) gets out
       of sync.

       We solve this issue by "relaying" packets from one server to another, so they both have the same set of accounting data.

       See raddb/sites-available/buffered-sql for more information.

BUFFERING FOR HIGH-LOAD SERVERS
       If the RADIUS server suddenly receives a many accounting packets, there may be insufficient CPU power to process them all in a timely  man-
       ner.  This problem is especially noticable when the accounting packets are going to a back-end database.

       Similarly,  you	may  have  one	database  that	tracks "live" sessions, and another that tracks historical accounting data.  In that case,
       accessing the first database is fast, as it is small.  Accessing the second database many be slower, as it may contain  multiple  gigabytes
       of data.  In addition, writing to the first database in a timely manner is important, while data may be written to the second database with
       a few minutes delay, without any harm being done.

       See raddb/sites-available/copy-to-home-server for more information.

SEE ALSO

       radiusd(8), rlm_sql_log(5)

AUTHOR

       The FreeRADIUS Server Project

								  23 October 2007						       RADRELAY(8)