| Author |
Message
|
| sumit |
 Posted: Thu Sep 03, 2009 1:26 am Post subject: conname change |
 |
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
Hi,
Platform: AS/400
MQ Version: 6.0.2.4
A PR queue manager QM1 is migrated from host/server A to server B. DNS table is updated so that host name A and B map to same new physical server (B). Necessary steps were taken during migration and QM1 was properly migrated .
Connname in clusrcvr channel of QM1 is set as A. Soon the entry of A will be deleted from DNS table and only B will remain. This means that I have to change conname from A to B in clusrcvr channel.
I'd like to know the proper method. Could it be:
1. a) Removing queue manager QM1 out of cluster as per documented steps
b) Correct the host name.
c) Add the queue manager QM1 back into cluster as per documented steps.
OR
2. a) Remove all QM1 cluster qs from cluster
b) Stop clussndr and clusrcvr channels and verify if it's stopped. Stop clussndr channel at FR.
c) Change the conname in clusrcvr.
d) Start clusrcvr at PR and clussndr at FR.
e) Start clussndr at PR.
f) Refresh cluster, so that changes can propogate
_________________
Regards
Sumit |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Sep 03, 2009 2:27 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I'd go with following:
- suspend qmgr from cluster
- stop cluster receiver
- change cluster receiver
- start cluster receiver
- resume qmgr to cluster
But then that's just me 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sumit |
| Posted: Thu Sep 03, 2009 2:37 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
Well.. I performed the same steps and also stopped clussndr at PR after stopping clusrcvr. When did refresh cluster in the end, it gave me a temp.qmgr entry.
I had to struggle to rectify the problem that time. Finally, I rolled back to old hostname.
Will check if I can get the error logs but chances are low.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Sep 03, 2009 3:00 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
if you stop the clussdr (to the FR)? your change of the clusrcvr channel can not be send to the FR. So, when you then perform a refresh cluster, the PR is not able to communicate with the FR so you see that tempqmgr stuff (imho this always comes when there is a problem with the FR during cluster join or refresh / reset)
i'd follow the procedure of fjb_saber. my procedure was similiar, except i did not suspend / resume in the cluster. not sure if it is required (or if it is dangerous, as clusterqueues may not be avalable till the resume)
however, i would also wait a bit before restarting the cluster receiver making sure, all implizit defined cluster senders to QM1 got their timeout and are in retry so they pick up the changed conname.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| sumit |
| Posted: Thu Sep 03, 2009 4:02 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| Mr Butcher wrote: |
| if you stop the clussdr (to the FR)? your change of the clusrcvr channel can not be send to the FR. |
True.. hence I started the clssndr before doing refresh cluster.
| Quote: |
| e) Start clussndr at PR. |
As per yours and fjb_saper's advice, there won't be any need to remove the cluster queues out of cluster.
I am quite concern as I have repeated option 2 (1st post) twice for different servers and every time I got a temp. qmgr entry.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Sep 03, 2009 6:30 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I'm thinking I've seen this described in the WMQ Clusters manual.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| sumit |
| Posted: Thu Sep 03, 2009 7:17 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
A part from manual says
| Quote: |
Alter any incorrect parameters in the remote cluster receiver definition. For example, the conname may be incorrect.
1 : alter chl(to.qm2) chltype(clusrcvr) conname(’newhost(1414)’)
AMQ8016: WebSphere MQ channel changed.
Changes to the remote cluster receiver definition will be propagated out to any cluster queue managers that are interested and the corresponding auto-defined channels will be updated accordingly. You can check that the updates have been propagated correctly by checking the changed parameter. For example:
1 : dis clusqmgr(qm2) conname
AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(QM2) CHANNEL(TO.QM2) CLUSTER(CLUSDEMO) CONNAME(newhost(1414)) |
As per the quote, change in conname from A to B should also work.
Doing double/triple check as don't want to mess up with Production config. 
_________________
Regards
Sumit |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Sep 03, 2009 7:23 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The Advanced Tasks section of the Clusters manual, says to take the definition out of the cluster, make the (conname) change, put the object back into the cluster.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 03, 2009 9:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bruce2359 wrote: |
| The Advanced Tasks section of the Clusters manual, says to take the definition out of the cluster, make the (conname) change, put the object back into the cluster. |
Can you please specify the section of the Advanced Tasks. I must be getting blind with old age because I checked both 6.0 and 7.0 infocenters and did not see it...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Sep 03, 2009 10:16 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
"Task 4: Removing a cluster queue from a queue manager." The same procedure works for channels, too.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Sep 03, 2009 11:56 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
well yes this may work, but i do not see why it should be required to remove the clusrcvr (and so remove the pr) from the cluster for that change.
we recently moved a Linux system with a clustered PR MQ into a different network and had to change the clusrcvr conname, and everything worked well by just changing the conname of the clusrcvr, taking care that it could reach the FR and take care that the implizit clussdr channels to that MQ were restarted.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| sumit |
| Posted: Fri Sep 04, 2009 1:33 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| Mr Butcher wrote: |
| we recently moved a Linux system with a clustered PR MQ into a different network and had to change the clusrcvr conname, and everything worked well by just changing the conname of the clusrcvr, taking care that it could reach the FR and take care that the implizit clussdr channels to that MQ were restarted. |
Nice to know that it worked somewhere.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Sep 04, 2009 1:56 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
maybe you did not have a cluster problem, but a networking problem? you said that you use dns names. are you sure, the new dns name was known everywhere it was needed at the time of the change?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| sumit |
| Posted: Fri Sep 04, 2009 2:21 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
Yes, DNS name is working fine. This queue manager is also connected in server-requester mode to the same gateway queue manager and that pair of channels properly running.
I'll try recommended steps on some dummy cluster config. Thanks for inputs.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Sep 04, 2009 6:57 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| but i do not see why it should be required to remove the clusrcvr (and so remove the pr) from the cluster for that change. |
Recall that most channel def changes require stopping and starting the channel. Removing the object def from the cluster ensures that there is no current (active) duplicate object def in the cluster.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
