Does TIBCO Support IPMP with TIBCO Rendezvous?
Article ID: KB0092292
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
Here is our official statement about IPMP support with TIBCO Rendezvous.
================================================
Engineering does not specifically code and test to IP Network Multipathing. However, we are willing to state directly that the configuration should work as long as the operating system's IP multipathing module is transparent to IP applications when used from both the TCP and UDP/multicast socket libraries.
Additionally, the modules that modify the IP stack dynamically cannot impose usage restrictions on the applications themselves or ask that they use vendor specific libraries/functions in our communication daemons. Such restrictions would require code changes that would break the compatibility between releases of the messaging product.
The issue is that operating system cannot change or 'break' point to point addresses incoming or outgoing; the result would be that the previously resolved and cached IP address information that the messaging software is using would be incorrect, potentially 'breaking' retransmission requests, CM acknowledgements, and other point to point communications between daemons and applications.
Product Support has carried out several tests with TIBCO Rendezvous and 2 of the features of the Solaris 8 implementation of IP Network Multipathing; so far, we have not seen any problems.
We believe that TIBCO Rendezvous should function under such conditions without difficulty. We will do our best to assist any customer who wishes to use this Solaris feature, in conjunction with TIBCO Rendezvous, in their environment. However, we cannot commit to being able to 'officially' support this type of configuration.
Please be aware that we have only tested the 'Failure Detection' and 'Repair Detection' features of IP Network Multipathing and have not tested 'Outbound Load Spreading'.
============================================================
Here is our official statement about IPMP support with TIBCO Rendezvous.
================================================
Engineering does not specifically code and test to IP Network Multipathing. However, we are willing to state directly that the configuration should work as long as the operating system's IP multipathing module is transparent to IP applications when used from both the TCP and UDP/multicast socket libraries.
Additionally, the modules that modify the IP stack dynamically cannot impose usage restrictions on the applications themselves or ask that they use vendor specific libraries/functions in our communication daemons. Such restrictions would require code changes that would break the compatibility between releases of the messaging product.
The issue is that operating system cannot change or 'break' point to point addresses incoming or outgoing; the result would be that the previously resolved and cached IP address information that the messaging software is using would be incorrect, potentially 'breaking' retransmission requests, CM acknowledgements, and other point to point communications between daemons and applications.
Product Support has carried out several tests with TIBCO Rendezvous and 2 of the features of the Solaris 8 implementation of IP Network Multipathing; so far, we have not seen any problems.
We believe that TIBCO Rendezvous should function under such conditions without difficulty. We will do our best to assist any customer who wishes to use this Solaris feature, in conjunction with TIBCO Rendezvous, in their environment. However, we cannot commit to being able to 'officially' support this type of configuration.
Please be aware that we have only tested the 'Failure Detection' and 'Repair Detection' features of IP Network Multipathing and have not tested 'Outbound Load Spreading'.
============================================================
Issue/Introduction
Does TIBCO Support IPMP with TIBCO Rendezvous?
Feedback
Yes
No
Powered by
