Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect Multi-Server » IM and Out of Sequence Installation
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
As part of testing Kerio Multi-Server 8.5.1 pre-release I installed the IM role out of the normal sequence to test if a defect I reported was reproduceable.

The IM provision works fine but it does generate a couple of interesting questions:

Does the IM role need a license applied to it? I logged in on the web console on the IM server and it does not contain our license (not a big deal if we need to do this step, just pointing it out).

I'm working with a load balancer and I noticed that the Front-End servers I'm using do not present the XMPP ports 5222, 5223, etc which would make sense as when I installed them the IM server role was not present. In the scenario I'm working in how would I activate these ports on the Front-End servers?

This second point is handy as let's say that one does not want IM server but after the initial installation we decide to run IM on our Back-End Servers. The same configuration would be needed as the Front-End would not present XMPP ports which means that a user in the field would point their XMPP client at the Back-End Server which should work but isn't as clean as using a VIP/load balancer as we do with the other parts of KMS at this point.

Sorry to be a pain here, working through different permutations of the setup, sequencing, what if scenarios, etc to wring out details.
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
The flip side of this setup, which I neglected to mention in my first post, is that if I point the load balancer VIP at the IM server role I get to the server via the LB but nothing actually happens - i.e. the other servers act like they are unaware of the IM server role being present.

Sort of like an application/configuration refresh type of a mechanism.
  •  
Jakub Schwarzmeier, Kerio

Messages: 67
Karma: 1
Send a private message to this user
License: You have to manually copy the license file you have to each Kerio Connect server (ie. all backends and instant messaging server role).

XMPP ports: Front-end does not proxy XMPP connections. You have to point your VIP/load balancer to forward XMPP traffic to Instant Messaging server role.

IM server role is "just another" slave in Kerio Connect distributed domain. Just not hosting mailboxes, providing instant messaging connectivity only. When using WebAdmin on master backend, in Domains --> Distributed Domains, IM server role has to be seen in the list in the same way as other backends.
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
Ah, that was the missing piece of the puzzle. I verified that my Kerio IM server shows up in the list of domains on the master FE server and then on the IM Server I added my email domain and set it as the primary domain.

Once I pointed my load balancer at the IM Server for XMPP and XMPP/SSL I was in business.

Thank you for the help on this.
Previous Topic: Kerio Directory Server Backup
Next Topic: Puppet Master Setup Error
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Fri Sep 22 13:44:51 CEST 2017

Total time taken to generate the page: 0.00398 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.