I've come across an issue regarding the CONNAME that is made 'public' in the CLUSRCVR definition. As you all know, the value will be stored in the repositories and used by any qmgr's joining the cluster to create an auto-defined CLUSSDR channel as needed. We have internal (inside of our firewall) qmgrs in the cluster, as well as external (outside of our firewall) qmgrs in the cluster. Here's my concern:
The IP address specified in the CONNAME of the CLUSRCVR definition needs to serve:
- qmgrs inside the firewall, who use an internal un'NAT'd address
AND
- qmgrs outside of the firewall who need to use an external NAT'd address
In a nutshell, I have one place to specify 2 addresses.
I know using the DNS name would be a possible remedy, however, certain external clients are reluctant to use the DNS name - they require an actual IP address.
I'm assuming someone else has run into this scenario - clustering with qmgrs in the cluster that are internal and external...
Thanks in advance.
Mike Davidson
TSYS MQ Tech Support
[EMAIL PROTECTED]
- qmgrs outside of the firewall who need to use an external NAT'd address
The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you
