| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cluster vulnerability - same ips will take it down |
« View previous topic :: View next topic » |
| Author |
Message
|
| jhidalgo |
 Posted: Thu Apr 03, 2008 12:02 pm Post subject: Cluster vulnerability - same ips will take it down |
 |
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
In the past we had a problem with a cluster, a lot of variables were on the table, but after our investigation is seems like the following issue made it all happened:
We were using virtualization, with one FR and 3 PR, someone by mistake ran another instance of the FR server, and it came up with the same IP, by the time we detected this we took it down and change the IP, but from that moment the cluster started lossing messages until it was not working at all.
So now I think this situation made the QMs register into the wrong FR and then these QMs kept sending messages to the FR without switching to the real FR.
Does MQ have a mechanism to correct inconsistencies on the fly ?, do I need to restart QMs if the FR change somehow ?
Thanks. |
|
| Back to top |
|
 |
| mvic |
| Posted: Thu Apr 03, 2008 12:35 pm Post subject: Re: Cluster vulnerability - same ips will take it down |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| jhidalgo wrote: |
| We were using virtualization, with one FR and 3 PR |
If you don't mind, could I ask for more details on this - what does "using virtualization" consist of in your scenario precisely?
| jhidalgo wrote: |
| Does MQ have a mechanism to correct inconsistencies on the fly ?, do I need to restart QMs if the FR change somehow ? |
Have you fixed it now? If not, call IBM support.
If this happens again in the future (but please make every effort to prevent it from happening!), call IBM support as soon as possible to give them and you the best chance of working everything out. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Fri Apr 04, 2008 12:16 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
jhidalgo,
it is possible to migrate repositories and this is well-described in the cluster manual (see "Cluster tasks"). Important issue: Each FR must have manual cluster channel definitions to each other FR. In this case each FR should have the same information.
To migrate the (accidentially created) second repository see the document "WebSphere MQ Queue Manager Clusters".
_________________
Regards
Hubert |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Apr 04, 2008 3:00 am Post subject: Re: Cluster vulnerability - same ips will take it down |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jhidalgo wrote: |
In the past we had a problem with a cluster, a lot of variables were on the table, but after our investigation is seems like the following issue made it all happened:
We were using virtualization, with one FR and 3 PR, someone by mistake ran another instance of the FR server, and it came up with the same IP, by the time we detected this we took it down and change the IP, but from that moment the cluster started lossing messages until it was not working at all.
So now I think this situation made the QMs register into the wrong FR and then these QMs kept sending messages to the FR without switching to the real FR.
Does MQ have a mechanism to correct inconsistencies on the fly ?, do I need to restart QMs if the FR change somehow ?
Thanks. |
Which inconsistencies?
The foolishness of running the same image in a different virtual machine?
If that did not get your attention think about the next one:
You now have 2 qmgrs with the SAME NAME in the cluster...
     says this is a NO NO.
This is your real problem. The ip problem was just masking it...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Apr 04, 2008 10:57 am Post subject: Re: Cluster vulnerability - same ips will take it down |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| fjb_saper wrote: |
If that did not get your attention think about the next one:
You now have 2 qmgrs with the SAME NAME in the cluster...
|
and with no way to eject it with RESET CLUSTER because both have the exact same QMID! IF you manually created a new QM with the same name at least the duplicate QM would have a new QMID. But you're clone has the exact same one. 
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
