Message Routing with authentication enabled is failing between TIBCO LogLogic LMI 4.9 and 5.1

Message Routing with authentication enabled is failing between TIBCO LogLogic LMI 4.9 and 5.1

book

Article ID: KB0077149

calendar_today

Updated On:

Products Versions
TIBCO LogLogic Log Management Intelligence 4.9.0 and higher

Description

Message Routing with authentication enabled will fail between an appliance running LMI 4.9 and an appliance running LMI 5.1. The upstream appliance will show the Tunnel Status as "Fail to connect" and the downstream appliance will show the Tunnel Status as "Peer error: failed to perform client challenge." This error is because version 4.9 uses Blowfish encryption whereas version 5.1 uses AES. 

Note: Even if "Enable Encryption" is set to No, Authentication still uses encryption to complete the connection.

Environment

Only occurs when mixing pre-5.1 LMI appliances with 5.1 and higher appliances.

Resolution

To forward messages between a 4.9 appliance and a 5.1 appliance, you must reconfigure the 5.1 appliance to use Blowfish encryption:

1. Login to the appliance CLI as "toor."
2. Backup the lltunnel.conf as shown in this command:

$ cp /loglogic/conf/ll_tunnel.conf /loglogic/conf/ll_tunnel.conf.ORIG

3. Edit /loglogic/conf/ll_tunnel.conf to include this line:

encrypt 0

4. Save the file and restart the application to pick up the change:

$ mtask stop; mtask start

Issue/Introduction

This article explains why message routing fails to function between LMI versions 4.9 and 5.1.