|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Clustering with multiple IP addresses |
« View previous topic :: View next topic » |
Author |
Message
|
g4Prakash |
Posted: Wed Jul 07, 2004 12:44 am Post subject: Clustering with multiple IP addresses |
|
|
 Apprentice
Joined: 17 Dec 2002 Posts: 25 Location: INDIA
|
Hi all,
I would appreciate if you could go thru the passage patiently and reply back with your comments...
My Scenario:
------------------------
I need to setup a queue manager cluster comprising 4 Qmgrs on 4machines: 2 NT boxes (BOX A & BOX B) & 2 AIX boxes (Box C & BOX D).
Box A, BOX C and Box D are in the same network. Box B is a part of a different network.BOX C & BOX D expose an IP address to BOX A which is different to what is exposed to BOX B. Box A and Box B cannot communicate with each other directly.
Box A IP Add: 111.222.333.443 exposed to Box C & Box D
Box B IP Add: 987.654.321.098 exposed to Box C & Box D
Box C IP Add: 111.222.333.444 exposed to Box A & Box D
Box C IP Add: 555.666.777.888 exposed to Box B
Box D IP Add: 111.222.333.445 exposed to Box A & Box D
Box D IP Add: 555.666.777.889 exposed to Box B
I have tried the following ... I need your opinion on the same ...
On Box C:
-------------
QMC -- Full Repository QMgr for Cluster -- "ClusterABCD"
ClusRcvr -- QMD.QMC-
ClusSdr -- QMC.QMD
ClusRcvr -- QMA.QMC
ClusSdr -- QMC.QMA
On Box D:
-------------
QMD -- Full Repository QMgr for Cluster -- "ClusterABCD"
ClusRcvr -- QMC.QMD
ClusSdr -- QMD.QMC
ClusRcvr -- QMB.QMD
ClusSdr -- QMD.QMB
**** To add the NT QMgrs as Full Repositories to ClusterABCD: *****
On Box A:
-------------
QMA -- Full Repository for Cluster -- "ClusterABCD"
ClusRcvr -- QMC.QMA
ClusSdr -- QMA.QMC
On Box B:
-------------
QMB -- Full Repository for Cluster -- "ClusterABCD"
ClusRcvr -- QMD.QMB
ClusSdr -- QMB.QMD
Hope this configuration is fine.
Note:
-------
A synchronous request would be sent from the NT box to AIX. The application on AIX will pick up the msg, process it and send a reply back to the NT. I have created a local queue QA for requests with Cluster attribute on both AIX boxes. The NT application at Box A and Box B put msgs to the logical cluster queue QA at its end. On Box A QR1, and on Box B QR2 have been defined as local queue with cluster attribute for reply msgs.
Multiple instances of a queue are defined on the AIX QMgrs to leverage load balancing.
I added the NT QMgrs as Full Repositories as opposed to Partial as I read somewhere (cant recollect where!!) that Partial repositories take considerable amount of time to locate a logical cluster queue nmae as that information has to come from the Full Repository that it points to ...
My Questions:
1) Do I need to define ClusSdr and ClusRcvr channels between the NT & AIX QMgrs as I have stated ... or I just define a ClusRcvr at NT (say BOX A) and then define a ClusSdr on BOX A that points to an existing ClusRcvr on AIX (say BOX C) ...
The same would not be possible for BOX B as the ClusRcvr on Box D has a different Conname ...So I would need to define a separate channel pair for them.
Awaiting your comments/suggesstions on the cluster configuration that I have designed and whether or not the NT QMgrs should be Partial or Full Repositories. Are ther any pros/cons if all QMgrs in a cluster are Full Repositories.
I am sorry if I have made the passage explanation confusing
Thanks in advance for you time & guidance. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jul 07, 2004 4:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You don't need four full repositories. There's no advantage to having more than two, except in extreme cases of network topology weirdness (which you don't have).
Likely, Box C would be sufficient. You want your repositories to be highly visible to the entire network, so putting a repository on Box A or Box B doesn't make sense.
Partial repositories only take a while to resolve names if the connection between them and a full repository is slow - which again, I think is not your case.
You need to define cluster channels from each full repository to each other full repository.
You also need to define cluster channels from each partial repository to at least one full repository.
You do not need to define cluster channels between any partial repositories and any other partial repository at all. The cluster will handle that.
You may also need to create queue manager aliases if for some reason you want Box A and Box B to communicate, as I don't think the cluster will automatically route messages through Box C or D as would be required. _________________ I am *not* the model of the modern major general. |
|
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
|
|
|
|