06-17-2014 05:14 AM - edited 03-17-2019 04:14 PM
Hi all,
For our client we are setting up an environment with IM & Presence (9.1) servers. This week, users are enjoying features provided by jabber clients (for windows, iphone, android ecc..).
Since i set up IM & Presence cluster i've never had any issue, but today i suddenly noticed a login issue on publisher node.
I've configured two IM & Presence servers, one Publisher and one Subscriber in cluster. IM & Presence cluster is integrated with CallManager 9.1.2 cluster, and callmanager is synchronized with active directory. Also user authentication is challenged against active directory.
Here a brief description of IM & Presence Cluster Topology:
- two im & presence nodes (publisher and one subscriber)
- im & presence users balanced over this two nodes
For subscriber node, everything work fine. I have login issue, for all users placed on publisher (jabber client display error message: Unable to connect the server). If i move one user from publisher to subscriber login works without problem.
Anyway if i restart Cisco XCP Router service (on publisher node), i don't have login issue anymore.
Can you tell me if it's a known bug or something missconfigured ?
thanks for your help!
marco
06-17-2014 08:49 PM
please check if you are receiving notification for core dumps in the cups publisher.Also check if there is a excessive memory utilization being carried out by any service. RTMT will be helpful in identifying the same.
06-18-2014 03:22 AM
Hello Amit,
i have performed those checks but no alert received.
we are performing some test and noticed what is the real cause of unsuccessful login. Here a brief description of the problem observed:
- jabber client (for windows, for iphone, for mac) can login successful
- as soon as ADIUM client sends request using port 5222 the login process on Publisher node of IM & Presence crashes (no alert received)
- we have publisher login working fine if restarting Cisco XCP Router service
- this scenario happens regardless the Routing Communication Type configuration
So i can confirm problem is due to ADIUM client requests generated . Still cannot understand the right solution to apply
regards
marco
06-19-2014 10:41 AM
I tried PIDGIN client and no issues found, so i'm going to suggest that to customer.
Now opened a cisco TAC for the strange behaviour when ADIUM try connection to IM & Presence server.
regards
marco
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide