Multiple Server Setup

Discuss installation of Scalix software

Moderators: ScalixSupport, admin

jlandry
Posts: 27
Joined: Mon Feb 13, 2006 3:38 pm
Location: Connecticut, USA

Multiple Server Setup

Postby jlandry » Thu Mar 23, 2006 1:05 pm

We have two sites in which each will contain one enterprise server. Both machines are identical with a clean install of Fedora Core 4. I have freshly installed Scalix on both as well.

I have read and attempted the information in the following thread: http://www.scalix.com/community/viewtop ... rver+route

I am trying to set up mailing between the two machines and I am having problems.

I have completed the following steps:

Add the routes between the servers
----------------------------------

On ServerA: omaddrt -m serverB,mailnode -q SMINTFC -i scalix@serverB.domain.com
On ServerB: omaddrt -m serverA,mailnode -q SMINTFC -i scalix@serverA.domain.com

On both machines: omoff -d 0 router ; sleep 1 ; omon router

This sets up the Scalix-to-Scalix transport gateway for sending messages between Scalix servers.


Create the dirsync agreements
-----------------------------

For this to work, you need an import agreement on one side and an export agreement on the other.

On ServerA: omaddds -i -m +DIRSYNC/serverB,mailnode -t "010000 00:00"
On ServerB: omaddds -e -m +DIRSYNC/serverA,mailnode

This sets up the import agreement on serverA and an export agreement on serverB. The -t option specifies when this agreement should come into effect. The format is yymmdd hh:mm.

To do this the other way around:

On ServerA: omaddds -e -m +DIRSYNC/serverB,mailnode
On ServerB: omaddds -i -m +DIRSYNC/serverA,mailnode -t "010000 00:00"

On both machines add the following to /var/opt/scalix/sys/general.cfg:

DS_CUST_SEND_REQ_NOW=TRUE
DS_CUST_MSGQ_TIMEOUT=2

This tells dirsync that it needs to make the update requests as soon as the service is started rather than waiting for a timeout.
You will need to restart the dirsync service but you should also enable auditing so that you can see the messages being transferred between machines:

omconfaud dirsync 15
omoff -d 0 dirsync ; sleep 1; omon dirsync

You can then review the messages in /var/opt/scalix/logs/audit to check that the mail is flowing correctly.


The output of /var/opt/scalix/logs/audit for serverA follows:

Code: Select all

dirsync-out
time 1143129991 Thu Mar 23 11:06:31 2006 -300
recipient +DIRSYNC / NHMAIL, NEWHAMPSHIRE
subject DIRECTORY SYNCHRONIZATION - REQUEST_Updates
operation REQUEST
command Updates
flags
export-directory **
import-directory **
syn-timestamp 1 Wed Dec 31 19:00:01 1969 -300
max-reply-size 1000
sending-ref 0
request-id 0011431299880001


The audit log for serverB is empty.

Routes on ServerA follow:

Code: Select all

[root@ServerA ~]# omshowrt -q all
LOCAL      mailnodeA
UNIX       internet                                        MIME
UNIX       internet,tnef                                   TNEF
SMINTFC    ServerB,mailnodeB                             scalix@ServerB.domain.com


And for ServerB

Code: Select all

[root@ServerB ~]# omshowrt -q all
SMINTFC    ServerA,mailnodeA                              scalix@ServerA.domain.com
UNIX       internet                                        MIME
UNIX       internet,tnef                                   TNEF
LOCAL      mailnodeC
LOCAL      mailnodeB


Directory Sync information for ServerA

Code: Select all

[root@ServerA ~]# omshowds -i 1
SYNCHRONIZING DIRECTORY       : **
EXPORT OR ADDRESS             : +DIRSYNC /ServerB,mailnodeB
DS-STRT-AT                    : 060323 11:03
DS-PERIOD                     : 15
DS-IR-FLG                     : N


Directory Sync information for ServerB

Code: Select all

[root@ServerB ~]# omshowds -e 1
SYNCHRONIZING DIRECTORY       : **
IMPORT OR ADDRESS             : +DIRSYNC /ServerA,mailnodeA
DS-EL-FLG                     : N


SAC is installed on ServerA and I connect to ServerB through RES.

When I send an email from a user on mailnodeA to a user on mailnodeB or vice versa, the mail is not delivered.
For example, a mail sent from testB@domain.com to testA@domain.com recieves the following error.
Message could not be delivered to the following recipient:

testA@domain.com

because: No route configured for the recipient address


I thought the routes were set up? Have I missed a step somewhere? Thanks.

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Thu Mar 23, 2006 1:28 pm

Looking through the instructions, I can see where I may have confused you.

The routes you set up should be for the remote mailnode on each machine.

