| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IP vs NAT vs DNS |
« View previous topic :: View next topic » |
| Author |
Message
|
| John89011 |
 Posted: Mon Dec 20, 2010 2:11 pm Post subject: IP vs NAT vs DNS |
 |
|
Voyager
Joined: 15 Apr 2009
Posts: 94
|
Here's my problem..
have 2 FRs in a cluster (interconnected of course) so now a vendor is attemting to join the cluster outside of the network via VPN. If I alter my clusrcvr to use the NATed IP, they connect fine (they defined an explicit clussdr with the NATed IP to my FR) however my internal clussdrs communicating to the FR go into retry since they they can't resolve the NATed IP. I then altered the clusrcvr to use the DNS VIP name instead and it worked fine for a couple of hours and their clussdr went into retry again stating that it could not resolve the IP.
So my question is, what's the best way of resolving this issue.. go with another receiver with real IP for my internal QMs communicating to the FRs and have a receiver for the vendor withe the NATed IP? Or should the DNS VIP work?
Thanks in advance! |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Dec 20, 2010 2:35 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The address needs to be resolvable from anyone who wants to use it.
You should really set up a gateway qmgr and have the vendor connect to that. Ideally you won't even use cluster channels for that.
Regardless, as you have found, spanning clusters across network boundaries is complicated. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Dec 20, 2010 7:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqjeff wrote: |
The address needs to be resolvable from anyone who wants to use it.
You should really set up a gateway qmgr and have the vendor connect to that. Ideally you won't even use cluster channels for that.
Regardless, as you have found, spanning clusters across network boundaries is complicated. |
 For ip setup in channel definitions this usually means DNS name. The challenge is that the DNS name needs to resolve correctly on both sides of the NAT. So on the existing cluster side there should be no problem. On the other side of the NAT attempting to connect, the DNS needs to resolve to the "natted" address... (different IP).
Often times this is either resolved by using a short dns name, a long dns name, or by forcing the dns resolution from the /etc/hosts file (last resort).
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| John89011 |
| Posted: Tue Dec 21, 2010 8:39 am Post subject: |
|
|
Voyager
Joined: 15 Apr 2009
Posts: 94
|
| Thanks guys! I appreciate your input. I'll take your suggestions and go from there. Thanks again! |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
