| Author |
Message
|
| x22ips |
 Posted: Mon Dec 02, 2013 1:24 am Post subject: Multi Instance Queue Manager, take over IP Adress |
 |
|
Novice
Joined: 02 Dec 2013
Posts: 22
|
We are considering moving from Veritas cluster to use Multi Instance Queue Manager.
With Veritas Cluster the same IP adress is moved to the other node when it takes over. Simple for MQ client connections.
With MI (Multi Instance QM) the IP adress will not be moved.
In our environment one active QM is running on Node1 and
another active QM is running on Node2 (both QM´s has Standby QM´s).
It there any solution to take over the IP adress from Node2 to Node1 (if e.g. active QM from Node2 switch to Node1?
Thanks! |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Dec 02, 2013 1:27 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Add both connections to the Queue Manager so that the AMQCLCHL.TAB file has them. Then the WMQClient code will automatically connect to the first available Queue Manager
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Dec 02, 2013 4:09 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Fine if apps use the CCDT, many do not and cannot easily be changed.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Mon Dec 02, 2013 5:28 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
If you don't want to use a CCDT then you can just specify a comma separated list of IP addresses in the connection name field.
The other alternative, albeit more expensive and complicated, is to use some virtual IP address technology list BigIP.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Dec 02, 2013 5:38 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Putting a comma in the middle of a configuration value might upset some applications, but it's worth a try - assuming the increased length of the value is accepted by the app.
The problem is that even if 90% of the apps are compatible (which I doubt in our case), not everyone is going to accept the solution, so we kept HA/CMP.
BigIP needs to know when one of the addresses shouldn't be used - it can probe http every few seconds, but it doesn't have that feature for MQ.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Dec 02, 2013 2:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
| zpat wrote: |
Putting a comma in the middle of a configuration value might upset some applications, but it's worth a try - assuming the increased length of the value is accepted by the app.
The problem is that even if 90% of the apps are compatible (which I doubt in our case), not everyone is going to accept the solution, so we kept HA/CMP.
BigIP needs to know when one of the addresses shouldn't be used - it can probe http every few seconds, but it doesn't have that feature for MQ. |
You could always define a service to the queue manager that would bind the virtual IP to the host the qmgr is running in... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Dec 03, 2013 12:23 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Yes, that is what Jeff keeps saying, but someone needs to code that script (or lovingly rip it off from HA/CMP).
A support pac for this would be a good idea (is it just me or has the supply of new support pacs dried up?)
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Tue Dec 10, 2013 8:07 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
| fjb_saper wrote: |
| You could always define a service to the queue manager that would bind the virtual IP to the host the qmgr is running in... |
All right, I'll confess. I don't understand how a service on the queue manager could "bind" an IP address to a host. I don't even understand it well enough to do a proper google search, though I tried.
Hints?  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 10, 2013 8:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
you'd need to bind the address on start up and release on shutdown.
It needs to happen the same way you allocate a static address to a machine... I'm sure your network people know of a way. Even if it is just in the dhcp host and you'd have to run the script there across the network....
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SAFraser |
| Posted: Wed Dec 11, 2013 4:21 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
Thanks, fjb. I think I understand.
We would like to go to CCDTs, but like zpat and others, our clients are not up to the challenge. (We've not given up - it's on our team's project list - but it will be an enormous undertaking.)
Our HA must control MQ, WMB, and Qpasa, two of those as critical resources and one as non-critical. Even using VCS, it's troublesome. I don't know that I would undertake it using homegrown scripts.
(We have upgraded to WMB 8 and are having the devil's time getting the VCS scripts to work in Solaris.)
Anyway, thanks for the tip which I am going to think about.  |
|
| Back to top |
|
|
| x22ips |
| Posted: Tue Mar 25, 2014 2:41 am Post subject: |
|
|
Novice
Joined: 02 Dec 2013
Posts: 22
|
Hello again,
thanks for your notes.
Does anyone know, if BIP-IP LTM is able to route the client userid to mq?
I think for MQ administrators it is not transparent to recognize which client connects to Queue Manager, because it is BIG-IP which performs the connection.
Normally (without BIG-IP) we have channel authentication for one or more Client ip-adresses and mapping a client asserted user ID to an MCAUSER userid.
thanks! |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Mar 25, 2014 5:01 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA
|
@x22ips,
Yes, BigIP can and should forward the IP address of the MQ Client. I've had clients use the combo of MQMI and BigIP successfully which allows MQ Client < MQ 7.0.1 to work (but those should be upgraded).
@SAFraser,
With MQMI, you will need to start/end everything that goes with the Qmgr as a SERVICE. So WMB would also need to be MI and Qpasa as an MQ SERVICE object. Having said that if you have HA software, then I would stick with that. |
|
| Back to top |
|
|
|
|