Say you have serverA with a mailnode called mailnodeA and serverB with a mailnode called mailnodeB, the routes should be set up on serverA as

Code: Select all

omaddrt -m mailnodeB -q SMINTFC -i scalix@serverB.domain.com
and on serverB as

Code: Select all

omaddrt -m mailnodeA -q SMINTFC -i scalix@serverA.domain.com


Cheers

Dave

surpac

Postby surpac » Thu Mar 23, 2006 11:30 pm

Further to this conversation, after completing the steps above, is it possible to add two servers on two different mailnodes under the same administrative interface so that the users can be administered and "viewed" from both mailnodes from one location, e.g. via ServerA SAC.

I've tried adding the SeverB mailnode under ServeA SAC "Server Info/Mailnodes" tab but got an error. Is there any documentation how to manage multiserver Scalix enterprise environment with enterprise users on different mailnodes?

jlandry
Posts: 27
Joined: Mon Feb 13, 2006 3:38 pm
Location: Connecticut, USA

Postby jlandry » Fri Mar 24, 2006 4:15 pm

You need to run the scalix installer to remove SAC and RES on the remote server you would like to control. After removal, you have to reinstall RES but NOT SAC. After going through the installation, it will ask you which server you would like to use for administration.

To summarize:

You would like to administer ServerB from ServerA. Remove SAC and RES on ServerB. Reinstall RES on ServerB. Configure ServerB to use ServerA for administration at the end of the setup wizard.

Regards,

Jay

surpac

Postby surpac » Sun Mar 26, 2006 10:56 pm

That worked like a treat! Thanks

surpac

Postby surpac » Tue Apr 04, 2006 10:54 pm

Another question related to the subject of this thread.

Although we're able to transfer messages between the two mailnodes (thanks to the advice in this thread) back and forth, after completing this procedure, only the new users created via SAC will "appear" in the SYSTEM Address Book (Outlook) on both mailnodes.

E.g. the users created prior setting up multiserver environment don't appear in the SYSTEM directory on serverB,mailnodeB. I've tried omresyncds to resync the system directory as well as within SAC in the user's properties untick and tick "Display in Address book" with no avail so far.

A note that a user attached to serverB,mailnodeB is still able to successfully send messages and vice versa to the users on serverA,mailnodeA that do not show up in the address book, just don't see them in the list. Meanwhile users on serverA,mailnodeA can see all users in the SYSTEM Address book.

It is a minor annoyance but is there a way to force/refresh a "copy" of Scalix SYSTEM Address book into serverB,mailnodeB?

Thanks

deyjvu
Posts: 175
Joined: Tue Oct 25, 2005 6:48 am
Location: Australia

Only one way synch setup, now do the reverse

Postby deyjvu » Fri Jun 02, 2006 4:47 am

Just for anyone else who picks up this thread and wonders how to fix this I wanted to share my many greyhairs gained from getting dirsyncs working in the past.

What the above customer had setup was one way synching only, that is


[root@servB ~]# omlistds -e
1 ** ** +DIRSYNC /servA
[root@servB ~]# omlistds -i
1 ** ** +DIRSYNC /servA
[root@servB ~]# omlistds -n
1 ** 60 120 120 0

Above was setup, now they need to add:

[root@servA ~]# omlistds -e
1 ** ** +DIRSYNC /servB
[root@servA ~]# omlistds -i
1 ** ** +DIRSYNC /servB
[root@serA ~]# omlistds -n
1 ** 60 120 120

ServA ServB

import <--------------------------------- export


export --------------------------------- > import

You need to have two sets of agreements to have directory synchs to go both ways between the two servers. If you view this old document at HP: http://www.openmail.hp.com/cyc/om/00/300-0183.pdf
it is a great source of how dirsyncs work, just replace the word "openmail" for Scalix and it still applies in most cases.

Just bear in mind that if you set this all up and expect something to happen right away it wont, if you don't adjust the times in this configuration then it takes 24hours for some thing to happen. Then if you do change the times for testing then make sure you change it back afterwards otherwise your system will be going crazy doing dirsyncs every 5 mins or so... not good. Be patient, dirsync does work, just get the config/setup right first.


:P

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Fri Jun 02, 2006 7:01 am

Good write-up, J....

Thanks,

Sascha.

dkelly
Scalix
Scalix
Posts: 593
Joined: Thu Mar 18, 2004 2:03 pm

Postby dkelly » Fri Aug 11, 2006 11:23 am

I've just completed a write-up for the wiki that gives hints on troubleshooting dirsync.

http://www.scalix.com/wiki/index.php?title=HowTos/DiagnosingDirsync

Cheers

Dave


Return to “Installation”



Who is online

Users browsing this forum: No registered users and 9 guests